public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Pavel Machek <pavel@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	ACPI mailing list <linux-acpi@vger.kernel.org>
Subject: Re: 2.6.27-rc1: critical thermal shutdown on thinkpad x60
Date: Thu, 07 Aug 2008 18:01:02 +0200	[thread overview]
Message-ID: <87bq046cht.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080806090246.GA1572@elf.ucw.cz> (Pavel Machek's message of "Wed, 6 Aug 2008 11:02:47 +0200")

Pavel Machek <pavel@suse.cz> writes:

> Hi!
>
> Aug  6 11:00:10 amd kernel: ACPI: Critical trip point
> Aug  6 11:00:10 amd kernel: Critical temperature reached (128 C),
> shutting down.
> Aug  6 11:00:10 amd shutdown[24414]: shutting down for system halt
>
> ...and machine went down at that point :-(.

I hope you can easily reproduce it?

So it's new in 2.6.27rc1 and wasn't in 2.6.26? Can you please
double check that? Are there are new warnings in the boot logs
from ACPI compared to .26?

I looked through the pile of patches that went in for ACPI and the 
only candidate that might have imho caused this would be 
ea51011a27db48ea0a80a5e20de3969b292d5d4d. Can you please 
try reverting that. If that doesn't help a full bisect will be needed.

-Andi

  parent reply	other threads:[~2008-08-07 16:01 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06  9:02 2.6.27-rc1: critical thermal shutdown on thinkpad x60 Pavel Machek
2008-08-07  9:13 ` Pavel Machek
2008-08-07 10:38   ` Pavel Machek
2008-08-07 11:34 ` Karel Zak
2008-08-07 13:05   ` Fabio Comolli
2008-08-07 14:41     ` Yves-Alexis Perez
2008-08-07 16:01 ` Andi Kleen [this message]
2008-08-12  9:41   ` Pavel Machek
2008-08-12 10:54     ` Andi Kleen
2008-08-12 11:02       ` Pavel Machek
2008-08-12 11:07       ` Milan Broz
2008-08-12 11:26         ` Pavel Machek
2008-08-12 11:44           ` Milan Broz
2008-08-12 11:55             ` Pavel Machek
2008-08-12 14:34               ` Rafael J. Wysocki
2008-08-12 14:57                 ` 2.6.27-rc1: critical thermal shutdown on thinkpad x60 (bisected) Milan Broz
2008-08-12 15:48                   ` Milan Broz
2008-08-12 16:01                     ` 2.6.27-rc1 and 2.6.26.1: " Thomas Renninger
2008-08-13  7:08                       ` Pavel Machek
2008-08-12 16:28                     ` 2.6.27-rc1: " Andi Kleen
2008-08-12 18:30                     ` Dominik Brodowski
2008-08-12 18:59                       ` Andi Kleen
2008-08-12 19:56                         ` Rafael J. Wysocki
2008-08-13 10:39                         ` Milan Broz
2008-08-14 13:56                         ` Milan Broz
2008-08-13  7:39                     ` Pavel Machek
2008-08-13  7:39                   ` Pavel Machek
2008-08-12 15:32                 ` 2.6.27-rc1: critical thermal shutdown on thinkpad x60 Matthew Garrett
2008-08-12 19:57                   ` Rafael J. Wysocki
2008-08-13 20:13           ` Henrique de Moraes Holschuh
2008-08-13 20:28             ` Pavel Machek
2008-08-13 20:42               ` Henrique de Moraes Holschuh
2008-08-13 20:55                 ` Pavel Machek
2008-08-13  0:55     ` Zhang Rui

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=87bq046cht.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.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