Re: [Cpufreqd-devel] cpufreqd stuck at 800mhz yet cpufreq working fine

[tehownt t. <te...@gm...>]

I've used strace in order to get more details on the execution hoping
to find something...

On Thu, Nov 6, 2008 at 5:40 PM, tehownt tehownt <te...@gm...> wrote:
> I managed to compile and install version 005, same problem.
>
> I launched the daemon with the AC OFF (values were correctly set) then
> plugged it, and unplugged it (values were then locked at 800000),
> output attached.
>
> Thanks again for your time !
>
>
>
> On Thu, Nov 6, 2008 at 5:28 PM, tehownt tehownt <te...@gm...> wrote:
>> Thanks for the follow-up, sorry for the delayed answer I had limited
>> acces to my mail today.
>>
>> It's funny that the new 2.3.3-3 logging has an error because when I
>> did the -V7 command with the 2.3.3-1 version I didn't have such errors
>> in the log:
>>
>> cpufreqd_loop            : New Rule ("AC Off - Medium Battery"), applying.
>> cpufreqd_set_profile     : Profile "Powersave High" set for CPU0
>> cpufreqd_set_profile     : Profile "Powersave High" set for CPU1
>> event_wait               : processor CPU0 00000080 0000000 (32)
>> alarm_handler            : Caught ALARM signal (Alarm clock).
>>
>> eventhough the frequencies still were stuck at 800-800 ondemand.
>>
>> But I also noticed that, if I restart the daemon while the AC is OFF,
>> it sometimes manages to get it right to 800000-2400000-ondemand
>> (attached the log too)...
>>
>>
>> Regarding cpufrequtils version, I had these installed:
>>
>> cpufrequtils 002-7.2
>> libcpufreq0 002-7.2
>>
>> I found some builds for 004-2 which I installed, but without much sucess...
>>
>> It removed the errors in the log though (full log attached).
>>
>> cpufreqd_loop            : New Rule ("AC Off - Medium Battery"), applying.
>> cpufreqd_set_profile     : Profile "Powersave High" set for CPU0
>> cpufreqd_set_profile     : Profile "Powersave High" set for CPU1
>> event_wait               : processor CPU0 00000080 0000000 (32)
>> alarm_handler            : Caught ALARM signal (Alarm clock).
>> cpufreqd_loop            : Current time is: 1226009471::769134
>>
>> But didn't change the frequencies correctly, still stuck at
>> 800000-800000-ondemand...
>>
>> I'll have to search more in order to get the 005 version of
>> cpufrequtils since it's not build for ubuntu yet, and it wasn't
>> compiling straight through when I tried.
>>
>> Thanks !
>>
>> On Thu, Nov 6, 2008 at 8:13 AM, Mattia Dongili <mal...@li...> wrote:
>>> On Thu, Nov 06, 2008 at 07:52:41AM -0500, tehownt tehownt wrote:
>>> ...
>>>> I followed your advice and installed a 2.3.3-3 Ubuntu .deb but without
>>>> luck, at least it removed the /energy_* debug output.
>>>>
>>>> I've attached the log from 2.3.3-3 in which I've plugged/unplugged the
>>>> laptop multiple times, I really am clueless as to why the frequency
>>>> gets locked at 800mhz because everything seems to work fine...
>>>
>>> cpufreqd_loop            : New Rule ("AC Off - Medium Battery"), applying.
>>> cpufreqd_set_profile     : Couldn't set profile "Powersave High" set for cpu0 (2400000-800000-ondemand)
>>> cpufreqd_loop            : Cannot set policy, Rule unchanged ("AC Rule").
>>>
>>> this is the culprit. Now,why is this happening... I have no idea.
>>> Actually there was a problem related to libcpufreq a few months ago.
>>> The latest cpufrequtils/libcpufreq is 005, what do you have?
>>>
>>> Best,
>>> --
>>> mattia
>>> :wq!
>>>
>>
>