From: Thomas Renninger <trenn@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
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, 2 Dec 2009 12:56:20 +0100 [thread overview]
Message-ID: <200912021256.21683.trenn@suse.de> (raw)
In-Reply-To: <20091126095202.GA15932@lst.de>
On Thursday 26 November 2009 10:52:02 Christoph Hellwig wrote:
> On Thu, Nov 26, 2009 at 12:23:11AM -0200, Henrique de Moraes Holschuh wrote:
> > If you go back to the previous kernel, does the problem disappear? Please
> > test and report (don't go by past experiences).
>
> Yes - in fact I had to revert to 2.6.31 because 2.6.32-rc is totally
> unusable for a kernel developers workload (this issue plus the wifi
> disconnects reported elsewhere).
>
> > If it does disappear, what are the highest temperatures your thinkpad hits?
>
> I haven't found a good monitoring applet to do constant monitoring, but
> the highest I've seen was around 95C so far.
The critical temperature for the shutdown should still be logged in:
/var/log/messages
Can you grab that one out, please.
But from what we know, this sounds like a real overheating and not a
wrongly read value, also thinkpads used to have a switch to let the
temperature jump above the critical trip point under certain conditions.
This seem to be the case on THM0 (I remember 127 C...):
/proc/acpi/thermal_zone/THM0/trip_points:critical (S5): 127 C
Can we be sure it's because of the fans?
2.6.31 works?
Also the latest stable one?
Then this one might be unrelated (11.2, 2.6.31.X based, Acer Aspire 5315):
[Bug 557850] System Fan is being stopped on boot, CPU goes overheated and shut down instantly
https://bugzilla.novell.com/show_bug.cgi?id=557850
Thomas
next prev parent reply other threads:[~2009-12-02 11:56 UTC|newest]
Thread overview: 15+ 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
2009-11-25 23:07 ` Len Brown
2009-11-26 10:17 ` Christoph Hellwig
2009-11-26 10:35 ` Christoph Hellwig
2009-12-02 12:00 ` Thomas Renninger
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 [this message]
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=200912021256.21683.trenn@suse.de \
--to=trenn@suse.de \
--cc=hch@lst.de \
--cc=hmh@hmh.eng.br \
--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