linux-kernel - Re: 2.6.27-rc1: critical thermal shutdown on thinkpad x60

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48A16EFC.1050401@redhat.com>
Date:	Tue, 12 Aug 2008 13:07:40 +0200
From:	Milan Broz <mbroz@...hat.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Pavel Machek <pavel@...e.cz>,
	kernel list <linux-kernel@...r.kernel.org>,
	ACPI mailing list <linux-acpi@...r.kernel.org>
Subject: Re: 2.6.27-rc1: critical thermal shutdown on thinkpad x60

Andi Kleen wrote:
> On Tue, Aug 12, 2008 at 11:41:35AM +0200, Pavel Machek wrote:
>>>> 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
>> Yes, I'm very sure. It makes machine basically unusable.
> 
> Does this mean you can easily reproduce it?  
> Please do a bisect then. 
> 
>> Not that one :-(. Thinkpad does not even have fan device: it is
>> controlled by hardware.

Hi,
I see exactly the same on my x60s, but during upgrade to 2.6.26.2.

I found that (at least in my case) the problem is, that in
2.6.25 the core frequency drop to 1GHz (instead of 1.67GHz) when
the temperature is above some limit.

Now, the CPU cores remains on 1.67GHz and fan is unable to cool them properly
under heavy load (even if I set "level disengaged" through thinkpad fan control,
temperature sensor shows after a while 128 C (probably not real temp,
I expect some critical flag => and it properly switch off the system...)

(I had bad reproducer script in bisect and bisect failed, so I'll try it again,
but anyway, for me the bug is even in 2.6.26 tree. It never happened in 2.6.25.)

Milan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/