FW Desktop: rear usb-A not responding after suspend

[davidhubbard]

Device Information

Framework Desktop AI Ryzen Max 300

• BIOS version 03.03 cannot reproduce
• BIOS versoin 03.04 @ancoron reports the issue

@SebbeM reports: Framework Laptop 13 AMD Ryzen AI 300, BIOS version 03.05

System Model or SKU

Please select one of the following

• Framework Laptop 12 (13th Gen Intel® Core™)
• Framework Laptop 13 (11th Gen Intel® Core™)
• Framework Laptop 13 (12th Gen Intel® Core™)
• Framework Laptop 13 (13th Gen Intel® Core™)
• Framework Laptop 13 (AMD Ryzen™ 7040 Series)
• Framework Laptop 13 (AMD Ryzen™ AI 300 Series)
• Framework Laptop 13 (Intel® Core™ Ultra Series 1)
• Framework Laptop 16 (AMD Ryzen™ 7040 Series)
• Framework Laptop 16 (AMD Ryzen™ AI 300 Series)
• Framework Desktop (AMD Ryzen™ AI 300 PRO Series)

BIOS VERSION

Please provide the bios version.

$ sudo dmidecode --string bios-version
03.03

(@ancoron reports 03.04, @SebbeM reports 03.05)

DIY Edition information

If you are experiencing an issue on a DIY system, Please also fill out the memory and storage devices you are using.

Memory: 128GB edition
Storage: WD_BLACK SN7100 500GB

Port/Peripheral information

If you are experiencing an issue with a peripheral or an expansion card/port please fill out the following information:

• Peripheral vendor and name.

1. Acer 4-port hub https://www.amazon.com/gp/aw/d/B0CPSTG4N3
2. Lenovo usb keyboard
3. Lenovo usb mouse

• Port the Peripheral was connected to. Desktop - both of the rear usb-A ports are affected
• Device or expansion card attached to the Adjacent port to the port that is having the issue.

1. Nothing

For Desktop only

1. usb-c to usb-c expansion card (with nothing attached)
2. usb-c to usb-c expansion card (with nothing attached)

Describe the bug

xhci controller does not resume successfully.

This results in the keyboard and mouse being unusable.

Steps To Reproduce

Steps to reproduce the behavior:

1. systemctl suspend
2. Wait 20 minutes
3. Tap power button to resume
4. Attempt to log in with password, keyboard is unresponsive (@SebbeM reports this impacts his fingerprint sensor)

The kernel logs have:

kernel: xhci_hcd 0000:c2:00.4: xHCI host not responding to stop endpoint command
kernel: xhci_hcd 0000:c2:00.4: xHCI host controller not responding, assume dead
kernel: xhci_hcd 0000:c2:00.4: HC died; cleaning up
kernel: usb 2-1: PM: dpm_run_callback(): usb_dev_resume returns -22
kernel: usb 1-1: PM: dpm_run_callback(): usb_dev_resume returns -22
kernel: usb 2-1: PM: failed to resume async: error -22
kernel: usb 1-1: PM: failed to resume async: error -22

Expected behavior

xhci controller works after suspend

Fingerprint sensor works after suspend

Operating System (please complete the following information):

• OS/Distribution: Ubuntu 24.04.3
• Version: 24.04.3
• Linux Kernel Version: Linux 6.17.0-8-generic # 8-Ubuntu Fri Nov 14 21:44:46 UTC 2025 / also tried 6.18.7-061807-generic via mainline ppa

1. Note that I have installed the mt7925 patch via dkms, from: https://community.frame.work/t/kernel-panic-from-wifi-mediatek-mt7925-nullptr-dereference/79301

Additional context

I checked, this is not related to #116

This appears to be a separate issue only affecting only the rear usb-A ports. It may also be that a Framework Laptop 13 is affected (link).

I don't know if it affects my system yet. I am reporting this before I've run into the bug myself.

[ancoron]

For anyone coming across this issue, I've created a script that tries to detect this issue at resume and then rebinds the xHCI controller that is affected. This script currently only works for a single PCI device as I've not come across the case of any other device failing to resume:

