linux-kernel - Re: High cpu temperature with 2.6.32, bisection shows commit 69d258 (fwd)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B4944FB.4040008@gmail.com>
Date:	Sat, 09 Jan 2010 21:09:47 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Ray Lee <ray-lk@...rabbit.org>
CC:	Arjan van de Ven <arjan@...radead.org>,
	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 01/09/2010 08:07 PM, Ray Lee wrote:
> 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?

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.
--
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/