Re: cpufreq: last commit for 2.6.29 break cpufreq performance module

[Guilherme Malschitzky Schroeder <guilherme.m.schroeder@gmail.com>]

Sorry about the wrong info, i used the last cpufreq_ondemand.c file
before this commit and get the same problem. So it' s not the last
commit that changes the behaviour.
I'll bisect it and give more info.

On Mon, Feb 9, 2009 at 11:21 PM, Guilherme Malschitzky Schroeder
<guilherme.m.schroeder@gmail.com> wrote:
> Hello,
>
> After this commit 6707fbb56c8fd3121e334291d170934bcaca2e7f, if i
> change the governor of cpufreq to performance, my processor still
> shows 800MHz instead of 2268.
>
> dub:/sys/devices/system/cpu/cpu0/cpufreq# cat scaling_governor
> ondemand
>
> dub:/sys/devices/system/cpu/cpu0/cpufreq# cat cpuinfo_cur_freq
> 800000
>
> dub:/sys/devices/system/cpu/cpu0/cpufreq# echo performance > scaling_governor
> dub:/sys/devices/system/cpu/cpu0/cpufreq# cat scaling_governor
> performance
> dub:/sys/devices/system/cpu/cpu0/cpufreq# cat cpuinfo_cur_freq
> 2267000
>
> But, /proc/cpuinfo shows 800MHz:
>
> model name      : Intel(R) Core(TM)2 Duo CPU     P8400  @ 2.26GHz
> stepping        : 6
> cpu MHz         : 800.000
>
> And i cannot remove the ondemand module:
>
> dub:/sys/devices/system/cpu/cpu0/cpufreq# rmmod cpufreq_ondemand
> ERROR: Module cpufreq_ondemand is in use
>
> I can confirm that it's not on 2268MHz because glxgears runs below the expected.
>
> No errors on dmesg too.
>