[Bug 219198] New: usb on Dell WD19TB Thunderbolt Dock stop working

[Bug 219198] New: usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

            Bug ID: 219198
           Summary: usb on Dell WD19TB Thunderbolt Dock stop working
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: maggu2810@gmail.com
        Regression: No

USB is working on my Dell WD19TB Thunderbolt Dock with Fedora kernel build
6.10.0-64.fc41.x86_64

It does not work with 6.11.0-0.rc4.38.fc41.x86_64 anymore.

Here is the kernel log after plug-in it while the system is running:

----
Aug 26 10:33:26 foobar kernel: thunderbolt 0-0:1.1: new retimer found,
vendor=0x8087 device=0x15ee
Aug 26 10:33:26 foobar kernel: thunderbolt 0-0:1.2: new retimer found,
vendor=0x8087 device=0x15ee
Aug 26 10:33:26 foobar kernel: thunderbolt 0-1: new device found, vendor=0xd4
device=0xb070
Aug 26 10:33:26 foobar kernel: thunderbolt 0-1: Dell WD19TB Thunderbolt Dock
Aug 26 10:33:28 foobar kernel: pcieport 0000:00:07.0: pciehp: Slot(3): Card
present
Aug 26 10:33:28 foobar kernel: pcieport 0000:00:07.0: pciehp: Slot(3): Link Up
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: [8086:15ef] type 01 class
0x060400 PCIe Switch Upstream Port
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: PCI bridge to [bus 00]
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0:   bridge window [io 
0x0000-0x0fff]
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0:   bridge window [mem
0x00000000-0x000fffff]
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0:   bridge window [mem
0x00000000-0x000fffff 64bit pref]
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: enabling Extended Tags
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: supports D1 D2
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2
D3hot D3cold
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: PTM enabled, 4ns granularity
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: 8.000 Gb/s available PCIe
bandwidth, limited by 2.5 GT/s PCIe x4 link at 0000:00:07.0 (capable of 31.504
Gb/s with 8.0 GT/s PCIe x4 link)
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: Adding to iommu group 18
Aug 26 10:33:28 foobar kernel: pcieport 0000:00:07.0: ASPM: current common
clock configuration is inconsistent, reconfiguring
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: bridge configuration invalid
([bus 00-00]), reconfiguring
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0: [8086:15ef] type 01 class
0x060400 PCIe Switch Downstream Port
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0: PCI bridge to [bus 00]
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0:   bridge window [io 
0x0000-0x0fff]
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0:   bridge window [mem
0x00000000-0x000fffff]
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0:   bridge window [mem
0x00000000-0x000fffff 64bit pref]
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0: enabling Extended Tags
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0: supports D1 D2
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0: PME# supported from D0 D1 D2
D3hot D3cold
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0: Adding to iommu group 19
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0: [8086:15ef] type 01 class
0x060400 PCIe Switch Downstream Port
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0: PCI bridge to [bus 00]
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0:   bridge window [io 
0x0000-0x0fff]
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0:   bridge window [mem
0x00000000-0x000fffff]
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0:   bridge window [mem
0x00000000-0x000fffff 64bit pref]
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0: enabling Extended Tags
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0: supports D1 D2
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0: PME# supported from D0 D1 D2
D3hot D3cold
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0: Adding to iommu group 20
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: PCI bridge to [bus 03-52]
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0: bridge configuration invalid
([bus 00-00]), reconfiguring
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0: bridge configuration invalid
([bus 00-00]), reconfiguring
Aug 26 10:33:28 foobar kernel: pci 0000:04:00.0: [8086:15f0] type 00 class
0x0c0330 PCIe Endpoint
Aug 26 10:33:28 foobar kernel: pci 0000:04:00.0: BAR 0 [mem
0x00000000-0x0000ffff]
Aug 26 10:33:28 foobar kernel: pci 0000:04:00.0: enabling Extended Tags
Aug 26 10:33:28 foobar kernel: pci 0000:04:00.0: supports D1 D2
Aug 26 10:33:28 foobar kernel: pci 0000:04:00.0: PME# supported from D0 D1 D2
D3hot D3cold
Aug 26 10:33:28 foobar kernel: pci 0000:04:00.0: 8.000 Gb/s available PCIe
bandwidth, limited by 2.5 GT/s PCIe x4 link at 0000:00:07.0 (capable of 31.504
Gb/s with 8.0 GT/s PCIe x4 link)
Aug 26 10:33:28 foobar kernel: pci 0000:04:00.0: Adding to iommu group 21
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0: PCI bridge to [bus 04-52]
Aug 26 10:33:28 foobar kernel: pci_bus 0000:04: busn_res: [bus 04-52] end is
updated to 04
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0: PCI bridge to [bus 05-52]
Aug 26 10:33:28 foobar kernel: pci_bus 0000:05: busn_res: [bus 05-52] end is
updated to 52
Aug 26 10:33:28 foobar kernel: pci_bus 0000:03: busn_res: [bus 03-52] end is
updated to 52
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0: bridge window [mem
0x00100000-0x001fffff 64bit pref] to [bus 05-52] add_size 100000 add_align
100000
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0: bridge window [mem
0x00100000-0x001fffff] to [bus 05-52] add_size 100000 add_align 100000
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: bridge window [mem
0x00100000-0x002fffff 64bit pref] to [bus 03-52] add_size 100000 add_align
100000
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: bridge window [mem
0x00100000-0x002fffff] to [bus 03-52] add_size 100000 add_align 100000
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: bridge window [mem
0x98000000-0xba0fffff]: assigned
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: bridge window [mem
0x6210000000-0x6245ffffff 64bit pref]: assigned
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: bridge window [io 
0x5000-0x6fff]: assigned
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0: bridge window [mem
0x98000000-0x980fffff]: assigned
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0: bridge window [mem
0x6210000000-0x62100fffff 64bit pref]: assigned
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0: bridge window [mem
0x98100000-0xba0fffff]: assigned
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0: bridge window [mem
0x6210100000-0x6245ffffff 64bit pref]: assigned
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0: bridge window [io 
0x5000-0x5fff]: assigned
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0: bridge window [io 
0x6000-0x6fff]: assigned
Aug 26 10:33:28 foobar kernel: pci 0000:04:00.0: BAR 0 [mem
0x98000000-0x9800ffff]: assigned
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0: PCI bridge to [bus 04]
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0:   bridge window [io 
0x5000-0x5fff]
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0:   bridge window [mem
0x98000000-0x980fffff]
Aug 26 10:33:28 foobar kernel: pci 0000:03:02.0:   bridge window [mem
0x6210000000-0x62100fffff 64bit pref]
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0: PCI bridge to [bus 05-52]
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0:   bridge window [io 
0x6000-0x6fff]
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0:   bridge window [mem
0x98100000-0xba0fffff]
Aug 26 10:33:28 foobar kernel: pci 0000:03:04.0:   bridge window [mem
0x6210100000-0x6245ffffff 64bit pref]
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0: PCI bridge to [bus 03-52]
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0:   bridge window [io 
0x5000-0x6fff]
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0:   bridge window [mem
0x98000000-0xba0fffff]
Aug 26 10:33:28 foobar kernel: pci 0000:02:00.0:   bridge window [mem
0x6210000000-0x6245ffffff 64bit pref]
Aug 26 10:33:28 foobar kernel: pcieport 0000:00:07.0: PCI bridge to [bus 02-52]
Aug 26 10:33:28 foobar kernel: pcieport 0000:00:07.0:   bridge window [io 
0x5000-0x6fff]
Aug 26 10:33:28 foobar kernel: pcieport 0000:00:07.0:   bridge window [mem
0x98000000-0xba0fffff]
Aug 26 10:33:28 foobar kernel: pcieport 0000:00:07.0:   bridge window [mem
0x6210000000-0x6245ffffff 64bit pref]
Aug 26 10:33:28 foobar kernel: pcieport 0000:02:00.0: enabling device (0000 ->
0003)
Aug 26 10:33:28 foobar kernel: pcieport 0000:03:02.0: enabling device (0000 ->
0003)
Aug 26 10:33:28 foobar kernel: pcieport 0000:03:04.0: enabling device (0000 ->
0003)
Aug 26 10:33:28 foobar kernel: pcieport 0000:03:04.0: pciehp: Slot #4 AttnBtn-
PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+
IbPresDis- LLActRep+
Aug 26 10:33:28 foobar kernel: pci 0000:04:00.0: enabling device (0000 -> 0002)
Aug 26 10:33:28 foobar kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Aug 26 10:33:28 foobar kernel: xhci_hcd 0000:04:00.0: new USB bus registered,
assigned bus number 5
Aug 26 10:33:28 foobar kernel: xhci_hcd 0000:04:00.0: hcc params 0x200077c1 hci
version 0x110 quirks 0x0000000200009810
Aug 26 10:33:28 foobar kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
Aug 26 10:33:28 foobar kernel: xhci_hcd 0000:04:00.0: new USB bus registered,
assigned bus number 6
Aug 26 10:33:28 foobar kernel: xhci_hcd 0000:04:00.0: Host supports USB 3.1
Enhanced SuperSpeed
Aug 26 10:33:28 foobar kernel: usb usb5: New USB device found, idVendor=1d6b,
idProduct=0002, bcdDevice= 6.11
Aug 26 10:33:28 foobar kernel: usb usb5: New USB device strings: Mfr=3,
Product=2, SerialNumber=1
Aug 26 10:33:28 foobar kernel: usb usb5: Product: xHCI Host Controller
Aug 26 10:33:28 foobar kernel: usb usb5: Manufacturer: Linux
6.11.0-0.rc4.38.fc41.x86_64 xhci-hcd
Aug 26 10:33:28 foobar kernel: usb usb5: SerialNumber: 0000:04:00.0
Aug 26 10:33:28 foobar kernel: DMAR: DRHD: handling fault status reg 2
Aug 26 10:33:28 foobar kernel: DMAR: [DMA Read NO_PASID] Request device
[04:00.0] fault addr 0xffffb000 [fault reason 0x06] PTE Read access is not set
Aug 26 10:33:28 foobar kernel: hub 5-0:1.0: USB hub found
Aug 26 10:33:28 foobar kernel: hub 5-0:1.0: 2 ports detected
Aug 26 10:33:28 foobar kernel: usb usb6: New USB device found, idVendor=1d6b,
idProduct=0003, bcdDevice= 6.11
Aug 26 10:33:28 foobar kernel: usb usb6: New USB device strings: Mfr=3,
Product=2, SerialNumber=1
Aug 26 10:33:28 foobar kernel: usb usb6: Product: xHCI Host Controller
Aug 26 10:33:28 foobar kernel: usb usb6: Manufacturer: Linux
6.11.0-0.rc4.38.fc41.x86_64 xhci-hcd
Aug 26 10:33:28 foobar kernel: usb usb6: SerialNumber: 0000:04:00.0
Aug 26 10:33:28 foobar kernel: hub 6-0:1.0: USB hub found
Aug 26 10:33:28 foobar kernel: hub 6-0:1.0: 2 ports detected
Aug 26 10:33:29 foobar kernel: DMAR: DRHD: handling fault status reg 2
Aug 26 10:33:29 foobar kernel: DMAR: [DMA Read NO_PASID] Request device
[04:00.0] fault addr 0xffffe000 [fault reason 0x06] PTE Read access is not set
Aug 26 10:33:33 foobar kernel: usb usb2-port1: attempt power cycle
Aug 26 10:33:49 foobar kernel: watchdog: Watchdog detected hard LOCKUP on cpu 0
Aug 26 10:33:49 foobar kernel: Modules linked in: uhid uinput rfcomm
snd_seq_dummy snd_hrtimer xt_comment nft_compat bridge stp llc
nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4
nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject
nft_ct sunrpc nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4
ip_set nvidia_drm(POE) nvidia_modeset(POE) nf_tables nvidia_uvm(POE) bnep
snd_hda_codec_hdmi nvidia(POE) binfmt_misc vfat fat snd_sof_pci_intel_tgl
snd_sof_pci_intel_cnl snd_sof_intel_hda_generic soundwire_intel
soundwire_cadence snd_sof_intel_hda_common iwlmvm snd_sof_intel_hda_mlink
snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof mac80211 snd_sof_utils
snd_soc_hdac_hda snd_soc_acpi_intel_match snd_ctl_led
soundwire_generic_allocation snd_soc_acpi soundwire_bus snd_hda_codec_realtek
snd_soc_avs snd_hda_codec_generic snd_soc_hda_codec snd_hda_scodec_component
snd_hda_ext_core libarc4 snd_soc_core snd_compress dell_pc ac97_bus
platform_profile snd_pcm_dmaengine snd_hda_intel
Aug 26 10:33:49 foobar kernel:  snd_usb_audio snd_intel_dspcfg
snd_intel_sdw_acpi intel_uncore_frequency snd_hda_codec
intel_uncore_frequency_common snd_usbmidi_lib x86_pkg_temp_thermal dell_rbtn
snd_hda_core intel_powerclamp snd_ump snd_rawmidi snd_hwdep coretemp uvcvideo
btusb snd_seq iTCO_wdt btrtl uvc mei_wdt intel_pmc_bxt r8153_ecm snd_seq_device
iwlwifi videobuf2_vmalloc btintel processor_thermal_device_pci videobuf2_memops
iTCO_vendor_support spi_nor hid_sensor_als kvm_intel dell_laptop mei_pxp
snd_pcm cdc_ether mei_hdcp processor_thermal_device btbcm dell_wmi usbnet
videobuf2_v4l2 hid_sensor_trigger hid_sensor_iio_common
processor_thermal_wt_hint mtd intel_rapl_msr kvm dell_smbios videobuf2_common
snd_timer dell_wmi_sysman btmtk dcdbas rapl intel_cstate intel_uncore pcspkr
cfg80211 dell_smm_hwmon dell_wmi_ddv firmware_attributes_class
dell_wmi_descriptor videodev wmi_bmof bluetooth processor_thermal_rfim
industrialio_triggered_buffer kfifo_buf r8152 mei_me snd processor_thermal_rapl
i2c_i801 intel_rapl_common spi_intel_pci mc
Aug 26 10:33:49 foobar kernel:  mii thunderbolt mei industrialio i2c_smbus
spi_intel idma64 processor_thermal_wt_req soundcore rfkill
processor_thermal_power_floor processor_thermal_mbox igen6_edac int3403_thermal
dptf_power joydev int340x_thermal_zone intel_pmc_core intel_vsec intel_hid
pmt_telemetry int3400_thermal sparse_keymap pmt_class acpi_thermal_rel acpi_pad
acpi_tad loop nfnetlink zram dm_crypt xe drm_ttm_helper gpu_sched
drm_suballoc_helper drm_gpuvm drm_exec hid_sensor_hub intel_ishtp_hid hid_jabra
i915 nvme nvme_core nvme_auth crct10dif_pclmul crc32_pclmul crc32c_intel
polyval_clmulni polyval_generic i2c_algo_bit drm_buddy rtsx_pci_sdmmc ttm
mmc_core ghash_clmulni_intel drm_display_helper ucsi_acpi sha512_ssse3
typec_ucsi intel_ish_ipc sha256_ssse3 hid_multitouch sha1_ssse3 rtsx_pci video
cec intel_ishtp typec vmd i2c_hid_acpi i2c_hid wmi pinctrl_tigerlake serio_raw
ip6_tables ip_tables fuse i2c_dev
Aug 26 10:33:49 foobar kernel: CPU: 0 UID: 0 PID: 6646 Comm: kworker/0:0
Tainted: P           OE     -------  ---  6.11.0-0.rc4.38.fc41.x86_64 #1
Aug 26 10:33:49 foobar kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE,
[E]=UNSIGNED_MODULE
Aug 26 10:33:49 foobar kernel: Hardware name: Dell Inc. Precision 5570/04NDTC,
BIOS 1.25.0 07/11/2024
Aug 26 10:33:49 foobar kernel: Workqueue: events xhci_handle_command_timeout
Aug 26 10:33:49 foobar kernel: RIP: 0010:xhci_handshake_check_state+0x52/0x100
Aug 26 10:33:49 foobar kernel: Code: 14 24 8b 06 21 c2 39 d1 0f 84 85 00 00 00
4d 85 e4 49 89 f7 41 89 ce 0f 95 44 24 07 eb 16 f3 90 48 81 eb e9 03 00 00 41
8b 07 <8b> 14 24 21 c2 44 39 f2 74 5f 83 f8 ff 74 42 89 ea 41 23 95 88 09
Aug 26 10:33:49 foobar kernel: RSP: 0018:ffff9a920cdf3c00 EFLAGS: 00000016
Aug 26 10:33:49 foobar kernel: RAX: 0000000000000008 RBX: 00000000247309b7 RCX:
0000000000000000
Aug 26 10:33:49 foobar kernel: RDX: 0000000000000041 RSI: 0000000000000018 RDI:
000002e7154a8710
Aug 26 10:33:49 foobar kernel: RBP: 0000000000000004 R08: 00000000004c4b40 R09:
0000000000000004
Aug 26 10:33:49 foobar kernel: R10: 0000000000000007 R11: 0000000000000007 R12:
00000000004c4b40
Aug 26 10:33:49 foobar kernel: R13: ffff8f90225df250 R14: 0000000000000000 R15:
ffff9a9203a40098
Aug 26 10:33:49 foobar kernel: FS:  0000000000000000(0000)
GS:ffff8f96eee00000(0000) knlGS:0000000000000000
Aug 26 10:33:49 foobar kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Aug 26 10:33:49 foobar kernel: CR2: 00000c24048ca048 CR3: 000000058742a000 CR4:
0000000000f50ef0
Aug 26 10:33:49 foobar kernel: PKRU: 55555554
Aug 26 10:33:49 foobar kernel: Call Trace:
Aug 26 10:33:49 foobar kernel:  <NMI>
Aug 26 10:33:49 foobar kernel:  ? watchdog_hardlockup_check.cold+0x149/0x14e
Aug 26 10:33:49 foobar kernel:  ? __perf_event_overflow+0x10c/0x320
Aug 26 10:33:49 foobar kernel:  ? x86_perf_event_set_period+0xdc/0x1c0
Aug 26 10:33:49 foobar kernel:  ? handle_pmi_common+0x1a5/0x400
Aug 26 10:33:49 foobar kernel:  ? intel_pmu_handle_irq+0x10b/0x510
Aug 26 10:33:49 foobar kernel:  ? perf_event_nmi_handler+0x2a/0x50
Aug 26 10:33:49 foobar kernel:  ? nmi_handle+0x65/0x130
Aug 26 10:33:49 foobar kernel:  ? default_do_nmi+0x40/0x130
Aug 26 10:33:49 foobar kernel:  ? exc_nmi+0x122/0x1a0
Aug 26 10:33:49 foobar kernel:  ? end_repeat_nmi+0xf/0x53
Aug 26 10:33:49 foobar kernel:  ? xhci_handshake_check_state+0x52/0x100
Aug 26 10:33:49 foobar kernel:  ? xhci_handshake_check_state+0x52/0x100
Aug 26 10:33:49 foobar kernel:  ? xhci_handshake_check_state+0x52/0x100
Aug 26 10:33:49 foobar kernel:  </NMI>
Aug 26 10:33:49 foobar kernel:  <TASK>
Aug 26 10:33:49 foobar kernel:  xhci_handle_command_timeout+0x3ec/0x530
Aug 26 10:33:49 foobar kernel:  process_one_work+0x176/0x330
Aug 26 10:33:49 foobar kernel:  worker_thread+0x256/0x390
Aug 26 10:33:49 foobar kernel:  ? __pfx_worker_thread+0x10/0x10
Aug 26 10:33:49 foobar kernel:  kthread+0xcf/0x100
Aug 26 10:33:49 foobar kernel:  ? __pfx_kthread+0x10/0x10
Aug 26 10:33:49 foobar kernel:  ret_from_fork+0x31/0x50
Aug 26 10:33:49 foobar kernel:  ? __pfx_kthread+0x10/0x10
Aug 26 10:33:49 foobar kernel:  ret_from_fork_asm+0x1a/0x30
Aug 26 10:33:49 foobar kernel:  </TASK>
Aug 26 10:33:49 foobar kernel: xhci_hcd 0000:04:00.0: Abort failed to stop
command ring: -110
Aug 26 10:33:49 foobar kernel: xhci_hcd 0000:04:00.0: xHCI host controller not
responding, assume dead
Aug 26 10:33:49 foobar kernel: xhci_hcd 0000:04:00.0: HC died; cleaning up
Aug 26 10:33:49 foobar kernel: xhci_hcd 0000:04:00.0: Error while assigning
device slot ID: Command Aborted
Aug 26 10:33:49 foobar kernel: xhci_hcd 0000:04:00.0: Max number of devices
this xHCI host supports is 64.
Aug 26 10:33:49 foobar kernel: usb usb5-port2: couldn't allocate usb_device
Aug 26 10:33:49 foobar kernel: usb usb6-port2: couldn't allocate usb_device
Aug 26 10:33:57 foobar kernel: usb usb2-port1: unable to enumerate USB device
----

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #1 from Markus Rathgeb (maggu2810@gmail.com) ---
Created attachment 306776
  --> https://bugzilla.kernel.org/attachment.cgi?id=306776&action=edit
