From: Thomas Renninger <trenn@suse.de>
To: Len Brown <len.brown@intel.com>
Cc: Pavel Machek <pavel@suse.cz>,
Arjan van de Ven <arjanv@redhat.com>,
seife@suse.de, Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Allow userspace do something special on overtemp
Date: Wed, 11 Aug 2004 17:28:31 +0200 [thread overview]
Message-ID: <411A3B1F.3010800@suse.de> (raw)
In-Reply-To: <1092235779.5028.93.camel@dhcppc4>
Len Brown wrote:
> On Wed, 2004-08-11 at 05:06, Pavel Machek wrote:
>
>>Hi!
>>
>>
>>>>.adds possibility to react to
>>>>critical overtemp: it tries to call /sbin/overtemp, and only if
>>
>>that fails calls /sbin/poweroff.
>
>
> Does /sbin/overtemp exist anyplace, or is this a proposal
> to create it? What might it do?
save some user info, suspend, standby, extreme throttling?
It should be somehow configurable in userspace.
For my opinion it would be nicest if kernel just throws a thermal event
to /proc/acpi/event (it already does this, but immediately shuts down)
and acpid or others should decide whether shutdown/suspend/standby or
whatever should be done next.
I have a machine with a broken DSDT which sets the critical tp to 200°C,
there always must be some HW shutdown..., or do you think this is too risky?
Some other related thing:
Why are no thermal events thrown if active/passive trip points are
reached/sub-ceeded?
The only way at the moment to figure out in userspace whether the system
is actively cooled or even slowed down by throttling (passive) is by
polling /proc/acpi/thermal/*/state. Isn't the purpose of thermal events
exactly for this?
I think about a possiblity to notify user if machine is slowed down.
Thomas
next prev parent reply other threads:[~2004-08-11 15:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 8:53 Allow userspace do something special on overtemp Pavel Machek
2004-08-11 9:03 ` Arjan van de Ven
2004-08-11 9:06 ` Pavel Machek
2004-08-11 14:49 ` Len Brown
2004-08-11 14:52 ` Wichert Akkerman
2004-08-11 15:28 ` Thomas Renninger [this message]
2004-08-11 21:08 ` Kronos
2004-08-11 20:26 ` Pavel Machek
2004-08-11 9:18 ` Måns Rullgård
2004-08-11 18:22 ` Olaf Hering
[not found] ` <411A239C.8060606@blue-labs.org>
2004-08-11 20:22 ` Pavel Machek
2004-08-12 0:08 ` Dax Kelson
2004-08-12 3:29 ` Len Brown
2004-08-12 7:40 ` Pavel Machek
2004-08-12 14:28 ` Len Brown
2004-08-12 20:24 ` Pavel Machek
2004-08-12 22:51 ` Len Brown
2004-08-12 23:21 ` Pavel Machek
2004-08-12 7:35 ` Pavel Machek
2004-08-12 15:19 ` Len Brown
2004-08-12 15:16 ` Randy.Dunlap
2004-08-12 15:50 ` Stefan Seyfried
2004-08-12 17:27 ` [ACPI] " Stefan Dösinger
[not found] ` <200408121927.11277.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-08-12 22:53 ` Len Brown
2004-08-12 22:53 ` [ACPI] " Len Brown
[not found] <fa.fd8nc62.oig6ao@ifi.uio.no>
[not found] ` <fa.g1p407b.1c569pj@ifi.uio.no>
2004-08-13 4:22 ` Robert Hancock
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=411A3B1F.3010800@suse.de \
--to=trenn@suse.de \
--cc=arjanv@redhat.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=seife@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.