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:	Fri, 03 Aug 2007 13:16:58 +0200
From:	Thomas Renninger <trenn@...e.de>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Pavel Machek <pavel@....cz>, Alan Cox <alan@...rguk.ukuu.org.uk>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Knut Petersen <Knut_Petersen@...nline.de>,
	linux-kernel@...r.kernel.org, mjg59@...f.ucam.org, lenb@...nel.org
Subject: Re: 2.6.22 regression: thermal trip points

On Thu, 2007-08-02 at 20:38 +0200, Andi Kleen wrote:
> On Thu, Aug 02, 2007 at 03:57:54PM +0000, Pavel Machek wrote:
> > On Thu 2007-08-02 15:16:22, Andi Kleen wrote:
> > > On Thu, Aug 02, 2007 at 02:04:42PM +0100, Alan Cox wrote:
> > > > > > Set a taint flag, 
> > > > > That's hardly any useful if the machine is dead afterwards.
> > > > 
> > > > It won't be the hardware will do a failsafe shutdown first.
> > > 
> > > Not necessarily. At SUSE we had at least one broken laptop
> > > with wrong trip points. The machine ran very hot for some time
> > > and afterwards the hard disk was dead.
> > 
> > Yes, but it was original BIOS trip points that were wrong. And yes,
> > its failsafe shutdown was too late. At least lowering the trip points
> > would allow me to run it safely.
> 
> I have no problem with lowering them (in fact I proposed this
> to Thomas as a possible solution at some point). Just rising 
> is a bad idea.

Ok.
If nobody screams (especially Len who has to accept this in the end, I
don't want to do work for nothing..), I'll try an implementation that:
  - Allows lowering trip points
  - If BIOS modifies trip points, the overridden ones might also
    get lowered if they are even lower
  - Allow the definition of a passive trip point (with some default
    values for hysteresis), even if the thermal zone does not
    provide one

If we have something like this, we could still discuss a config option,
that also allows to increase trip points, marking it with "If you set
this you can destroy your machine, you have been warned...". While this
would not be an option for distributions to compile in, some people may
come around the biggest hammer -> overriding DSDT.

I cannot promise, but I try to get this for 2.6.24.

   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/