/usr/lib/systemd/system-sleep/framework-desktop-quirks.sh

#!/usr/bin/env bash

time_check="$(date --iso-8601=seconds -d '-30 seconds')"

quirks_enabled="$(sed -n -E 's/^QUIRKS_ENABLED\s*=\s*(true|false).*/\1/p' /etc/default/framework-quirks 2>/dev/null)"
[ -n "${quirks_enabled}" ] || quirks_enabled="true"

log() {
  printf "[FrameworkDesktop] %s: %s\n" "$1" "$2"
}

if [ "${quirks_enabled}" != "true" ]; then
  log "config" "quirks disabled"
  exit 0
fi

device_path="$(sed -n -E 's/^DEVICE_PATH\s*=\s*(.+)/\1/p' /etc/default/framework-quirks 2>/dev/null)"
[ -n "${device_path}" ] || device_path="auto"


suspend() {
  log "suspend" "no action"
}

resume() {
  sleep 2
  local xhci_dead=""
  if [ "${device_path}" = "auto" ]; then
    xhci_dead="$(journalctl --output cat --no-pager -b -k --since "${time_check}" --grep 'xHCI host controller not responding' -n 1 | sed -n -E 's/^.*xhci_hcd\s+([0-9]{4}:[0-9a-f]{2}:[0-9a-f]{2}\.[0-9]):\s+xHCI host controller not responding.*$/\1/p')"
    [ -z "${xhci_dead}" ] || device_path="${xhci_dead}"
  else
    xhci_dead="$(journalctl --output cat --no-pager -b -k --since "${time_check}" --grep "${device_path}" -n 5 | grep -F 'xHCI host controller not responding')"
  fi

  if [ -n "${xhci_dead}" ]; then
    log "resume" "rebind xHCI (device: ${device_path})"
    echo -n "${device_path}" > /sys/bus/pci/drivers/xhci_hcd/unbind
    sleep 2
    echo -n "${device_path}" > /sys/bus/pci/drivers/xhci_hcd/bind
  else
    log "resume" "xHCI rebind not needed (device: ${device_path})"
  fi
}

case "$1" in
  pre)
    suspend "$2"
    ;;
  post)
    resume "$2"
    ;;
esac

Which will then print out lines like these:

2026-01-08T07:34:57+01:00 purgatori systemd-sleep[92866]: [FrameworkDesktop] resume: xHCI rebind not needed (device: auto)
2026-01-08T21:28:03+01:00 purgatori systemd-sleep[134000]: [FrameworkDesktop] resume: xHCI rebind not needed (device: auto)
2026-01-10T10:33:03+01:00 purgatori systemd-sleep[202408]: [FrameworkDesktop] resume: xHCI rebind not needed (device: auto)
2026-01-10T19:46:18+01:00 purgatori systemd-sleep[229446]: [FrameworkDesktop] resume: xHCI rebind not needed (device: auto)
2026-01-11T22:17:04+01:00 purgatori systemd-sleep[45554]: [FrameworkDesktop] resume: rebind xHCI (device: 0000:c3:00.4)
2026-01-12T08:02:17+01:00 purgatori systemd-sleep[46369]: [FrameworkDesktop] resume: rebind xHCI (device: 0000:c3:00.4)
2026-01-13T07:18:00+01:00 purgatori systemd-sleep[6868]: [FrameworkDesktop] resume: rebind xHCI (device: 0000:c3:00.4)
2026-01-13T22:53:35+01:00 purgatori systemd-sleep[7865]: [FrameworkDesktop] resume: rebind xHCI (device: 0000:c3:00.4)
2026-01-14T07:47:37+01:00 purgatori systemd-sleep[13253]: [FrameworkDesktop] resume: xHCI rebind not needed (device: auto)
2026-01-14T19:43:28+01:00 purgatori systemd-sleep[39515]: [FrameworkDesktop] resume: rebind xHCI (device: 0000:c3:00.4)
2026-01-15T09:00:10+01:00 purgatori systemd-sleep[62882]: [FrameworkDesktop] resume: rebind xHCI (device: 0000:c3:00.4)
2026-01-17T10:23:50+01:00 purgatori systemd-sleep[1829533]: [FrameworkDesktop] resume: rebind xHCI (device: 0000:c3:00.4)
2026-01-17T16:52:40+01:00 purgatori systemd-sleep[1852076]: [FrameworkDesktop] resume: xHCI rebind not needed (device: auto)
2026-01-18T10:50:22+01:00 purgatori systemd-sleep[1885684]: [FrameworkDesktop] resume: xHCI rebind not needed (device: auto)
2026-01-19T07:31:42+01:00 purgatori systemd-sleep[1922059]: [FrameworkDesktop] resume: rebind xHCI (device: 0000:c3:00.4)

