From: Dave Jones <davej@redhat.com>
To: Eric Sandall <eric@sandall.us>
Cc: linux-kernel@vger.kernel.org, Mattia Dongili <malattia@linux.it>
Subject: Re: cpufreq and kernel >2.6.15.6 is limited
Date: Tue, 30 May 2006 20:40:40 -0400 [thread overview]
Message-ID: <20060531004040.GI13966@redhat.com> (raw)
In-Reply-To: <447CE276.5080808@sandall.us>
On Tue, May 30, 2006 at 05:25:26PM -0700, Eric Sandall wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> It seems that any kernel on my Dell Inspiron 5100 after 2.6.15.6
> (including 2.6.17-rc5) 'breaks' my cpufreq in that up to and including
> 2.6.15.6 I can scale between 300MHz-2.4GHz, but after (starting with
> 2.6.16) I can only scale between 2.1GHz and 2.4GHz.
>
> I've attached the files, sorted by kernel, I assume may be helpful. Let
> me know if you need any more.
It may have worked in the past, but the CPU has an errata which makes
it an unsafe operation to scale below 2GHz.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-05-31 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 0:25 cpufreq and kernel >2.6.15.6 is limited Eric Sandall
2006-05-31 0:40 ` Dave Jones [this message]
[not found] <6imLa-3G2-11@gated-at.bofh.it>
[not found] ` <6in4s-44o-13@gated-at.bofh.it>
2006-05-31 3:51 ` Robert Hancock
2006-05-31 23:30 ` Eric Sandall
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=20060531004040.GI13966@redhat.com \
--to=davej@redhat.com \
--cc=eric@sandall.us \
--cc=linux-kernel@vger.kernel.org \
--cc=malattia@linux.it \
/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