kernel log 6.11.0-0.rc4.38.fc41

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #2 from Markus Rathgeb (maggu2810@gmail.com) ---
Created attachment 306777
  --> https://bugzilla.kernel.org/attachment.cgi?id=306777&action=edit
kernel log 6.11.0-0.rc5.43.fc41

Problem still exists with fedora kernel 6.11.0-0.rc5.43

On rc4 the dock has been connected on boot up and I disconnected it and
attached the log while reconnect it againn.

On this log the dock has not been connected on boot up. I had to connect it,
unplug it and connect it again (first I received an "failed to initial" and no
more).

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #3 from Markus Rathgeb (maggu2810@gmail.com) ---
Created attachment 306779
  --> https://bugzilla.kernel.org/attachment.cgi?id=306779&action=edit
kernel log 6.11.0-0.rc0.20240716gitd67978318827.2.fc41.x86_64

On Fedora kernel 6.11.0-0.rc0.20240716gitd67978318827.2.fc41.x86_64 USB is
still working.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |regressions@leemhuis.info

--- Comment #4 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
Do you run "powertop --auto-tune" somewhere? Then it might be related to
https://lore.kernel.org/all/be791564-ccca-4dd5-915f-aa32b2482817@molgen.mpg.de/

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

Adam Williamson (adamw@happyassassin.net) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adamw@happyassassin.net

