Pavel Machek wrote:
In-kernel ACPI will happily call /sbin/halt for you in case of system overheat.
Watch /proc/acpi/thermal/*/*
Thank you for this information - when digging through the sources I was able to locate the responsible lines.
To get behind these shutdowns I added some lines dealing with thermal events, mainly cat'ting /proc/acpi/thermal_zone/THRx/temperature, to the script /usr/sbin/acpid_proxy.
This script is called by acpid with the text of the occured event as parameter (The SuSE-way of handling acpi-events).
Three days ago another shutdown occured, showing two things:
1) I made some mistake when extending acpid_proxy. But the temperatures were logged.
2) The temperature logged are far below the trip-points for a shutdown. (see the attached files)
The trip-point for my thermal zone THRS is 92C, the actual temperature when the event occured was 46C (logged)
What does this mean?
Any hints are welcome
Regards,
Maier Gerfried
Please mind the attached files:
acpid - a cut from the acpid-logfile
THRC-trip_points - /proc/acpi/thermal_zone/THRC/trip_points
THRS-trip_points - /proc/acpi/thermal_zone/THRS/trip_points
The System is an Acer Travelmate Notebook with
Kernel 2.4.22 acpi and the
preemptive-patch (although I do not think that preemptive has anything todo with my problems - the shuthdowns already occured when I knew nothing about preemptive, meaning with vanilla 2.4.xx + acpi-patch)
Base-system: SuSE 8.1