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, 14 Jul 2026 13:50:00 +0000 [thread overview]
Message-ID: <bug-221073-208809-hfF5SDvRWE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221073-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221073
Mario Limonciello (AMD) (mario.limonciello@amd.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
Assignee|drivers_usb@kernel-bugs.ker |mario.limonciello@amd.com
|nel.org |
--- Comment #68 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
> v4 (attachment 310447 [details]) results on the Framework Desktop (AMD Ryzen
> AI Max 300, BIOS 03.05, xHCI 0000:c2:00.4): 146 clean s2idle cycles, zero
> controller deaths
>
OK - thanks for feedback guys. If this W/A patch is accepted upstream we'll
close this ticket based on it.
> If it ever fires again the panic trace will be preserved and I will attach
> it.
Let's please treat the full system hang as a separate issue and attach it to
it's own ticket.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2026-07-14 13:50 UTC|newest]
Thread overview: 70+ 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
2026-06-17 15:17 ` bugzilla-daemon
2026-06-17 15:50 ` Alan Stern
2026-06-17 15:50 ` bugzilla-daemon
2026-07-08 15:30 ` bugzilla-daemon
2026-07-09 4:46 ` bugzilla-daemon
2026-07-09 9:53 ` bugzilla-daemon
2026-07-09 11:57 ` bugzilla-daemon
2026-07-12 15:23 ` bugzilla-daemon
2026-07-12 16:02 ` bugzilla-daemon
2026-07-13 3:20 ` bugzilla-daemon
2026-07-13 6:00 ` bugzilla-daemon
2026-07-13 13:06 ` bugzilla-daemon
2026-07-13 13:08 ` bugzilla-daemon
2026-07-13 18:29 ` bugzilla-daemon
2026-07-13 19:14 ` bugzilla-daemon
2026-07-13 19:15 ` bugzilla-daemon
2026-07-13 19:56 ` bugzilla-daemon
2026-07-13 20:28 ` bugzilla-daemon
2026-07-13 20:30 ` bugzilla-daemon
2026-07-13 21:18 ` bugzilla-daemon
2026-07-13 21:52 ` bugzilla-daemon
2026-07-13 21:54 ` bugzilla-daemon
2026-07-13 22:12 ` bugzilla-daemon
2026-07-14 6:46 ` bugzilla-daemon
2026-07-14 13:04 ` bugzilla-daemon
2026-07-14 13:50 ` 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-hfF5SDvRWE@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.