With Kernel 5.8.0-2 my system seems to be only running at it’s minimum clock of 800mhz. If more information on this is need, please let me know what and where to provide it correctly.
If someone is having issues with reinstalling GRUB on their EFI system, don’t pull a Beerfoo and make sure you also boot your USB device in EFI mode
I suppose it should go without saying, but perhaps it would be worth mentioning on the wiki.
Once that was out of the way, everything was super easy.
How do you check that?
What I see in conky is that 5.8 stays on the base frequency longer. That might be due to the new power management that was added with 5.8. But it definitely uses all frequencies when needed. On an AMD Ryzen 7 2700X that is.
The system was significantly slower than usual even when logging in or starting applications. After a while of wondering what was going on, I looked at conky and noticed that it was stuck at 800mhz, which would not change.
Output of inxi MCxxa --no-host under 5.7 (if output from 5.8 is needed please let me know)
I’ve got a similar issue when I boot my laptop unplugged. It also occur with 5.7.15. Nethertheless it seems to be related to the recent manjaro stable update (probably the 2020-08-16 one) as I didn’t notice it before.
there is this
line 181 aug 23 11:53:36 cheetah kernel: Trampoline variant of Tasks RCU enabled.
–> i hope that microcode is updated too
line 188 Aug 23 11:53:36 cheetah kernel: ACPI: Core revision 20200528
in both case
Aug 23 11:53:36 cheetah kernel: core: PMU erratum BJ122, BV98, HSD29 worked around, HT is on
Aug 23 11:53:36 cheetah kernel: ENERGY_PERF_BIAS: Set to ‘normal’, was ‘performance’
may be this ( not getting values ? )
Aug 23 11:53:36 cheetah kernel: at24 0-0050: supply vcc not found, using dummy regulator
Aug 23 11:53:36 cheetah kernel: at24 0-0050: 256 byte spd EEPROM, read-only
Aug 23 11:53:36 cheetah kernel: at24 0-0051: supply vcc not found, using dummy regulator
Aug 23 11:53:36 cheetah kernel: at24 0-0051: 256 byte spd EEPROM, read-only
Aug 23 11:53:36 cheetah kernel: at24 0-0052: supply vcc not found, using dummy regulator
Aug 23 11:53:36 cheetah kernel: at24 0-0052: 256 byte spd EEPROM, read-only
Aug 23 11:53:36 cheetah kernel: at24 0-0053: supply vcc not found, using dummy regulator
Aug 23 11:53:36 cheetah kernel: at24 0-0053: 256 byte spd EEPROM, read-only
sudo cpupower frequency-info
analyzing 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.
hardware limits: 800 MHz - 4.50 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 4.50 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.18 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
Under 5.8.1-3
sudo cpupower frequency-info
analyzing 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
hardware limits: 800 MHz - 4.50 GHz
available cpufreq governors: powersave performance schedutil
current policy: frequency should be within 800 MHz and 4.50 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 800 MHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
You Sir, are a wizard! It worked and things are back to normal!
Just passing intel_pstate=active did the trick.
Would you suggest I add the parameter to my grub configuration or will this change in a future kernel version? (I normally do not reboot all that often).
Thank you very much stephane for your help, I could not have figured this out on my own.
yes you should add on your grub configuration for the moment ,
it easy to try just before launch boot on grub screen
your processor is using pstate before generation skylake , and do not active on hardware at start ,
because it will use “passive” by default , or in this case it a minima