From: Pavel Machek <pavel@ucw.cz>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.32-rc5: unexpected thermal shutdown?
Date: Tue, 3 Nov 2009 20:17:34 +0100 [thread overview]
Message-ID: <20091103191734.GD3312@elf.ucw.cz> (raw)
In-Reply-To: <200911032012.53556.elendil@planet.nl>
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
prev parent reply other threads:[~2009-11-03 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 10:57 2.6.32-rc5: unexpected thermal shutdown? Pavel Machek
2009-11-03 17:25 ` Frans Pop
2009-11-03 18:37 ` Pavel Machek
2009-11-03 19:12 ` Frans Pop
2009-11-03 19:17 ` Pavel Machek [this message]
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=20091103191734.GD3312@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox