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: Mon, 31 Aug 2026 15:51:46 +0000 [thread overview]
Message-ID: <bug-221103-208809-njhe3vydcw@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 #35 from Andrew Skalski (voltara@gmail.com) ---
(In reply to Michał Pecio from comment #34)
> Makes sense, I only suggested the alternative placement to confirm that this
> line is really the trigger and not merely a timing accident.
I went back and double-checked the effect of different mdelay/msleep
placements, and I no longer believe the xhci_read_64 call is involved. So I
will need to do more building & testing to find out what's really happening.
(Thankfully it will be much less time consuming now that I have my rebuild
streamlined.)
--
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-08-31 15:51 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 [this message]
2026-08-31 19:32 ` bugzilla-daemon
2026-09-01 1:56 ` bugzilla-daemon
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-njhe3vydcw@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.