All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Alexey Starikovskiy <aystarik@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns
Date: Sun, 01 Apr 2007 21:53:38 -0700	[thread overview]
Message-ID: <46108C52.7030301@goop.org> (raw)
In-Reply-To: <20070402023846.GC28561@khazad-dum.debian.net>

Henrique de Moraes Holschuh wrote:
> On Sun, 01 Apr 2007, Jeremy Fitzhardinge wrote:
>   
>> control problems.  Perhaps the ambient temperature was lower when I
>> reported success.
>>     
>
> You can use ibm-acpi to properly track your thinkpad thermal sensors, load
> it with the "experimental=1" parameter, and look at what gets exported at
> /proc/acpi/ibm/thermal.
>   

Interesting.  The first number corresponds with the ACPI THM0
temperature, but I can't see anything corresponding to THM1.  Is there
something that documents what all the temperatures are measuring in an
X60?  Thinkwiki doesn't seem to have any info.

ezr:pts/1; cat /proc/acpi/ibm/thermal
temperatures:   72 55 -128 65 40 -128 35 -128 51 53 -128 -128 -128 -128
-128 -128

> You can also use /proc/acpi/ibm/fan to check the fan's state.  And use the
> "level 7" /proc/acpi/ibm/fan command to set the emergency cooling level, and
> "level disengaged" command to set the really badass fan cooling level (might
> damage your hardware, we don't know if it is safe and IBM/Lenovo isn't
> talking).
>   

It's set to auto.  Presumably that means its tied into the temperature
sensors and will be able to keep the temp under control...

    J


  reply	other threads:[~2007-04-02  4:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-31  6:36 2.6.21-rc5: Thinkpad X60 gets critical thermal shutdowns Jeremy Fitzhardinge
2007-03-31  9:31 ` Andi Kleen
2007-04-01 16:30   ` Pavel Machek
2007-04-01 22:44     ` Henrique de Moraes Holschuh
     [not found] ` <8f8ff01d0703310033y74421cfcl747ece1be003471@mail.gmail.com>
2007-04-01  6:28   ` Jeremy Fitzhardinge
2007-04-01 14:53     ` Matthew Garrett
2007-04-01 16:32     ` Pavel Machek
2007-04-01 22:46       ` Henrique de Moraes Holschuh
2007-04-01 23:19     ` Jeremy Fitzhardinge
2007-04-02  2:38       ` Henrique de Moraes Holschuh
2007-04-02  4:53         ` Jeremy Fitzhardinge [this message]
2007-04-03 12:34           ` Henrique de Moraes Holschuh
2007-04-03 18:35             ` Jeremy Fitzhardinge
2007-04-03 21:25               ` RusH
2007-04-04  3:46               ` Henrique de Moraes Holschuh
2007-04-01 18:57 ` Kyle Moffett
2007-04-01 21:13   ` Jeremy Fitzhardinge
2007-04-02  8:35   ` Rene Rebe
2007-04-02  8:35     ` Rene Rebe
2007-04-08 19:09     ` Valdis.Kletnieks

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=46108C52.7030301@goop.org \
    --to=jeremy@goop.org \
    --cc=aystarik@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.