All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Andi Kleen <ak@suse.de>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"Brown, Len" <len.brown@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
Date: Sun, 1 Apr 2007 16:30:31 +0000	[thread overview]
Message-ID: <20070401163031.GA5762@ucw.cz> (raw)
In-Reply-To: <200703311131.54704.ak@suse.de>

Hi!

> > When I run 2.6.21-rc5 + Andi's x86 patches + paravirt_ops patches, I've
> > been getting my machine shut down with critical thermal shutdown messages:
> 
> Hmm, don't think there's anything either in x86 that would touch this code.
> But can you double check with plain rc5? 
> 
> > Mar 30 23:19:03 localhost kernel: ACPI: Critical trip point
> > Mar 30 23:19:03 localhost kernel: Critical temperature reached (128 C), shutting down.
> > Mar 30 23:19:03 localhost kernel: Critical temperature reached (128 C), shutting down.
> > Mar 30 23:19:03 localhost shutdown[19417]: shutting down for system halt
> > 
> > and the machine does feel pretty hot.
> 
> Pavel has been complaining about higher power consumption on his laptop versus
> .20 too.

Yep, sometimes it takes 30W instead of 12W... Anyway, this seems to
be measurement error. Notice how acpi claims 128C. I do not think cpu
can work at 128C and hardware should kill us before cpu is that hot.

Are you running lm_sensors?

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-04-01 16:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-31  6:36 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns Jeremy Fitzhardinge
2007-03-31  9:31 ` Andi Kleen
2007-04-01 16:30   ` Pavel Machek [this message]
2007-04-01 22:44     ` Henrique de Moraes Holschuh
     [not found] ` <8f8ff01d0703310033y74421cfcl747ece1be003471@mail.gmail.com>
2007-04-01  6:28   ` Jeremy Fitzhardinge
2007-04-01 14:53     ` Matthew Garrett
2007-04-01 16:32     ` Pavel Machek
2007-04-01 22:46       ` Henrique de Moraes Holschuh
2007-04-01 23:19     ` Jeremy Fitzhardinge
2007-04-02  2:38       ` Henrique de Moraes Holschuh
2007-04-02  4:53         ` Jeremy Fitzhardinge
2007-04-03 12:34           ` Henrique de Moraes Holschuh
2007-04-03 18:35             ` Jeremy Fitzhardinge
2007-04-03 21:25               ` RusH
2007-04-04  3:46               ` Henrique de Moraes Holschuh
2007-04-01 18:57 ` Kyle Moffett
2007-04-01 21:13   ` Jeremy Fitzhardinge
2007-04-02  8:35   ` Rene Rebe
2007-04-02  8:35     ` Rene Rebe
2007-04-08 19:09     ` Valdis.Kletnieks

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=20070401163031.GA5762@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=jeremy@goop.org \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.