Bug 2128458 - usb of thunderbold 3 dock broken after update f36 silverblue to 36.20220919.0, kernel 5.19.9-200.fc36.x86_64
Summary: usb of thunderbold 3 dock broken after update f36 silverblue to 36.20220919.0...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 36
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-20 16:25 UTC by Armin Warda
Modified: 2022-10-03 07:23 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-26 16:40:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
kernel log (108.87 KB, text/plain)
2022-09-20 16:25 UTC, Armin Warda
no flags Details
fwupdmgr get-histor (10.65 KB, application/octet-stream)
2022-09-20 16:26 UTC, Armin Warda
no flags Details

Description Armin Warda 2022-09-20 16:25:52 UTC
Created attachment 1913156 [details]
kernel log

1. Please describe the problem:
usb ports (incl. ethernet port) of the thunderbold 3 dock not working.
charging and display ports (DP) via the thunderbold 3 link cable are working.
This is a 
- Lenovo ThinkPad X1 Carbon 7th Gen, with a
- Lenovo Thinkpad Thunderbold-3 Gen. 2 Dock

2. What is the Version-Release number of the kernel:
5.19.9-200.fc36.x86_64

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 :
yes, it worked on versions before f36 silverblue 36.20220919.0
unfortunately I cannot say which exact version of f36 silverblue and which kernel version that was

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

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``:
I have not tried the latest rawhide kernel - I do not know how I would use the rawhide kernel with fedora silverblue - unless completely rebasing to rawhide

6. Are you running any modules that not shipped with directly Fedora's kernel?:
I use v4l2loopback that I build myself, but the problem also exists when this module is not 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.
Kernel logs attached. Lots of error messages for DMAR, xhci_hcd, usb5-port2 and usb6-port2, e.g.:

DMAR: DRHD: handling fault status reg 2
DMAR: [INTR-REMAP] Request device [0a:00.0] fault index 0x8080 [fault reason 0x25] Blocked a compatibility format interrupt request
xhci_hcd 0000:0a:00.0: Error while assigning device slot ID
xhci_hcd 0000:0a:00.0: Max number of devices this xHCI host supports is 64.
usb usb5-port2: couldn't allocate usb_device

Comment 1 Armin Warda 2022-09-20 16:26:46 UTC
Created attachment 1913157 [details]
fwupdmgr get-histor

Comment 2 Jason Montleon 2022-09-20 17:06:45 UTC
See https://bugzilla.redhat.com/show_bug.cgi?id=2127753 and the linked kernel.org bugzilla. The offending commit is in the process of being reverted.

Comment 3 Armin Warda 2022-09-24 08:17:11 UTC
Fixed for me after latest update:

awarda@fedora:~$ uname -a 
Linux fedora 5.19.10-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Sep 20 15:15:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

awarda@fedora:~$ rpm-ostree status -b
State: idle
BootedDeployment:
● fedora:fedora/36/x86_64/silverblue
                  Version: 36.20220924.0 (2022-09-24T00:52:10Z)
               BaseCommit: f7aa984aa5b860dee496c3bf471cbc606a71a7355aa1aef57840a48c49c89015
             GPGSignature: Valid signature by 53DED2CB922D8B8D9E63FD18999F7CBF38AB71F4
          LayeredPackages: f33-backgrounds-base.noarch f33-backgrounds-extras-base.noarch f33-backgrounds-extras-gnome.noarch f33-backgrounds-gnome.noarch gnome-tweaks google-chrome-stable igt-gpu-tools libguestfs-tools libvirt
                           libvirt-daemon-config-network libvirt-daemon-kvm libvirt-nss python3-libguestfs qemu-kvm virt-install virt-manager virt-top virt-viewer

Comment 4 Armin Warda 2022-09-26 05:52:25 UTC
Immediatly after the update 2022-09-24 the problem was solved for me, thus I reported that and closed the bug report, but now the problem is back!!!

When plugging the Thunderbold-3-Dock:

[  689.802740] DMAR: DRHD: handling fault status reg 2
[  689.802749] DMAR: [INTR-REMAP] Request device [0a:00.0] fault index 0x8080 [fault reason 0x25] Blocked a compatibility format interrupt request
[  697.005467] xhci_hcd 0000:0a:00.0: Error while assigning device slot ID
[  697.005488] xhci_hcd 0000:0a:00.0: Max number of devices this xHCI host supports is 64.
[  697.005505] usb usb5-port2: couldn't allocate usb_device

Still running the same kernel and rpm-ostree deployment that I reported on 2022-09-24, I didn't update anything in the last 2 days.

awarda@fedora:~$ uname -a
Linux fedora 5.19.10-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Sep 20 15:15:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

awarda@fedora:~$ rpm-ostree status -b
State: idle
BootedDeployment:
● fedora:fedora/36/x86_64/silverblue
                  Version: 36.20220924.0 (2022-09-24T00:52:10Z)
               BaseCommit: f7aa984aa5b860dee496c3bf471cbc606a71a7355aa1aef57840a48c49c89015
             GPGSignature: Valid signature by 53DED2CB922D8B8D9E63FD18999F7CBF38AB71F4
          LayeredPackages: f33-backgrounds-base.noarch f33-backgrounds-extras-base.noarch f33-backgrounds-extras-gnome.noarch f33-backgrounds-gnome.noarch gnome-tweaks google-chrome-stable igt-gpu-tools libguestfs-tools libvirt
                           libvirt-daemon-config-network libvirt-daemon-kvm libvirt-nss python3-libguestfs qemu-kvm virt-install virt-manager virt-top virt-viewer

Comment 5 Armin Warda 2022-09-26 16:40:31 UTC
Now it seems to be fixed in the current release.

I rebooted twice, including one complete powered-down & powered-up to confirm.

I updated to today's new rpm-ostree release, which included a new kernel:

awarda@fedora:~$ uname -a
Linux fedora 5.19.11-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Sep 23 15:07:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

awarda@fedora:~$ rpm-ostree status -b
State: idle
BootedDeployment:
● fedora:fedora/36/x86_64/silverblue
                  Version: 36.20220926.0 (2022-09-26T01:03:48Z)
               BaseCommit: 029c64a8c42a1f6aa8b48e03d2e8049619d750abaac16ffc893d3f5034c362bf
             GPGSignature: Valid signature by 53DED2CB922D8B8D9E63FD18999F7CBF38AB71F4
          LayeredPackages: f33-backgrounds-base.noarch f33-backgrounds-extras-base.noarch f33-backgrounds-extras-gnome.noarch
                           f33-backgrounds-gnome.noarch gnome-tweaks google-chrome-stable igt-gpu-tools libguestfs-tools libvirt
                           libvirt-daemon-config-network libvirt-daemon-kvm libvirt-nss python3-libguestfs qemu-kvm virt-install
                           virt-manager virt-top virt-viewer

Comment 6 Jason Montleon 2022-09-26 19:43:17 UTC
5.9.10 did not have the fix. 4d8637f1d67242207410734844ca4b143ac5585e in 5.9.11 reverted the PR that caused the issue:

https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.19.11


Note You need to log in before you can comment on or make changes to this bug.