From: Thomas Renninger <trenn@suse.de>
To: Stijn Van Nieuwenhuyse <stivani@gmail.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Dell bios + cpufreqd problem
Date: Thu, 03 Aug 2006 14:09:52 +0200 [thread overview]
Message-ID: <1154606992.4302.496.camel@queen.suse.de> (raw)
In-Reply-To: <e29f4c3f0608030232n695737f6yd249b24f059f5c6e@mail.gmail.com>
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
next prev parent reply other threads:[~2006-08-03 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 9:32 Dell bios + cpufreqd problem Stijn Van Nieuwenhuyse
2006-08-03 12:09 ` Thomas Renninger [this message]
2006-08-04 15:45 ` Stijn Van Nieuwenhuyse
2006-08-04 20:53 ` Thomas Renninger
2006-08-04 21:10 ` Thomas Renninger
2006-08-05 8:28 ` Mattia Dongili
2006-08-05 10:57 ` Stijn Van Nieuwenhuyse
2006-08-05 11:52 ` Mattia Dongili
2006-08-05 16:40 ` Stijn Van Nieuwenhuyse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1154606992.4302.496.camel@queen.suse.de \
--to=trenn@suse.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=stivani@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox