Linux USB
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221073] xHCI host controller dies on resume from s2idle on AMD Strix Halo [1022:1587]
Date: Tue, 19 May 2026 09:14:27 +0000	[thread overview]
Message-ID: <bug-221073-208809-Tr6gg0LyLH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221073-208809@https.bugzilla.kernel.org/>

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

jase_harley@protonmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jase_harley@protonmail.com

--- Comment #43 from jase_harley@protonmail.com ---
I can reproduce a very similar issue on a Lenovo ThinkPad T14 Gen 6 AMD / Ryzen
AI 7 PRO 350.

I do not currently have access to the device, so this is from notes/memory
rather than freshly collected logs.

Hardware:
- Lenovo ThinkPad T14 Gen 6 AMD
- CPU: AMD Ryzen AI 7 PRO 350
- BIOS: 1.13
- Internal camera: Chicony USB camera 04f2:b840

Distributions/kernels where observed:
- Ubuntu 24.04 LTS
- Ubuntu 26.04
- Fedora 43
- Fedora 44
- Kernel range observed: approximately 6.17.0 through 7.0.8

Symptoms:
- Internal Chicony USB camera 04f2:b840 disappears after suspend/resume.
- /dev/video* disappears when the failure occurs.
- Logs have shown USB resume failure / PM resume errors.
- The visible symptom is the webcam disappearing, but the failure appears to be
at the AMD xHCI / USB controller layer rather than a camera-specific issue.
- The machine has also had hard freezes/lockups around power-management events.

Workaround observations:
- Unbind/rebind of the affected xHCI controller can restore the camera.
- Forcing the AMD USB/xHCI PCI controllers to power/control=on before suspend
appears to have prevented the hard freezes so far.
- However, power/control=on has not fully prevented the internal webcam from
disappearing after resume.

Affected controllers seen on this machine include:
- 0000:c4:00.4
- 0000:c6:00.0
- 0000:c6:00.3
- 0000:c6:00.4

This may suggest two related behaviours:
1. runtime PM / autosuspend seems involved in the more severe freeze/lockup
behaviour;
2. the remaining webcam disappearance may still match this bug’s suspected xHCI
resume / interrupt / MSI-X issue.

I have not yet tested xhci_hcd.quirks=0x40. I can provide logs and test
xhci_hcd.quirks=0x40 if that would help.

-- 
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-05-19  9:14 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 17:46 [Bug 221073] New: xHCI host controller dies on resume from s2idle on AMD Strix Halo [1022:1587] bugzilla-daemon
2026-02-10 18:04 ` [Bug 221073] " bugzilla-daemon
2026-02-11  6:54 ` bugzilla-daemon
2026-02-11 23:04 ` bugzilla-daemon
2026-02-12  8:27 ` bugzilla-daemon
2026-02-12 10:02 ` bugzilla-daemon
2026-02-12 16:15 ` bugzilla-daemon
2026-02-25 11:10 ` bugzilla-daemon
2026-02-26  8:48 ` bugzilla-daemon
2026-02-26  8:50 ` bugzilla-daemon
2026-02-26  9:30 ` bugzilla-daemon
2026-02-26  9:37 ` bugzilla-daemon
2026-02-26 12:16 ` bugzilla-daemon
2026-02-26 12:18 ` bugzilla-daemon
2026-02-26 22:51 ` bugzilla-daemon
2026-02-27 14:04 ` bugzilla-daemon
2026-03-02 16:45 ` bugzilla-daemon
2026-03-02 18:08 ` bugzilla-daemon
2026-03-02 18:14 ` bugzilla-daemon
2026-03-02 19:05 ` bugzilla-daemon
2026-03-03 14:54 ` bugzilla-daemon
2026-03-03 14:55 ` bugzilla-daemon
2026-03-03 14:55 ` bugzilla-daemon
2026-03-03 14:56 ` bugzilla-daemon
2026-03-03 15:05 ` bugzilla-daemon
2026-03-03 15:47 ` bugzilla-daemon
2026-03-03 15:51 ` bugzilla-daemon
2026-03-03 16:59 ` bugzilla-daemon
2026-03-03 17:05 ` bugzilla-daemon
2026-03-03 22:57 ` bugzilla-daemon
2026-03-04  0:20 ` bugzilla-daemon
2026-03-04  9:15 ` bugzilla-daemon
2026-03-06 11:11 ` bugzilla-daemon
2026-03-06 11:40 ` bugzilla-daemon
2026-03-09 10:31 ` bugzilla-daemon
2026-03-11 22:09 ` bugzilla-daemon
2026-03-12  0:04 ` bugzilla-daemon
2026-03-12  6:49 ` bugzilla-daemon
2026-03-12 10:35 ` bugzilla-daemon
2026-03-14  4:29 ` bugzilla-daemon
2026-03-16  0:39 ` bugzilla-daemon
2026-03-17  0:03 ` bugzilla-daemon
2026-03-18 23:18 ` bugzilla-daemon
2026-05-19  9:14 ` bugzilla-daemon [this message]

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-221073-208809-Tr6gg0LyLH@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