RE: Ondemand/Conservative not working with 2.6.18

[Pallipadi, Venkatesh]

>-----Original Message-----
>From: S.Çaglar Onur [mailto:caglar@xxxxxxxxxxxxx] 
>Sent: Tuesday, October 10, 2006 1:55 PM
>To: Pallipadi, Venkatesh
>Cc: Dave Jones; linux-kernel@xxxxxxxxxxxxxxx
>Subject: Re: Ondemand/Conservative not working with 2.6.18
>
>10 Eki 2006 Sal 02:35 tarihinde, Pallipadi, Venkatesh şunları 
>yazmıştı: 
>> What CPU is this? Pentium M?
>
>Yes it is.
>
>
>zangetsu cpu0 # cd cpufreq/
>zangetsu cpufreq # echo "ondemand" > scaling_governor
>zangetsu cpufreq # cat scaling_governor
>ondemand
>zangetsu cpufreq # cat scaling_available_frequencies
>1733000 1333000 1067000 800000
>zangetsu cpufreq # cat scaling_cur_freq
>1733000
>
>But frequency never changes and stays at 1.73ghz
>
>zangetsu cpufreq # echo "powersave" > scaling_governor
>zangetsu cpufreq # cat scaling_cur_freq
>800000
>zangetsu cpufreq # echo "performance" > scaling_governor
>zangetsu cpufreq # cat scaling_cur_freq
>1733000
>

I guess I misunderstood the original issue. You have available_frequencies showing all the values and after you load ondemand, frequency remains at the highest, even though CPUs are idle. Is this correct?

And everything above used to work fine with 2.6.16?

Can you configure with CPU_FREQ_DEBUG and do "echo 5 > /sys/module/cpufreq/parameter/debug" before switching the governor to ondemand and see whether you see any messages in dmesg?

Thanks,
Venki
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/