cpuinfo wrong report ?

[David Bandel]

On 1/30/07, Vu Pham <vu at sivell.com> wrote:
> I am playing some settings of the new motherboard.
>
> When I change the clock multiplier, /proc/cpuinfo does show the change
> of CPU Mhz accordingly and shows the same value that the motherboard
> shows ( 3.2Ghz )
>
> But when I change ( increase ) the host clock, the cpuinfo shows the cpu
> mhz dropped dramtically : 600 Mhz ( less than 1Ghz ) instead of 3.54
> Ghz.
>
> In both cases, the bpgomips values increase as expected.
>
> Is it a bug ?

Is it a bug that apples and oranges taste different?

>
>
> The second question: this Intel CPU will run at lower clock  ( 1.6 Ghz )
> when there is little load and moves to a higher (3.2Ghz) when there is
> more load. Is there any kernel settings that can keep the cpu always at
> high frequency clock ?

Why, when the CPU is idle (over 80% of the time) would you want to run
it hotter?

Besides, do you know that Linux (but not all OS's) sends the the Halt
command to the CPU?  Perhaps you'd like to kill that too?

Stepping the processor down and halting it while it's not working
extends the CPU life, reduces power consumption, but does not hurt
performance. Why do you:
a.  insist on overclocking rather than just buying a faster board and processor?
b.  want to defeat mechanisms that don't hurt performance?

If you want to destroy your CPU, a hammer will do it faster and you
won't have to worry about errors, random lockups that have no apparent
cause, etc., as the system dies a tortured death.

Ciao,

David A. Bandel
-- 
Focus on the dream, not the competition.
            - Nemesis Air Racing Team motto