--- Comment #5 from Adam Williamson (adamw@happyassassin.net) ---
I'm seeing something similar, and powertop doesn't seem to be involved.

I also have a Dell laptop - an XPS 13 9315. It's connected to a CalDigit TS3+
Thunderbolt docking station. Connected to the CalDigit are a 4K monitor
(connected by USB-C), Ethernet, a USB webcam, USB headset, and a USB keyboard.
The laptop has an internal keyboard and trackpad, of course. And I have a
Bluetooth external mouse.

When I boot kernel 6.9.12 or 6.10.6, all of these work fine more or less
immediately after boot, every time.

When I boot kernel 6.11 (tried rc3, rc4 and rc5) this is what happens:

* At the point where I have to enter the passphrase to decrypt my storage, the
USB keyboard always works.
* When I reach the login screen - whether GDM or just a tty, I tested boot to
multi-user.target and it's the same - nothing works for quite some time. After
about 20 seconds, the laptop's internal keyboard and trackpad, and the
Bluetooth mouse, start working. But the USB external keyboard never starts
working. (I'm not sure of the status of the webcam and headset, I didn't
check).

I have powertop and power-profiles-daemon installed, but I tried removing both
and doing a test boot of 6.11rc5, and the symptoms were exactly the same,
nothing changed.

