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: Sat, 23 Oct 2010 06:03:36 GMT [thread overview]
Message-ID: <201010230603.o9N63a6n023784@demeter1.kernel.org> (raw)
In-Reply-To: <bug-16072-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16072
--- Comment #19 from Patrick Viane <patrickviane@yahoo.com> 2010-10-23 06:03:16 ---
Same sentiment here (sadness) as expressed by Markos Chandras in Comment #17.
The CPU is clearly capable of frequency scaling (and voltage scaling).
Please consider the following:
> Comment #14
> It came out this type of CPU is not speedstep capable
Somewhat misleading: the CPU is "Enhanced Intel SpeedStep® Technology" capable,
and should (imo) be handled by the acpi-cpufreq driver.
> You might want to verify with the Intel CPU sheet the guy found.
I did: please see for yourself at
http://www.intel.com/design/mobile/datashts/321111.pdf
> Comment #15
> The machine is a standard HP Pavilion A630N machine
Incorrect: see discription of bug: "[HP Pavilion dm1-1110ev] Cpufreq doesn't
work at all ( Intel Celeron U2300 )". AFAIK this notebook was introduced in Q1
2010. (As were many other notebooks using this CPU)
> Comment #16
> Markos, the CPU is very old (~5+ years).
Incorrect: launch date of this CPU was Q3 '09; please see:
http://ark.intel.com/Product.aspx?id=42779
These CPU's are still being sold/implemented.
> Comment #18
> Sigh, a p4_clockmod discussion again.
Yes, I think the correct discussion should mostly be about acpi-cpufreq.
But just to make certain: in case of overheating, where does linux control the
thermal protection of these CPU's? Especially now, WITHOUT drivers? If the
answer here is p4_clockmod (or acpi-cpufreq), one might even think about
raising the importance of this bug, considering the potential overheating
isues, which are of course not uncommon in notebooks.
> machine is a
> > standard HP Pavilion A630N machine (presumably which hundreds of thousands
> > were manufactured in the 2003-2005 time frame).
> Which does not support CPU frequency scaling, where is the problem?
> The CPU itself simply cannot do it.
I hope it is clear by now that the SU2300 in the HP Pavilion dm1-1110ev *DOES*
support CPU frequency scaling.
> Hmm, this machine does not even support C2...
Luckily for us, the SU2300 supports C1/AutoHALT, C1/MWAIT, C2, C3 and C4,
otherwise we would all (presumably) be forced to go back to running Windows on
our notebooks.
I hope this bug can be truly resolved, if not, can anyone point me to the
"documentation" with which to "Resolve" this bug, as mentioned in the bug
"Status"?
Thanks.
--
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-23 6: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 [this message]
2010-10-23 11:28 ` bugzilla-daemon
2010-10-24 10:03 ` bugzilla-daemon
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=201010230603.o9N63a6n023784@demeter1.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.