ACPI sets cpufreq to lowest after some work

[sithmein]

Hi,

I have a very strange behaviour on my Dell Latitude D600 mit a 1.7 GHz Pentium M. I use the ondemand cpufreq governor and the temperature stays at about 50 without much work. Then if I give it some work the temperature slowly rises to about 65-70 degrees. This works for maybe 10 minutes and then suddenly the frequency is set back to 600 MHz although the temperature is still only about 70 degrees (sometimes even less). ACPI at the same moment gives the following message:

Code: Select all

Apr 11 21:50:45 [kernel] acpi_utils-0287 [03] evaluate_integer      : Return value [3567]
Apr 11 21:50:48 [kernel] Execute Method: [\_GPE._L1D] (Node c20f5c28)
Apr 11 21:50:48 [logger] ACPI group processor / action processor is not defined

The acpid.log shows

Code: Select all

[Tue Apr 11 21:50:48 2006] received event "processor CPU0 00000080 00000007"
[Tue Apr 11 21:50:48 2006] executing action "/etc/acpi/default.sh processor CPU0 00000080 00000007"
[Tue Apr 11 21:50:48 2006] BEGIN HANDLER MESSAGES
[Tue Apr 11 21:50:48 2006] END HANDLER MESSAGES
[Tue Apr 11 21:50:48 2006] action exited with status 0
[Tue Apr 11 21:50:48 2006] completed event "processor CPU0 00000080 00000007"
[Tue Apr 11 22:01:58 2006] received event "processor CPU0 00000080 00000002"
[Tue Apr 11 22:01:58 2006] executing action "/etc/acpi/default.sh processor CPU0 00000080 00000002"
[Tue Apr 11 22:01:58 2006] BEGIN HANDLER MESSAGES
[Tue Apr 11 22:01:58 2006] END HANDLER MESSAGES
[Tue Apr 11 22:01:58 2006] action exited with status 0
[Tue Apr 11 22:01:58 2006] completed event "processor CPU0 00000080 00000002"

Now there is now way to set the frequency to anything higher than 600MHz (scaling_max_freq has been set to 600) even with any other governor or if the system has cooled down to 50 degrees. Most of the times a reboot is necessary to get to full speed again, sometimes after about 10 minutes it magically offers 1700MHz again.
Everything works perfectly fine with ACPI, so no error message while booting or other strange things. Has anyone a clue where this comes from?

Regards,

Thorsten

[sonicbhoc]

performance governer is the full speed one. powersave is the low speed one. If you use KDE and have all the right packages emerged and the correct kernel support (apm, acpi, emerge klaptop, have governers installed into kernel), you can use the laptop configuration screen to tell it to automatically switch governers depending on your situation.

[sithmein]

performance governer is the full speed one. powersave is the low speed one. If you use KDE and have all the right packages emerged and the correct kernel support (apm, acpi, emerge klaptop, have governers installed into kernel), you can use the laptop configuration screen to tell it to automatically switch governers depending on your situation.

I know, but that's not the problem at all. The problem ist, that "someone" is cutting down the processor to 600MHz without any obvious reason after it has worked hard for some minutes. I only wanted to say, that this is _not_ a governor issue, as none of the governors is able to increase the speed after is has gone down to 600MHz.

[OneInchMen]

I only use cpufrequtils and the 'ondemand' governer.

My CPU defaults to it's lowest frequency and when needed (>80% cpu utilization) the governer switches my cpu to full processing power. As soon as there is no more need for that power, the governer switches back to the lowest frequency...

...and thus lowering the consumed power and thermal dispension of the CPU, with full power when needed...

-H-

[hplehn]

I have exactly the same problem on a D600: After some work /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq falls to 600000 and can not be increased to 1700000 any more. In my understanding scaling_max_freq shouldn't be changed at all? BTW, cpuinfo_max_freq stays at 1700000.

The problem started about two weeks ago. Before, I was able to switch scaling governor and frequencies using klaptop and the behaviour was as expected (using scaling_governor ondemand the cpu-frequency was set automatically according to system load). It could be related to the upgrade of kde to 3.5.3.

As a workaround it is possible to use the command 'cpufreq-set -u 1700000' (package cpufrequtils) to increase the maximum frequency.

Beste regards
H. Plehn