I'll attach the journal from an affected 6.11rc5 boot and from a working 6.10
boot. Something I notice is that early in boot we see:

Aug 26 11:47:03 xps13a.happyassassin.net kernel: hid-generic
0003:154A:0002.0002: input,hidraw1: USB HID v1.00 Keyboard [ID Innovations Inc.
Input Device] on usb-0000:56:00.0-2/input0

but then later, we see:

Aug 26 11:47:44 xps13a.happyassassin.net kernel: xhci_hcd 0000:57:00.0: Abort
failed to stop command ring: -110
Aug 26 11:47:44 xps13a.happyassassin.net kernel: xhci_hcd 0000:57:00.0: xHCI
host controller not responding, assume dead
Aug 26 11:47:44 xps13a.happyassassin.net kernel: xhci_hcd 0000:57:00.0: HC
died; cleaning up
Aug 26 11:47:44 xps13a.happyassassin.net kernel: xhci_hcd 0000:57:00.0: Error
while assigning device slot ID: Command Aborted
Aug 26 11:47:44 xps13a.happyassassin.net kernel: xhci_hcd 0000:57:00.0: Max
number of devices this xHCI host supports is 64.
Aug 26 11:47:44 xps13a.happyassassin.net kernel: usb usb9-port1: couldn't
allocate usb_device
Aug 26 11:47:44 xps13a.happyassassin.net systemd[1]:
NetworkManager-dispatcher.service: Deactivated successfully.
Aug 26 11:47:44 xps13a.happyassassin.net audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=NetworkManager-dispatcher comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 26 11:47:50 xps13a.happyassassin.net kernel: Bluetooth: hci0: Opcode 0x200e
failed: -110
Aug 26 11:48:00 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: Abort
failed to stop command ring: -110
Aug 26 11:48:00 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: xHCI
host controller not responding, assume dead
Aug 26 11:48:00 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: HC
died; cleaning up
Aug 26 11:48:00 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: Error
while assigning device slot ID: Command Aborted
Aug 26 11:48:00 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: Max
number of devices this xHCI host supports is 32.
Aug 26 11:48:00 xps13a.happyassassin.net kernel: usb usb7-port2: couldn't
allocate usb_device
Aug 26 11:48:00 xps13a.happyassassin.net kernel: usb usb8-port4: couldn't
allocate usb_device

