My best guess so far is it some how relates to the cpufreq governer.As of 2.6.14, changing between performance and userspace seems to hose up the clock values in cpuinfo.
At the moment it is using the userspace governor (powernowd) and returning between 7 and 14 GHz and 15-28k bogomips. So, I'm inclined to think this is a kernel bug. The available clock speeds should be between 500MHz and 1.5GHz.
I'm going to reboot again and experiment a bit to see if I can nail down what triggers the abberation.
dcm
On 12/13/05, darren kirby
<[EMAIL PROTECTED]> wrote:
quoth the Devon Miller:
> If only it were so...
>
> Anyone have an idea as to what I've hosed up here?
> (I'm running 2.6.14-suspend2-r7)
>
> dcm
>
> [EMAIL PROTECTED] ~ $ cat /proc/cpuinfo
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 6
> model : 8
> model name : mobile AMD Athlon(tm) XP 1600+
> stepping : 0
> cpu MHz : 10676.718
> cache size : 256 KB
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 1
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov
> pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow
> bogomips : 21376.31
Wow, that's pretty fast...
Can you think of _anything_ you may have changed since before it was hosed? If
not then perhaps you have found a kernel bug.
-d
--
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972
