Re: [loongson-dev] Re: a pre-release of merging loongson patchs to linux-2.6.29.1

[Erwan Lerale <erwan@thiscow.com>]

Erwan Lerale a écrit :

> Now, let's talk about the cpufreq stuff :)
>
> cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
> Report errors and bugs to cpufreq@vger.kernel.org, please.
> analyzing CPU 0:
>  driver: loongson2f
>  CPUs which need to switch frequency at the same time: 0
>  hardware limits: 199 MHz - 797 MHz
>  available frequency steps: 199 MHz, 299 MHz, 398 MHz, 498 MHz, 598 
> MHz, 697 MHz, 797 MHz
>  available cpufreq governors: conservative, ondemand, userspace, 
> powersave, performance
>  current policy: frequency should be within 199 MHz and 797 MHz.
>                  The governor "ondemand" may decide which speed to use
>                  within this range.
>  current CPU frequency is 797 MHz (asserted by call to hardware).
>  cpufreq stats: 199 MHz:0.00%, 299 MHz:0.00%, 398 MHz:0.00%, 498 
> MHz:0.00%, 598 MHz:0.00%, 697 MHz:0.00%, 797 MHz:100.00%
>
> It seems to be working but it's weird. When I start X and gnome 
> (cpufreq applet). I can see
> that's the system is using the ondemand performance but is stuck at 
> 797 Mhz if I don't do anything.
> If i start working (yeah it's happening sometimes), the frequency is 
> moving from 199Mhz to 797Mhz.
>
> The other thing which is weird is that I don't have this problem with 
> the Loonux stock kernel.

Hello,

I've switched from the ondemand governor to the conservative one and it 
seems
to be working properly.

I have also noticed that the fans seems to be running at full speed all 
the time.
Any comment, on this issue ?

Is there a way to query the sensors ?

Cheers
r1