-rc6: annoying thermal messages

-rc6: annoying thermal messages

[Pavel Machek]

My dmesg log is rather full of. Thinkpad x60.
							Pavel

	

wlan0: RX AssocResp from 00:11:95:05:30:d7 (capab=0x421 status=0
aid=2)
wlan0: associated
wlan0: deauthenticated from 00:11:95:05:30:d7 (Reason: 3)
thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
extremely hot!
thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
extremely hot!
thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
extremely hot!
thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
extremely hot!
thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
extremely hot!
thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
extremely hot!
thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
extremely hot!
thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
extremely hot!
thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
extremely hot!
thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
extremely hot!
thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
extremely hot!
thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
extremely hot!
thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
extremely hot!
hub 1-0:1.0: state 7 ports 8 chg 0000 evt 0004
ehci_hcd 0000:00:1d.7: GetStatus port 2 status 001002 POWER sig=se0
CSC
hub 1-0:1.0: port 2, status 0100, change 0001, 12 Mb/s
usb 1-2: USB disconnect, address 6

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: -rc6: annoying thermal messages

[Henrique de Moraes Holschuh]

n Mon, 16 Nov 2009 12:23 +0100, "Pavel Machek" <pavel@ucw.cz> wrote:
>
> My dmesg log is rather full of. Thinkpad x60.
> Pavel

I think I will have to rate-limit it somehow.  Do we have any ready-to-
use generic rate-limiters that can do 'once a minute', or should I
cook my own?

But your thinkpad needs some sort of hardware loving care, it seems.
What does "sensors" report (or cat /proc/acpi/ibm/thermal) ?

> thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
> extremely hot!

That is a direct alarm from the firmware, the EC thinks your hardware
is damaged and about to catch fire.

Either that, or something  in the driver is seriously broken. But
you're the first one to ever report that alarm :)

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Re: -rc6: annoying thermal messages

[Pavel Machek]

On Mon 2009-11-16 10:54:29, Henrique de Moraes Holschuh wrote:
> n Mon, 16 Nov 2009 12:23 +0100, "Pavel Machek" <pavel@ucw.cz> wrote:
> >
> > My dmesg log is rather full of. Thinkpad x60.
> > Pavel
> 
> I think I will have to rate-limit it somehow.  Do we have any ready-to-
> use generic rate-limiters that can do 'once a minute', or should I
> cook my own?
> 
> But your thinkpad needs some sort of hardware loving care, it seems.
> What does "sensors" report (or cat /proc/acpi/ibm/thermal) ?

guest@amd:~/.gnupg$ cat /proc/acpi/ibm/thermal
temperatures:	59 49 -128 60 38 -128 34 -128 48 50 -128 -128 -128 -128 -128 -128

...sensors are not installed. I see THERMAL EMERGENCY in dmesg, but
I'm not sure how long ago it was generated.

> > thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something is
> > extremely hot!
> 
> That is a direct alarm from the firmware, the EC thinks your hardware
> is damaged and about to catch fire.

Well, working sensors report temperatures in 34C (battery) to 68C
range (PCI).

guest@amd:~$ cat /proc/acpi/thermal_zone/THM*/*
<setting not supported>
<polling disabled>
state:                   ok
temperature:             58 C
critical (S5):           127 C
<setting not supported>
<polling disabled>
state:                   ok
temperature:             67 C
critical (S5):           97 C
passive:                 93 C: tc1=5 tc2=4 tsp=600 devices=CPU0 CPU1 
guest@amd:~$ 

> Either that, or something  in the driver is seriously broken. But
> you're the first one to ever report that alarm :)

Well, being only in kernel log, those messages are not exactly easy to
notice.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html