* Re: xhci_hcd 0000:00:0d.0 (Panther Lake, 8086:e431): “Unknown event condition 199”, then HC died, with a TB4 dock and two displays
[not found] <CAMcR36+hWzhS_Pytej3uoDvOU6160v5vtuWXSnyFb=zEoRFQJQ@mail.gmail.com>
@ 2026-11-04 12:10 ` Mika Westerberg
2026-11-10 9:08 ` Mathias Nyman
1 sibling, 0 replies; 5+ messages in thread
From: Mika Westerberg @ 2026-11-04 12:10 UTC (permalink / raw)
To: Phani Kumar; +Cc: mathias.nyman, linux-usb
Hi,
On Tue, Nov 03, 2026 at 10:18:28AM -0800, Phani Kumar wrote:
> Hi,
>
> On a Framework Laptop 13 Pro (Panther Lake), the Type-C Subsystem xHCI
> controller (0000:00:0d.0, 8086:e431) reports a vendor-defined completion code
> 199 and then stops responding, taking down every USB 3 device behind a
> Thunderbolt 4 dock. It is triggered by Ethernet traffic through the dock. With
> two displays connected to the dock at boot it happens reliably within 1 to 4
> minutes; without displays it happens intermittently.
>
> Hardware:
> Laptop: Framework Laptop 13 Pro (Intel Core Ultra Series 3)
> CPU: Intel Core Ultra X7 358H, microcode 0x11a
> BIOS: 03.02 (2026-05-26), ME firmware 21.0.6.1503
> xHCI: 00:0d.0 Intel Core Ultra (Series 3) Type-C Subsystem xHCI
> [8086:e431] (rev 01)
> TB host: Intel Gen16 USB4 host router (8087:a000)
> Dock: Razer Thunderbolt 4 Dock Chroma (TB vendor 0x127, device 0x8), NVM
> 30.0
> Ethernet: RTL8153 (0bda:8153) inside the dock, in-tree r8152 driver
> Displays: two 2560x1440@60 on the dock's downstream TB4 ports
> (one USB-C to DisplayPort, one USB-C to HDMI adapter)
>
> Kernel: 7.3.1 (Ubuntu mainline build 7.3.1-070301-generic)
>
> Reproduction:
> 1. Boot with the dock and both displays connected.
> 2. Generate network traffic over the dock's Ethernet (e.g. open a browser).
> 3. Within about 1 minute the xHCI controller dies, and every USB 3 device
> behind the dock disconnects.
>
> Log:
> xhci_hcd 0000:00:0d.0: ERROR Unknown event condition 199 for slot 5 ep 3 , HC
> probably busted
> r8152 2-3.4.5:1.0 eth0: NETDEV WATCHDOG: CPU: 11: transmit queue 0 timed out
> 5665 ms
> r8152 2-3.4.5:1.0 eth0: Tx timeout
> r8152 2-3.4.5:1.0 eth0: Tx status -2
> r8152-cfgselector 2-3.4.5: reset SuperSpeed USB device number 6 using
> xhci_hcd
> xhci_hcd 0000:00:0d.0: ERROR Unknown event condition 199 for slot 5 ep 3 , HC
> probably busted
> r8152 2-3.4.5:1.0 eth0: Stop submitting intr, status -71
> xhci_hcd 0000:00:0d.0: xHCI host not responding to stop endpoint command
> xhci_hcd 0000:00:0d.0: xHCI host controller not responding, assume dead
> xhci_hcd 0000:00:0d.0: HC died; cleaning up
> usb 2-3: USB disconnect, device number 3
>
> Full kernel log attached.
>
> Observations:
> - With only one display connected (either one), it does not happen.
> - Booting with one display and hot-plugging the second after login did not
> trigger it in one test.
> - With thunderbolt.dyndbg=+p, the Thunderbolt driver logs nothing in the
> window before the failure, so tunnel and bandwidth changes don't appear to be
> involved.
I agree, I checked the log you shared (although it missed some details)
tunnels look fine. One thing you can try is to run "sudo tbunnels -v" after
this happens so we can see if the USB3 tunnel is up.
You can get tbtunnels from [1].
[1] https://github.com/intel/tbtools
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: xhci_hcd 0000:00:0d.0 (Panther Lake, 8086:e431): “Unknown event condition 199”, then HC died, with a TB4 dock and two displays
[not found] <CAMcR36+hWzhS_Pytej3uoDvOU6160v5vtuWXSnyFb=zEoRFQJQ@mail.gmail.com>
2026-11-04 12:10 ` xhci_hcd 0000:00:0d.0 (Panther Lake, 8086:e431): “Unknown event condition 199”, then HC died, with a TB4 dock and two displays Mika Westerberg
@ 2026-11-10 9:08 ` Mathias Nyman
[not found] ` <CAMcR36LCr0RFrHsLFPaPziPS=1CMbEnO3GcDk=3Oe33S8uZFpw@mail.gmail.com>
1 sibling, 1 reply; 5+ messages in thread
From: Mathias Nyman @ 2026-11-10 9:08 UTC (permalink / raw)
To: Phani Kumar; +Cc: linux-usb, mika.westerberg
On 11/3/26 20:18, Phani Kumar wrote:
> Hi,
>
> On a Framework Laptop 13 Pro (Panther Lake), the Type-C Subsystem xHCI
> controller (0000:00:0d.0, 8086:e431) reports a vendor-defined completion
> code 199 and then stops responding, taking down every USB 3 device behind a
> Thunderbolt 4 dock. It is triggered by Ethernet traffic through the dock.
> With two displays connected to the dock at boot it happens reliably within
> 1 to 4 minutes; without displays it happens intermittently.
>
> Hardware:
> Laptop: Framework Laptop 13 Pro (Intel Core Ultra Series 3)
> CPU: Intel Core Ultra X7 358H, microcode 0x11a
> BIOS: 03.02 (2026-05-26), ME firmware 21.0.6.1503
> xHCI: 00:0d.0 Intel Core Ultra (Series 3) Type-C Subsystem xHCI
> [8086:e431] (rev 01)
> TB host: Intel Gen16 USB4 host router (8087:a000)
> Dock: Razer Thunderbolt 4 Dock Chroma (TB vendor 0x127, device 0x8),
> NVM 30.0
> Ethernet: RTL8153 (0bda:8153) inside the dock, in-tree r8152 driver
> Displays: two 2560x1440@60 on the dock's downstream TB4 ports
> (one USB-C to DisplayPort, one USB-C to HDMI adapter)
>
> Kernel: 7.3.1 (Ubuntu mainline build 7.3.1-070301-generic)
>
> Reproduction:
> 1. Boot with the dock and both displays connected.
> 2. Generate network traffic over the dock's Ethernet (e.g. open a
> browser).
> 3. Within about 1 minute the xHCI controller dies, and every USB 3 device
> behind the dock disconnects.
>
> Log:
> xhci_hcd 0000:00:0d.0: ERROR Unknown event condition 199 for slot 5 ep 3
> , HC probably busted
> r8152 2-3.4.5:1.0 eth0: NETDEV WATCHDOG: CPU: 11: transmit queue 0 timed
> out 5665 ms
> r8152 2-3.4.5:1.0 eth0: Tx timeout
> r8152 2-3.4.5:1.0 eth0: Tx status -2
> r8152-cfgselector 2-3.4.5: reset SuperSpeed USB device number 6 using
> xhci_hcd
> xhci_hcd 0000:00:0d.0: ERROR Unknown event condition 199 for slot 5 ep 3
> , HC probably busted
> r8152 2-3.4.5:1.0 eth0: Stop submitting intr, status -71
> xhci_hcd 0000:00:0d.0: xHCI host not responding to stop endpoint command
> xhci_hcd 0000:00:0d.0: xHCI host controller not responding, assume dead
> xhci_hcd 0000:00:0d.0: HC died; cleaning up
> usb 2-3: USB disconnect, device number 3
>
> Full kernel log attached.
>
Could you take both xhci traces, and log with xhci and usb core dynamic debug enabled?
Looks like the endpoint or its contexts may be in some odd state
(vendor event for specific endpoint, and failure to stop endpoint)
mount -t debugfs none /sys/kernel/debug
echo 'module xhci_hcd =p' >/sys/kernel/debug/dynamic_debug/control
echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control
echo 81920 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/xhci-hcd/enable
echo 1 > /sys/kernel/debug/tracing/tracing_on
< Reproduce issue >
Send output of dmesg
Send content of /sys/kernel/debug/tracing/trace
xHC may also refuse to add an endpoints if it doesn't have the bandwidth to handle it.
What do files under /sys/kernel/debug/usb/xhci/0000:00:0d.0/port_bandwidth'
show right after starting network traffic?
Thanks
Mathias
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: xhci_hcd 0000:00:0d.0 (Panther Lake, 8086:e431): “Unknown event condition 199”, then HC died, with a TB4 dock and two displays
[not found] ` <CAMcR36LCr0RFrHsLFPaPziPS=1CMbEnO3GcDk=3Oe33S8uZFpw@mail.gmail.com>
@ 2026-11-12 14:55 ` Mathias Nyman
[not found] ` <CAMcR36KcP7cMZ2D1pu_bC-R0uPn2chd_1jEzp4FBBq-jZz=D3A@mail.gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Mathias Nyman @ 2026-11-12 14:55 UTC (permalink / raw)
To: Phani Kumar; +Cc: linux-usb, mika.westerberg
On 11/11/26 01:58, Phani Kumar wrote:
> Hi Mathias, Mika,
>
> Thanks both. Here are the captures you asked for. All runs are on
> kernel 7.3.3 with Secure Boot (lockdown) disabled.
>
> == xHCI traces and dynamic debug (Mathias) ==
>
> xhci_hcd and usbcore dyndbg and the xhci-hcd trace were enabled from
> boot (xhci_hcd.dyndbg=+p usbcore.dyndbg=+p trace_event=xhci-hcd:*
> trace_buf_size=80M log_buf_len=16M). Nothing overflowed. Files: Attached.
>
> 1) xhci-debug-20261110-capture3-event199.tar.xz: the event 199 case.
> - 52.10 s: "Unknown event condition 199 for slot 5 ep 3"
> (slot 5 is the RTL8153 in the dock, 2-3.4.5)
> - 52.28 s: "Unknown event condition 199 for slot 2 ep 0"
> - 67.94 s: "xHCI host not responding to stop endpoint command",
> "HC died; cleaning up"
> - The trace covers 34.5 s to 73.5 s.
>
> 2) xhci-debug-20261110-capture2.tar.xz: a run without event 199 or
> HC died.
> - 114.4 s: "usb 2-3-port2: link state change", "do warm reset,
> port only", and the warm reset does not complete
> - 115.2 s: repeated "Transfer error for slot 5 ep 3" and "ep 2",
> with soft and hard endpoint resets
> - later, usb2-port3 stays stuck in warm reset (portsc 0x2f4)
>
> port_bandwidth: the same before network traffic, during traffic, and
> after the failure in run 2. After the event 199 failure it can't be
> read ("Cannot send after transport endpoint shutdown").
> FS_BW: port[1] 90%, port[2-5] 0%
> HS_BW: port[1] 80%, port[2-5] 0%
> SS_BW: port[1] 0%, port[2] 90%, port[3] 90%, port[4] 89%, port[5] 90%
>
Thanks
case 1
Tunneled USB3 link goes bad somewhere between the hub 2-3 and RTL8153
2-3.4.5 at 52.09.
All URBs behind 2-3 hub fail with transaction errors after this.
r8153 driver immediately re-queues URBs, even the ones returned with -PROTO,
so we end up in a massive endpoint reset and restart churn with
225 endpoint resets, Setting deq, and restart during 1.6 seconds.
xHC then just stops submitting any events.
case 2
In this case the link between xHC and Hub 2-3 goes bad. xhci detects
the bad link early and prevents URBs from being queueud.
Only 28 transfer errors in 100ms, xHC seems to handles this.
Several unsuccessful attempts to recover the link to 2-3 hub are done.
xHC stays functional.
I don't know why the links suddenly fails.
hub 2-3 port2 is unsuccessfully being reset all the time in both cases.
Any Idea what's connected to hub 2-3 port2? can it be unplugged? (if yes, does it help?)
Thanks
Mathias
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [WARNING: UNSCANNABLE EXTRACTION FAILED]Re: xhci_hcd 0000:00:0d.0 (Panther Lake, 8086:e431): “Unknown event condition 199”, then HC died, with a TB4 dock and two displays
[not found] ` <CAMcR36KcP7cMZ2D1pu_bC-R0uPn2chd_1jEzp4FBBq-jZz=D3A@mail.gmail.com>
@ 2026-11-20 7:12 ` Mika Westerberg
2026-11-20 10:30 ` Michal Pecio
0 siblings, 1 reply; 5+ messages in thread
From: Mika Westerberg @ 2026-11-20 7:12 UTC (permalink / raw)
To: Phani Kumar; +Cc: Mathias Nyman, linux-usb
Hi,
On Thu, Nov 19, 2026 at 11:35:28AM -0800, Phani Kumar wrote:
> Hey,
>
> Thanks for the reply. I did a few more tests to figure out this
> problem, and below is what I found.
>
> Summary: the failure only happens on Linux when the USB4 link to the
> dock runs at Gen 3 (2 x 20 Gb/s). At Gen 2 (20 Gbps cable) Linux is
> stable. Windows 11 on the same laptop is stable at both Gen 2 and
> Gen 3, under the same load, with no USB/USB4/network errors logged.
> When it fails on Linux, the tunneled USB 3 link is stuck in Recovery
> at both USB 3 adapters while all tunnels stay up and the thunderbolt
> driver logs nothing.
>
> == Hub 2-3 port 2 ==
>
> Nothing USB 3 is enumerated behind 2-3 port 2 in my setup. In all
> these tests the displays are connected to the dock's downstream USB-C
> ports with video-only cables (one USB-C to HDMI, one USB-C to
> DisplayPort). Unplugging doesn't help: with no displays and only a
> USB 3 thumb drive on the dock, the failure still happens. In the
> latest run (7.4-rc3, usbcore.dyndbg=+p, both displays connected) I see
> no 2-x-portN warm reset messages before the failure, so the port 2
> resets do not seem to be required for it.
>
> == Test matrix ==
>
> Same laptop (Framework Laptop 13 Pro, Core Ultra X7 358H, BIOS 03.02),
> same Razer TB4 Dock (NVM 30.0), same displays (2560x1440@60 and @75).
> Dock always links in USB4 mode (sysfs generation 4).
>
> Cable Link Linux Windows 11
> TB4 cable x3 Gen 3, 2 x 20 Gb/s fails stable
> USB4 40Gbps cable Gen 3, 2 x 20 Gb/s fails stable
> USB4 20Gbps cable x2 Gen 2, 2 x 10 Gb/s stable stable
>
> Linux: kernels 7.3.3 and 7.4-rc3, every laptop port. Any USB 3 device
> behind the dock triggers it (RTL8153 or a thumb drive). When the xHC
> dies, USB 3 on all of the laptop's own ports goes down too; removing
> and rescanning 0000:00:0d.0 restores it.
>
> Windows stress test (TB4 cable, "40Gbps/40Gbps (Gen 3, dual lane)",
> dock connected at boot, both displays): 20 GB download through the
> dock's RTL8153 at ~800 Mbps, USB 3 thumb drive on the dock at 146 MB/s
> read and 45-68 MB/s write, and both at the same time. No drops. The
> System event log has no USB, USB4, xHCI or network errors, only two
> "monitor ... successfully enumerated by the USB4 Connection Manager"
> entries at boot.
>
> Control test without USB4: the USB-C monitor's hub (0bda:0412 +
> RTL8153) connected directly to the laptop as native USB 3 at 5 Gbps,
> same xHC: stable under heavy Ethernet traffic.
>
> == USB 3 adapters stuck in Recovery ==
>
> USB4 register snapshots (debugfs regs, tbadapters, tbtunnels) at
> Gen 2, at Gen 3 before the failure, and at Gen 3 after it
> (usb4-snapshots.tar.xz, including diff-report.txt):
>
> tbadapters Gen 3 before Gen 3 after failure
> host 0:12 USB3 Down U0 Recovery
> dock 1:16 USB3 Up U0 Recovery
> tbtunnels: identical before and after, all tunnels present
>
> Timeline (7.4-rc3): transfer errors at 70.3 s, event 199 for slot 8
> ep 3 at 78.0 s, "HC died" at 88.7 s. With thunderbolt.dyndbg=+p the
> thunderbolt driver logged nothing between 44 s and 138 s (no hotplug,
> notifications or link events). Vendor-specific registers on both USB 3
> adapters jump across the failure (e.g. 0x00000909 -> 0x0000b6b6 /
> 0x0011bcbc), and lane adapter cap 0x01 dword 2 goes from 0x7/0x3 to
> 0x0 on both ends.
>
> == Lane margining ==
>
> thunderbolt.ko rebuilt for 7.4-rc3 with USB4_DEBUGFS_WRITE and
> MARGINING, 3 runs per rate, raw debugfs results included
> (margining.tar.xz):
>
> Receiver Gen 2 Gen 3
> dock 1:1 voltage low/high ~207/197 mV (at max) ~77/75 mV
> dock 1:1 lane 1 time (raw) 354-370 mUI 241-290 mUI
> host retimer 1-0:1.1 time 387-403 mUI 370-403 mUI
> host retimer voltage (not readable) ~107-121 mV
> host router port 1 (SW) 0 errors 0 errors
>
> So every receiver has margin at Gen 3, but the laptop -> dock
> direction (dock receiver) has noticeably less than dock -> laptop.
> Host retimer 8087:0d9c NVM 28.02 (fwupd), no newer firmware offered;
> BIOS 03.02 is the latest.
>
> == Ruled out ==
>
> - Bandwidth: USB 3 tunnel gets 9003/9003 Mb/s at Gen 3 (fails) but
> only 9003/4751 Mb/s at Gen 2 (stable). xHCI port_bandwidth SS_BW is
> ~90% available at both.
> - Thunderbolt 3 compatibility mode: both rates link as USB4
> (generation 4).
> - thunderbolt.clx=0, bw_alloc_mode=0, pcie_aspm=off, runtime PM off on
> 0d.0/.2/.3, LPM/autosuspend off on the RTL8153, Realtek's r8152
> v2.22.1: no effect. host_reset=Y.
>
> == Questions ==
>
> 1. Since Windows' CM keeps the Gen 3 link and the USB 3 tunnel clean on
> the same hardware, what could Linux be configuring differently at
> Gen 3 (TMU mode, lane/retimer equalization, USB 3 adapter setup)?
Windows CM should follow the CM guide as does Linux. USB3 tunnels are the
same regardless of the Gen, except that the isoc bandwidth limit is put
lower in case of Gen2.
> 2. Are ~75 mV / ~0.26 UI at the dock's receiver typical for Gen 3?
It's a good question. The hardware margin has bit set when these exceed the
ranges and in your case they are not set, also the host direction you don't
see errors so I would say this is okay.
> 3. Should r8152 back off after -EPROTO instead of resubmitting
> immediately? That seems to be what pushes the xHC over in case 1.
For this I hope Mathias has an answer :)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [WARNING: UNSCANNABLE EXTRACTION FAILED]Re: xhci_hcd 0000:00:0d.0 (Panther Lake, 8086:e431): “Unknown event condition 199”, then HC died, with a TB4 dock and two displays
2026-11-20 7:12 ` [WARNING: UNSCANNABLE EXTRACTION FAILED]Re: " Mika Westerberg
@ 2026-11-20 10:30 ` Michal Pecio
0 siblings, 0 replies; 5+ messages in thread
From: Michal Pecio @ 2026-11-20 10:30 UTC (permalink / raw)
To: Mika Westerberg, Mathias Nyman; +Cc: Phani Kumar, linux-usb
On Fri, 20 Nov 2026 08:12:02 +0100, Mika Westerberg wrote:
> > 3. Should r8152 back off after -EPROTO instead of resubmitting
> > immediately? That seems to be what pushes the xHC over in case 1.
>
> For this I hope Mathias has an answer :)
FYI, Microsoft asks drivers to check if the device still exists before
attempting any recovery (and also to cancel all URBs and reset the pipe
before submitting more URBs, but that's unrelated).
https://learn.microsoft.com/en-us/windows-hardware/drivers/usbcon/how-to-recover-from-usb-pipe-errors
This may be the reason why I have observed Windows in QEMU reading the
root hub port register before performing endpoint reset. And xhci-hcd
does similar checks, but it only detects root hub disconnection.
It seems that Intel HW either assumes that unreachable endponts won't
be restarted, or it has some general problems with restars that weren't
happening in other circumstances often enough to be noticed.
I wonder what happens if the same devices is disconnected from the same
or similar Intel HC, but behind an ordinary USB3 hub?
We also have that case of repeated UVC operations and/or isochronous
stream restarts (?) on some USB3 cameras crashing some Intel HCs.
I don't have any Intel HW to play with, only AMD.
Regards,
Michal
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2026-11-20 10:30 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAMcR36+hWzhS_Pytej3uoDvOU6160v5vtuWXSnyFb=zEoRFQJQ@mail.gmail.com>
2026-11-04 12:10 ` xhci_hcd 0000:00:0d.0 (Panther Lake, 8086:e431): “Unknown event condition 199”, then HC died, with a TB4 dock and two displays Mika Westerberg
2026-11-10 9:08 ` Mathias Nyman
[not found] ` <CAMcR36LCr0RFrHsLFPaPziPS=1CMbEnO3GcDk=3Oe33S8uZFpw@mail.gmail.com>
2026-11-12 14:55 ` Mathias Nyman
[not found] ` <CAMcR36KcP7cMZ2D1pu_bC-R0uPn2chd_1jEzp4FBBq-jZz=D3A@mail.gmail.com>
2026-11-20 7:12 ` [WARNING: UNSCANNABLE EXTRACTION FAILED]Re: " Mika Westerberg
2026-11-20 10:30 ` Michal Pecio
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox