CPU frequency stuck at low values after suspend/resume on firmware 3.06 #91
Description
Device Information
System Model or SKU
Please select one of the following
- 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 (Intel® Core™ Ultra Series 1)
- Framework Laptop 16 (AMD Ryzen™ 7040 Series)
BIOS VERSION
3.06
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: 2 x Kingston KF556S40-32
Storage: WD Black SN850X
Describe the bug
After upgrading to firmware version 3.06, the system exhibits CPU throttling following a suspend/resume cycle.
- The issue only occurs if the laptop remains suspended for a longer period. A quick suspend/resume does not trigger it.
- So far, it reliably reproduces when the laptop is connected to the PSU. I have not yet tested battery-only scenarios but will provide feedback in a follow-up comment.
- Once resumed, CPU frequencies remain limited between ~540 MHz and 1.1 GHz, resulting in a noticeable performance drop.
Additional observations:
- According to cpufreq sysfs, the configured min/max CPU speeds are 1.1 GHz and ~5.1 GHz respectively.
- Switching power profiles or adjusting the energy performance preference does not restore normal operation.
- Disconnecting and reconnecting the PSU immediately resolves the throttling.
I will collect and attach EC logs from ectool console in the comments for further analysis.
Steps To Reproduce
Steps to reproduce the behavior (Linux):
- Connect PSU.
- Suspend the system.
- Keep it suspended for a while (~1h)
- Resume the system and monitor CPU frequency on idle and load. None of it exceeds 1100Mhz, bottom remains around 540Mhz.
Expected behavior
Observing CPU frequencies above 4GHz under load.
Operating System (please complete the following information):
- OS/Distribution: Arch Linux
- Linux Kernel Version: 6.16.1
Additional context
Discussed on the Framework Community Forum: here