and after that, we never see "USB HID v1.00 Keyboard" appear again. In
contrast, in the 6.10 logs, we see "USB HID v1.00 Keyboard" appear twice, and
we never see any "couldn't allocate usb_device" or "Abort failed to stop
command ring" errors.

I *think* the 're-enumeration' that seems to be happening here (which seems to
work fine on 6.10, but lead to problems on 6.11) is a result of
thunderbolt.service starting up.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #6 from Adam Williamson (adamw@happyassassin.net) ---
Created attachment 306782
  --> https://bugzilla.kernel.org/attachment.cgi?id=306782&action=edit
journal from a 6.10.6 boot where the bug doesn't happen

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #7 from Adam Williamson (adamw@happyassassin.net) ---
Created attachment 306783
  --> https://bugzilla.kernel.org/attachment.cgi?id=306783&action=edit
journal from a 6.11 rc5 boot where the bug does happen

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #8 from Markus Rathgeb (maggu2810@gmail.com) ---
Created attachment 306784
  --> https://bugzilla.kernel.org/attachment.cgi?id=306784&action=edit
kernel log 6.11.0-rc1

I build a vanilla kernel 6.11.0-rc1 with the configuration based on the Fedora
kernel.
Replugging the dock result into non working dock USB ports, too.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #9 from Markus Rathgeb (maggu2810@gmail.com) ---
Does a git bisect help you to identify the problematic change(s)

I am currently in the progress...

$ git bisect log
git bisect start
# status: waiting for both good and bad commits
# bad: [8400291e289ee6b2bf9779ff1c83a291501f017b] Linux 6.11-rc1
git bisect bad 8400291e289ee6b2bf9779ff1c83a291501f017b
# status: waiting for good commit(s), bad commit known
# good: [7ba498d9d1bb67bcbc2a79f19a9054cdc8b95098] Linux 6.10.6
git bisect good 7ba498d9d1bb67bcbc2a79f19a9054cdc8b95098
# good: [0c3836482481200ead7b416ca80c68a29cfdaabd] Linux 6.10
git bisect good 0c3836482481200ead7b416ca80c68a29cfdaabd
# good: [280e36f0d5b997173d014c07484c03a7f7750668] nsfs: use cleanup guard
git bisect good 280e36f0d5b997173d014c07484c03a7f7750668

But if you already know what related changes has been done, I could cancel it.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #10 from Markus Rathgeb (maggu2810@gmail.com) ---
Forget the bisect.

I currently tested the another commit.

I started the laptop without the dock attached.
In a Wayland session I opened a terminal to look at the kernel messages.
I plugged in the dock.
All loooks good.
The USB keyboard attached to the dock is working.
Before I entered "git bisect good" I had the idee to test again.
I disconnected the dock, waited a moment
I connected the dock again
Now the lines
Aug 27 11:51:07 b0v9by3 kernel: DMAR: DRHD: handling fault status reg 2
Aug 27 11:51:07 b0v9by3 kernel: DMAR: [DMA Read NO_PASID] Request device
[04:00.0] fault addr 0xffffe000 [fault reason 0x0c] non-zero reserved fields in
PTE
are part of the kernel log
additional the USB keyboard attached to the dock are not recognized again

So, we need to disconnect and reconnect the dock at least once to run into the
error.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #11 from Adam Williamson (adamw@happyassassin.net) ---
I'm not replugging mine, but as I noted, the Thunderbolt service (I forgot it's
bolt.service , not thunderbolt.service) is producing a similar effect. I do
indeed see similar messages to yours *after* bolt.service starts:

Aug 26 11:47:21 xps13a.happyassassin.net systemd[1]: Started bolt.service -
Thunderbolt system service.
...
Aug 26 11:47:22 xps13a.happyassassin.net kernel: pci 0000:55:00.0: enabling
device (0000 -> 0002)
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:55:00.0: xHCI
Host Controller
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:55:00.0: new USB
bus registered, assigned bus number 5
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:55:00.0: hcc
params 0x200071e9 hci version 0x100 quirks 0x0000000000000010
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:55:00.0: xHCI
Host Controller
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:55:00.0: new USB
bus registered, assigned bus number 6
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:55:00.0: Host
supports USB 3.0 SuperSpeed
Aug 26 11:47:22 xps13a.happyassassin.net kernel: DMAR: DRHD: handling fault
status reg 2
Aug 26 11:47:22 xps13a.happyassassin.net kernel: DMAR: [DMA Read NO_PASID]
Request device [55:00.0] fault addr 0xffffb000 [fault reason 0x06] PTE Read
access is not set
...
Aug 26 11:47:22 xps13a.happyassassin.net kernel: pci 0000:56:00.0: enabling
device (0000 -> 0002)
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: xHCI
Host Controller
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: new USB
bus registered, assigned bus number 7
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: hcc
params 0x200071e9 hci version 0x100 quirks 0x0000000000000010
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: xHCI
Host Controller
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: new USB
bus registered, assigned bus number 8
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:56:00.0: Host
supports USB 3.0 SuperSpeed
Aug 26 11:47:22 xps13a.happyassassin.net kernel: DMAR: DRHD: handling fault
status reg 2
Aug 26 11:47:22 xps13a.happyassassin.net kernel: DMAR: [DMA Read NO_PASID]
Request device [56:00.0] fault addr 0xffffb000 [fault reason 0x0c] non-zero
reserved fields in PTE
...
Aug 26 11:47:22 xps13a.happyassassin.net kernel: pci 0000:57:00.0: enabling
device (0000 -> 0002)
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:57:00.0: xHCI
Host Controller
Aug 26 11:47:22 xps13a.happyassassin.net kernel: xhci_hcd 0000:57:00.0: new USB
bus registered, assigned bus number 9
Aug 26 11:47:22 xps13a.happyassassin.net audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=colord comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?
addr=? terminal=? res=success'
[snip unrelated messages]
Aug 26 11:47:22 xps13a.happyassassin.net kernel: DMAR: DRHD: handling fault
status reg 2
Aug 26 11:47:22 xps13a.happyassassin.net kernel: DMAR: [DMA Read NO_PASID]
Request device [57:00.0] fault addr 0xffffb000 [fault reason 0x06] PTE Read
access is not set

And indeed there are no similar messages in my 6.10.6 log.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #12 from Adam Williamson (adamw@happyassassin.net) ---
I would guess the thing to focus on here is the "big set of USB and Thunderbolt
changes for 6.11-rc1" - commit 04d17331ca33744e1426fdeee7ba5e975c4b2239 in
Linus' tree . It had 112 commits.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #13 from Markus Rathgeb (maggu2810@gmail.com) ---
One additional information:

I masked bolt.service (systemctl mask bolt.service) and restarted my system
with dock disconnected.
After the system is running (Wayland session) I looked at the kernel messages
and connect the dock, disconnect the dock, connect the dock...
The thunderbolt dock itself is detected but no peripheral.

security is set to user

$ cat /sys/bus/thunderbolt/devices/domain0/security
user

I created this udev rule "/etc/udev/rules.d/99-removable.rules"
ACTION=="add", SUBSYSTEM=="thunderbolt", ATTR{authorized}=="0",
ATTR{authorized}="1"

Reload the rules and added the dock again.
The attached USB keyboard has been detected.

I disconnected the dock and reconnected it again.
I see the DMAR error and no USB device is detect now.

Just to replace bolt with a the simple udev rule and reduce the user space
service(s) that are involved.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #14 from Markus Rathgeb (maggu2810@gmail.com) ---
I did a git checkout aba9753c0677e860f982edff98c7fe5a2b97758c (the commit id
before 04d17331ca33744e1426fdeee7ba5e975c4b2239).
It seems to trigger the same error.

So, I already tried a some different kernel builds / commit IDs and the RCs.
They all result into non recognized USB devices.
But additional behaviour differs. On some kernels if the error is hit, the
system is not usable anymore as the mouse does not react for seconds. Other
ones shows kernel dumps, other ones only non working USB...

I still try to find the commit / merge that stops USB first.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #15 from Markus Rathgeb (maggu2810@gmail.com) ---
I found the commit that initially break the USB on second connect.

[2b989ab9bc89b29dd4b5509408b8fa42337eda56] iommu/vt-d: Add helper to allocate
paging domain

