[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c0942db1001091807k542b1052s96111775d6431bd0@mail.gmail.com>
Date: Sat, 9 Jan 2010 18:07:14 -0800
From: Ray Lee <ray-lk@...rabbit.org>
To: Arjan van de Ven <arjan@...radead.org>
Cc: Dimitrios Apostolou <jimis@....net>, Alex Chiang <achiang@...com>,
Len Brown <lenb@...nel.org>,
Bjorn Helgaas <bjorn.helgaas@...com>,
Andrew Morton <akpm@...ux-foundation.org>,
Yinghai Lu <yinghai@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: High cpu temperature with 2.6.32, bisection shows commit 69d258
(fwd)
On Sat, Jan 9, 2010 at 4:42 PM, Arjan van de Ven <arjan@...radead.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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists