http://bugzilla.kernel.org/show_bug.cgi?id=13995 Dave Jones <davej@xxxxxxxxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |davej@xxxxxxxxxxxxxxxxx Resolution| |INVALID --- Comment #6 from Dave Jones <davej@xxxxxxxxxxxxxxxxx> 2009-08-17 22:20:10 --- when overclocked, there is no way of getting an accurate reading of the processor speed other than running a benchmark. What you're seeing in /proc/cpuinfo is the best guess that the cpufreq code could come up with based on the wrong information that it had to work with from the BIOS. (The BIOS typically only has information about the stock cpu speeds, not the overclocked ones) There's no bug here afaics. You ran your hardware outside of spec, and stuff broke as a consequence. Expected behaviour. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
