From: Robert Hancock <hancockrwd@gmail.com>
To: Ray Lee <ray-lk@madrabbit.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
Dimitrios Apostolou <jimis@gmx.net>, Alex Chiang <achiang@hp.com>,
Len Brown <lenb@kernel.org>, Bjorn Helgaas <bjorn.helgaas@hp.com>,
Andrew Morton <akpm@linux-foundation.org>,
Yinghai Lu <yinghai@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: High cpu temperature with 2.6.32, bisection shows commit 69d258 (fwd)
Date: Sat, 09 Jan 2010 21:09:47 -0600 [thread overview]
Message-ID: <4B4944FB.4040008@gmail.com> (raw)
In-Reply-To: <2c0942db1001091807k542b1052s96111775d6431bd0@mail.gmail.com>
On 01/09/2010 08:07 PM, Ray Lee wrote:
> On Sat, Jan 9, 2010 at 4:42 PM, Arjan van de Ven<arjan@infradead.org> wrote:
>> basically it appears that your machine, when the kernel asks for C2,
>> exits C2 immediately again.
>>
>> The old algorithm somehow caught this and stopped asking for C2 most of
>> the time; the new algorithm doesn't see any activity and asks for C2
>> again.
>
> This change of behavior will certainly bite more users out there. Is
> there any way we can detect the systems that aren't honoring the C2
> request and limit back to C1?
That seems like it would be a better approach, rather than adding to a
DMI list which is almost certainly incomplete.. We've got too many DMI
special cases in the kernel already.
next prev parent reply other threads:[~2010-01-10 3:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LNX.2.00.1001071941470.1363@localhost.localdomain>
2010-01-08 17:15 ` High cpu temperature with 2.6.32, bisection shows commit 69d258 (fwd) Alex Chiang
2010-01-09 21:43 ` Arjan van de Ven
2010-01-09 23:55 ` Dimitrios Apostolou
2010-01-10 0:08 ` Arjan van de Ven
2010-01-10 0:32 ` Dimitrios Apostolou
2010-01-10 0:42 ` Arjan van de Ven
2010-01-10 1:05 ` Dimitrios Apostolou
2010-01-10 1:38 ` Arjan van de Ven
2010-01-13 0:07 ` Andrew Morton
2010-01-13 5:32 ` Arjan van de Ven
2010-02-10 20:51 ` Dimitrios Apostolou
2010-02-10 21:42 ` Dimitrios Apostolou
2010-02-11 4:56 ` Arjan van de Ven
2010-02-11 18:00 ` Dimitrios Apostolou
2010-02-11 21:58 ` Wojciech Ploskonka
2010-02-12 5:24 ` Arjan van de Ven
2010-02-12 21:05 ` Matthew Garrett
2010-02-18 20:27 ` Dimitrios Apostolou
2010-02-18 20:34 ` Rafael J. Wysocki
2010-02-22 16:43 ` Dimitrios Apostolou
2010-02-23 1:55 ` Arjan van de Ven
2010-02-12 5:23 ` Arjan van de Ven
2010-01-10 2:07 ` Ray Lee
2010-01-10 3:09 ` Robert Hancock [this message]
2010-01-10 4:15 ` Arjan van de Ven
2010-01-15 20:00 ` -O0 kernel " Pavel Machek
2010-01-15 20:40 ` Dimitrios Apostolou
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=4B4944FB.4040008@gmail.com \
--to=hancockrwd@gmail.com \
--cc=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=bjorn.helgaas@hp.com \
--cc=jimis@gmx.net \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-lk@madrabbit.org \
--cc=yinghai@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