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, 03 Mar 2026 14:56:07 +0000 [thread overview]
Message-ID: <bug-221073-208809-m3m2f5fRG1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221073-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221073
--- Comment #23 from David Hubbard (david.c.hubbard@gmail.com) ---
Created attachment 309526
--> https://bugzilla.kernel.org/attachment.cgi?id=309526&action=edit
comment16-dmesg02.gz
I'm fascinated with diagnosing the xHC USBSTS with the EINT bit set, using the
instructions in comment #5. I'm zeroing in on that. Maybe the issues with
resume taking 10 seconds in comment #19 can be considered separately in a
different bug?
My kernel has hand-applied patches I backported from
https://github.com/mkopec/linux/tree/hdmi_frl to 6.17.7 (ROCm 6.4 is still 10%
faster than newer ROCm versions). I also applied the Mediatek driver patches in
https://zbowling.github.io/mt7925/.
Anyway, I took a few interesting captures:
Cap1: used power button to resume. Can anyone else confirm this is a
workaround? The bug did not appear for this attempt.
* For some reason, debugfs files were all 0 in size?
Cap2: used space bar on keyboard to resume. Bug appeared.
* For some reason, debugfs files were all 0 in size?
# free
total used free shared buff/cache
available
Mem: 32636908 4008008 27282920 35664 1764500
28628900
Swap: 0 0 0
# (this shows 32GB free because the BIOS setting is iGPU = custom, iGPU memory
= 96GB)
# echo "module xhci_hcd +p" >/proc/dynamic_debug/control
# systemctl suspend
# (wait 2 minutes, press power button to resume, no bug)
# tar czf cap01.tgz /sys/kernel/debug/usb/xhci/0000\:c2\:00.4
# dmesg | gzip > dmesg01.gz
# systelctl shutdown
# (press power button, wait for system to boot)
# echo "module xhci_hcd +p" >/proc/dynamic_debug/control
# systemctl suspend
# (wait 2 minutes, press spacebar, get this in dmesg)
[ 243.002269] xhci_hcd 0000:c2:00.4: xHCI host controller not responding,
assume dead
# (unplug usb hub from c2:00.4 and plug it into c4:00.0, keyboard and mouse
alive again)
# tar czf cap02.tgz /sys/kernel/debug/usb/xhci/0000\:c2\:00.4
# dmesg | gzip > dmesg02.gz
--
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-03-03 14:56 UTC|newest]
Thread overview: 43+ 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 [this message]
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
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-m3m2f5fRG1@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.