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

[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

[quinchou77]

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

[pjbuterbaugh]

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

[quinchou77]

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

[pjbuterbaugh]

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.

[pjbuterbaugh]

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.

[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.