From: Pavel Machek <pavel@suse.cz>
To: Giuliano Pochini <pochini@denise.shiny.it>,
linux-kernel@vger.kernel.org, Micha? Roszka <michal@roszka.pl>
Subject: Re: [.config] CONFIG_THERM_WINDTUNNEL
Date: Wed, 24 Mar 2004 01:18:28 +0100 [thread overview]
Message-ID: <20040324001828.GB238@elf.ucw.cz> (raw)
In-Reply-To: <20040318120311.GD3686@ibrium.se>
Hi!
> > > Btw, I would like to get reports about how well this driver works
> > > with respect to noise reduction. I'm in particular interested
> > > in the dual 1.4 GHz model...
> >
> > The author has a dual-1.2 and I tested it on another dual-1.2. I don't
> > know if it has been tested on other mathines. The driver writes in
> > the system logs the temperature and the fan speed every time they change,
> > so you can check what it's doing (and you can unload the module if you
> > see it does something wrong).
>
> Yes I know... I wrote it :-)
>
> It should be perfectly safe to use. It contains a (very conservative)
> fail safe; if the temperature exceeds the working point by a few
> degrees, the hardware overheat protection is programmed to turn
> on the fans 100%. This works even if the kernel has locked up
> solidly.
Is it actually possible to set that hardware to self-destruct?
[ACPI notebooks have very simple hardware failsafe: if temperature
exceeds some hard limit, power is simply cut.]
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-03-24 0:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 7:21 Michał Roszka
2004-03-18 9:16 ` Giuliano Pochini
2004-03-18 11:20 ` Samuel Rydh
2004-03-18 11:27 ` Giuliano Pochini
2004-03-18 11:36 ` Michał Roszka
2004-03-18 12:03 ` Samuel Rydh
2004-03-24 0:18 ` Pavel Machek [this message]
2004-03-26 18:30 ` Samuel Rydh
2004-03-26 22:32 ` Pavel Machek
2004-03-18 16:17 ` Michał Roszka
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=20040324001828.GB238@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@roszka.pl \
--cc=pochini@denise.shiny.it \
/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®