From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220936] ASMedia ASM4242 USB 3.2 xHCI Controller gives command timeout
Date: Tue, 25 Aug 2026 11:31:27 +0000 [thread overview]
Message-ID: <bug-220936-208809-DW0wIdH6Jf@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220936-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220936
--- Comment #8 from Michał Pecio (michal.pecio@gmail.com) ---
"Clearing Run/Stop failed" is same thing as "xHC CMD_RUN timeout", somebody
reworded the error message, that's all. The chip should stop operation within
16ms of clearing the Run/Stop bit, but it still hasn't after 64ms.
Passing quirks=0x20000 parameter to xhci_hcd increases the timeout further to
640ms, so you could try that.
The issue occurs during PCI auto PM attempt (shutting down the whole controller
when all USB devices are idle) if you are seeing the message in normal
operation. Does it also show up when suspending the system?
Can we know if there are successful suspend/resume cycles, or does it fail on
the first try every time? Enabling this will produce some debug info in dmesg:
echo 'func xhci_suspend +p' >/proc/dynamic_debug/control
echo 'func xhci_resume +p' >/proc/dynamic_debug/control
The cause may be some remaining bug in the chip's FW or possibly out of spec
behavior by the kernel. For one, USB subsystem is not particularly good at
stopping drivers from trying to communicate with suspended devices and some
particular drivers may have bugs like that. The issue would go away when the
offending device is disconnected.
Are you able to compile and test patches?
--
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-25 11:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2026-06-24 13:22 ` bugzilla-daemon
2026-08-24 19:18 ` bugzilla-daemon
2026-08-25 11:31 ` bugzilla-daemon [this message]
2026-08-27 0:18 ` 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-220936-208809-DW0wIdH6Jf@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