I’ve just run into the same issue myself. Or rather, I’ve run into it a few times. Normally a reboot will fix it, or just simply waiting. This time however it persisted through reboots even after the system had cooled down to ambient temperature.
Unfortunately I don’t have my framework screwdriver handy, nor a thumbdrive or other boot device so trying to do a CMOS reset or checking for a BIOS update wasn’t an option (I’m on Linux and the latest seems to not be available via fwupd). Resetting the BIOS did not work.
However, I was able to resolve it by disabling quick/quiet boot and started getting normal performance again and the processor is at a more appropriate frequency, bouncing around between 1 -2 ghz.
I’ve battled overheating and severe CPU throttling (as severe as pinning the CPU to 200 MHz for a while) issues for the last month or so w/ my 13", 11th gen Intel Framework, running NixOS.
Laptop would get hot to the touch just by running anything that required a bit of CPU power. On an average day, video calls would consistently render the laptop extremely hot and slow - if not completely crippled by reducing the CPU clock speeds to 200 MHz.
I’ve spent some time reapplying the thermal paste and cleaning the fans and heatsink (incl. the intake and exhaust) rigorously. In my case clearing the heatsink and the air paths made the biggest difference.
It’s been about a month since I’ve made these changes. Despite daily video calls and light gaming, my laptop hasn’t overheated to the point it used to or had an extreme thermal throttling issue.
I think what happened was: I left the laptop on the couch, where the air intake wasn’t clear. It slowly overheated and went into sleep mode. When I turned my laptop on in the morning, as in - even with a cold laptop, CPU was throttled at 0.2 GHz. Rebooting or turning the laptop off and on didn’t make a difference.
I found that if it did thermal throttle, that once those conditions were no longer present, it needed a least 30 seconds running in the throttled state before it would consider going up to full speed.
Just rebooting it would not clear the issue, even though it was cooler
I’m having this exact issue on an 11th gen i7-1165G7 mainboard.
It’s running Ubuntu Studio 24.04 and worked fine for the longest time, but today it suddenly started lagging while running Mixxx, which has worked fine for months before.
It’s been stuck for hours now and is not recovering. Neither shutdown nor sleep and wakeup are helping. The CPU was running cool at about 50C and the battery was at roughly 30% when it happened.
I had a similar issue on my 12th gen too, there a BIOS update fixed it. But my 11th gen board is already at the latest version.
Sorry for double posting, it seems like I can’t edit my post.
I have made some progress on this issue. It seems that this is caused by the BD PROCHOT signal as described here:
The workaround from this post worked for me, but be aware that this is potentially dangerous:
(the package is called msr-tools in Ubuntu 24.04)
There might be a legitimate reason the CPU is getting that signal, and disabling it could cause something to go up in smoke!
But I’ll take the risk of frying my board over it being effectively bricked as-is.