mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: ACPI mailing list <linux-acpi@vger.kernel.org>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: x60 - spontaneous thermal shutdown
Date: Tue, 5 Sep 2006 00:26:14 +0200	[thread overview]
Message-ID: <20060904222614.GA1614@rhlx01.fht-esslingen.de> (raw)
In-Reply-To: <20060904214059.GA1702@elf.ucw.cz>

Hi,

On Mon, Sep 04, 2006 at 11:40:59PM +0200, Pavel Machek wrote:
> Hi!
> 
> x60 shut down after quite a while of uptime, in period of quite heavy
> load:
> 
> Sep  4 23:33:01 amd kernel: ACPI: Critical trip point
> Sep  4 23:33:01 amd kernel: Critical temperature reached (128 C), shutting down.
> Sep  4 23:33:01 amd shutdown[32585]: shutting down for system halt
> Sep  4 23:34:42 amd init: Switching to runlevel: 0
> 
> I do not think cpu reached 128C, as I still have my machine... Did
> anyone else see that?

Could this be in any way related to the (in)famous Random Shutdown issues
on a little too many Apple MacBooks?
(since the x60 incidentally just happens to be Core Duo architecture, too)

Those Random Shutdown issues at least in several cases appear to happen
due to trouble with the temperature sensor or mainboard issues.
Thermal management is in quite some trouble there, judging from
the rather diverse aspects of machine shutdown failure...
(fan not working, CPU overheating, NOT overheating but shutting down
directly after boot, ...)

There's nothing like rushing out immature hardware to unsuspecting consumers...

Andreas Mohr

  reply	other threads:[~2006-09-04 22:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04 21:40 Pavel Machek
2006-09-04 22:26 ` Andreas Mohr [this message]
2006-09-04 22:35   ` Pavel Machek
2006-09-04 22:53     ` Andreas Mohr
2006-09-05  6:10     ` Jan Engelhardt
2006-09-11  9:46 ` Stefan Seyfried
2006-09-11 14:10   ` Rafael J. Wysocki
2006-09-11 15:13     ` Stefan Seyfried

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=20060904222614.GA1614@rhlx01.fht-esslingen.de \
    --to=andi@rhlx01.fht-esslingen.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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®