* [Bug 220936] ASMedia ASM4242 USB 3.2 xHCI Controller gives command timeout
2026-01-04 1:42 [Bug 220936] New: ASMedia ASM4242 USB 3.2 xHCI Controller gives command timeout bugzilla-daemon
@ 2026-01-08 21:56 ` bugzilla-daemon
2026-03-09 16:20 ` bugzilla-daemon
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2026-01-08 21:56 UTC (permalink / raw)
To: linux-usb
https://bugzilla.kernel.org/show_bug.cgi?id=220936
--- Comment #1 from Stuart Hayhurst (stuart.a.hayhurst@gmail.com) ---
After the error is thrown the USB 4 ports attached completely stop working, and
don't recognise anything plugged in.
Before the error is thrown, it still seems very unhappy.
Mice and keyboards are basically non-functional. Both devices tested were
Logitech HID++ peripherals (G502 mouse, G915 TKL keyboard), and took ~10
seconds to be completely detected / initialised by hid-logitech-hidpp.
Afterwards, the keyboard is totally unresponsive, and the mouse position
updates every now and then. Normally, the HID++ part would be initialised
immediately after being interacted with, and be completely smooth.
USB storage devices (and NVMes over Thunderbolt) take a long time to open for
benchmarking, but afterwards their throughput is as expected.
The controller will also complain with errors in the format of `[ 293.922068]
xhci_hcd 0000:77:00.0: bad transfer trb length 13 in event trb` when a device
is plugged in, but the size seems to vary.
I tried looking for firmware updates, but MSI doesn't seem to have published
any. `fwupdmgr get-devices` reports the current version as `200011.240802`.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug 220936] ASMedia ASM4242 USB 3.2 xHCI Controller gives command timeout
2026-01-04 1:42 [Bug 220936] New: ASMedia ASM4242 USB 3.2 xHCI Controller gives command timeout bugzilla-daemon
2026-01-08 21:56 ` [Bug 220936] " bugzilla-daemon
@ 2026-03-09 16:20 ` bugzilla-daemon
2026-03-09 18:21 ` bugzilla-daemon
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2026-03-09 16:20 UTC (permalink / raw)
To: linux-usb
https://bugzilla.kernel.org/show_bug.cgi?id=220936
--- Comment #2 from Stuart Hayhurst (stuart.a.hayhurst@gmail.com) ---
I had another go at troubleshooting, disabling ASPM doesn't seem to help.
If I can get a device connected without the controller giving up, when I unplug
it I get:
```
[ 243.504068] xhci_hcd 0000:77:00.0: WARN Set TR Deq Ptr cmd failed due to
incorrect slot or ep state.
```
When I shut the computer down, if the controller hasn't already given up I see
the previously mentioned warning about command timeouts. Sometimes it throws it
when plugging a device in, but this isn't as reliable.
I tested it on Windows 11, and everything seems to work flawlessly.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug 220936] ASMedia ASM4242 USB 3.2 xHCI Controller gives command timeout
2026-01-04 1:42 [Bug 220936] New: ASMedia ASM4242 USB 3.2 xHCI Controller gives command timeout bugzilla-daemon
2026-01-08 21:56 ` [Bug 220936] " bugzilla-daemon
2026-03-09 16:20 ` bugzilla-daemon
@ 2026-03-09 18:21 ` bugzilla-daemon
2026-03-09 18:32 ` bugzilla-daemon
2026-03-09 18:59 ` bugzilla-daemon
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2026-03-09 18:21 UTC (permalink / raw)
To: linux-usb
https://bugzilla.kernel.org/show_bug.cgi?id=220936
Michał Pecio (michal.pecio@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michal.pecio@gmail.com
--- Comment #3 from Michał Pecio (michal.pecio@gmail.com) ---
That's some bizarre behavior. The CMD_RUN timeout on suspend probably occurs
due to runtime autosuspend, you can disable that with
echo on > /sys/bus/pci/devices/0000:77:00.0/power/control
I wonder if this would improve anything? If not, try also
echo 0000:77:00.0 > /sys/bus/pci/drivers/xhci_hcd/unbind
echo 0000:77:00.0 > /sys/bus/pci/drivers/xhci_hcd/bind
and maybe check if power/control stays 'on' and doesn't flip back to 'auto'.
If any overclocking is involved, try without it.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug 220936] ASMedia ASM4242 USB 3.2 xHCI Controller gives command timeout
2026-01-04 1:42 [Bug 220936] New: ASMedia ASM4242 USB 3.2 xHCI Controller gives command timeout bugzilla-daemon
` (2 preceding siblings ...)
2026-03-09 18:21 ` bugzilla-daemon
@ 2026-03-09 18:32 ` bugzilla-daemon
2026-03-09 18:59 ` bugzilla-daemon
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2026-03-09 18:32 UTC (permalink / raw)
To: linux-usb
https://bugzilla.kernel.org/show_bug.cgi?id=220936
--- Comment #4 from Stuart Hayhurst (stuart.a.hayhurst@gmail.com) ---
Thanks, disabling autosuspend seems to solve the CMD_RUN timeout, I can at
least connect and disconnect devices now (I only tested, maybe 10 unplugs and
replugs, but that far beats any previous attempt).
The device is still unbearably slow though, it still takes 10+ seconds to get
my mouse to finish connecting:
```
[ 8344.769964] usb 5-1.1: new full-speed USB device number 4 using xhci_hcd
[ 8345.029328] usb 5-1.1: New USB device found, idVendor=046d, idProduct=c539,
bcdDevice=39.06
[ 8345.029333] usb 5-1.1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 8345.029334] usb 5-1.1: Product: USB Receiver
[ 8345.029335] usb 5-1.1: Manufacturer: Logitech
[ 8345.049306] logitech-djreceiver 0003:046D:C539.000C: hidraw0: USB HID v1.11
Keyboard [Logitech USB Receiver] on usb-0000:77:00.0-1.1/input0
[ 8345.104692] logitech-djreceiver 0003:046D:C539.000D: hiddev0,hidraw1: USB
HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:77:00.0-1.1/input1
[ 8345.160297] logitech-djreceiver 0003:046D:C539.000E: hiddev1,hidraw2: USB
HID v1.11 Device [Logitech USB Receiver] on usb-0000:77:00.0-1.1/input2
[ 8347.111395] logitech-djreceiver 0003:046D:C539.000E: device of type eQUAD
Lightspeed 1 (0x0c) connected on slot 1
[ 8347.127481] input: Logitech G502 as
/devices/pci0000:00/0000:00:02.2/0000:15:00.0/0000:16:02.0/0000:77:00.0/usb5/5-1/5-1.1/5-1.1:1.2/0003:046D:C539.000E/0003:046D:407F.000F/input/input31
[ 8347.205902] logitech-hidpp-device 0003:046D:407F.000F: input,hidraw4: USB
HID v1.11 Keyboard [Logitech G502] on usb-0000:77:00.0-1.1/input2:1
[ 8357.290785] logitech-hidpp-device 0003:046D:407F.000F: HID++ 4.2 device
connected.
```
Unbind and rebind didn't improve anything.
I believe I've had this problem with 2 different CPUs (both R7 7700Xs, but the
first one had a useless memory controller). It's undervolted, so I'll give it a
try without that.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug 220936] ASMedia ASM4242 USB 3.2 xHCI Controller gives command timeout
2026-01-04 1:42 [Bug 220936] New: ASMedia ASM4242 USB 3.2 xHCI Controller gives command timeout bugzilla-daemon
` (3 preceding siblings ...)
2026-03-09 18:32 ` bugzilla-daemon
@ 2026-03-09 18:59 ` bugzilla-daemon
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2026-03-09 18:59 UTC (permalink / raw)
To: linux-usb
https://bugzilla.kernel.org/show_bug.cgi?id=220936
--- Comment #5 from Stuart Hayhurst (stuart.a.hayhurst@gmail.com) ---
Dropping the undervolt didn't have any effect, but it might actually be the
that it doesn't like Logitech wireless peripherals connected through USB
hubs...
Connecting my mouse dongle to it via an adapter is fine.
Connecting an NVMe via an enclosure is fine.
Connecting a USB stick via an adapter is fine.
Connecting a USB stick via a USB hub is fine.
Connecting my mouse or keyboard dongle to it via a USB hub is extremely slow.
Connecting my headset dongle to it via a USB hub is fine.
Last time I tested this I tried 2 different USB hubs to make sure it wasn't the
hub acting up, and the hubs both work fine on ports connected to a different
controller. Unfortunately I only have 1 USB hub with me to test with at the
moment, so I can't reconfirm that.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread