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]

Message-Id: <1186056386.18821.497.camel@queen.suse.de>
Date:	Thu, 02 Aug 2007 14:06:26 +0200
From:	Thomas Renninger <trenn@...e.de>
To:	Matthew Garrett <mjg59@...f.ucam.org>
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, 2007-08-02 at 12:57 +0100, Matthew Garrett wrote:
> On Thu, Aug 02, 2007 at 12:59:47PM +0100, Alan Cox wrote:
> > > I strongly suspect that the vast majority[1] of hardware that "needs" 
> > > the trip points changing works perfectly well under Windows, so it's 
> > 
> > Windows as I understand it has vendor mechanisms to allow the bits
> > shipped with the OS to override/ignore just about everything trip points
> > included. Lots of hardware that requires fixups in Linux and just works
> > in Windows is not Linux bugs but Windows magic .inf files and other
> > registry gunge done by the machine vendor. We see this in ATA, in power
> > management and elsewhere.
> 
> I've seen no evidence that this happens with thermal trip points.

WMI needed for fan control -- FSC Amilo M3438G
http://bugzilla.kernel.org/show_bug.cgi?id=5670

   Thomas

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