The affected device is always:

c3:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Strix Halo USB 3.1 xHCI [1022:1587] (prog-if 30 [XHCI])
        Subsystem: Framework Computer Inc. Device [f111:000a]
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin D routed to IRQ 25
        Region 0: Memory at 90000000 (64-bit, non-prefetchable) [size=1M]
        Capabilities: [48] Vendor Specific Information: Len=08 <?>
        Capabilities: [50] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [64] Express (v2) Endpoint, IntMsgNum 0
                DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
                        ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 0W TEE-IO-
                DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
                        RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- NonFatalErr+ FatalErr- UnsupReq+ AuxPwr- TransPend-
                LnkCap: Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us
                        ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
                LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- FltModeDis-
                LnkSta: Speed 16GT/s, Width x16
                        TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR-
                         10BitTagComp+ 10BitTagReq- OBFF Not Supported, ExtFmt+ EETLPPrefix+, MaxEETLPPrefixes 1
                         EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
                         FRS- TPHComp- ExtTPHComp-
                         AtomicOpsCap: 32bit- 64bit- 128bitCAS-
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
                         AtomicOpsCtl: ReqEn-
                         IDOReq- IDOCompl- LTR- EmergencyPowerReductionReq-
                         10BitTagReq- OBFF Disabled, EETLPPrefixBlk-
                LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete- EqualizationPhase1-
                         EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
                         Retimer- 2Retimers- CrosslinkRes: unsupported, FltMode-
        Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Capabilities: [c0] MSI-X: Enable+ Count=1 Masked-
                Vector table: BAR=0 offset=000fe000
                PBA: BAR=0 offset=000ff000
        Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Capabilities: [2a0 v1] Access Control Services
                ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
                ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci

[davidhubbard]

@ancoron it would be really helpful to collect your system information. Perhaps in the diff between yours and mine, a clue would surface.

System Model or SKU

BIOS VERSION

Please provide the bios version.

$ sudo dmidecode --string bios-version

DIY Edition information

If you are experiencing an issue on a DIY system, Please also fill out the memory and storage devices you are using.

Port/Peripheral information

If you are experiencing an issue with a peripheral or an expansion card/port please fill out the following information:

• Peripheral vendor and name.

• Port the Peripheral was connected to. Desktop - both of the rear usb-A ports are affected

• Device or expansion card attached to the Adjacent port to the port that is having the issue.

Operating System (please complete the following information):

OS/Distribution:
Version:
Linux Kernel Version:

[ancoron]

Device Information

System Model or SKU

Please select one of the following

• Framework Laptop 12 (13th Gen Intel® Core™)
• Framework Laptop 13 (11th Gen Intel® Core™)
• Framework Laptop 13 (12th Gen Intel® Core™)
• Framework Laptop 13 (13th Gen Intel® Core™)
• Framework Laptop 13 (AMD Ryzen™ 7040 Series)
• Framework Laptop 13 (AMD Ryzen™ AI 300 Series)
• Framework Laptop 13 (Intel® Core™ Ultra Series 1)
• Framework Laptop 16 (AMD Ryzen™ 7040 Series)
• Framework Laptop 16 (AMD Ryzen™ AI 300 Series)
• Framework Desktop (AMD Ryzen™ AI 300 PRO Series)

