Comment 3 for bug 410043

This has been bedeviling me for quite some time now as well: cpufreq-info presents incorrect information about my T2500 Intel Core 2 CPU (attached).

SysRescueCD, Puppy Linux, and other live CDs detect the correct MHz for both cores: 1997.xx

I can't help but believe this problem is related to my problem with CPU frequency scaling. On logging into Gnome, the ondemand governor steps the two cores between 1.0GHz and 2.0GHz, as I wish, and as confirmed by cpufreq-info. A short time later, the processors are set to the lowest frequency, and cpufreq-info has the governor scaling between 1000Mhz and 1000Mhz.

I know from googling forums that this is a very, very common problem. I thought I had found a solution with a combination of boot options set in GRUB and selected by brute-force testing of one combination after another among boot options recommended in the fora -- "noapm, acpi=noirq, pnpacpi=off"

This may have been broken by the last update of 10.04 Lucid. Just a wild guess.

uname -a = macunaimachine 2.6.32-10-generic #14-Ubuntu SMP Thu Jan 7 17:38:40 UTC 2010 i686 GNU/Linux