I found an older thread from 2015 that also highlights this issue. Also, a bug report concerning the matter was raised for the kernel, which spawned from that thread.
]]>I will have a look at the thread you linked.
]]>sudo cpupower -c all info -b
If you're having performance issues after suspend/hibernate, my experience is that it often happens on my thinkpad when I keep a browser opened before going into either mode. If you've mistakenly done so with a browser open, I believe a relog of your user can help, if not then a reboot.
I'm sure there's a better solution out there, but I haven't bothered to troubleshoot it properly since personally, I rarely use suspend/hibernate. Much rather turn on or off my laptop as I see fit. I remove suspend from when I close my lid even, by editing /etc/systemd/logind.conf, and finding:
[Login]
#HandleLidSwitch=suspend
#HandleLidSwitchDocked=suspend
then uncommenting and changing to:
[Login]
HandleLidSwitch=ignore
HandleLidSwitchDocked=ignore
Then restart systemd-logind.
There are other threads pointing similar issues with suspend, for instance.
]]>Will this setting persist after reboots?
]]>If you're already using cpupower, you can try the command:
sudo cpupower set -b 6
This will set the profile to normal. You can also try 0 for maximum performance.
]]>While plugged into the wall, everything works as expected, the CPU scales it's frequency up and down.
But when unplugging the power cord, the CPU is stuck at 400MHz which makes even an optimized Linux system unusable...
I tried manually setting the frequency and changing the governor using cpupower but it didn't help.
Thermald is also not installed.
Any ideas on what could be the culprit?
]]>