From: Pavel Machek <pavel@suse.cz>
To: Thomas Renninger <trenn@suse.de>
Cc: Milan Broz <mbroz@redhat.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Andi Kleen <andi@firstfloor.org>,
kernel list <linux-kernel@vger.kernel.org>,
ACPI mailing list <linux-acpi@vger.kernel.org>,
Alexey Starikovskiy <astarikovskiy@suse.de>,
Greg Kroah-Hartman <gregkh@novell.com>,
stable@kernel.org
Subject: Re: 2.6.27-rc1 and 2.6.26.1: critical thermal shutdown on thinkpad x60 (bisected)
Date: Wed, 13 Aug 2008 09:08:18 +0200 [thread overview]
Message-ID: <20080813070818.GC1813@elf.ucw.cz> (raw)
In-Reply-To: <200808121801.21374.trenn@suse.de>
On Tue 2008-08-12 18:01:18, Thomas Renninger wrote:
> On Tuesday 12 August 2008 17:48:27 Milan Broz wrote:
> > >>>> yes. maybe some userspace tool controlling frequency is involved, no
> > >>>> idea yet. But it is 2.6.26 tree for sure.
> > >>>
> > >>> So it definitely is in 2.6.26.2, and it definitely is in 2.6.26?
> > >
> > > The bug is _not_ in 2.6.26, it was introduced in 2.6.26.1.
> > >
> > > The problem is, that now the CPU frequency doesn't decrease at some
> > > temperature level and fan is unable to cool it properly.
> Hmm, the machine should still not shut down. We need the virtual
> passive trip point...
Won't help here.
We already do have real passive trip point on the other thermal zone,
and the zone that actually forces shutdown goes 95->128C instantly
(see that DSDT). Virtual passive trip point at 115C will not help
anything.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-08-13 7:47 UTC|newest]
Thread overview: 35+ 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
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 [this message]
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 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=20080813070818.GC1813@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=andi@firstfloor.org \
--cc=astarikovskiy@suse.de \
--cc=gregkh@novell.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=rjw@sisk.pl \
--cc=stable@kernel.org \
--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 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.