From: Matthew <jackdachef@gmail.com>
To: "Len Brown" <lenb@kernel.org>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: Linux 2.6.25
Date: Sat, 19 Apr 2008 12:18:33 +0200 [thread overview]
Message-ID: <e85b9d30804190318u74e14f0ct6ab53cb86f6ce15f@mail.gmail.com> (raw)
In-Reply-To: <20080419061701.GA7688@cvg>
>Hello Mat,
>I'm not familiar with "coretemp", can you point me to the exact version
>of the application you are running so I can see how it is getting at
>the underlying information?
>Also, do you see any change with and without kernel built with
CONFIG_THERMAL=y?
>thanks,
>-Len
Hi Len,
sure, the apps I am using for reading out the processor's temp via
coretemp are / were:
lm_sensors: version 2.10.4, 2.10.6 and (currently) 3.0.1: all report
the same (higher) temperatures (compared to 2.6.24 series)
CONFIG_THERMAL currently is enabled in the kernel:
grep CONFIG_THERMAL /usr/src/linux/.config
CONFIG_THERMAL=y
I'll recompile the kernel now & let you know the effect in a few hours
(currently I'm working on the box)
"Dairinin" on forums.gentoo.org pointed out that the desktop-cpu
simply might not be identified correctly:
http://forums.gentoo.org/viewtopic-p-5065902.html#5065902
"Thats because new kernel (lm_sensors, etc?, etc?)incorrectly thinks
our cpu's Tj is 100C, whereas for all core 2 duo's it is 85C (100C is
for C0 stepping and above, AFAIK). Substract 15 and you'll get real
temps."
I don't know if that's the case but it sounds plausible to me
thanks everyone for your answer & help so far
Regards
Mat
next prev parent reply other threads:[~2008-04-19 10:19 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 15:37 Matthew
2008-04-18 15:43 ` Linus Torvalds
2008-04-18 16:02 ` Matthew
2008-04-18 19:38 ` Cyrill Gorcunov
2008-04-18 20:03 ` Cyrill Gorcunov
2008-04-19 3:05 ` Rene Herman
2008-04-19 3:20 ` Rene Herman
2008-04-19 6:17 ` Cyrill Gorcunov
2008-04-19 10:18 ` Matthew [this message]
2008-04-19 10:22 ` Matthew
2008-04-20 12:02 ` Matthew
2008-04-24 3:36 ` Len Brown
2008-04-18 16:24 ` Gene Heskett
2008-04-18 16:27 ` Gene Heskett
2008-04-18 19:18 ` Bart Van Assche
2008-04-18 20:24 ` Jiri Slaby
2008-04-18 20:50 ` Rudolf Marek
2008-04-19 1:51 ` Linux 2.6.25 (coretemp reads high temperatures) Len Brown
2008-04-21 16:10 ` Thomas Bächler
2008-04-21 16:28 ` Matthew
2008-04-21 17:07 ` Fwd: " Matthew
2008-04-22 9:26 ` Matthew
2008-04-23 8:43 ` Maxim Levitsky
2008-04-28 18:19 ` Kasper Sandberg
2008-04-29 13:07 ` Thomas Renninger
2008-04-29 15:08 ` Jean Delvare
2008-04-29 22:14 ` Rudolf Marek
2008-04-29 22:58 ` Matthew
2008-04-30 6:10 ` Jean Delvare
2008-04-30 14:46 ` Henrique de Moraes Holschuh
2008-04-30 14:50 ` Rudolf Marek
2008-04-30 15:18 ` Jean Delvare
2008-05-02 20:35 ` Pavel Machek
2008-04-30 0:11 ` Kasper Sandberg
2008-04-30 6:20 ` Jean Delvare
2008-04-30 14:51 ` Henrique de Moraes Holschuh
2008-04-30 15:28 ` Jean Delvare
2008-05-02 20:36 ` Pavel Machek
2008-05-04 17:42 ` Henrique de Moraes Holschuh
2008-05-05 13:45 ` Pavel Machek
2008-05-02 20:35 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2008-04-17 3:32 Linux 2.6.25 Linus Torvalds
2008-04-17 4:22 ` david
2008-04-17 18:56 ` Rafael J. Wysocki
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=e85b9d30804190318u74e14f0ct6ab53cb86f6ce15f@mail.gmail.com \
--to=jackdachef@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®