Bug 206109 - Boltd probing is timing out
Summary: Boltd probing is timing out
Status: REOPENED
Alias: None
Product: Drivers
Classification: Unclassified
Component: PCI (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_pci@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-07 08:27 UTC by Cédric Bellegarde
Modified: 2020-08-24 07:18 UTC (History)
4 users (show)

See Also:
Kernel Version: 5.4.8
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Cédric Bellegarde 2020-01-07 08:27:01 UTC 
Since 5.4 on ArchLinux, I got this in my journal:

janv. 07 09:24:45 arch boltd[1831]: probing: timeout, done: [2900280] (2000000)
janv. 07 09:24:41 arch boltd[1831]: probing: started [1000]
janv. 07 09:24:31 arch boltd[1831]: probing: timeout, done: [2807405] (2000000)
janv. 07 09:24:27 arch boltd[1831]: probing: started [1000]
janv. 07 09:24:25 arch boltd[1831]: probing: timeout, done: [2342204] (2000000)
janv. 07 09:24:22 arch boltd[1831]: probing: started [1000]
janv. 07 09:24:12 arch boltd[1831]: probing: timeout, done: [2770254] (2000000)
janv. 07 09:24:05 arch boltd[1831]: probing: started [1000]
janv. 07 09:23:58 arch boltd[1831]: probing: timeout, done: [2002975] (2000000)
janv. 07 09:23:56 arch boltd[1831]: probing: started [1000]
janv. 07 09:23:55 arch boltd[1831]: probing: timeout, done: [2002337] (2000000)
janv. 07 09:23:53 arch boltd[1831]: probing: started [1000]

Does not happen using linux-lts or with Fedora 31 (linux 5.3).

Tell me how give you more information on this issue.
Comment 1 Cédric Bellegarde 2020-01-07 09:16:13 UTC 
Fedora 31 just updated to 5.4.7 and the issue does not exist.

So, looks like an ArchLinux only issue.

Closing.
Comment 2 Luca Botti 2020-01-08 11:34:55 UTC 
The issue is present in fedora 31 - Dell XPS 15 with thunderbolt dock (WD16TB) since 5.4.7-200.

I receive lot of probing timeout from boltd.
Comment 3 Cédric Bellegarde 2020-01-08 12:14:11 UTC 
Ok, I can confirm timeout is present on Fedora 31 logs.

Was wrong because on ArchLinux, Thunderbolt indicator is flashing all the time so I guessed it was fixed.
Comment 4 Bjorn Helgaas 2020-01-08 14:41:14 UTC 
Sounds like this is a regression?  What is the most recent working version?  Please attach a complete dmesg log and "sudo lspci -vv" output.

I guess boltd is a Thunderbolt daemon; not sure the kernel PCI category is correct.  The dmesg log might have more clues.  Adding Mika.
Comment 5 Mika Westerberg 2020-01-08 14:55:07 UTC 
I think there is already similar issue reported against bolt here:

  https://gitlab.freedesktop.org/bolt/bolt/issues/156

Please check that one and comment there. It is not yet clear whether the issue is in the bolt itself or the kernel. According to Christian the kernel started emitting additional uevents which seem to confuse bolt.
Comment 6 Luca Botti 2020-01-21 10:45:11 UTC 
Worth additional evaluation in my opinion - I get connection issues with the ethernet adapter inside the TB16 docking station (as far as I have to use the wifi).
Note You need to log in before you can comment on or make changes to this bug.