Skip to content

FW16: Ports 1, 2 do not work after wake from suspend #174

Open

Description

@pjbuterbaugh

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)

BIOS VERSION

4.03

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: Crucial 32GB (2x 16GB) DDR5-5600 CT2K16G56C46S5
Storage: Crucial P3 Plus 2TB CT2000P3PSSD8

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. Please see the following for port numbering: Laptop 16 or Laptop 13 or Desktop
  • Device or expansion card attached to the Adjacent port to the port that is having the issue.
  1. USB-C Translucent Black
  2. USB-A
  3. HDMI
  4. USB-C Translucent Black
  5. USB-A
  6. Full-size SD

Standalone Operation (Laptop Only)

Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS?

  • Yes
  • No

Describe the bug

Ports 1 and 2 are completely disabled after waking from sleep. Cannot charge using standard 180W Framework adapter and stock cable, and devices plugged in (mice, phones, etc.) are not detected by the OS and the relevant log out does not appear in journalctl . All other ports appear to work.

When powered off completely, the ports will allow charging. However, after turning on, unplugging and plugging back in the charger to the same port, it will stop working again. Turning it on and then plugging it in, regardless of if it was plugged in before, also does not work.

Going into the BIOS, selecting "disconnect battery", hitting save/exit and then plugging in AC adapter appear to fix this issue temporarily (unknown amount of days).

Steps To Reproduce

  1. Place laptop in suspend
  2. Wake from sleep/suspend
  3. Attempt to charge/use (data or power) relevant ports

Expected behavior

I am able to charge, transfer data, or otherwise use the ports as normal.

Screenshots

If applicable, add screenshots to help explain your problem.

Video

Operating System (please complete the following information):

  • OS/Distribution: NixOS KDE
  • Version: 25.11
  • Linux Kernel Version: 6.18.6

Additional context

System is configured with a Gen 1 RX7700S dGPU.

Attempting to charge on ports 1 and 2 while this condition occurs leads to no change on ectool -interface dev console (i.e., EC does not appear to register that a power source is connected).

No change when plugging in directly into the USB-C ports on the chassis.

configuration.nix

