From: Pavel Machek <pavel@ucw.cz>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Brown, Len" <len.brown@intel.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
acpi-devel@kernel.org, cpufreq@lists.linux.org.uk,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Strange entries in /proc/acpi/thermal_zone for Thinkpad X60
Date: Fri, 13 Oct 2006 14:44:57 +0000 [thread overview]
Message-ID: <20061013144457.GA5512@ucw.cz> (raw)
In-Reply-To: <452EBF7C.3000409@goop.org>
Hi!
> I have a Thinkpad X60 with an Intel Core Duo T2400. In
> /proc/acpi/thermal_zone, I'm getting two subdirectories,
> each with their own set of files:
Looks okay to me. One thermal zone is cpu temperature, and second is
temperature of something else.
> The interesting thing is that the two sets of files are
> not consistent - sometimes they don't even show the same
> temperature.
You have two (actually you have more, see tp_smapi) physical
thermometers.
> The reason I'm interested in this is that I think it's
> behind some of my cpufreq problems. Sometimes the
> kernel decides that I just can't raise the max frequency
> above 1GHz, because its been thermally limited (I've put
> printks in to confirm that its the ACPI thermal limit on
> the policy notifier chain which is limiting the max
> speed). It seems to me that having a thermal zone for
> each core is a BIOS bug, since they're really the same
> chip, but the THM1 entries should be ignored. I don't
THM1 does not seem to be cpu temperature.
Pavel
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-10-13 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 22:19 Strange entries in /proc/acpi/thermal_zone for Thinkpad X60 Jeremy Fitzhardinge
2006-10-13 4:53 ` Len Brown
2006-10-13 14:44 ` Pavel Machek [this message]
[not found] <fa.P/oAhFV0AVrh8PKSKzP+xVGih2s@ifi.uio.no>
2006-10-13 3:57 ` Robert Hancock
2006-10-13 4:28 ` Jeremy Fitzhardinge
2006-10-13 18:10 ` Tomasz Torcz
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=20061013144457.GA5512@ucw.cz \
--to=pavel@ucw.cz \
--cc=acpi-devel@kernel.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=jeremy@goop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox