From: Tim Blechmann <tim@klingt.org>
To: linux-kernel@vger.kernel.org
Subject: cpu temperature after wakeup
Date: Sat, 28 Mar 2009 11:45:54 +0100 [thread overview]
Message-ID: <gqkv57$5e8$1@ger.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
hi all,
after a wakeup from suspending to ram, the cpu temperature (reported by
acpi) for the second core is about 15° higher than for the first core
(core2 duo t7400, x86_64).
i am not sure, if it is just an issue of reporting the wrong value or if
the cpu temperature is actually that different.
on a more or less idle machine: cpu0: 44°c, cpu1: 60°c
doing some work: cpu0: 55°c, cpu1: 70°c
any idea, what could be the reason? usually both temperatures are quite
similar, after a reboot, it seems to be fine again. i am running 2.6.29,
but i think i already saw it on earlier kernels, i didn't look into it
at that time, though ...
thnx, tim
--
tim@klingt.org
http://tim.klingt.org
The aim of education is the knowledge, not of facts, but of values
William S. Burroughs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2009-03-28 10:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='gqkv57$5e8$1@ger.gmane.org' \
--to=tim@klingt.org \
--cc=linux-kernel@vger.kernel.org \
/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