Bug 1790889

Summary: Thunderbolt 3 Dock USB not working when connecting it the second time
Product: [Fedora] Fedora Reporter: Wayne <D-2rr382f82xa2d>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: airlied, bskeggs, ckellner, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, jtougne, kernel-maint, linville, masami256, mchehab, mjg59, steved
Target Milestone: ---Keywords: Reopened
Target Release: ---Flags: D-2rr382f82xa2d: needinfo-
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-08 07:19:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
kernel-5.4.10-200.fc31.x86_64.log
none
error extract none

Description Wayne 2020-01-14 13:28:48 UTC
Created attachment 1652212 [details]
kernel-5.4.10-200.fc31.x86_64.log

1. Please describe the problem:

I'm using this Thunderbolt 3 Dock together with my ThinkPad T480s:

https://i-tec.cz/de/produkt/tb3hdmidock-3/ (P/N TB3HDMIDOCK)
https://web.archive.org/web/20180929103728/https://i-tec.cz/de/produkt/tb3hdmidock-3/

It contains HDMI and USB outputs.

When connecting the Dock the second time after boot, USB devices connected to
the Dock are not working (at least I've tried keyboard, mouse and mass storage devices).
The HDMI output continues to work.

2. What is the Version-Release number of the kernel:

I can still reproduce this bug with kernel-5.4.10-200.fc31.x86_64, which I installed from updates-testing.

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

The bug first occurred after upgrading to kernel-0:5.4.7-200.fc31.x86_64 from kernel-5.3.16-300.fc31.x86_64.
I can still boot kernel-5.3.16-300.fc31.x86_64 which works fine.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

1. Boot Notebook
2. Connect Dock
(HDMI and USB devices connected to the Dock are now working.)
3. Disconnect Dock
4. Connect Dock again
(HDMI device connected to the Dock is now working again, USB devices connected to the Dock are not working until reboot.)

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Could not install:
> The GPG keys listed for the "Fedora - Rawhide - Developmental packages for the next Fedora release" repository are already installed but they are not correct for this package.

6. Are you running any modules that not shipped with directly Fedora's kernel?:

Usually VirtualBox kernel modules, however the bug also occurs without them loaded.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

The timestamp when connecting the Dock for the second time is Jan 14 08:04:48. I've attached the full log.

> Jan 14 08:04:48 kernel: Registered IR keymap rc-cec
> Jan 14 08:04:48 kernel: rc rc0: DP-1 as /devices/pci0000:00/0000:00:02.0/rc/rc0
> Jan 14 08:04:48 kernel: input: DP-1 as /devices/pci0000:00/0000:00:02.0/rc/rc0/input38
> Jan 14 08:04:48 kernel: typec_displayport port1-partner.0: failed to enter mode
> Jan 14 08:04:48 kernel: thunderbolt 0-1: new device found, vendor=0x16b device=0x9003
> Jan 14 08:04:48 kernel: thunderbolt 0-1: ComDis TB3HDMIDOCK

Comment 1 Wayne 2020-01-21 09:58:34 UTC
Still happens with kernel-5.4.12-200.fc31.x86_64.

Comment 2 Justin M. Forbes 2020-03-03 16:35:36 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs.

Fedora 31 has now been rebased to 5.5.7-200.fc31.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32.

If you experience different issues, please open a new bug report for those.

Comment 3 Justin M. Forbes 2020-03-25 22:29:05 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 4 Wayne 2020-03-28 12:14:55 UTC
Still happening.

Comment 5 jtougne 2020-04-29 14:23:33 UTC
Created attachment 1682953 [details]
error extract

Comment 6 jtougne 2020-04-29 14:26:19 UTC
Kernel: 5.6.7-300.fc32.x86_64
Fedora 32



It looks OK from a bolt perspective:

[user@localhost ~]$ boltctl list
 ● Lenovo ThinkPad Thunderbolt 3 Dock
   ├─ type:          peripheral
   ├─ name:          ThinkPad Thunderbolt 3 Dock
   ├─ vendor:        Lenovo
   ├─ uuid:          000f3958-1ccb-0801-ffff-ffffffffffff
   ├─ status:        authorized
   │  ├─ domain:     cb010000-0082-8098-2022-ad1c5402eb22
   │  └─ authflags:  none
   ├─ authorized:    Wed 29 Apr 2020 14:19:32 UTC
   ├─ connected:     Wed 29 Apr 2020 14:19:32 UTC
   └─ stored:        Wed 29 Apr 2020 07:01:13 UTC
      ├─ policy:     auto
      └─ key:        no

[user@localhost ~]$ systemctl status bolt.service 
● bolt.service - Thunderbolt system service
     Loaded: loaded (/usr/lib/systemd/system/bolt.service; static; vendor preset: disabled)
     Active: active (running) since Wed 2020-04-29 16:19:36 CEST; 5min ago
       Docs: man:boltd(8)
   Main PID: 1775 (boltd)
     Status: "authmode: enabled, force-power: unset"
      Tasks: 5 (limit: 19006)
     Memory: 5.0M
        CPU: 58ms
     CGroup: /system.slice/bolt.service
             └─1775 /usr/libexec/boltd

Apr 29 16:19:36 localhost.localdomain boltd[1775]: security level set to 'none'
Apr 29 16:19:36 localhost.localdomain boltd[1775]: [cb010000-0082-domain0                    ] connected: as domain0 [none] (/sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/0000:05:00.0/0000:06:0>
Apr 29 16:19:36 localhost.localdomain boltd[1775]: [cb010000-0082-Thinkpad T480s             ] device added, status: authorized, at /sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/0000:05:00.0/00>
Apr 29 16:19:36 localhost.localdomain boltd[1775]: [cb010000-0082-Thinkpad T480s             ] labeling device: Lenovo Thinkpad T480s
Apr 29 16:19:36 localhost.localdomain boltd[1775]: [000f3958-1ccb-ThinkPad Thunderbolt 3 Dock] parent is cb010000-0082...
Apr 29 16:19:36 localhost.localdomain boltd[1775]: [000f3958-1ccb-ThinkPad Thunderbolt 3 Dock] connected: authorized (/sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/0000:05:00.0/0000:06:00.0/dom>
Apr 29 16:19:36 localhost.localdomain boltd[1775]: dbus: exported domain at /org/freedesktop/bolt/domains/cb010000_0082_8098_2022_ad1c5402eb22
Apr 29 16:19:36 localhost.localdomain boltd[1775]: [000f3958-1ccb-ThinkPad Thunderbolt 3 Dock] dbus: exported device at /org/freedesktop/bolt/devices/000f3958_1ccb...
Apr 29 16:19:36 localhost.localdomain boltd[1775]: [cb010000-0082-Thinkpad T480s             ] dbus: exported device at /org/freedesktop/bolt/devices/cb010000_0082...
Apr 29 16:19:36 localhost.localdomain systemd[1]: Started Thunderbolt system service.

Cheers,

Comment 7 Wayne 2020-05-16 06:37:22 UTC
More people with the same problem: https://askubuntu.com/questions/1235285/usb-ethernet-thunderbolt-errors

Comment 8 Christian Kellner 2020-05-18 08:26:44 UTC
Wayne: just to rule out that this is not a bolt issue, can you post the bolt device db via "boltctl list -a" as well as the logs from a boot where this happens "journalctl -u bolt -b"?

Comment 9 Wayne 2020-05-30 11:28:09 UTC
Due to the COVID 19 pandemic I'm working from home and don't have access to the device. I will deliver the requested logs as soon as possible.

However, I can remember that "boltctl list" listed the device as authorized and it had the green dot. (Basically same output that jtougne posted.)

Comment 10 Wayne 2020-12-08 07:19:54 UTC
I tried again today and I'm no longer able to reproduce the problem (using Linux 5.8 now). Closing.