From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Phani Kumar <phanigudipally@gmail.com>
Cc: linux-usb@vger.kernel.org, mika.westerberg@linux.intel.com
Subject: 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
Date: Thu, 12 Nov 2026 16:55:25 +0200 [thread overview]
Message-ID: <78b30387-f71d-4e6d-b49c-aea1f8fbc98b@linux.intel.com> (raw)
In-Reply-To: <CAMcR36LCr0RFrHsLFPaPziPS=1CMbEnO3GcDk=3Oe33S8uZFpw@mail.gmail.com>
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
next prev parent reply other threads:[~2026-11-12 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[not found] ` <CAMcR36KcP7cMZ2D1pu_bC-R0uPn2chd_1jEzp4FBBq-jZz=D3A@mail.gmail.com>
2026-11-20 7:12 ` [WARNING: UNSCANNABLE EXTRACTION FAILED]Re: " Mika Westerberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=78b30387-f71d-4e6d-b49c-aea1f8fbc98b@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=phanigudipally@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox