From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 14771] "ondemand" never raises frequency on an Intel Core2 Due (T9900) in a recent Dell E6500
Date: Fri, 12 Nov 2010 19:09:38 GMT [thread overview]
Message-ID: <201011121909.oACJ9clT016169@demeter2.kernel.org> (raw)
In-Reply-To: <bug-14771-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=14771
vyncere <vyncere@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vyncere@gmail.com
--- Comment #23 from Thomas Renninger <trenn@suse.de> 2010-06-28 15:43:23 ---
> note that when i'm plugged in to my 90W power supply, the ondemand gov works
> fine.
Ah yes..., this really isn't a kernel bug. Can someone with enough privileges
(the reporter?), close it. You should also modify the title, so that others get
a quick idea that this is about power supply and whether their problem is
related...
> I on the other hand am working with a 4-5 year old Pentium IV Prescott
I expect it doesn't support SpeedStep at all (without Enhanced you only got 2
steps), but I am not entirely sure. Theoretically you could read up the Intel
docs whether it's supported at all. If, you also could try some rudimentary
things in userspace, in this case it's IO and not MSR driven. But instead of
wasting the time to finally find out that Pentium IV wasted power like hell and
there is not much you can do about that, you better invest some bugs into a new
cheap board and a new processor...
--- Comment #24 from vyncere <vyncere@gmail.com> 2010-11-12 19:09:35 ---
Hi all,
My personal experience may help too. I had the same problem with my Thinkpad
T410 (Core i5 520 M). With kernel 2.6.36, I had to set the "Performance"
Profile in my BIOS, for AC/DC power and Battery mode, instead of "Power-saving
/ Balanced / etc.". After that, the bios_limit managed to reach the max value,
2.40 GHz instead of 1.20GHz, and cpufreq managed to do its job.
But it's not the only thing. This observation was made with my battery plugged
on my laptop, with AC/DC power. Another day, without battery, I was very
surprised when I saw that the bios_limit was still stuck to 1.20GHz (!). I
think it's a BIOS related problem, very similar to the previous power supply
case. But fortunately, "processor.ignore_ppc=1" boot parameter does perfectly
the job. (Phew !!!)
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next parent reply other threads:[~2010-11-12 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14771-12968@https.bugzilla.kernel.org/>
2010-11-12 19:09 ` bugzilla-daemon [this message]
2010-11-15 12:04 ` [Bug 14771] "ondemand" never raises frequency on an Intel Core2 Due (T9900) in a recent Dell E6500 bugzilla-daemon
2011-04-22 2:30 ` [Bug 14771] "ondemand" never raises frequency if smaller power supply is used (60w vs. 90w) -- " bugzilla-daemon
2011-07-30 4:56 ` bugzilla-daemon
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=201011121909.oACJ9clT016169@demeter2.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@vger.kernel.org \
/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