From: Stefan Seyfried <seife@suse.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: Mon, 11 Sep 2006 11:46:07 +0200 [thread overview]
Message-ID: <20060911094607.GA14095@suse.de> (raw)
In-Reply-To: <20060904214059.GA1702@elf.ucw.cz>
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?
my usual suspect: use ec_intr=0. I have seen this rather often on HP machines.
I attributed it to "communication problems with embedded controller" and
ec_intr=0 seemed to help somehow. But then, this was some kernel versions
ago and i did not encounter it recently.
--
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, Nürnberg \ -- Leonard Cohen
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Seyfried <seife@suse.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: Mon, 11 Sep 2006 11:46:07 +0200 [thread overview]
Message-ID: <20060911094607.GA14095@suse.de> (raw)
In-Reply-To: <20060904214059.GA1702@elf.ucw.cz>
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?
my usual suspect: use ec_intr=0. I have seen this rather often on HP machines.
I attributed it to "communication problems with embedded controller" and
ec_intr=0 seemed to help somehow. But then, this was some kernel versions
ago and i did not encounter it recently.
--
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, Nürnberg \ -- Leonard Cohen
next prev parent reply other threads:[~2006-09-11 9:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 21:40 x60 - spontaneous thermal shutdown Pavel Machek
2006-09-04 22:26 ` Andreas Mohr
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 [this message]
2006-09-11 9:46 ` Stefan Seyfried
2006-09-11 14:10 ` Rafael J. Wysocki
2006-09-11 15:13 ` Stefan Seyfried
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=20060911094607.GA14095@suse.de \
--to=seife@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.