Concretely:

Name	Value
CPU:	AMD RYZEN AI MAX+ 395 w/ Radeon 8060S
System Version:	A6
SKU:	FRAMDACP06
Mainboard SKU:	FRANMFCP06

BIOS VERSION

$ sudo dmidecode --string bios-version

03.04

DIY Edition information

Memory: 128 GiB (8x 16 GiB) Micron Technology (part number: MT62F4G32D8DV-023 WT)
Storage:

• Seagate FireCuda 530 2TB (system)
• WD Black SN850X 4TB (data)

Port/Peripheral information

If you are experiencing an issue with a peripheral or an expansion card/port please fill out the following information:

• Peripheral vendor and name: Dell UltraSharp U4924DW (acting as a hub; also connected via DisplayPort):
  • Logitech, Inc. G510 Gaming Keyboard (PCI-ID: 046d:c22d)
  • Evoluent Evoluent VerticalMouse D (PCI-ID: 1a7c:0197)
  • Logitech, Inc. C922 Pro Stream Webcam (PCI-ID: 046d:085c)
• Port the Peripheral was connected to: at least both USB3.2 Gen2x1 ports affected
• Device or expansion card attached to the Adjacent port to the port that is having the issue: not tried

Operating System (please complete the following information):

• OS/Distribution: Arch Linux
• Version: rolling
• Linux Kernel Version: Linux purgatori 6.18.5-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Sun, 11 Jan 2026 17:10:37 +0000 x86_64 GNU/Linux

[davidhubbard]

@ancoron I don't get the suspend issue on BIOS 03.03.

I saw 03.04 suffered from long delays on boot. Would it be reasonable for you to downgrade to 03.03 and retest?

[ancoron]

@davidhubbard I've never done such a downgrade. Can I also do that with fwupdmgr?

[davidhubbard]

Yeah it should be as simple as:

$ fwupdmgr downgrade
0.      Cancel
1.      f8571b257837e7537ea0508dc9793e90f594fdb2 (System Firmware)
2.      5bc922b7bd1adb5b6f99592611404036bd9f42d0 (UEFI CA)
3.      362301da643102b9f38477387e2193e57abaa590 (UEFI dbx)
Choose device [0-3]:

You would select 1 (System Firmware)

This is what I got on mine, of course you will see 0.0.3.4 here:

╔══════════════════════════════════════════════════════════════════════════════╗
║ Downgrade System Firmware from 0.0.3.3 to 0.0.3.2?                           ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ This stable release fixes the following issues:                              ║
║                                                                              ║
║ • Fixed EC power led still breathing after resuming from suspend.            ║
║ • Serial Console Redirection will not turn off anymore by itself.            ║
║                                                                              ║
║ Desktop (AMD Ryzen AI Max 300 Series) must remain plugged into a power       ║
║ source for the duration of the update to avoid damage.                       ║
╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]: n
Request canceled

[SebbeM]

I had this problem on my Laptop 13 but currently not bothered by it thanks to the script above. For me, the only device I have noticed being affected is the fingerprint reader, connected to an internal USB 2.0 port. System information provided below.

System Model or SKU

Framework Laptop 13 (AMD Ryzen™ AI 300 Series)

BIOS VERSION

03.05

DIY Edition information

Kingston 32GB DDR5 5600MHz Impact SODIMM
Samsung SSD 970 EVO Plus 500GB

Port/Peripheral information

Peripheral vendor and name.

Shenzhen Goodix Technology Co.,Ltd. Goodix Fingerprint USB Device

Port the Peripheral was connected to.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Operating System (please complete the following information):

OS/Distribution: Arch
Version: Updated
Linux Kernel Version: 6.18.5

[ancoron]

@davidhubbard Just downgraded to 3.0.3 and the first sleep after boot (mine were not slow with 3.0.4 / not faster now):

