d.healey wrote: ↑Sun May 09, 2021 12:49 pm
What does this do?
From
https://access.redhat.com/articles/65410 :
A system may be prevented from entering power-saving states by booting with the processor.max_cstates=1 command line option. Additionally, the idle=poll option may be added for the fastest time out of the idle state. Unfortunately both of these options tend to cause power usage to spike.
The rest of that article is also quite interesting, perhaps the comments as well.
I use the Liquorix kernel which has CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y set in it's config which may confuse the issue too. So much varied advice on the net, what can a poor boy do?
Edit (a bit later) - this thread got my wondering why I still had variable CPU frequency. A bit more tweaking and I found in UEFI setup by disabling "CPU EnhancedHalt (C1E)" the frequency would stay fixed, so perhaps the kernel parameters are not the full monty. Curiosity was piqued by a comment in that RedHat article. Ran xruncounter and got "first Xrun happen at DSP load 99.51%". Seems acceptable.
A quick run of a Mixbus 32C mix seemed happy.
Sorry to hijack your topic TAERSH but maybe some of this discussion will lead to a fix for your heating.