Messages in this thread | | | Date | Tue, 3 Nov 2009 20:17:34 +0100 | From | Pavel Machek <> | Subject | Re: 2.6.32-rc5: unexpected thermal shutdown? |
| |
On Tue 2009-11-03 20:12:52, Frans Pop wrote: > 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.
Well, I'll try _not_ to recreate this situation :-). If it starts happening too often, I'll play with passive limits. But... thanks!
> > 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
It has some values between 58 and 128, but I'm not sure how many.
Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
| |