From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221103] xhci_hcd: System lockup under CPU load during usbfs polling of USB devices on AMD platforms
Date: Tue, 01 Sep 2026 01:56:32 +0000 [thread overview]
Message-ID: <bug-221103-208809-Ng4q7tBjMS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221103-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221103
--- Comment #37 from Andrew Skalski (voltara@gmail.com) ---
(In reply to Lovekesh Solanki from comment #36)
> I have posted a patch series that addresses
> https://lore.kernel.org/linux-usb/07435e6b-ee30-4c85-8c8b-
> 0ce3a4ead1d9@leemhuis.info/
>
> It should fix your issue.
>
I applied your patch to the 7.0 kernel on Ubuntu 26.04, and here are the
results:
OK: I ran "adb" in the background for about two hours without any problems
BAD: The "sleep 0.1; cat /dev/bus/usb/002/001" loop still triggers the lockup
For the "colord" test, I used a patched 6.8 kernel and Ubuntu 24.04 due to
differences in colord behavior between versions (the 24.04 version opened the
device nodes O_RDONLY, but the 26.04 version only tried O_RDWR and failed due
to EACCES.)
OK(?): I tested plugging/unplugging devices for about 10 minutes while colord
was running, without issues.
OK(?): I repeated the colord plug/unplug test with adb running in the
background. No issues after 10-15 minutes of doing this.
While it doesn't prevent the lockup in all cases, it does improve things.
--
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:[~2026-09-01 1:56 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 14:52 [Bug 221103] New: xhci_hcd: System lockup under CPU load during rapid usbfs polling of SuperSpeed root hubs on AMD Ryzen platforms bugzilla-daemon
2026-02-20 7:30 ` [Bug 221103] xhci_hcd: System lockup under CPU load during usbfs polling of USB devices on AMD platforms bugzilla-daemon
2026-02-20 8:31 ` bugzilla-daemon
2026-02-20 9:17 ` Greg KH
2026-02-20 9:16 ` bugzilla-daemon
2026-02-20 9:17 ` bugzilla-daemon
2026-02-20 9:24 ` bugzilla-daemon
2026-02-20 9:26 ` bugzilla-daemon
2026-02-20 9:28 ` bugzilla-daemon
2026-02-20 9:40 ` bugzilla-daemon
2026-02-20 10:07 ` bugzilla-daemon
2026-02-20 10:17 ` Greg KH
2026-02-20 10:17 ` bugzilla-daemon
2026-02-20 10:21 ` bugzilla-daemon
2026-02-20 11:19 ` bugzilla-daemon
2026-02-20 14:07 ` bugzilla-daemon
2026-02-20 17:18 ` bugzilla-daemon
2026-02-21 1:12 ` bugzilla-daemon
2026-02-23 13:05 ` bugzilla-daemon
2026-02-23 17:52 ` bugzilla-daemon
2026-02-23 22:33 ` bugzilla-daemon
2026-02-24 7:45 ` bugzilla-daemon
2026-02-24 8:52 ` bugzilla-daemon
2026-02-24 10:19 ` bugzilla-daemon
2026-02-24 12:03 ` bugzilla-daemon
2026-02-24 12:21 ` bugzilla-daemon
2026-02-24 15:42 ` bugzilla-daemon
2026-03-08 17:56 ` bugzilla-daemon
2026-07-09 11:58 ` bugzilla-daemon
2026-08-28 3:49 ` bugzilla-daemon
2026-08-28 5:52 ` bugzilla-daemon
2026-08-28 12:19 ` bugzilla-daemon
2026-08-28 12:28 ` bugzilla-daemon
2026-08-30 1:50 ` bugzilla-daemon
2026-08-30 20:57 ` bugzilla-daemon
2026-08-30 21:51 ` bugzilla-daemon
2026-08-31 2:56 ` bugzilla-daemon
2026-08-31 15:51 ` bugzilla-daemon
2026-08-31 19:32 ` bugzilla-daemon
2026-09-01 1:56 ` bugzilla-daemon [this message]
2026-09-01 9:09 ` bugzilla-daemon
2026-09-01 9:41 ` bugzilla-daemon
2026-09-03 21:59 ` bugzilla-daemon
2026-09-03 22:12 ` bugzilla-daemon
2026-10-08 17:27 ` bugzilla-daemon
2026-10-08 19:51 ` 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-221103-208809-Ng4q7tBjMS@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.