Dell bios + cpufreqd problem

Dell bios + cpufreqd problem

[Stijn Van Nieuwenhuyse]

I have posted a couple of monts ago a bugreport about my cpufreq problems.
I have a Dell Latitude D800 with a Dothan Pentium M processor.
When I switched to ac adapter, the frequency was locked to 600 MHz
(frequency should be within 600 MHz and 600 MHz). In the meantime this
problem has been resolved.

I have noticed approximately the same problem again while running cpufeqd.
If I only use cpufrequtils and set the governor with cpufreq-set,
everything seems to be working (when I switch to battery, the
processor is locked for approximately 15 seconds to 600 MHz, but
afterwards, everything is OK)
But if I use cpufreqd, the processor is locked to 600 MHz when I
switch to battery, and the maximum freqency does not get updated. A
workaround I have found is restarting the cpufreqd daemon.
(when I boot on battery power, cpufreq-info gives the correct output,
when I switch to ac adapter and to battery again, the problem occurs
again.

Can somebody point my to a solution for my problem?

I am running Gentoo Linux with 2.6.16-suspend2-r8 kernel.

Re: Dell bios + cpufreqd problem

[Thomas Renninger]

On Thu, 2006-08-03 at 11:32 +0200, Stijn Van Nieuwenhuyse wrote:
> I have posted a couple of monts ago a bugreport about my cpufreq problems.
> I have a Dell Latitude D800 with a Dothan Pentium M processor.
> When I switched to ac adapter, the frequency was locked to 600 MHz
> (frequency should be within 600 MHz and 600 MHz). In the meantime this
> problem has been resolved.
> 
> I have noticed approximately the same problem again while running cpufeqd.
> If I only use cpufrequtils and set the governor with cpufreq-set,
> everything seems to be working (when I switch to battery, the
> processor is locked for approximately 15 seconds to 600 MHz, but
> afterwards, everything is OK)
> But if I use cpufreqd, the processor is locked to 600 MHz when I
> switch to battery, and the maximum freqency does not get updated. A
> workaround I have found is restarting the cpufreqd daemon.
> (when I boot on battery power, cpufreq-info gives the correct output,
> when I switch to ac adapter and to battery again, the problem occurs
> again.
> 
> Can somebody point my to a solution for my problem?
> 
> I am running Gentoo Linux with 2.6.16-suspend2-r8 kernel.

This problem should be fixed in more recent kernels.

   Thomas

Re: Dell bios + cpufreqd problem

[Stijn Van Nieuwenhuyse]

I have still the same problem with kernel version 2.6.17.7

Since which kernel version should this be fixed?

On 8/3/06, Thomas Renninger <trenn@suse.de> wrote:
> On Thu, 2006-08-03 at 11:32 +0200, Stijn Van Nieuwenhuyse wrote:
> > I have posted a couple of monts ago a bugreport about my cpufreq problems.
> > I have a Dell Latitude D800 with a Dothan Pentium M processor.
> > When I switched to ac adapter, the frequency was locked to 600 MHz
> > (frequency should be within 600 MHz and 600 MHz). In the meantime this
> > problem has been resolved.
> >
> > I have noticed approximately the same problem again while running cpufeqd.
> > If I only use cpufrequtils and set the governor with cpufreq-set,
> > everything seems to be working (when I switch to battery, the
> > processor is locked for approximately 15 seconds to 600 MHz, but
> > afterwards, everything is OK)
> > But if I use cpufreqd, the processor is locked to 600 MHz when I
> > switch to battery, and the maximum freqency does not get updated. A
> > workaround I have found is restarting the cpufreqd daemon.
> > (when I boot on battery power, cpufreq-info gives the correct output,
> > when I switch to ac adapter and to battery again, the problem occurs
> > again.
> >
> > Can somebody point my to a solution for my problem?
> >
> > I am running Gentoo Linux with 2.6.16-suspend2-r8 kernel.
>
> This problem should be fixed in more recent kernels.
>
>    Thomas
>
>

Re: Dell bios + cpufreqd problem

[Thomas Renninger]

Am Fr 04.08.2006 17:45 schrieb Stijn Van Nieuwenhuyse
<stivani@gmail.com>:

> I have still the same problem with kernel version 2.6.17.7
>
> Since which kernel version should this be fixed?
>
> On 8/3/06, Thomas Renninger <trenn@suse.de> wrote:
> > On Thu, 2006-08-03 at 11:32 +0200, Stijn Van Nieuwenhuyse wrote:
> > > I have posted a couple of monts ago a bugreport about my cpufreq
> > > problems.
> > > I have a Dell Latitude D800 with a Dothan Pentium M processor.
> > > When I switched to ac adapter, the frequency was locked to 600 MHz
> > > (frequency should be within 600 MHz and 600 MHz). In the meantime
> > > this
> > > problem has been resolved.
> > >
Sorry I meant this one you already mentioned fixed.
I don't know about the cpufreqd problem.
 
   Thomas

> > > I have noticed approximately the same problem again while running
> > > cpufeqd.
> > > If I only use cpufrequtils and set the governor with cpufreq-set,
> > > everything seems to be working (when I switch to battery, the
> > > processor is locked for approximately 15 seconds to 600 MHz, but
> > > afterwards, everything is OK)
> > > But if I use cpufreqd, the processor is locked to 600 MHz when I
> > > switch to battery, and the maximum freqency does not get updated.
> > > A
> > > workaround I have found is restarting the cpufreqd daemon.
> > > (when I boot on battery power, cpufreq-info gives the correct
> > > output,
> > > when I switch to ac adapter and to battery again, the problem
> > > occurs
> > > again.
> > >
> > > Can somebody point my to a solution for my problem?
> > >
> > > I am running Gentoo Linux with 2.6.16-suspend2-r8 kernel.
> >
> > This problem should be fixed in more recent kernels.

Re: Dell bios + cpufreqd problem

[Thomas Renninger]

Am Fr 04.08.2006 17:45 schrieb Stijn Van Nieuwenhuyse
<stivani@gmail.com>:
> On 8/3/06, Thomas Renninger <trenn@suse.de> wrote:
> > On Thu, 2006-08-03 at 11:32 +0200, Stijn Van Nieuwenhuyse wrote:
> > > I have posted a couple of monts ago a bugreport about my cpufreq
> > > problems.
> > > I have a Dell Latitude D800 with a Dothan Pentium M processor.
> > > When I switched to ac adapter, the frequency was locked to 600 MHz
> > > (frequency should be within 600 MHz and 600 MHz). In the meantime
> > > this
> > > problem has been resolved.
> > >
> > > I have noticed approximately the same problem again while running
> > > cpufeqd.
> > > If I only use cpufrequtils and set the governor with cpufreq-set,
> > > everything seems to be working (when I switch to battery, the
> > > processor is locked for approximately 15 seconds to 600 MHz, but
> > > afterwards, everything is OK)
> > > But if I use cpufreqd, the processor is locked to 600 MHz when I
> > > switch to battery, and the maximum freqency does not get updated.
> > > A
> > > workaround I have found is restarting the cpufreqd daemon.
> > > (when I boot on battery power, cpufreq-info gives the correct
> > > output,
> > > when I switch to ac adapter and to battery again, the problem
> > > occurs
> > > again.
> > >
> > > Can somebody point my to a solution for my problem?
These Dells behave very strange:
if you unplug AC adapter:
    - bios limits processor to the lowest freq
      (scaling_max_freq == scaling_min_freq in /sys/devices/.../cpufreq)
    - after some seconds bios allows all freqs again
      scaling_max_freq is increased again
normally the kernel should remember the last freq told from cpufreqd if
in
userspace governor mode.
You can watch acpi processor events when the bios limits frequencies
and allows them again (last value, if it's zero all frequencies are
allowed).
Maybe cpufreqd gets confused by this?
 
    Thomas

Re: Dell bios + cpufreqd problem

[Mattia Dongili]

On Fri, Aug 04, 2006 at 11:10:04PM +0200, Thomas Renninger wrote:
> Am Fr 04.08.2006 17:45 schrieb Stijn Van Nieuwenhuyse
> <stivani@gmail.com>:
> > On 8/3/06, Thomas Renninger <trenn@suse.de> wrote:
> > > On Thu, 2006-08-03 at 11:32 +0200, Stijn Van Nieuwenhuyse wrote:
> > > > I have posted a couple of monts ago a bugreport about my cpufreq
> > > > problems.
> > > > I have a Dell Latitude D800 with a Dothan Pentium M processor.
> > > > When I switched to ac adapter, the frequency was locked to 600 MHz
> > > > (frequency should be within 600 MHz and 600 MHz). In the meantime
> > > > this
> > > > problem has been resolved.
> > > >
> > > > I have noticed approximately the same problem again while running
> > > > cpufeqd.
> > > > If I only use cpufrequtils and set the governor with cpufreq-set,
> > > > everything seems to be working (when I switch to battery, the
> > > > processor is locked for approximately 15 seconds to 600 MHz, but
> > > > afterwards, everything is OK)
> > > > But if I use cpufreqd, the processor is locked to 600 MHz when I
> > > > switch to battery, and the maximum freqency does not get updated.
> > > > A
> > > > workaround I have found is restarting the cpufreqd daemon.
> > > > (when I boot on battery power, cpufreq-info gives the correct
> > > > output,
> > > > when I switch to ac adapter and to battery again, the problem
> > > > occurs
> > > > again.
> > > >
> > > > Can somebody point my to a solution for my problem?
> These Dells behave very strange:
> if you unplug AC adapter:
> ?????? - bios limits processor to the lowest freq
> ?????????? (scaling_max_freq == scaling_min_freq in /sys/devices/.../cpufreq)
> ?????? - after some seconds bios allows all freqs again
> ?????????? scaling_max_freq is increased again
> normally the kernel should remember the last freq told from cpufreqd if
> in
> userspace governor mode.
> You can watch acpi processor events when the bios limits frequencies
> and allows them again (last value, if it's zero all frequencies are
> allowed).
> Maybe cpufreqd gets confused by this?

probably, cpufreqd gets the available frequencies at startup, if it
tries to set the higher frequency while the BIOS limits frequencies the
it can get confused. If you want to check you can enable the
"double_check" option in cpufreqd.conf, this will at lesat spit a
warning in the logs.
I'll see if I can make cpufreqd handle this Dell BIOS case.

BTW: cpufreqd doesn't use the userspace governor :)

-- 
mattia
:wq!

Re: Dell bios + cpufreqd problem

[Stijn Van Nieuwenhuyse]

I get this in the logs, while using cpufreqd 2.1.1 and the example
cpufreqd.conf which can be found on the cpufreqd website:

Aug  5 12:51:50 asterix cpufreqd: cpufreqd_set_profile     : I haven't
been able to set the chosen policy for CPU0. I set
1700000-600000-ondemand System says 600000-600000-ondemand
Aug  5 12:51:55 asterix logger: ACPI group battery / action battery is
not defined
Aug  5 12:51:55 asterix logger: ACPI group battery / action battery is
not defined
Aug  5 12:52:06 asterix logger: ACPI group processor / action
processor is not defined
Aug  5 12:52:40 asterix cpufreqd: cpufreqd_set_profile     : I haven't
been able to set the chosen policy for CPU0. I set
1700000-1700000-performance System says 1700000-600000-performance
Aug  5 12:52:40 asterix logger: ACPI group ac_adapter / action
ac_adapter is not defined
Aug  5 12:52:40 asterix logger: ACPI group battery / action battery is
not defined
Aug  5 12:52:47 asterix logger: ACPI group battery / action battery is
not defined
Aug  5 12:52:47 asterix logger: ACPI group battery / action battery is
not defined


On 8/5/06, Mattia Dongili <malattia@linux.it> wrote:
> On Fri, Aug 04, 2006 at 11:10:04PM +0200, Thomas Renninger wrote:
> > Am Fr 04.08.2006 17:45 schrieb Stijn Van Nieuwenhuyse
> > <stivani@gmail.com>:
> > > On 8/3/06, Thomas Renninger <trenn@suse.de> wrote:
> > > > On Thu, 2006-08-03 at 11:32 +0200, Stijn Van Nieuwenhuyse wrote:
> > > > > I have posted a couple of monts ago a bugreport about my cpufreq
> > > > > problems.
> > > > > I have a Dell Latitude D800 with a Dothan Pentium M processor.
> > > > > When I switched to ac adapter, the frequency was locked to 600 MHz
> > > > > (frequency should be within 600 MHz and 600 MHz). In the meantime
> > > > > this
> > > > > problem has been resolved.
> > > > >
> > > > > I have noticed approximately the same problem again while running
> > > > > cpufeqd.
> > > > > If I only use cpufrequtils and set the governor with cpufreq-set,
> > > > > everything seems to be working (when I switch to battery, the
> > > > > processor is locked for approximately 15 seconds to 600 MHz, but
> > > > > afterwards, everything is OK)
> > > > > But if I use cpufreqd, the processor is locked to 600 MHz when I
> > > > > switch to battery, and the maximum freqency does not get updated.
> > > > > A
> > > > > workaround I have found is restarting the cpufreqd daemon.
> > > > > (when I boot on battery power, cpufreq-info gives the correct
> > > > > output,
> > > > > when I switch to ac adapter and to battery again, the problem
> > > > > occurs
> > > > > again.
> > > > >
> > > > > Can somebody point my to a solution for my problem?
> > These Dells behave very strange:
> > if you unplug AC adapter:
> > ?????? - bios limits processor to the lowest freq
> > ?????????? (scaling_max_freq == scaling_min_freq in
> /sys/devices/.../cpufreq)
> > ?????? - after some seconds bios allows all freqs again
> > ?????????? scaling_max_freq is increased again
> > normally the kernel should remember the last freq told from cpufreqd if
> > in
> > userspace governor mode.
> > You can watch acpi processor events when the bios limits frequencies
> > and allows them again (last value, if it's zero all frequencies are
> > allowed).
> > Maybe cpufreqd gets confused by this?
>
> probably, cpufreqd gets the available frequencies at startup, if it
> tries to set the higher frequency while the BIOS limits frequencies the
> it can get confused. If you want to check you can enable the
> "double_check" option in cpufreqd.conf, this will at lesat spit a
> warning in the logs.
> I'll see if I can make cpufreqd handle this Dell BIOS case.
>
> BTW: cpufreqd doesn't use the userspace governor :)
>
> --
> mattia
> :wq!
>

Re: Dell bios + cpufreqd problem

[Mattia Dongili]

On Sat, Aug 05, 2006 at 12:57:33PM +0200, Stijn Van Nieuwenhuyse wrote:
> I get this in the logs, while using cpufreqd 2.1.1 and the example
> cpufreqd.conf which can be found on the cpufreqd website:
> 
> Aug  5 12:51:50 asterix cpufreqd: cpufreqd_set_profile     : I haven't
> been able to set the chosen policy for CPU0. I set
> 1700000-600000-ondemand System says 600000-600000-ondemand
> Aug  5 12:51:55 asterix logger: ACPI group battery / action battery is
> not defined
> Aug  5 12:51:55 asterix logger: ACPI group battery / action battery is
> not defined
> Aug  5 12:52:06 asterix logger: ACPI group processor / action
> processor is not defined
> Aug  5 12:52:40 asterix cpufreqd: cpufreqd_set_profile     : I haven't
> been able to set the chosen policy for CPU0. I set
> 1700000-1700000-performance System says 1700000-600000-performance
> Aug  5 12:52:40 asterix logger: ACPI group ac_adapter / action
> ac_adapter is not defined
> Aug  5 12:52:40 asterix logger: ACPI group battery / action battery is
> not defined
> Aug  5 12:52:47 asterix logger: ACPI group battery / action battery is
> not defined
> Aug  5 12:52:47 asterix logger: ACPI group battery / action battery is
> not defined

It seems to be as Thomas diagnosed.
Out of curiosity, which cpufrequtils version do you have? see
cpufreq-info full output, if you don't have version 002, please upgrade
it and retry.

Anyway I'll try to fix the 15secs delay in cpufreqd 2.2.0, the failure
to se a new policy should be better handled.
Stijin, could you try out some patches I'd forward you privately later?

Thanks
-- 
mattia
:wq!

Re: Dell bios + cpufreqd problem

[Stijn Van Nieuwenhuyse]

I was using cpufrequtils version 001, but have upgraded to 002 now.
Everything seems to be the same like before the upgrade.

I would like to try your patches.
Do you need some more info from me?

Greets,

Stijn

On 8/5/06, Mattia Dongili <malattia@linux.it> wrote:

>
> It seems to be as Thomas diagnosed.
> Out of curiosity, which cpufrequtils version do you have? see
> cpufreq-info full output, if you don't have version 002, please upgrade
> it and retry.
>
> Anyway I'll try to fix the 15secs delay in cpufreqd 2.2.0, the failure
> to se a new policy should be better handled.
> Stijin, could you try out some patches I'd forward you privately later?
>
> Thanks
> --
> mattia
> :wq!
>