$ git bisect log
git bisect start
# status: waiting for both good and bad commits
# good: [3d51520954154a476bfdacf9427acd1d9538734c] Merge tag 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma
git bisect good 3d51520954154a476bfdacf9427acd1d9538734c
# status: waiting for bad commit, 1 good commit known
# bad: [aba9753c0677e860f982edff98c7fe5a2b97758c] Merge tag 'tty-6.11-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty
git bisect bad aba9753c0677e860f982edff98c7fe5a2b97758c
# bad: [a4f9285520584977127946a22eab2adfbc87d1bf] Merge tag 'clk-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
git bisect bad a4f9285520584977127946a22eab2adfbc87d1bf
# bad: [f66b07c56119833b88bffa4ecaf9f983834675de] Merge tag 'vfio-v6.11-rc1' of
https://github.com/awilliam/linux-vfio
git bisect bad f66b07c56119833b88bffa4ecaf9f983834675de
# bad: [afd81d914f6fb3e74a46bf5d0dd0b028591ea22e] Merge tag
'dma-mapping-6.11-2024-07-19' of git://git.infradead.org/users/hch/dma-mapping
git bisect bad afd81d914f6fb3e74a46bf5d0dd0b028591ea22e
# bad: [afd81d914f6fb3e74a46bf5d0dd0b028591ea22e] Merge tag
'dma-mapping-6.11-2024-07-19' of git://git.infradead.org/users/hch/dma-mapping
git bisect bad afd81d914f6fb3e74a46bf5d0dd0b028591ea22e
# good: [cbf9520823bdd4c44c94b5988e354ee12d57fa58] Merge branch
'iommu/arm/smmu' into iommu/next
git bisect good cbf9520823bdd4c44c94b5988e354ee12d57fa58
# bad: [c2b2e5c50330b29804339df4e7adf70e9f19b793] Merge branch 'iommu/core'
into iommu/next
git bisect bad c2b2e5c50330b29804339df4e7adf70e9f19b793
# bad: [31000732d56b43765d51e08cccb68818fbc0032c] iommu/vt-d: Fix identity map
bounds in si_domain_init()
git bisect bad 31000732d56b43765d51e08cccb68818fbc0032c
# good: [804f98e224e41c16e3b70f97790f84894745a392] iommu/vt-d: Downgrade
warning for pre-enabled IR
git bisect good 804f98e224e41c16e3b70f97790f84894745a392
# bad: [3753311c9190f833963fb47336dfe17221d93706] iommu/vt-d: Refactor PCI PRI
enabling/disabling callbacks
git bisect bad 3753311c9190f833963fb47336dfe17221d93706
# bad: [f90584f4beb84211c4d21b319cc13f391fe9f3c2] iommu/vt-d: Add helper to
flush caches for context change
git bisect bad f90584f4beb84211c4d21b319cc13f391fe9f3c2

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #16 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
Thx Markus. Can I CC you on a mail to the developers? This would expose your
email address to the public.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #17 from Markus Rathgeb (maggu2810@gmail.com) ---
Yes, sure.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #18 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
Forwarded by mail:
https://lore.kernel.org/all/c844faa0-343a-46f4-a54f-0fd65f4d4679@leemhuis.info/

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #19 from Markus Rathgeb (maggu2810@gmail.com) ---
For the record:

The laptop I used for testing is a "Dell Precision 5570".

The docks I identified the error and tested the kernels:
* Dell WD19TB Thunderbolt Dock
* Lenovo ThinkPad Thunderbolt 3 Dock

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #20 from Markus Rathgeb (maggu2810@gmail.com) ---
Created attachment 306785
  --> https://bugzilla.kernel.org/attachment.cgi?id=306785&action=edit
kernel-6.10.0.804f98e224e4+.txt

Here the log of plug-in the dock, unplug it and plug it again for commit
804f98e224e41c16e3b70f97790f84894745a392

It is the commit before the problem occurs, so all fine here.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #21 from Markus Rathgeb (maggu2810@gmail.com) ---
Created attachment 306786
  --> https://bugzilla.kernel.org/attachment.cgi?id=306786&action=edit
kernel-6.10.0.f90584f4beb8+.txt

Here the log of plug-in the dock, unplug it and plug it again for commit
f90584f4beb84211c4d21b319cc13f391fe9f3c2

It is the commit that git bisect told me as the problematic one.

Reading the git log, I wonder why git bisect did not try
2b989ab9bc89b29dd4b5509408b8fa42337eda56

For me it seems it is between the good and bad one and not tested.
But the same author, so I assume he can judge better.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #22 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from
comment #4)
> Do you run "powertop --auto-tune" somewhere? Then it might be related to
> https://lore.kernel.org/all/be791564-ccca-4dd5-915f-aa32b2482817@molgen.mpg.
> de/

