linux-kernel - Re: 2.6.22 regression: thermal trip points

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 2 Aug 2007 13:47:29 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Thomas Renninger <trenn@...e.de>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Adrian Schröter <adrian@...e.de>,
	Knut Petersen <Knut_Petersen@...nline.de>,
	linux-kernel@...r.kernel.org, Andrew Morton <akpm@...l.org>,
	pavel@....cz, lenb@...nel.org, "Zhang, Rui" <rui.zhang@...el.com>,
	Jean Delvare <khali@...ux-fr.org>,
	Alexey Starikovskiy <aystarik@...il.com>
Subject: Re: 2.6.22 regression: thermal trip points

On Thu, Aug 02, 2007 at 02:35:18PM +0200, Thomas Renninger wrote:
> On Thu, 2007-08-02 at 13:15 +0100, Matthew Garrett wrote:
> > That machine has no active thermal trip points, so I'm not sure how it's 
> > relevant here.
> >From above: "Windows as I understand it has vendor mechanisms to..."
> Maybe thermal trip points are not influenced here, it's at least about
> thermal management and another prove that we cannot just try to copy
> Windows behavior, but need to provide workarounds wherever possible.

There's absolutely no evidence in the bug log there that the user's 
problems are in any way due to Windows-specific code. The SetSilentMode 
stuff is an additional item of functionality that underclocks various 
bits of hardware, not one that's actually required for the platform to 
function correctly.
-- 
Matthew Garrett | mjg59@...f.ucam.org
-
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/