From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220069] [6.13.9] regression USB controller dies
Date: Wed, 30 Apr 2025 09:42:36 +0000 [thread overview]
Message-ID: <bug-220069-208809-RmJ1n9dNK9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220069-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220069
--- Comment #6 from Claudio Wunder (cwunder@gnome.org) ---
> If "abort failed" is what starts everything, this looks like a genuine case
> of hardware going bad for some reason, unlike the February "hc died"
> regression which was a trivial driver bug and the HW worked as designed. This
> may be harder to solve and HW specific, possibly including connected devices.
Here's some sample logs with the correct times, apologies for not providing the
timestamps.
```
Apr 26 23:16:09 angel-thesis kernel: xhci_hcd 0000:6b:00.0: Event TRB for slot
18 ep 0 with no TDs queued
Apr 26 23:16:24 angel-thesis kernel: xhci_hcd 0000:6b:00.0: ERROR unknown event
type 4
Apr 26 23:16:24 angel-thesis kernel: xhci_hcd 0000:6b:00.0: Abort failed to
stop command ring: -110
Apr 26 23:16:24 angel-thesis kernel: xhci_hcd 0000:6b:00.0: xHCI host
controller not responding, assume dead
Apr 26 23:16:24 angel-thesis kernel: xhci_hcd 0000:6b:00.0: HC died; cleaning
up
Apr 26 23:16:24 angel-thesis kernel: xhci_hcd 0000:6b:00.0: Timeout while
waiting for setup device command
```
```
Apr 26 23:16:24 angel-thesis kernel: usb 7-2: USB disconnect, device number 2
Apr 26 23:16:24 angel-thesis kernel: usb 7-2.3: USB disconnect, device number 5
Apr 26 23:16:24 angel-thesis kernel: usb 7-2.3.1: USB disconnect, device number
10
Apr 26 23:16:24 angel-thesis kernel: usb 7-2.4: USB disconnect, device number 8
Apr 26 23:16:24 angel-thesis kernel: usb 7-2.5: USB disconnect, device number
13
Apr 26 23:16:24 angel-thesis kernel: usb 7-3: USB disconnect, device number 3
Apr 26 23:16:25 angel-thesis kernel: usb 7-3.1: USB disconnect, device number 7
Apr 26 23:16:25 angel-thesis kernel: usb 8-3: USB disconnect, device number 3
Apr 26 23:16:25 angel-thesis kernel: usb 8-3.4: USB disconnect, device number 5
Apr 26 23:16:25 angel-thesis kernel: usb 8-2: USB disconnect, device number 2
Apr 26 23:16:25 angel-thesis kernel: usb 8-5: USB disconnect, device number 4
Apr 26 23:16:25 angel-thesis kernel: usb 7-3.3: USB disconnect, device number
12
Apr 26 23:16:25 angel-thesis kernel: usb 7-3.4: USB disconnect, device number
14
Apr 26 23:16:25 angel-thesis kernel: usb 7-3.4.2: USB disconnect, device number
19
Apr 26 23:16:25 angel-thesis kernel: usb 7-3.5: USB disconnect, device number
15
Apr 26 23:16:25 angel-thesis kernel: usb 7-5: USB disconnect, device number 4
Apr 26 23:16:25 angel-thesis kernel: usb 7-5.2: USB disconnect, device number 9
Apr 26 23:16:25 angel-thesis kernel: usb 7-7: USB disconnect, device number 6
Apr 26 23:16:25 angel-thesis kernel: usb 7-11: USB disconnect, device number 11
```
```
Apr 28 18:54:12 angel-thesis kernel: xhci_hcd 0000:6a:00.0: Event TRB for slot
18 ep 0 with no TDs queued
Apr 28 18:54:28 angel-thesis kernel: xhci_hcd 0000:6a:00.0: ERROR unknown event
type 4
Apr 28 18:54:28 angel-thesis kernel: xhci_hcd 0000:6a:00.0: Abort failed to
stop command ring: -110
Apr 28 18:54:28 angel-thesis kernel: xhci_hcd 0000:6a:00.0: xHCI host
controller not responding, assume dead
Apr 28 18:54:28 angel-thesis kernel: xhci_hcd 0000:6a:00.0: HC died; cleaning
up
Apr 28 18:54:28 angel-thesis kernel: xhci_hcd 0000:6a:00.0: Timeout while
waiting for setup device command
```
```
Apr 28 18:51:25 angel-thesis kernel: usb 7-3.4.2: USB disconnect, device number
18
Apr 28 18:54:28 angel-thesis kernel: usb 7-2: USB disconnect, device number 2
Apr 28 18:54:28 angel-thesis kernel: usb 7-2.3: USB disconnect, device number 5
Apr 28 18:54:28 angel-thesis kernel: usb 7-2.3.1: USB disconnect, device number
10
Apr 28 18:54:28 angel-thesis kernel: usb 7-2.3.2: USB disconnect, device number
13
Apr 28 18:54:28 angel-thesis kernel: usb 7-2.5: USB disconnect, device number 8
Apr 28 18:54:28 angel-thesis kernel: usb 7-3: USB disconnect, device number 3
Apr 28 18:54:28 angel-thesis kernel: usb 7-3.1: USB disconnect, device number 7
Apr 28 18:54:28 angel-thesis kernel: usb 8-3: USB disconnect, device number 3
Apr 28 18:54:28 angel-thesis kernel: usb 8-3.4: USB disconnect, device number 5
Apr 28 18:54:28 angel-thesis kernel: usb 8-2: USB disconnect, device number 2
Apr 28 18:54:28 angel-thesis kernel: usb 8-5: USB disconnect, device number 4
Apr 28 18:54:28 angel-thesis kernel: usb 7-3.3: USB disconnect, device number
12
Apr 28 18:54:28 angel-thesis kernel: usb 7-3.4: USB disconnect, device number
14
Apr 28 18:54:28 angel-thesis kernel: usb 7-3.5: USB disconnect, device number
15
Apr 28 18:54:28 angel-thesis kernel: usb 7-5: USB disconnect, device number 4
Apr 28 18:54:28 angel-thesis kernel: usb 7-5.2: USB disconnect, device number 9
Apr 28 18:54:28 angel-thesis kernel: usb 7-7: USB disconnect, device number 6
Apr 28 18:54:28 angel-thesis kernel: usb 7-11: USB disconnect, device number 11
Apr 29 10:05:16 angel-thesis kernel: usb 5-1: USB disconnect, device number 2
```
> Actually, a regression could conceivably be caused by a change in some device
> driver. And distro regressions can also be caused by changes in kernel
> .config, so you may want to ask them about that too.
I'll reach out to Fedora's Discourse/Universal Blue Discourse.
> Well, at the very least, it would be nice to see complete and unmodified
> kernel log from the event you are complaining about ;) The snippet quoted
> above, for example, appears to be in reverse order and I don't know why.
> Timestamps can useful too.
Here's the full dmesg log via `journalctl -o short-precise -k -b -3`:
https://gist.github.com/ovflowd/0b0aa5c748683eca33909dc3ed7c66f7 (I shared on
GitHub Gist due to the large size, if you rather have me hosting it on a FOSS
alternative, let me know, I can upload it to gitlab.gnome.org)
> Going forward, does your system support dynamic debug and/or debugfs? Please
> try:
Let me check and circle back.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-04-30 9:42 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 14:28 [Bug 220069] New: [6.13.9] regression USB controller dies bugzilla-daemon
2025-04-29 20:07 ` [Bug 220069] " bugzilla-daemon
2025-04-29 20:43 ` bugzilla-daemon
2025-04-29 20:45 ` bugzilla-daemon
2025-04-30 5:57 ` bugzilla-daemon
2025-04-30 8:57 ` bugzilla-daemon
2025-04-30 9:42 ` bugzilla-daemon [this message]
2025-04-30 9:49 ` bugzilla-daemon
2025-04-30 9:53 ` bugzilla-daemon
2025-04-30 21:36 ` bugzilla-daemon
2025-04-30 22:36 ` bugzilla-daemon
2025-04-30 22:52 ` bugzilla-daemon
2025-05-01 7:29 ` bugzilla-daemon
2025-05-01 7:45 ` bugzilla-daemon
2025-05-01 9:48 ` bugzilla-daemon
2025-05-01 21:04 ` bugzilla-daemon
2025-05-01 21:43 ` bugzilla-daemon
2025-05-01 23:43 ` bugzilla-daemon
2025-05-02 0:07 ` bugzilla-daemon
2025-05-02 0:08 ` bugzilla-daemon
2025-05-02 9:28 ` bugzilla-daemon
2025-05-02 11:02 ` bugzilla-daemon
2025-05-02 11:03 ` bugzilla-daemon
2025-05-03 0:23 ` bugzilla-daemon
2025-05-03 8:08 ` bugzilla-daemon
2025-05-03 12:09 ` bugzilla-daemon
2025-05-03 12:10 ` bugzilla-daemon
2025-05-03 14:00 ` bugzilla-daemon
2025-05-03 17:49 ` bugzilla-daemon
2025-05-03 18:25 ` bugzilla-daemon
2025-05-03 19:09 ` bugzilla-daemon
2025-05-04 11:40 ` bugzilla-daemon
2025-05-04 12:41 ` bugzilla-daemon
2025-05-04 13:58 ` bugzilla-daemon
2025-05-04 14:17 ` bugzilla-daemon
2025-05-04 17:23 ` bugzilla-daemon
2025-05-05 8:49 ` bugzilla-daemon
2025-05-05 8:58 ` bugzilla-daemon
2025-05-05 9:13 ` bugzilla-daemon
2025-05-05 9:32 ` bugzilla-daemon
2025-05-05 9:40 ` bugzilla-daemon
2025-05-05 9:48 ` bugzilla-daemon
2025-05-05 10:53 ` bugzilla-daemon
2025-05-05 14:07 ` bugzilla-daemon
2025-05-05 21:22 ` bugzilla-daemon
2025-05-05 21:41 ` bugzilla-daemon
2025-05-07 23:02 ` bugzilla-daemon
2025-05-11 11:18 ` bugzilla-daemon
2025-05-11 12:49 ` bugzilla-daemon
2025-05-11 12:53 ` bugzilla-daemon
2025-05-11 12:58 ` bugzilla-daemon
2025-05-11 13:00 ` bugzilla-daemon
2025-05-15 10:05 ` bugzilla-daemon
2025-05-17 16:04 ` bugzilla-daemon
2025-05-18 23:37 ` bugzilla-daemon
2025-05-19 0:02 ` bugzilla-daemon
2025-05-19 0:13 ` bugzilla-daemon
2025-05-19 6:47 ` bugzilla-daemon
2025-05-19 12:08 ` bugzilla-daemon
2025-05-20 16:18 ` bugzilla-daemon
2025-05-20 16:22 ` bugzilla-daemon
2025-05-23 21:43 ` bugzilla-daemon
2025-05-23 21:44 ` bugzilla-daemon
2025-09-12 12:36 ` bugzilla-daemon
2025-09-12 20:41 ` bugzilla-daemon
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=bug-220069-208809-RmJ1n9dNK9@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.org \
/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