From: Aaron Lehmann <aaronl@vitelus.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: ACPI mailing list <acpi-devel@lists.sourceforge.net>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Tell user when ACPI is killing machine
Date: Fri, 28 Nov 2003 14:01:40 -0800 [thread overview]
Message-ID: <20031128220140.GB1714@vitelus.com> (raw)
In-Reply-To: <20031128145558.GA576@elf.ucw.cz>
On Fri, Nov 28, 2003 at 03:55:58PM +0100, Pavel Machek wrote:
> On critical overheat (or perceived critical overheat -- acpi bioses on
> some notebooks apparently report bogus values from time to time),
> kernel itself calls /sbin/halt *without telling anything*. User can
> not see anything, his machine just shuts down cleanly. Bad.
Sorry if this is a bit OT, but why doesn't ACPI scale the CPU
frequency back instead of shutting down? This is what APM does on my
laptop (presumably in the BIOS) but when I enable ACPI the machine
shuts down whenever I do something CPU intensive (yes; it's a poorly
designed laptop). I have cpufreq support (cpufreq: P4/Xeon(TM) CPU
On-Demand Clock Modulation available). Has this kind of thing been
added since I last tried it, or do I actually have to actively set up
cpufreq in user space to get thermally-induced clock modulation? Or is
not even possible with the current state of things?
next prev parent reply other threads:[~2003-11-28 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 14:55 Tell user when ACPI is killing machine Pavel Machek
[not found] ` <20031128145558.GA576-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2003-11-28 16:52 ` Pavel Machek
2003-11-28 22:01 ` Aaron Lehmann [this message]
2003-11-28 23:43 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 5:27 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720BFD-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-04 9:54 ` Pavel Machek
2003-12-04 10:01 ` Damien Sandras
2003-12-04 10:56 ` Pavel Machek
2003-12-04 11:24 ` Måns Rullgård
2003-12-08 3:26 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C05-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-09 11:25 ` Pavel Machek
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=20031128220140.GB1714@vitelus.com \
--to=aaronl@vitelus.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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