On Tue, 30 Mar 2010, Thomas Renninger wrote:
> My idea is to also shutdown the system on _HOT by default,
> the same way as done if _CRT is exceeded as long as no userspace
> explicitly set a sysfs (only one file set by thermal_sys.c somewhere
> in /sys?).
> Background is that S4 needs some setup (e.g. swap) or userspace hooks
> to make sure S4 succeeds and everything (network, whatever...) is set
> up correctly afterwards.
>
> Requirement for the userspace tool setting the "do not shutdown if a
> hot thermal event happened" would be:
> - Fetch the thermal hot event
> - Reliably power off the system (shutdown if S4 did not succeed)
> - ...
>
> Comments?
ThinkPads have specific alarms that would benefit from a generic interface
to report the above stuff to userspace, and to kick a S3/S4/S5 transition if
userspace fails to do something about it.
These are:
1. Emergency Thermal alarms (Lenovo tells me we should enter S3 or S4)
- Battery alarm (very dangerous, risk of Lithium fire)
- Sensor alarm (less dangerous, risk of permanent hardware damage)
2. Wakeup from S3 because the battery is nearly empty (enter S4 or S5)
- Pretty much guarantees the user is !@#$#@ if we don't act on it,
since it will cause a mess even on a hibernate-to-S3 setup
if the user didn't tell the BIOS he does "RediSafe"...
It would be nice to have flags to tell userspace if we want any sleep, or if
we need S4/S5.
It would also be nice to have a generic way to deliver these alarms,
thinkpads have pre-alarms that should be used to notify the user before
things get too dire...
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
