Linux USB
 help / color / mirror / Atom feed
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: Thu, 08 Oct 2026 17:27:27 +0000	[thread overview]
Message-ID: <bug-221103-208809-VBci6fptDG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221103-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=221103

langosz@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |langosz@gmail.com

--- Comment #42 from langosz@gmail.com ---
New affected system: ASUS ProArt B850-CREATOR WIFI NEO + Ryzen 7 9700X — total
freeze from adb legacy USB backend polling, no Android device connected

I can confirm this bug on my system. Symptoms are identical to the ones
described here: complete freeze (keyboard dead including SysRq, mouse dead, no
SSH response, display frozen), only a hard reset recovers, and zero kernel logs
— no panic, no soft lockup message, nothing. I had kernel.softlockup_panic=1,
kernel.watchdog_thresh=5, and hung_task_panic=1 enabled with kdump installed
and verified working; the NMI watchdog stayed completely silent and no vmcore
was ever produced, so this is a hard halt below what the kernel can report.

System:

Motherboard: ASUS ProArt B850-CREATOR WIFI NEO (BIOS 1103, 2026-09-18; also
reproduced on BIOS 0239)
CPU: AMD Ryzen 7 9700X (Raphael/Mendocino iGPU driving the display)
GPU: 2× Radeon RX 9060 XT (Navi 44, headless compute via ROCm/llama.cpp)
RAM: 32 GB DDR5-6000 (EXPO enabled)
OS: Ubuntu 26.04.1 LTS, kernel 7.0.0-38-generic (also reproduced on 7.0.0-34
and 7.0.0-14)
Trigger: a resident adb server from android-tools-adb (platform-tools
34.0.5-debian, legacy NATIVE USB backend that polls /dev/bus/usb every second).
Important: no Android device was connected during any of the freezes — the adb
server was simply running in the background after I had used adb devices/adb
logcat, so polling of the root hubs alone was sufficient. The load condition
was sustained CPU/PCIe/memory load from local LLM inference (llama.cpp,
HIP/ROCm backend, both 9060 XTs active). Freezes happened randomly over several
days, always while that workload was running.

USB topology (matches the xHCI superspeed root hub pattern from comment #59):
three 1d6b:0003 Linux Foundation 3.0 root hubs (Bus 2/4/6) plus 2.0 hubs;
attached devices are an IMC Bluetooth radio, an ASUS AURA LED controller
(0b05:19af), a keyboard and a mouse — nothing unusual.

Ruled out on my side: BIOS update 0239 → 1103 (AGESA 1.3.0.1d) did not help;
kernel downgrade to 7.0.0-14 and upgrade to 7.0.0-38 did not help; disabling
EXPO (running at JEDEC speed) did not help — freezes continued, and I have
since re-enabled EXPO with the adb workaround in place and the system remains
stable, so memory speed is not a factor; temperatures normal (37–43 °C); no
MCE/EDAC errors, no PCIe AER errors ever logged.

Workaround: setting ADB_LIBUSB=1 system-wide (forces the libusb backend) — no
freezes for days since, with the same inference workload running, adb
available, and EXPO re-enabled.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2026-10-08 17:27 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
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 [this message]
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-VBci6fptDG@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