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: Mon, 26 Oct 2026 06:13:23 +0000 [thread overview]
Message-ID: <bug-220936-208809-ezYKbhR32B@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220936-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220936
Jiayi Li (jiayi_dec@163.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jiayi_dec@163.com
--- Comment #11 from Jiayi Li (jiayi_dec@163.com) ---
Hi,
> ```
> [ 160.064098] xhci_hcd 0000:77:00.0: WARN: xHC CMD_RUN timeout
> [ 160.064117] xhci_hcd 0000:77:00.0: PM: suspend_common(): xhci_pci_suspend
> [xhci_pci] returns -110
> [ 160.064124] xhci_hcd 0000:77:00.0: can't suspend (hcd_pci_runtime_suspend
> [usbcore] returned -110)
> ```
>
I encountered the same error on the same controller model, and enabling
XHCI_SUSPEND_DELAY resolved it for me. You could try xhci_hcd.quirks=0x40000000
as well.
--
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-10-26 6:13 UTC|newest]
Thread overview: 13+ 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
2026-08-27 0:18 ` bugzilla-daemon
2026-08-30 11:05 ` bugzilla-daemon
2026-10-26 6:13 ` bugzilla-daemon [this message]
2026-10-26 18:53 ` 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-ezYKbhR32B@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