mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Zhang Rui <rui.zhang@intel.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: regression: 2.6.32-rc8 shuts down after reaching critical temperature
Date: Wed, 25 Nov 2009 16:56:19 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0911251647000.3950@localhost.localdomain> (raw)
In-Reply-To: <20091125102857.GA28310@lst.de>

On Wed, 25 Nov 2009, Christoph Hellwig wrote:

> I recently upgraded my Thinkpad T500 from Linux 2.6.31 to Linux
> 2.6.32-rc (first -rc7 but I've also tried with -rc6 and -rc8) and when
> putting load on it, e.g. by building a kernel tree.  It shuts down soon
> with the
> 
> 	Critical temperature reached (%ld C), shutting down.\n"
> 
> printk from drivers/thermal/thermal_sys.c, where the temperature is
> usually 100C or slightly above.  The system is a Lenovo Thinkpad T500
> with a Intel Core 2 Dueo T9600 running a 32 bit kernel.

"thermal.nocrt=1" will disable the actual shutdown -- but you'll
still get the warning -- which might be helpful.  "thermal.crt=105"
would override all critical trip points to be 105, for example,
but otherwise not change any behaviour.

> I've done some attempts at bisecting it, but for most of the 2.6.32-rc
> series the system crashes during boot in ACPI code with a backtrace
> longer than the screen can display.

Hmm, I don't have a T500, but I've not seen such crashes during -rc.
Please send along your .config
Do you still get them when disabling the thinkpad-acpi driver?

Probably the most interesting place to bisect is drivers/acpi/ec.c

If you can send along the dmesg from the recent failing kernel,
plus the output from "grep . /proc/acpi/thermal_zone/*/*"
that may be helpful.

thanks,
-Len


  reply	other threads:[~2009-11-25 21:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 10:28 Christoph Hellwig
2009-11-25 21:56 ` Len Brown [this message]
2009-11-25 22:13   ` Christoph Hellwig
2009-11-25 23:07     ` Len Brown
2009-11-26 10:17       ` Christoph Hellwig
2009-11-26 10:35       ` Christoph Hellwig
2009-12-02 15:14   ` Christoph Hellwig
2009-11-26  2:23 ` Henrique de Moraes Holschuh
2009-11-26  9:52   ` Christoph Hellwig
2009-12-02 11:56     ` Thomas Renninger
2009-12-02 13:30       ` Christoph Hellwig
2009-12-02 15:07         ` Thomas Renninger
2009-12-02 15:35           ` Christoph Hellwig
2009-12-11  6:49             ` Len Brown

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=alpine.LFD.2.00.0911251647000.3950@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    /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

all inboxes | Powered by JetHome®