cpufreq live
Interesting finding and I see that you're a hard working user. You should report this result to bugzilla in your thread. Bump!
I was confident that forcing the hardware to maximum speed would help. The bug is deeper. BTW, forcing maximum speed is reset default the next morning or probably after restart.
Have you tried a fresh install of Ubuntu latest to see if Gnome produces the same undesirable result?
About the cmd line that monitors cpufreq live, is reading the same? ' watch grep "cpu MHz" /proc/cpuinfo'
Default reading:
Stay safe!
Interesting finding and I see that you're a hard working user. You should report this result to bugzilla in your thread. Bump!
I was confident that forcing the hardware to maximum speed would help. The bug is deeper. BTW, forcing maximum speed is reset default the next morning or probably after restart.
Have you tried a fresh install of Ubuntu latest to see if Gnome produces the same undesirable result?
About the cmd line that monitors cpufreq live, is reading the same? ' watch grep "cpu MHz" /proc/cpuinfo'
Default reading:
Code:
cpupower frequency-info analyzing CPU 0: driver: [B]acpi-cpufreq[/B] 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: 1.60 GHz - 2.20 GHz available frequency steps: 2.20 GHz, 1.70 GHz, 1.60 GHz available cpufreq governors: [B]performance schedutil[/B] current policy: frequency should be within 1.60 GHz and 2.20 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.33 GHz (asserted by call to kernel) [B]<<never goes under, 1.55 is your minimum>>[/B] boost state support: Supported: no Active: no
Comment