On Thu, May 13, 2021 at 06:39:08PM +0800, Ingo Molnar wrote:
- Ingo Molnar mingo@kernel.org wrote:
No need to send v5, done!
I have a system that appears to be affected by this bug:
kepler:~> lscpu | grep -i mhz CPU MHz: 4000.000 CPU max MHz: 7140.6250 CPU min MHz: 2200.0000
So I should be able to confirm after a reboot.
'CPU max Mhz' seems to be saner now:
kepler:~> lscpu | grep -i mhz
CPU MHz: 2200.000 CPU max MHz: 4917.9678 CPU min MHz: 2200.0000
Yes, happy to know this :-)
Thanks, Ray