From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
Knut Petersen <Knut_Petersen@t-online.de>,
linux-kernel@vger.kernel.org, trenn@suse.de, pavel@ucw.cz,
mjg59@srcf.ucam.org, lenb@kernel.org
Subject: Re: 2.6.22 regression: thermal trip points
Date: Thu, 2 Aug 2007 14:04:42 +0100 [thread overview]
Message-ID: <20070802140442.62c56dbd@the-village.bc.nu> (raw)
In-Reply-To: <20070802120511.GA440@one.firstfloor.org>
> > 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.
> You'll just end up with "Linux destroyed my laptop" headlines all
> over the internet and rightfully very annoyed users.
You have to systematically sit down and tweak your machine.
> The philosophy didn't include physically destroying hardware
> as far as I know.
It most certainly did. With safety checks you could override.
> > As root you can erase the bios,
> We don't ship the devbios driver for good reasons.
Thats debatably a bad reason (the user space API is wrong thats all), and
one thats totally inconsistent with some of the other drivers we do ship.
> > lock the hard disk with a random
> > password, reflash your video card ....
>
> That all requires significant effort and custom software. It's not that we
> have a one liner echo destroy > /sys/.../flash-bios.
Well you can do the hard disk one in one line of perl, the video card one
in a small bit of C. And this merely makes the argument that raising the
trip points should be harder.
Alan
next prev parent reply other threads:[~2007-08-02 12:58 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 8:40 Knut Petersen
2007-08-02 8:52 ` Andrew Morton
2007-08-02 10:48 ` Andi Kleen
2007-08-02 11:00 ` Alan Cox
2007-08-02 12:05 ` Andi Kleen
2007-08-02 13:04 ` Alan Cox [this message]
2007-08-02 13:16 ` Andi Kleen
2007-08-02 15:57 ` Pavel Machek
2007-08-02 18:38 ` Andi Kleen
2007-08-02 18:40 ` Matthew Garrett
2007-08-03 11:16 ` Thomas Renninger
2007-08-03 18:59 ` Len Brown
2007-08-06 9:55 ` Pavel Machek
2007-08-07 18:58 ` Len Brown
2007-08-07 21:49 ` Pavel Machek
2007-08-13 12:30 ` Pavel Machek
2007-08-02 15:55 ` Pavel Machek
2007-08-02 9:42 ` Thomas Renninger
2007-08-02 9:45 ` Adrian Schröter
2007-08-02 9:58 ` Thomas Renninger
2007-08-02 11:02 ` Alan Cox
2007-08-02 11:13 ` Matthew Garrett
2007-08-02 11:45 ` Thomas Renninger
2007-08-02 11:56 ` Matthew Garrett
2007-08-02 12:42 ` Thomas Renninger
2007-08-02 12:55 ` Matthew Garrett
2007-08-02 11:59 ` Alan Cox
2007-08-02 11:57 ` Matthew Garrett
2007-08-02 12:06 ` Thomas Renninger
2007-08-02 12:15 ` Matthew Garrett
2007-08-02 12:35 ` Thomas Renninger
2007-08-02 12:47 ` Matthew Garrett
2007-08-02 21:56 ` Len Brown
2007-08-02 11:32 ` Knut Petersen
2007-08-02 12:06 ` Andi Kleen
2007-08-02 13:06 ` Alan Cox
2007-08-02 16:07 ` Pavel Machek
2007-08-02 19:25 ` Krzysztof Halasa
2007-08-02 21:56 ` Len Brown
2007-08-03 11:43 ` Renato S. Yamane
2007-08-03 18:35 ` Len Brown
2007-08-03 12:53 ` Knut Petersen
2007-08-03 18:30 ` Len Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070802140442.62c56dbd@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Knut_Petersen@t-online.de \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pavel@ucw.cz \
--cc=trenn@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®