From: Christoph Hellwig <hch@lst.de>
To: Thomas Renninger <trenn@suse.de>
Cc: Christoph Hellwig <hch@lst.de>,
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 14:30:32 +0100 [thread overview]
Message-ID: <20091202133032.GA9265@lst.de> (raw)
In-Reply-To: <200912021256.21683.trenn@suse.de>
On Wed, Dec 02, 2009 at 12:56:20PM +0100, Thomas Renninger wrote:
> The critical temperature for the shutdown should still be logged in:
> /var/log/messages
> Can you grab that one out, please.
brick:/home/hch# grep "Critical temperature reached" /var/log/kern.log.1
Nov 23 17:58:27 brick kernel: [ 976.674070] Critical temperature reached (100 C), shutting down.
Nov 23 18:05:59 brick kernel: [ 411.639261] Critical temperature reached (102 C), shutting down.
Nov 23 22:20:43 brick kernel: [15159.677691] Critical temperature reached (102 C), shutting down.
Nov 25 11:06:33 brick kernel: [10947.132102] Critical temperature reached (103 C), shutting down.
Nov 25 11:53:50 brick kernel: [ 2795.261765] Critical temperature reached (102 C), shutting down.
Nov 25 11:53:55 brick kernel: [ 2800.128671] Critical temperature reached (100 C), shutting down.
Nov 26 11:30:24 brick kernel: [ 395.692667] Critical temperature reached (100 C), shutting down.
Nov 27 13:36:18 brick kernel: [ 390.408366] Critical temperature reached (100 C), shutting down.
>
> But from what we know, this sounds like a real overheating and not a
> wrongly read value,
It sounds like that to me, but something in .32-rc causes it to not
throttle early enough. .31 goes very close to the max all the time, but
something thottles it to not actually go over it.
> Can we be sure it's because of the fans?
No idea, really. The fan rarely every starts when using .31, but comes
in a lot using .32-rc
> 2.6.31 works?
Yes, perfectly. Have been running it for a couple of days now again
after I had all these reproducible .32-rc shutdowns when testiong it.
> Also the latest stable one?
Haven't tried that yet, will do if it helps you.
> 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
Well, I do hear the fan on .32-rc (not on .31 usually).
next prev parent reply other threads:[~2009-12-02 13:31 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
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 [this message]
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=20091202133032.GA9265@lst.de \
--to=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 \
--cc=trenn@suse.de \
/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