...
2026-01-20T08:01:57+01:00 purgatori kernel: amdgpu 0000:c3:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
2026-01-20T08:01:57+01:00 purgatori kernel: amdgpu 0000:c3:00.0: amdgpu: ring vpe uses VM inv eng 7 on hub 8
2026-01-20T08:01:57+01:00 purgatori kernel: xhci_hcd 0000:c3:00.4: xHCI host not responding to stop endpoint command
2026-01-20T08:01:57+01:00 purgatori kernel: xhci_hcd 0000:c3:00.4: xHCI host controller not responding, assume dead
2026-01-20T08:01:57+01:00 purgatori kernel: xhci_hcd 0000:c3:00.4: HC died; cleaning up
2026-01-20T08:01:57+01:00 purgatori kernel: usb 1-1: PM: dpm_run_callback(): usb_dev_resume returns -22
2026-01-20T08:01:57+01:00 purgatori kernel: usb 1-1: PM: failed to resume async: error -22
2026-01-20T08:01:57+01:00 purgatori kernel: usb 2-1: PM: dpm_run_callback(): usb_dev_resume returns -22
2026-01-20T08:01:57+01:00 purgatori kernel: usb 2-1: PM: failed to resume async: error -22
2026-01-20T08:01:57+01:00 purgatori kernel: OOM killer enabled.
2026-01-20T08:01:57+01:00 purgatori kernel: Restarting tasks: Starting
...

So at least on my box, it is not a BIOS regression.

[n-peugnet]

So at least on my box, it is not a BIOS regression.

In my case, Framework Desktop with bios 3.0.3, I only started to have this issue after upgrading the Linux Kernel from 6.17.x to 6.18.4.
See also: https://community.frame.work/t/wake-from-suspend/76109/42?u=nicolasp

But it might be biased as I was not using suspend that much due to the resume sometimes not working at all.

[davidhubbard]

@n-peugnet thanks for the brief comment. Please could you post all your system details?

For what it's worth, everyone who has reported the issue here has a 6.18.x kernel. And I don't see the issue on 6.17.x. But please, share your system details. :)

[ancoron]

OK, just tested with my Arch LTS kernel (6.12.66-1-lts), and:

2026-01-23T08:20:48+01:00 purgatori kernel: xhci_hcd 0000:c3:00.4: xHCI host not responding to stop endpoint command
2026-01-23T08:20:48+01:00 purgatori kernel: xhci_hcd 0000:c3:00.4: xHCI host controller not responding, assume dead
2026-01-23T08:20:48+01:00 purgatori kernel: xhci_hcd 0000:c3:00.4: HC died; cleaning up
2026-01-23T08:20:48+01:00 purgatori kernel: usb 2-1: PM: dpm_run_callback(): usb_dev_resume returns -22
2026-01-23T08:20:48+01:00 purgatori kernel: usb 1-1: PM: dpm_run_callback(): usb_dev_resume returns -22
2026-01-23T08:20:48+01:00 purgatori kernel: usb 2-1: PM: failed to resume async: error -22
2026-01-23T08:20:48+01:00 purgatori kernel: usb 1-1: PM: failed to resume async: error -22

So it's not a regression in the Linux kernel for me (unless the regression that leads to this was backported that far).

[davidhubbard]

I installed mainline and switched to Linux fwd 6.18.7-061807-generic #202601231045 SMP PREEMPT_DYNAMIC Fri Jan 23 11:25:00 UTC 2026 x86_64 GNU/Linux

Over the next few days I will know if it causes my Framework Desktop to fail after suspend. I did a little testing already and the issue is not present.

It's looking like it is not a regression in the Linux kernel.

[davidhubbard]

Ugh. I'll test for a few days, and it looks like the linux 6.17.7 kernel is the "golden version" for Framework Desktop (AMD Strix Halo).

Downgrading to Kernel 6.17.7, linux-firmware-amdgpu 20251111 makes ROCm and PyTorch work again.

As a bisect help, 6.17.7 works, but 6.17.9 was broken.

• [Issue]: Segmentation Fault after ROCM/Torch update [OS: Arch Linux running 6.18.4-arch1-1, Strix Halo] ROCm/TheRock#2850 (comment)