Activity

  1. changed the title [-]Computer Issue[/-] [+]FW16: Ports 1, 2 do not work after wake from suspend[/+] on Feb 2, 2026
  2. quinchou77 commented on Feb 2, 2026

    @quinchou77

    @pjbuterbaugh Could you share the password of the video for me? I cannot watch the video.

  3. self-assigned this
    on Feb 2, 2026
  4. pjbuterbaugh commented on Feb 2, 2026

    @pjbuterbaugh
    Author

    @quinchou77 Apologies, a typo in the link prevented access. Please try again.

  5. quinchou77 commented on Feb 2, 2026

    @quinchou77

    Looks like it only fails on port 1 and port2. Did they work with previous BIOS version?

  6. added theissue type on Feb 2, 2026
  7. pjbuterbaugh commented on Feb 2, 2026

    @pjbuterbaugh
    Author

    Unsure. And, this issue has happened before with port 4. I did not test any other ports on the system (other than port 1, which did work at the time) for functionality at the time. A mistake...

    Again, going into the BIOS and initiating a battery disconnect temporarily resolved this issue.

  8. pjbuterbaugh commented on Feb 2, 2026

    @pjbuterbaugh
    Author

    If this issue occurs again I will post here once more. Do advise on how I can gather information should that happen - nothing obvious popped up in the kernel logs.

  9. quinchou77 commented on Feb 2, 2026

    @quinchou77

    Regarding Port 4, we have received user feedback describing similar issues on both Ports 1 and 4 following the 4.02/4.03 update. The PD engineers are currently debugging this, as the 4.02 release included some changes of the PD firmware.
    We are trying to root cause it, then have solution to fix them. I think you may encounter the similar issue.

  10. pjbuterbaugh commented on Feb 11, 2026

    @pjbuterbaugh
    Author

    Issue has reappeared again with port 4. If there's any information I can send forward to help, please let me know.

  11. DataHearth commented on Jun 17, 2026

    @DataHearth

    Same thing happened here. BIOS version: 4.03. The battery disconnect worked. Ports went back online after the first boot. Data and power were out on ports 1/2 on the left side. Right side was OK

  12. pjbuterbaugh commented on Jun 22, 2026

    @pjbuterbaugh
    Author

    Issue still persists. Any further progress?

  13. p-reclaw commented on Sep 28, 2026

    @p-reclaw

    Hardware / software

    • Framework Laptop 16, AMD Ryzen 7040 series, NVIDIA RTX 5070 graphics module
    • BIOS 04.05 (latest per fwupdmgr and Framework release notes)
    • Ubuntu 24.04. Reproduced on kernels 6.17.0-40-generic and 7.0.0-34-generic

    Summary
    The internal Genesys Logic USB3.2 hub (05e3:0625) sits behind the xHCI controller at 0000:c3:00.3 and shows up as usb 2-2, or usb 4-2 on some boots. The kernel reports it as fixed internal hardware: removable: fixed, physical_location: panel=left, dock=no. With nothing plugged in downstream, it is runtime-autosuspended almost immediately (power/control=auto, autosuspend_delay_ms=0, runtime_status=suspended).

    Every so often, resuming it fails. The controller retries every ~5 s and the whole system hard-freezes about 20 s later:

    xhci_hcd 0000:c3:00.3: Timeout while waiting for setup device command
    usb 2-2: device not accepting address 2, error -62
    xhci_hcd 0000:c3:00.3: Timeout while waiting for setup device command
    ... repeats every ~5 s until the machine locks up

    No disconnect event comes before the timeouts. This is a failed resume, not a real unplug. When it freezes, the journal stops mid-stream and any playing audio loops its last buffer indefinitely, so this is a genuine kernel-level lockup. A manual power-off is required.

    What it is not

    • Not the GPU driver. Reproduces with amdgpu blacklisted (Module amdgpu is blacklisted confirmed in the log) and the NVIDIA dGPU driving all displays.
    • Not an external device. Reproduces with no dock, monitors or KVM attached. Unplugging expansion cards does not remove the hub.
    • Not a physical link or thermal fault. No PCIe AER errors (DevSta: CorrErr- NonFatalErr- FatalErr-), no MCE, no NVIDIA Xid errors, temperatures normal.
    • Not USB3 LPM. The kernel already disables it on this host: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.

    Related symptom: USB-C dead after suspend
    USB-C ports sometimes didn't work after resume from suspend. Setting power/wakeup=disabled on 0000:c3:00.3 and 0000:c3:00.4 fixed that; a suspend/resume test afterwards came back clean. It did not stop the runtime freezes, and a hang with the same signature happened later in the same session.

    Workaround (applied, being monitored)
    Keep the hub from autosuspending:

    udev rule

    ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="05e3", ATTR{idProduct}=="0625", TEST=="power/control", ATTR{power/control}="on"

    plus globally, on the kernel cmdline

    usbcore.autosuspend=-1
    Both confirmed active: the hub reads control=on, runtime_status=active. These were only just applied, so it isn't yet confirmed that they stop the freezes long-term. I'll update the issue.

    Secondary observations (possibly downstream of the same fault)

    • Earlier hangs with amdgpu loaded ended in a hung_task panic (captured via pstore) with an amdgpu display commit_work worker blocked in dma_fence_wait_timeout, preceded by repeated nvidia-drm ... atomic driver check failed: -22. NVIDIA driver 610.57.04 made this much more frequent than 595.91.07.
    • Enabling kdump (kexec_load at boot) made hangs happen within a minute of every login.
    • With a Lenovo ThinkPad TB3 dock, one Thunderbolt port repeatedly dropped the dock (retimer disconnected / device disconnected) while the other port was stable.
    • pstore stopped capturing panics for a while because EFI NVRAM was 100% full, mostly with Secure Boot db/dbx/KEK/PK data. It later freed up.
  14. quinchou77 commented on Nov 11, 2026

    @quinchou77

    Please refer to the issue#255.
    This issue USB Port 5 Lost on Framework Laptop 16 AMD Ryzen™ 7040 Series. be the similar issue. The issue may happens on port 1, 2, 4, 5.
    We have identified the root cause of the issue; however, due to hardware design constraints, we are implementing a firmware workaround to address it. We are targeting this fix for the 4.06 release, scheduled for mid-December.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions