Hello,
Running linux 2.6.23.1-21.fc7
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
correctly reflects the cpu speed, when idle it is 996000 and when
compiling it is 1826000.
Its also the same as what is in /proc/cpuinfo.
But with 2.6.23.8-34.fc7
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
is always the max cpu speed of 1826000.
While cpuinfo_cur_freq is the max 1826000 /proc/cpuinfo relflects the
correct speed when idle of
996000
This is on an asus laptop with an intel core 2 duo T5600 processor.
Anyone else see this problem.
Regards,
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
Hi Steve,
Stephen Clark <[email protected]> writes:
> But with 2.6.23.8-34.fc7
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
> is always the max cpu speed of 1826000.
>
> While cpuinfo_cur_freq is the max 1826000 /proc/cpuinfo relflects the
> correct speed when idle of
> 996000
Which governor are you using? ondemand?
Hannes
Hi,
Stephen Clark <[email protected]> writes:
>>Which governor are you using? ondemand?
> Not sure - but the only thing that is changed is the kernel - if I go
> back to 2.6.23.1 it works correctly.
Have a look at /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Hannes
PS: Steve, please keep the list in CC.
Johannes Weiner wrote:
>Hi,
>
>Stephen Clark <[email protected]> writes:
>
>
>
>>>Which governor are you using? ondemand?
>>>
>>>
>>Not sure - but the only thing that is changed is the kernel - if I go
>>back to 2.6.23.1 it works correctly.
>>
>>
>
>Have a look at /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
>
> Hannes
>
>PS: Steve, please keep the list in CC.
>
>
>
userspace
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
Hi,
Stephen Clark <[email protected]> writes:
> userspace
Please supply the full dmesg output on the non-working kernel the
corresponding .config (or /proc/config.gz).
Added Dave to CC.
Hannes
Johannes Weiner wrote:
>Hi,
>
>Stephen Clark <[email protected]> writes:
>
>
>
>>userspace
>>
>>
>
>Please supply the full dmesg output on the non-working kernel the
>corresponding .config (or /proc/config.gz).
>
>Added Dave to CC.
>
> Hannes
>
>
>
Duh - I rebooted into the new kernel and no longer see the behavior I
described above. Maybe I had something going in
the background i didn't realize. Thing was I even started a bash empty
while loop to see if /proc/cpuinfo speed would go
up and it did.
I have an applet that displays on my kde kicker panel that every 2
seconds reads /sys/.../cpuinfo_cur_freq and it was
sitting on the max speed all the time. Hmmm.
Well Thanks for the response and sorry for the false alarm.
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)