(In reply to Markus Rathgeb from comment #15)
> I found the commit that initially break the USB on second connect.
> 
> [2b989ab9bc89b29dd4b5509408b8fa42337eda56] iommu/vt-d: Add helper to
> allocate paging domain

At least with the commit reverted the Dell DA300z adapter still disconnected,
so my problem seems to be a *different* one.

    $ git log --no-decorate --oneline -2
    43275d604d974 Revert "iommu/vt-d: Add helper to allocate paging domain"
    86987d84b968b Merge tag 'v6.11-rc5-client-fixes' of
git://git.samba.org/sfrench/cifs-2.6
    $ sudo dmesg
    [    0.000000] Linux version 6.11.0-rc5-00058-g43275d604d97
(build@bohemianrhapsody.molgen.mpg.de) (gcc (Debian 13.3.0-2) 13.3.0, GNU ld
(GNU Binutils for Debian) 2.42.50.20240710) #289 SMP PREEMPT_DYNAMIC Wed Aug 28
15:29:09 CEST 2024
    [    0.000000] Command line:
BOOT_IMAGE=/vmlinuz-6.11.0-rc5-00058-g43275d604d97
root=UUID=32e29882-d94d-4a92-9ee4-4d03002bfa29 ro quiet pci=noaer
mem_sleep_default=deep log_buf_len=8M cryptomgr.notests
    […]
    [ 7951.874589] usb 4-1: reset SuperSpeed Plus Gen 2x1 USB device number 2
using xhci_hcd
    [ 7952.369334] r8152-cfgselector 4-1.2: USB disconnect, device number 3
    [ 7952.542017] usb 4-1: reset SuperSpeed Plus Gen 2x1 USB device number 2
using xhci_hcd

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #23 from Adam Williamson (adamw@happyassassin.net) ---
Paul: do you see the DMAR fault status log messages that I and Markus see?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #24 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
Created attachment 306787
  --> https://bugzilla.kernel.org/attachment.cgi?id=306787&action=edit
[unrelated] Linux 6.11-rc5+ messages (output of `dmesg`)

(In reply to Adam Williamson from comment #23)
> Paul: do you see the DMAR fault status log messages that I and Markus see?

No, there are *no* such fault status messages.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #25 from Adam Williamson (adamw@happyassassin.net) ---
OK, I would say that kinda seems like a different bug then.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #26 from Markus Rathgeb (maggu2810@gmail.com) ---
I resetted the git tree to 2b989ab9bc89, did another build + test.
This commit is still a good one.

$ git bisect good
f90584f4beb84211c4d21b319cc13f391fe9f3c2 is the first bad commit
commit f90584f4beb84211c4d21b319cc13f391fe9f3c2
Author: Lu Baolu <baolu.lu@linux.intel.com>
Date:   Tue Jul 2 21:08:38 2024 +0800

    iommu/vt-d: Add helper to flush caches for context change

    This helper is used to flush the related caches following a change in a
    context table entry that was previously present. The VT-d specification
    provides guidance for such invalidations in section 6.5.3.3.

    This helper replaces the existing open code in the code paths where a
    present context entry is being torn down.

    Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
    Reviewed-by: Kevin Tian <kevin.tian@intel.com>
    Link:
https://lore.kernel.org/r/20240701112317.94022-2-baolu.lu@linux.intel.com
    Link:
https://lore.kernel.org/r/20240702130839.108139-7-baolu.lu@linux.intel.com
    Signed-off-by: Will Deacon <will@kernel.org>

 drivers/iommu/intel/iommu.c |  32 +-------------------------------
 drivers/iommu/intel/iommu.h |   4 ++++
 drivers/iommu/intel/pasid.c | 106
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------
 3 files changed, 92 insertions(+), 50 deletions(-)


$ git bisect log
git bisect start
# status: waiting for both good and bad commits
# good: [3d51520954154a476bfdacf9427acd1d9538734c] Merge tag 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma
git bisect good 3d51520954154a476bfdacf9427acd1d9538734c
# status: waiting for bad commit, 1 good commit known
# bad: [aba9753c0677e860f982edff98c7fe5a2b97758c] Merge tag 'tty-6.11-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty
git bisect bad aba9753c0677e860f982edff98c7fe5a2b97758c
# bad: [a4f9285520584977127946a22eab2adfbc87d1bf] Merge tag 'clk-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
git bisect bad a4f9285520584977127946a22eab2adfbc87d1bf
# bad: [f66b07c56119833b88bffa4ecaf9f983834675de] Merge tag 'vfio-v6.11-rc1' of
https://github.com/awilliam/linux-vfio
git bisect bad f66b07c56119833b88bffa4ecaf9f983834675de
# bad: [afd81d914f6fb3e74a46bf5d0dd0b028591ea22e] Merge tag
'dma-mapping-6.11-2024-07-19' of git://git.infradead.org/users/hch/dma-mapping
git bisect bad afd81d914f6fb3e74a46bf5d0dd0b028591ea22e
# bad: [afd81d914f6fb3e74a46bf5d0dd0b028591ea22e] Merge tag
'dma-mapping-6.11-2024-07-19' of git://git.infradead.org/users/hch/dma-mapping
git bisect bad afd81d914f6fb3e74a46bf5d0dd0b028591ea22e
# good: [cbf9520823bdd4c44c94b5988e354ee12d57fa58] Merge branch
'iommu/arm/smmu' into iommu/next
git bisect good cbf9520823bdd4c44c94b5988e354ee12d57fa58
# bad: [c2b2e5c50330b29804339df4e7adf70e9f19b793] Merge branch 'iommu/core'
into iommu/next
git bisect bad c2b2e5c50330b29804339df4e7adf70e9f19b793
# bad: [31000732d56b43765d51e08cccb68818fbc0032c] iommu/vt-d: Fix identity map
bounds in si_domain_init()
git bisect bad 31000732d56b43765d51e08cccb68818fbc0032c
# good: [804f98e224e41c16e3b70f97790f84894745a392] iommu/vt-d: Downgrade
warning for pre-enabled IR
git bisect good 804f98e224e41c16e3b70f97790f84894745a392
# bad: [3753311c9190f833963fb47336dfe17221d93706] iommu/vt-d: Refactor PCI PRI
enabling/disabling callbacks
git bisect bad 3753311c9190f833963fb47336dfe17221d93706
# bad: [f90584f4beb84211c4d21b319cc13f391fe9f3c2] iommu/vt-d: Add helper to
flush caches for context change
git bisect bad f90584f4beb84211c4d21b319cc13f391fe9f3c2
# good: [2b989ab9bc89b29dd4b5509408b8fa42337eda56] iommu/vt-d: Add helper to
allocate paging domain
git bisect good 2b989ab9bc89b29dd4b5509408b8fa42337eda56
# first bad commit: [f90584f4beb84211c4d21b319cc13f391fe9f3c2] iommu/vt-d: Add
helper to flush caches for context change

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #27 from Markus Rathgeb (maggu2810@gmail.com) ---
Created attachment 306788
  --> https://bugzilla.kernel.org/attachment.cgi?id=306788&action=edit
0001-fix-iommu-vt-d-Add-helper-to-flush-caches-for-contex.patch

This patch fixed 6.11.rc5 for me.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #28 from Adam Williamson (adamw@happyassassin.net) ---
6.11rc6 (with the patch merged upstream) is good for me too. Thanks a lot.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #29 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
For the record, that seems to be commit 7af6c720417f (iommu/vt-d: Fix incorrect
domain ID in context flush helper) [1]. No idea, why neither this bug report
URL nor Markus is mentioned in the patch.

[1]:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7af6c720417f21f015f46baa33e182f349ddc93b

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #30 from Adam Williamson (adamw@happyassassin.net) ---
Because there was a parallel - actually somewhat earlier - discussion on a
mailing list that led to that patch:
https://lore.kernel.org/linux-iommu/20240814162726.5efe1a6e.alex.williamson@redhat.com/
. (no, Alex Williamson is not me, though we get each other's email quite a lot.
:>)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.