Messages in this thread |  | | | From | Frans Pop <> | | Subject | Re: 2.6.32-rc5: unexpected thermal shutdown? | | Date | Tue, 3 Nov 2009 20:12:52 +0100 |
On Tuesday 03 November 2009, you wrote: > pavel@amd:~$ grep . /proc/acpi/thermal_zone/*/* > /proc/acpi/thermal_zone/THM0/cooling_mode:<setting not supported> > /proc/acpi/thermal_zone/THM0/polling_frequency:<polling disabled> > /proc/acpi/thermal_zone/THM0/state:state: ok > /proc/acpi/thermal_zone/THM0/temperature:temperature: 58 C > /proc/acpi/thermal_zone/THM0/trip_points:critical (S5): 127 C
Right, so this zone does not have a passive trip point. If it reaches critical temp before THM1, it would cause exactly what you saw.
Try recreating the same situation while watching the temp for both thermal zones.
The solution would be to force a passive cooling point for this zone using for example (X could be either 0 or 1; depends on order in which zones are defined in BIOS): echo 95000 > /sys/class/thermal/thermal_zoneX/passive Should work with current kernels, but Andrew has a patch set from me for .33 that has some improvements: http://lkml.org/lkml/2009/10/26/41.
> 128C means "slightly fake" temperature sensor. It seems that it just > produces 128 in THM0 when temperature exceeds some other limit.
Hmm. If THM0 does not have *any* other values between 58 and 128 then the above will probably not work. If it makes a few jumps, you should adjust the trip value in my example accordingly. For my HP2510p the 2 zones that have no passive trip point in BIOS luckily do have a "real" sensor.
Cheers, FJP
|  |