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: Sun, 12 Jul 2026 16:02:56 +0000	[thread overview]
Message-ID: <bug-221073-208809-3ZcBkNpymG@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 #51 from David Hubbard (david.c.hubbard@gmail.com) ---
(In reply to Alexander F from comment #50)
> Unfortunately it still failed. First on the 2nd cycle, then on the 8th.

I also got a failure now, after more cycles of testing the patched kernel:

[ 1213.160470] ACPI: EC: interrupt blocked
[300397.315230] ACPI: EC: interrupt unblocked
[300398.002554] [drm] PCIE GART of 512M enabled (table at 0x0000008000900000).
[300398.002615] amdgpu 0000:c2:00.0: amdgpu: SMU is resuming...
[300398.008114] nvme nvme0: 32/0/0 default/read/poll queues
[300398.026094] amdgpu 0000:c2:00.0: amdgpu: SMU is resumed successfully!
[300398.053810] xhci_hcd 0000:c2:00.4: Port resume timed out, port 1-1:
0x400e03
[300398.104761] EDID block 1 (tag 0x80) checksum is invalid, remainder is 191
[300398.107810] amdgpu 0000:c2:00.0: [drm] detect_link_and_local_sink:
manufacturer_id = 6904, product_id = 26A4, serial_number = 21BB1,
manufacture_week = 26, manufacture_year = 19, display_name = ASUS VW266H,
speaker_flag = 0, audio_mode_count = 0
[300398.148104] [HW_LINK_TRAINING]:enable_link entered
[300398.148105] [HW_LINK_TRAINING]:link disabled
[300398.148106] [HW_LINK_TRAINING]:enable_link_hdmi entered
[300398.182298] amdgpu 0000:c2:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0
on hub 0
[300398.182305] amdgpu 0000:c2:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1
on hub 0
[300398.182306] amdgpu 0000:c2:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4
on hub 0
[300398.182307] amdgpu 0000:c2:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6
on hub 0
[300398.182308] amdgpu 0000:c2:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7
on hub 0
[300398.182309] amdgpu 0000:c2:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8
on hub 0
[300398.182309] amdgpu 0000:c2:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9
on hub 0
[300398.182310] amdgpu 0000:c2:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10
on hub 0
[300398.182311] amdgpu 0000:c2:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11
on hub 0
[300398.182312] amdgpu 0000:c2:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on
hub 0
[300398.182312] amdgpu 0000:c2:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng
0 on hub 8
[300398.182313] amdgpu 0000:c2:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng
1 on hub 8
[300398.182314] amdgpu 0000:c2:00.0: amdgpu: ring jpeg_dec_0 uses VM inv eng 4
on hub 8
[300398.182315] amdgpu 0000:c2:00.0: amdgpu: ring jpeg_dec_1 uses VM inv eng 6
on hub 8
[300398.182316] amdgpu 0000:c2:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng
13 on hub 0
[300398.182316] amdgpu 0000:c2:00.0: amdgpu: ring vpe uses VM inv eng 7 on hub
8
[300408.195596] xhci_hcd 0000:c2:00.4: xHCI host not responding to stop
endpoint command
[300408.211433] xhci_hcd 0000:c2:00.4: xHCI host controller not responding,
assume dead
[300408.211448] xhci_hcd 0000:c2:00.4: HC died; cleaning up
[300408.211785] usb 2-1: PM: dpm_run_callback(): usb_dev_resume returns -22
[300408.211810] usb 2-1: PM: failed to resume async: error -22
[300408.216609] OOM killer enabled.
[300408.216612] Restarting tasks: Starting
[300408.216696] usb 2-1.2: USB disconnect, device number 3
[300408.216712] usb 2-1: USB disconnect, device number 2
[300408.216760] usb 1-1: USB disconnect, device number 2
[300408.216768] usb 1-1.2: USB disconnect, device number 3
[300408.216771] usb 1-1.2.3: USB disconnect, device number 4
[300408.217523] Restarting tasks: Done
[300408.217569] random: crng reseeded on system resumption
[300408.217614] PM: suspend exit

-- 
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-07-12 16:02 UTC|newest]

Thread overview: 52+ 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 ` 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 [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-3ZcBkNpymG@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