@cowpod Two adjustments you can make on Throttlestop that potentially could be a temporary fix until framework comes with a bios fix… The problem seems to be when it throttles to some critical temperature, it goes to 400 mhz and doesn’t know how to come back up again.
You could maybe use throttlestop to decrease the temperature at which it throttles 2-3C so it never gets too hot, though if the bug could happen anytime it throttles, this might cause the bug to happen more frequently.
Another potential solution may be to lower the turbo ratios down incrementally to decrease the spiky nature of turbo and or set PL1 and PL2 time to infinity and cap the TDP value to a wattage that it will never reach a thermal limit and start throttling. You can maybe start at 28W and increase or decrease the TDP to maximize wattage while never throttling.
Yes, I’m running Debian testing, which is on 5.18 now. I’ve also tried 5.19 (in experimental), but that caused unusable mouse pointer jerkiness and stuttering.
I’m getting stuck on 0.39 Ghz with both linux and windows 10 on the alderlake laptop. I just started up the laptop today and it was slow, even in the BIOS.
It doesn’t make any difference if it’s on battery or plugged in, it’s still stuck at 0.39 ghz
edit: hmm, disabling the battery through the BIOS seems to have fixed this…
edit 2: This is weird… it seems like the disconnect battery option only applies for the next reboot (it isn’t saved like the rest of the BIOS settings).
Anyways, I think what happened was that I set the “disconnect battery” option, then on the next boot I disconnected the power to see if disconnecting the battery would cause it to fail to boot. It seems like it tried to boot, but ran out of power and shut off again. This seems to have reset something internally and fixed my problem in the process, so I will leave this here for anyone else who happens to stumble on this issue:
My steps were to set the “disconnect battery” option in the bios, then disconnect the power and try to turn it on again. It should try to boot without power and then fail. After that, it should work.
Hi there, don’t know if anybody else tried this, but I may have found a workaround to keep this problem from happening:
The only caveats are that it keeps the CPU from using the full speed available, but it keeps the laptop stable, and if you update the BIOS it resets the settings, so make sure to keep an eye on that.
If you go into BIOS and set CPU to Max-Non Turbo Performance and Disable Intel SpeedStep, SpeedShift and Turbo Boost Max, then it should keep the problem from happening.
This is with a Intel 11 i5, 16gb RAM and Windows 11, but it also fixed the problem on a Intel 12 i5 as well.
Hope this helps somebody!
Same experience, linking to my previous reply for visibility. I have tried everything - there is a major issue here, whether it be in power delivery in firmware or elsewhere.
Edit: nevermind after another half hour or so, one of the core temperatures spiked to 100C, and now all cores are stuck throttled down to 400MHz again.
Thought I’d follow up here as well: after going through a ton of troubleshooting steps, Framework Support finally sent me a new mainboard, and that seems to have solved this issue (Excessive CPU thermal(?) throttling on 12th-gen - #12 by kelnos for details).
my laptop’s CPU (12th gen Intelcore i7 - 1260p) has been stuck at 0,4 GHZ. I understand that this might be a BIOS issue, however i haven’t change any, nor there’s a resent update for them.
I would like to learn how to reset this particular bios settings or which setting I have to change.
I’ve been having this issue off an on for a few months. It seemed to resolve itself once automatically after leaving the laptop off for an entire weekend.
Since the issue started again for a second time I was unable to resolve the problem / find a workaround until this thread. There is one comment that mentions they removed the HDMI port from their framework laptop and it resolved the issue. I just wanted to leave a comment saying that doing so instantly resolved my problem as well.
I’m playing APEX and have high cpu usage, after some time(e.g. 10 min). It will go to 400Mhz for a long time. I only have this problem for some days. But it occurs every day.
This still happens to me from time to time, usually after being plugged in for days. I find that unplugging and running on battery for a while and then rebooting and running on battery for a while solve the issue.
OMG. Thanks for battery trick, finally CPU clock can be adjusted again to full speed.
I’ve wasted hours trying to understand what was going wrong with my laptop, stuck at 400Mhz for no reason. It was barely usable…
I have 12th gen Intel and BIOS 3.06. I see there is a 3.08 update but ChangeLog doesn’t really mention this issue as fixed. Could we get an official answer from @Framework ? Thanks.
It’s interesting to see this problem happening on Framework AMD. The early Steam Decks had what appears to be this same issue. They would permanently clock down to cpu@400mhz and gpu@200mhz. People just had to RMA them until the fix was found.
Valve eventually fixed it with a firmware update (assumed bios) that resolved it:
Firmware 116
Fixed a rare issue that would set the processor TDP limit too low causing CPU and GPU frequencies to be stuck at 400 MHz and 200 MHz respectively.
At this point I’m loosely convinced it’s a problem with the embedded controller’s firmware. Since that is / can be CPU chipset agnostic, it’s not surprising that this bug could affect CPU/GPU from more than one vendor.
after another half hour or so, one of the core temperatures spiked to 100C, and now all cores are stuck throttled down to 400MHz again.
