[Bug 221103] xhci_hcd: System lockup under CPU load during usbfs polling of USB devices on AMD platforms

[bugzilla-daemon@kernel.org]

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

Andrew Skalski (voltara@gmail.com) changed:

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

--- Comment #27 from Andrew Skalski (voltara@gmail.com) ---
I believe this same crash is affecting my system as well.

Motherboard: Asus Pro WS WRX90E-SAGE SE
CPU: AMD Ryzen Threadripper PRO 7985WX
Kernels I tried: 6.8, 7.0 (Ubuntu 24.04 LTS packages)

Like others have reported, the "adb" command tends to trigger the crash.  I
also experience intermittent crashes upon plugging in a USB device (either by
physically plugging in the cable, or by toggling the USB switch I use to share
keyboard/mouse between two systems.)  All ports seem to be affected: front
panel, rear panel, and also the ports on my Thunderbolt dock.

When the crash is a result of plugging in a device, it generates an MCE (cache
error, processor context corrupt, uncorrected.)

This loop alone is enough to cause a crash eventually.  My latest attempt ran
12000+ iterations before it crashed:

while sleep 0.01 < /dev/bus/usb/002/001; do echo -n .; done

So far, I have only tried a couple nodes in /dev/bus/usb, but these two both
led to a crash:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

I tested both kernel patches mentioned in this ticket (retry xhci_resume, and
the D3cold delay) but neither one resolved the crashes.  I tested both using
the Ubuntu 6.8 kernel package as a basis.  I was not able to successfully build
the 7.0 kernel package.

The usbcore.autosuspend=-1 parameter appears to solve both of the crashes.

I tried enabling xhci_hcd debug logging through netconsole, but so far I have
not been able to reproduce either crash with debug logging enabled.

In case it's helpful, here's one message I've seen in the "dmesg -W" output
(running via IPMI serial console) logged right at the moment of the crash:

xhci_hcd 0000:04:00.4: Refused to change power state from D0 to D3hot

Thanks for your work so far looking into this.

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

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