From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220069] New: [6.13.9] regression USB controller dies
Date: Tue, 29 Apr 2025 14:28:08 +0000 [thread overview]
Message-ID: <bug-220069-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220069
Bug ID: 220069
Summary: [6.13.9] regression USB controller dies
Product: Drivers
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: cwunder@gnome.org
Regression: No
This seems, at least to me, a regression after the apparent fix on 6.13.7; I've
tested on 6.13.9 and 6.14.3, and 6.13.7 seems to be working fine to me.
At random times (whether idle or with actual active usage), there is a high
chance that any of the xHCI controllers will fail.
```
Apr 28 6:54:28 PM kernel: usb 7-11: USB disconnect, device number 11
Apr 28 6:54:28 PM kernel: usb 7-7: USB disconnect, device number 6
Apr 28 6:54:28 PM kernel: usb 7-5.2: USB disconnect, device number 9
Apr 28 6:54:28 PM kernel: usb 7-5: USB disconnect, device number 4
Apr 28 6:54:28 PM kernel: usb 7-3.5: USB disconnect, device number 15
Apr 28 6:54:28 PM kernel: usb 7-3.4: USB disconnect, device number 14
Apr 28 6:54:28 PM kernel: usb 7-3.3: USB disconnect, device number 12
Apr 28 6:54:28 PM kernel: usb 8-5: USB disconnect, device number 4
Apr 28 6:54:28 PM kernel: usb 8-2: USB disconnect, device number 2
Apr 28 6:54:28 PM kernel: usb 8-3.4: USB disconnect, device number 5
Apr 28 6:54:28 PM kernel: usb 8-3: USB disconnect, device number 3
Apr 28 6:54:28 PM kernel: usb 7-3.1: USB disconnect, device number 7
Apr 28 6:54:28 PM kernel: usb 7-3: USB disconnect, device number 3
Apr 28 6:54:28 PM kernel: usb 7-2.5: USB disconnect, device number 8
Apr 28 6:54:28 PM kernel: usb 7-2.3.2: USB disconnect, device number 13
Apr 28 6:54:28 PM kernel: usb 7-2.3.1: USB disconnect, device number 10
Apr 28 6:54:28 PM kernel: usb 7-2.3: USB disconnect, device number 5
Apr 28 6:54:28 PM kernel: usb 7-2: USB disconnect, device number 2
Apr 28 6:51:25 PM kernel: usb 7-3.4.2: USB disconnect, device number 18
Apr 28 11:23:44 AM kernel: usb 7-3.4.2: USB disconnect, device number 17
Apr 27 1:06:10 AM kernel: usb 7-3.4.2: USB disconnect, device number 16
```
Running (replace `??` for the actual guid)
```
echo -n "0000:??:00.0" | sudo tee /sys/bus/pci/drivers/xhci_hcd/unbind && echo
-n "0000:??:00.0" | sudo tee /sys/bus/pci/drivers/xhci_hcd/bind
```
Reinitialises the controller.
----
uname:
```
6.13.9-103.bazzite.fc42.x86_64
```
rpm-ostree:
```
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
Digest:
sha256:1a7ae28b95fde42b976cc9aa159219c0aaaa0611f7416f4b3b30284e292b0875
Version: 42.20250417 (2025-04-17T07:35:37Z)
LayeredPackages: android-tools
LocalPackages: 1password-8.10.70-1.x86_64
sublime-text-4192-1.x86_64
```
--
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 reply other threads:[~2025-04-29 14:28 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 14:28 bugzilla-daemon [this message]
2025-04-29 20:07 ` [Bug 220069] [6.13.9] regression USB controller dies 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
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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.