All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	"Brown, Len" <len.brown@intel.com>,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Subject: Re: Strange entries in /proc/acpi/thermal_zone for Thinkpad X60
Date: Thu, 12 Oct 2006 21:28:12 -0700	[thread overview]
Message-ID: <452F15DC.8080701@goop.org> (raw)
In-Reply-To: <452F0EB7.2060508@shaw.ca>

Robert Hancock wrote:
> I would expect they wouldn't, otherwise there would be no reason for 
> the BIOS people to set up two thermal zones..

Ah, OK.  I misunderstood what thermal zones are.

> How do you know they are one for each core? ACPI thermal zones can be 
> anywhere in the machine that needs OS-controlled cooling. Could be the 
> CPU heatsink, voltage regulator, or someplace else.

Right, bad assumption on my part.  Is there any way to find out what 
they might correspond to?  /proc/acpi/ibm/thermal has a bunch of 
temperature-like numbers in them; I guess there should be some 
correlation between those and the thermal zones.

> I think we need more information to decide what is going on here.. 
> what temperatures are registering in the thermal zones when the CPU 
> clock is being limited?

I'll gather a bit more info.

    J

  reply	other threads:[~2006-10-13  4:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.P/oAhFV0AVrh8PKSKzP+xVGih2s@ifi.uio.no>
2006-10-13  3:57 ` Strange entries in /proc/acpi/thermal_zone for Thinkpad X60 Robert Hancock
2006-10-13  4:28   ` Jeremy Fitzhardinge [this message]
2006-10-13 18:10     ` Tomasz Torcz
2006-10-12 22:19 Jeremy Fitzhardinge
2006-10-12 22:19 ` Jeremy Fitzhardinge
2006-10-13  4:53 ` Len Brown
2006-10-13 14:44 ` Pavel Machek

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=452F15DC.8080701@goop.org \
    --to=jeremy@goop.org \
    --cc=hancockr@shaw.ca \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.com \
    /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.