CPU Clock speed gets stuck sometimes

Which Linux distro are you using? Gentoo

If rolling release, last date updated? 18.10.2025

Which kernel are you using? 6.17.3

Which BIOS version are you using? 3.04

Which Framework Laptop 13 model are you using? AMD Ryzen™ AI 300 Series

Sometimes I find my clocks speeds stuck at 1,6 (1,4 for zen4c cores) and need to reboot to get reclocking to work properly. I notice it when Firefox gets laggy while compiling updates…

I’m not even sure what method is used to control the frequencies.

changing governor using cpupower, doesn’t fix it, changing profile using power profiles does nothing either. A reboot does.

TLP is installed, its daemon isn’t running, but it gets somehow invoked, I guess by power-profiles-daemon. I use it to disable the sound card when on battery.

Title mentions only CPU, I haven’t looked at GPU.

Any ideas where to start?

I’m not familiar with Gentoo, but I think that you should check out the BIOS updates page for Framework to see if there’s a new BIOS, because I did hear about a bug that “Freezes“ the CPU clock speed sometimes. Maybe it could work. The page for the FW13 is here. Alternatively, it could be an issue with Gentoo. I recommend creating a bootable USB with Ubuntu and running it in a live environment or its “try Ubuntu“ mode so it doesn’t install. Once Ubuntu is fully booted and you’re in the desktop, click the app drawer and navigate to the Terminal, or do Ctrl + Alt + T. When in the terminal, try the command lscpu | grep MHz Once you do that, please post the CPU speed so we can see if it’s an issue with Gentoo or not.

I’m on the 7040 series, but I’ve occasionally had issues with that in arch, where the CPU gets set into a state where it cannot boost, so it’s “max” clock is whatever the min clock is (~800mhz? I forget). Reboot definitely fixes it, but I’ve also had success with sleeping it.

It’s never happened enough that I’ve dug into it though, sorry. I am on the latest bios, and 6.17.3.

the BIOS got updated a week ago, after I first noticed the issue, and before I noticed it again. Although I probably hadn’t yet rebooted, so the new microcode probably hadn’t loaded yet…

I’m sorry, I’ll be a bit negative with the Ubuntu suggestion: How would doing that help when I don’t know how to reproduce the issue? It happens at some point during normal usage, and I notice it when the system gets under very heavy load. It could have triggered days before (I rarely power off). I can’t use a live system for days on end…

I’ll keep monitoring, I guess…

I’m sorry for the late response and for the Ubuntu thing, I just know it’s one of the OS’s that are officially supported and maybe doing it could help to see if it’s a hardware or software issue. You can do the same with Fedora or Bazzite.

I get that, thanks for commenting. AFAIK there are no special patches for framework on ubuntu/fedora, so I take that it’s mainly for the out of the box setup. Which I wouldn’t keep anyway :smiley:

I haven’t been hit by this since the reboot after BIOS update. OTOH I haven’t seen boost frequencies either…

1 Like

I wish I better knew the inner working of the laptop, but I’m glad you are able to see mostly normal frequencies now. I think that contacting support would be the best thing to do because they know best when it at least comes to the hardware and they might be able to tell you for sure if you’re having a hardware issue or not.

It keeps happening… kernel 6.18.1 :frowning:

1 Like

That’s not good, I don’t know how to help. Is there any way that support can help or someone else in the community using your specific distro?