Limiting maximu CPU frequency doesn't work after a sleep/resume cycle

English Open Chat
1

Starting from kernel version 13, there’s a problem with limiting the maximum CPUs frequency.
After a sleep/resume cycle my laptop doesn’t respect `cpupower frequency-set -u’ limit and allows to run CPUs with a maximum frequency. Before the sleep/resume cycle all works fine.
Anyone else observing similar issue?

HW
AMD Ryzen 5 PRO 5650U with Radeon Graphics
amd-pstate-epp

2

Amendment: the effect is that although cpupower reports success but the actual allowed cpu frequency is at the maximum (that can be verified by reading `scaling_cur_freq’ in sysfs, plus the cpu temperature gets high and cpu the fan gets loud)

3

You can make a system service that runs after it resumes from sleep.
You can make them run before sleep or after. Use “pre)” for before sleep and “post)” to make it run after waking. Post in the below script means after waking. You can research this more later so you’ll know more about it.

Name it whatever you want, like setspeed or whatever so you’ll know what it is.

Put the file in /usr/lib/systemd/system-sleep/

Make it executable.

Here you go.

#!/bin/sh
case $1 in
  post)
    /usr/bin/cpupower FINISH YOUR COMMAND HERE.
  ;;
esac
4

Thanks, but that’s not the issue. I do run cpupower after the system resumes from sleep, and cpupower indicates success and shows that the frequencies have been changed. However, the actual frequencies do not change.

5

@mkos88 ,

I just hopped by here by incident and wondered why you posted this in Open Chat instead of in one of the technical help forums.

There are technical sophisticated people willing to help in computer technical questions, that will never look into this place. Thus your problem will not be seen by them.