From: Christoph Hellwig <hch@lst.de>
To: Len Brown <lenb@kernel.org>
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 23:13:32 +0100 [thread overview]
Message-ID: <20091125221332.GA24173@lst.de> (raw)
In-Reply-To: <alpine.LFD.2.00.0911251647000.3950@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2200 bytes --]
On Wed, Nov 25, 2009 at 04:56:19PM -0500, Len Brown wrote:
> "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.
Well, I suspect the warnings are there for a reason, e.g. with 2.6.32-rc
I also hear the fan regularly while I've almost never done before. So I
guess the reason for it is that throtteling might have problems.
> > 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
Attached.
> Do you still get them when disabling the thinkpad-acpi driver?
I'll try. This is my main work machine (and I'm travelling right now),
so any sort of bisection and testing will take a while..
> Probably the most interesting place to bisect is drivers/acpi/ec.c
>
> If you can send along the dmesg from the recent failing kernel,
That is failing to boot, or the 2.6.32-rc8 kernel? No chance to capture
the dmesg of the one failing to boot unfortunately..
> plus the output from "grep . /proc/acpi/thermal_zone/*/*"
> that may be helpful.
brick:~# 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: 46 C
/proc/acpi/thermal_zone/THM0/trip_points:critical (S5): 127 C
/proc/acpi/thermal_zone/THM1/cooling_mode:<setting not supported>
/proc/acpi/thermal_zone/THM1/polling_frequency:<polling disabled>
/proc/acpi/thermal_zone/THM1/state:state: ok
/proc/acpi/thermal_zone/THM1/temperature:temperature: 49 C
/proc/acpi/thermal_zone/THM1/trip_points:critical (S5): 100 C
/proc/acpi/thermal_zone/THM1/trip_points:passive: 96 C:
tc1=5 tc2=4 tsp=600 devices=CPU0 CPU1
[-- Attachment #2: .config.bz2 --]
[-- Type: application/octet-stream, Size: 6772 bytes --]
next prev parent reply other threads:[~2009-11-25 22:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 10:28 regression: 2.6.32-rc8 shuts down after reaching critical temperature Christoph Hellwig
2009-11-25 21:56 ` Len Brown
2009-11-25 22:13 ` Christoph Hellwig [this message]
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=20091125221332.GA24173@lst.de \
--to=hch@lst.de \
--cc=lenb@kernel.org \
--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