Description of problem: After the upgrade to kernel 5.10 the CPU frequency is stuck at 798MHz. [fred@localhost ~]$ cpupower frequency-info analyse du CPU 0 : driver: intel_cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 20.0 us limitation matérielle : 800 MHz - 3.90 GHz régulateurs disponibles : conservative ondemand userspace powersave performance schedutil tactique actuelle : la fréquence doit être comprise entre 800 MHz et 3.90 GHz. Le régulateur "powersave" est libre de choisir la vitesse dans cette plage de fréquences. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes [fred@localhost ~]$ cpupower frequency-info analyse du CPU 0 : driver: intel_cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 20.0 us limitation matérielle : 800 MHz - 3.90 GHz régulateurs disponibles : conservative ondemand userspace powersave performance schedutil tactique actuelle : la fréquence doit être comprise entre 800 MHz et 3.90 GHz. Le régulateur "powersave" est libre de choisir la vitesse dans cette plage de fréquences. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes [fred@localhost ~]$ uname -a Linux localhost.localdomain 5.10.6-desktop-1.mga7 #1 SMP Sat Jan 9 20:09:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux cpupower reports the same on each core. The CPU is a core i7 4770. The machine a Lenovo Thinkcentre. All the packages are up to date. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
ok found the problem. sysconfig/cpupower had been modified in the past, to use powersave. [root@localhost etc]# cat sysconfig/cpupower CPUPOWER_START_OPTS="frequency-set -g powersave" CPUPOWER_STOP_OPTS="frequency-set -g powersave" Although powersave is available: [root@localhost etc]# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors conservative ondemand userspace powersave performance schedutil it does not work as before in 5.10. Changing it to powersave fixed the problem. [root@localhost etc]# cat sysconfig/cpupower CPUPOWER_START_OPTS="frequency-set -g ondemand" CPUPOWER_STOP_OPTS="frequency-set -g ondemand" may be the install script of the kernel rpm should check for this? I did make this modification a long time ago because I did not want either my CPU to be at max freq 100% of the time (why are you using performance by default?), I now remember I chose powersave because ondemand stopped working at one point. However I had forgotten about it, that's why maybe the update script should check this (?) anyway thanks!
$ uname -r 5.10.9-desktop-1.mga8 $ cat /proc/cpuinfo | grep 'model name' model name : Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz model name : Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz model name : Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz model name : Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz $ cpupower frequency-info analyse du CPU 0 : driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. limitation matérielle : 800 MHz - 3.90 GHz régulateurs disponibles : performance powersave tactique actuelle : la fréquence doit être comprise entre 800 MHz et 3.90 GHz. Le régulateur "performance" est libre de choisir la vitesse dans cette plage de fréquences. current CPU frequency: Unable to call hardware current CPU frequency: 3.83 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes Note that since 5.8 series Kernel, upstream prefers the use of "powersave" governor for all intel_pstate compatible Intel CPU. That's why when you upgrade such system to newer kernel, there is such behaviour. This is landed in RELEASE_NOTES for M8. https://wiki.mageia.org/mw-en/index.php?title=Mageia_8_Release_Notes#Kernel_and_hardware_support Closing as duplicate. *** This bug has been marked as a duplicate of bug 27191 ***
CC: (none) => ouaurelienResolution: (none) => DUPLICATEStatus: NEW => RESOLVED