I f***ed around. This is before sleep-wake:
$ grep . /sys/devices/system/cpu/cpu*/cpufreq/scaling_* 2>/dev/null | sed -n '1,40p'
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:userspace performance schedutil
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:800068
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:userspace
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:4400000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:800000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:800000
/sys/devices/system/cpu/cpu1/cpufreq/scaling_available_governors:userspace performance schedutil
/sys/devices/system/cpu/cpu1/cpufreq/scaling_cur_freq:800087
/sys/devices/system/cpu/cpu1/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu1/cpufreq/scaling_governor:userspace
/sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq:4400000
/sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq:800000
/sys/devices/system/cpu/cpu1/cpufreq/scaling_setspeed:800000
/sys/devices/system/cpu/cpu2/cpufreq/scaling_available_governors:userspace performance schedutil
/sys/devices/system/cpu/cpu2/cpufreq/scaling_cur_freq:800145
/sys/devices/system/cpu/cpu2/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu2/cpufreq/scaling_governor:userspace
/sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq:4400000
/sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq:800000
/sys/devices/system/cpu/cpu2/cpufreq/scaling_setspeed:800000
/sys/devices/system/cpu/cpu3/cpufreq/scaling_available_governors:userspace performance schedutil
/sys/devices/system/cpu/cpu3/cpufreq/scaling_cur_freq:799928
/sys/devices/system/cpu/cpu3/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu3/cpufreq/scaling_governor:userspace
/sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq:4400000
/sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq:800000
/sys/devices/system/cpu/cpu3/cpufreq/scaling_setspeed:800000
/sys/devices/system/cpu/cpu4/cpufreq/scaling_available_governors:userspace performance schedutil
/sys/devices/system/cpu/cpu4/cpufreq/scaling_cur_freq:800049
/sys/devices/system/cpu/cpu4/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu4/cpufreq/scaling_governor:userspace
/sys/devices/system/cpu/cpu4/cpufreq/scaling_max_freq:4400000
/sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq:800000
/sys/devices/system/cpu/cpu4/cpufreq/scaling_setspeed:800000
/sys/devices/system/cpu/cpu5/cpufreq/scaling_available_governors:userspace performance schedutil
/sys/devices/system/cpu/cpu5/cpufreq/scaling_cur_freq:800000
/sys/devices/system/cpu/cpu5/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu5/cpufreq/scaling_governor:userspace
/sys/devices/system/cpu/cpu5/cpufreq/scaling_max_freq:4400000
This is after sleep-wake:
$grep . /sys/devices/system/cpu/cpu*/cpufreq/scaling_* 2>/dev/null | sed -n '1,40p'
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:userspace performance schedutil
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:4000372
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:userspace
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:4400000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:800000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:800000
/sys/devices/system/cpu/cpu1/cpufreq/scaling_available_governors:userspace performance schedutil
/sys/devices/system/cpu/cpu1/cpufreq/scaling_cur_freq:800000
/sys/devices/system/cpu/cpu1/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu1/cpufreq/scaling_governor:userspace
/sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq:4400000
/sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq:800000
/sys/devices/system/cpu/cpu1/cpufreq/scaling_setspeed:800000
/sys/devices/system/cpu/cpu2/cpufreq/scaling_available_governors:userspace performance schedutil
/sys/devices/system/cpu/cpu2/cpufreq/scaling_cur_freq:4000339
/sys/devices/system/cpu/cpu2/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu2/cpufreq/scaling_governor:userspace
/sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq:4400000
/sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq:800000
/sys/devices/system/cpu/cpu2/cpufreq/scaling_setspeed:800000
/sys/devices/system/cpu/cpu3/cpufreq/scaling_available_governors:userspace performance schedutil
/sys/devices/system/cpu/cpu3/cpufreq/scaling_cur_freq:4000242
/sys/devices/system/cpu/cpu3/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu3/cpufreq/scaling_governor:userspace
/sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq:4400000
/sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq:800000
/sys/devices/system/cpu/cpu3/cpufreq/scaling_setspeed:800000
/sys/devices/system/cpu/cpu4/cpufreq/scaling_available_governors:userspace performance schedutil
/sys/devices/system/cpu/cpu4/cpufreq/scaling_cur_freq:800000
/sys/devices/system/cpu/cpu4/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu4/cpufreq/scaling_governor:userspace
/sys/devices/system/cpu/cpu4/cpufreq/scaling_max_freq:4400000
/sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq:800000
/sys/devices/system/cpu/cpu4/cpufreq/scaling_setspeed:800000
/sys/devices/system/cpu/cpu5/cpufreq/scaling_available_governors:userspace performance schedutil
/sys/devices/system/cpu/cpu5/cpufreq/scaling_cur_freq:4001780
/sys/devices/system/cpu/cpu5/cpufreq/scaling_driver:intel_cpufreq
/sys/devices/system/cpu/cpu5/cpufreq/scaling_governor:userspace
/sys/devices/system/cpu/cpu5/cpufreq/scaling_max_freq:4400000
Definitely the cpu is stuck at 800mhz, after sleep-wake it can boost like normal. Do you know what could cause this?
The data points to thermald as a likely cause: the governor is set to "userspace" with scaling_setspeed=800000, which is how thermald controls CPU frequency for thermal management. It typically sets the minimum at boot as a starting point and should then raise it — but in your case it may not be doing so until the sleep-wake cycle triggers a thermal re-evaluation.
It may be worth checking thermald's logs to confirm:
journalctl -u thermald
In the meantime, switching the governor manually should help:
echo "schedutil" | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
Note that cpupower-gui is no longer installed by default and is no longer recommended. It has been replaced by thermald for Intel CPUs, which handles thermal management — keeping the CPU within safe temperature limits. Performance profile management (switching between power-saving, balanced and performance) is a separate concern, handled by power-profiles-daemon.
From the distribution side, power-profiles-daemon has just been packaged and is currently in the devel-makedist repository, where it will go through testing before being made available in the base repository and installed automatically as a dependency of powerdevil for all users.
This is right after a boot
$sudo journalctl -u thermald [...] -- Boot 55d42ef6be3b4e66ad022368c0fba8f4 -- mag 31 11:26:35 ms7816 systemd[1]: Starting thermald.service... mag 31 11:26:35 ms7816 thermald[4773]: NO RAPL sysfs present mag 31 11:26:35 ms7816 thermald[4773]: 13 CPUID levels; family:model:stepping 0x6:3c:3 (6:60:3) mag 31 11:26:35 ms7816 thermald[4773]: NO RAPL sysfs present mag 31 11:26:35 ms7816 thermald[4773]: 13 CPUID levels; family:model:stepping 0x6:3c:3 (6:60:3) mag 31 11:26:36 ms7816 thermald[4773]: Using config file /etc/thermald/thermal-conf.xml mag 31 11:26:36 ms7816 thermald[4773]: Polling mode is enabled: 4 mag 31 11:26:36 ms7816 systemd[1]: Started thermald.service.$grep . /sys/devices/system/cpu/cpu*/cpufreq/scaling_* 2>/dev/null | sed -n '1,40p' | grep scaling_cur_freq /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:800019 /sys/devices/system/cpu/cpu1/cpufreq/scaling_cur_freq:800068 /sys/devices/system/cpu/cpu2/cpufreq/scaling_cur_freq:800313 /sys/devices/system/cpu/cpu3/cpufreq/scaling_cur_freq:800067 /sys/devices/system/cpu/cpu4/cpufreq/scaling_cur_freq:799757 /sys/devices/system/cpu/cpu5/cpufreq/scaling_cur_freq:800054
After a sleep/wake, thermald logs don't have any new lines
$sudo journalctl -u thermald [...] -- Boot 55d42ef6be3b4e66ad022368c0fba8f4 -- mag 31 11:26:35 ms7816 systemd[1]: Starting thermald.service... mag 31 11:26:35 ms7816 thermald[4773]: NO RAPL sysfs present mag 31 11:26:35 ms7816 thermald[4773]: 13 CPUID levels; family:model:stepping 0x6:3c:3 (6:60:3) mag 31 11:26:35 ms7816 thermald[4773]: NO RAPL sysfs present mag 31 11:26:35 ms7816 thermald[4773]: 13 CPUID levels; family:model:stepping 0x6:3c:3 (6:60:3) mag 31 11:26:36 ms7816 thermald[4773]: Using config file /etc/thermald/thermal-conf.xml mag 31 11:26:36 ms7816 thermald[4773]: Polling mode is enabled: 4 mag 31 11:26:36 ms7816 systemd[1]: Started thermald.service.$grep . /sys/devices/system/cpu/cpu*/cpufreq/scaling_* 2>/dev/null | sed -n '1,40p' | grep scaling_cur_freq /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:4000319 /sys/devices/system/cpu/cpu1/cpufreq/scaling_cur_freq:4000283 /sys/devices/system/cpu/cpu2/cpufreq/scaling_cur_freq:800000 /sys/devices/system/cpu/cpu3/cpufreq/scaling_cur_freq:4000328 /sys/devices/system/cpu/cpu4/cpufreq/scaling_cur_freq:4002378 /sys/devices/system/cpu/cpu5/cpufreq/scaling_cur_freq:4000768
I did notice that cpuower-gui is no longer installed by default. I wait for further instructions to debug this issue.
The thermald log suggests a likely cause: "NO RAPL sysfs present" means thermald cannot find the Intel RAPL (Running Average Power Limit) interface it uses to monitor power consumption. Without it, thermald falls back to polling mode and sets the CPU to minimum frequency as a conservative measure, without knowing when it is safe to raise it.
First, check whether the RAPL kernel module is available:
ls /sys/class/powercap/
If the directory is empty or missing, try loading it manually:
sudo modprobe intel_rapl_common
Then restart thermald and check whether the CPU frequency recovers:
sudo systemctl restart thermald
If RAPL is not available on your kernel build, an alternative is to disable thermald entirely — the i7-4790K has its own built-in thermal protection and will throttle itself if temperatures become critical:
sudo systemctl disable --now thermald
echo "schedutil" | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
Note that power-profiles-daemon is now available in the repository, but it would not resolve this issue on its own as long as thermald is overriding the governor.
Interestingly, the directory does exist
$ls /sys/class/powercap/
intel-rapl intel-rapl:0 intel-rapl:0:0 intel-rapl:0:1 intel-rapl:0:2

