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 15:51:16 +0000 [thread overview]
Message-ID: <bug-221073-208809-beIsGj4pDN@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 #26 from David Hubbard (david.c.hubbard@gmail.com) ---
Created attachment 309532
--> https://bugzilla.kernel.org/attachment.cgi?id=309532&action=edit
comment25-cap03.tgz
Ok tried it again:
Cap3:
# free
total used free shared buff/cache
available
Mem: 32636916 3709384 27486748 37088 1822492
28927532
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 spacebar, get this in dmesg)
[ 183.231723] 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)
# cd /; find sys/kernel/debug/usb/xhci/0000\:c2\:00.4 -type f | while read a;
do echo "$a"; mkdir -p "/home/user/c/$(dirname "$a")"; cp "$a"
"/home/user/c/$a"; done
sys/kernel/debug/usb/xhci/0000:c2:00.4/port_bandwidth/FS_BW
cp: error reading
'sys/kernel/debug/usb/xhci/0000:c2:00.4/port_bandwidth/FS_BW': Cannot send
after transport endpoint shutdown
sys/kernel/debug/usb/xhci/0000:c2:00.4/port_bandwidth/HS_BW
cp: error reading
'sys/kernel/debug/usb/xhci/0000:c2:00.4/port_bandwidth/HS_BW': Cannot send
after transport endpoint shutdown
sys/kernel/debug/usb/xhci/0000:c2:00.4/port_bandwidth/SS_BW
cp: error reading
'sys/kernel/debug/usb/xhci/0000:c2:00.4/port_bandwidth/SS_BW': Cannot send
after transport endpoint shutdown
sys/kernel/debug/usb/xhci/0000:c2:00.4/ports/port01/portsc
sys/kernel/debug/usb/xhci/0000:c2:00.4/ports/port02/portsc
sys/kernel/debug/usb/xhci/0000:c2:00.4/event-ring/trbs
sys/kernel/debug/usb/xhci/0000:c2:00.4/event-ring/cycle
sys/kernel/debug/usb/xhci/0000:c2:00.4/event-ring/dequeue
sys/kernel/debug/usb/xhci/0000:c2:00.4/event-ring/enqueue
sys/kernel/debug/usb/xhci/0000:c2:00.4/command-ring/trbs
sys/kernel/debug/usb/xhci/0000:c2:00.4/command-ring/cycle
sys/kernel/debug/usb/xhci/0000:c2:00.4/command-ring/dequeue
sys/kernel/debug/usb/xhci/0000:c2:00.4/command-ring/enqueue
sys/kernel/debug/usb/xhci/0000:c2:00.4/reg-ext-dbc:00
sys/kernel/debug/usb/xhci/0000:c2:00.4/reg-ext-protocol:01
sys/kernel/debug/usb/xhci/0000:c2:00.4/reg-ext-protocol:00
sys/kernel/debug/usb/xhci/0000:c2:00.4/reg-ext-legsup:00
sys/kernel/debug/usb/xhci/0000:c2:00.4/reg-runtime
sys/kernel/debug/usb/xhci/0000:c2:00.4/reg-op
sys/kernel/debug/usb/xhci/0000:c2:00.4/reg-cap
# dmesg | gzip > dmesg03.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 15:51 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
2026-03-03 15:05 ` bugzilla-daemon
2026-03-03 15:47 ` bugzilla-daemon
2026-03-03 15:51 ` bugzilla-daemon [this message]
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-beIsGj4pDN@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