From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 16072] [HP Pavilion dm1-1110ev] Cpufreq doesn't work at all ( Intel Celeron U2300 )
Date: Sun, 24 Oct 2010 10:03:45 GMT [thread overview]
Message-ID: <201010241003.o9OA3j7t023325@demeter2.kernel.org> (raw)
In-Reply-To: <bug-16072-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16072
--- Comment #21 from Patrick Viane <patrickviane@yahoo.com> 2010-10-24 10:03:34 ---
After a deeper look into the link provided by Thomas Renninger in Comment #14,
and into the datasheet (both of which I should have done in the first place
instead of skimming them, sorry for that), it's clear that an important point
is the reference to the datasheet, page 30, note 10, which states: "SU2300
processor operates at same core frequency in HFM and LFM" (HFM = Highest
Frequency Mode, LFM = Lowest Frequency Mode). *If* the processor doesn't have
a Super Low Frequency Mode (SuperLFM) as stated on page 26 of the datasheet
(not really clear), the processor would indeed run at only one frequency. So
it looks like "Enhanced Intel SpeedStep Technology" doesn't automatically imply
frequency scaling.
Without SuperLFM, voltage scaling and/or C-states seem to be the best
candidates to explain why battery life under Windows was longer than under
Linux (but I'm not the expert here).
The question in my previous comment about thermal management in situations
where one is not able to load p4-clockmod as a "driver of last resort", stems
from the following remark at https://patchwork.kernel.org/patch/7786/ and
similar comments elsewhere:
> This is one reason why in .30 the user interface for p4-clockmod is disabled.
> It'll only get throttled when ACPI goes into OMG I'M OVERHEATING mode,
> and ramp back up once it cools off.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2010-10-24 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16072-12968@https.bugzilla.kernel.org/>
2010-08-02 18:57 ` [Bug 16072] [HP Pavilion dm1-1110ev] Cpufreq doesn't work at all ( Intel Celeron U2300 ) bugzilla-daemon
2010-10-22 15:34 ` bugzilla-daemon
2010-10-22 19:37 ` bugzilla-daemon
2010-10-22 21:09 ` bugzilla-daemon
2010-10-22 21:49 ` bugzilla-daemon
2010-10-22 22:00 ` bugzilla-daemon
2010-10-22 23:52 ` bugzilla-daemon
2010-10-23 6:03 ` bugzilla-daemon
2010-10-23 11:28 ` bugzilla-daemon
2010-10-24 10:03 ` bugzilla-daemon [this message]
2010-10-24 23:10 ` bugzilla-daemon
2010-10-25 17:34 ` bugzilla-daemon
2010-10-28 15:31 ` 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=201010241003.o9OA3j7t023325@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