All of lore.kernel.org
 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: Sat, 14 Mar 2026 04:29:59 +0000	[thread overview]
Message-ID: <bug-221073-208809-TzAdgWqsvO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221073-208809@https.bugzilla.kernel.org/>

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

bugzilla@logical.ink changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugzilla@logical.ink

--- Comment #39 from bugzilla@logical.ink ---
Also experiencing this bug on Framework 13 AMD Ryzen AI 300 using Fedora. 

### System Information

| Field | Value |
|---|---|
| Machine | Framework Laptop 13 (AMD Ryzen AI 300 Series) |
| CPU | AMD Ryzen AI 9 HX 370 (Hawk Point, 24 threads) |
| GPU | AMD Radeon 890M (integrated) |
| BIOS | FRANMGCP09 v03.05 (2025-10-30) |
| RAM | 64 GB DDR5 |
| Kernel (at time of event) | 6.18.12-100.fc42.x86_64 |
| Kernel (current) | 6.18.16-100.fc42.x86_64 |
| Distribution | Fedora 42 |
| xHCI controller | 0000:c1:00.4 |
| xHCI hcc params | 0x0118ffc5 |
| xHCI version | 0x120 (USB 3.1) |
| xHCI quirks at init | 0x0000000200000010 |

The affected USB device is `usb 1-1`: a full-speed internal device (device
number 2, bus 1) which corresponds to the Framework laptop's internal input
device hub (trackpad, keyboard controller, fingerprint reader).

Relevant Logs:
**Failing resume (44-minute sleep, lid closed):**
```
Mar 13 22:40:43 kernel: usb 1-1: reset full-speed USB device number 2 using
xhci_hcd
Mar 13 22:40:43 kernel: PM: suspend entry (s2idle)

[~44 minutes elapse]

Mar 13 23:25:33 kernel: PM: suspend devices took 0.162 seconds
Mar 13 23:25:33 kernel: PM: resume devices took 0.285 seconds
Mar 13 23:25:33 systemd-logind: Lid opened.
Mar 13 23:25:33 kernel: PM: suspend exit
                                                          <-- usb 1-1 reset
ABSENT
Mar 13 23:26:13 kernel: PM: suspend entry (s2idle)        <-- next suspend,
still no usb 1-1 reset
Mar 13 23:26:18 kernel: PM: suspend exit
                                                          <-- usb 1-1 reset
still ABSENT
Mar 13 23:27:09 kernel: PM: suspend entry (s2idle)
Mar 13 23:28:56 kernel: PM: suspend exit
                                                          <-- usb 1-1 reset
still ABSENT
[reboot required to restore input]
```

**xHCI controller initialization (boot):**
```
kernel: xhci_hcd 0000:c1:00.4: xHCI Host Controller
kernel: xhci_hcd 0000:c1:00.4: new USB bus registered, assigned bus number 1
kernel: xhci_hcd 0000:c1:00.4: hcc params 0x0118ffc5 hci version 0x120 quirks
0x0000000200000010
```

Additional Context:
- The xHCI controller at `0000:c1:00.4` already has quirks `0x0000000200000010`
applied at init. The `XHCI_RESET_ON_RESUME` bit (0x80) is not present and may
need to be added to the AMD platform quirk table for this hardware.
- `bluetoothd` logs `Controller resume with wake event 0x0` on all resumes
including the failing one, indicating the Bluetooth/wakeup path is not the
differentiating factor.
- No kernel error or warning is emitted at the time of the failed USB reinit —
the failure is silent.

-- 
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-03-14  4:29 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
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 [this message]
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-TzAdgWqsvO@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.