From: "Thomas Bächler" <thomas@archlinux.org>
To: Len Brown <lenb@kernel.org>
Cc: Matthew <jackdachef@gmail.com>,
linux-acpi@vger.kernel.org, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.25 (coretemp reads high temperatures)
Date: Mon, 21 Apr 2008 18:10:58 +0200 [thread overview]
Message-ID: <480CBC92.4070502@archlinux.org> (raw)
In-Reply-To: <200804182151.49021.lenb@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
Len Brown schrieb:
> 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?
I think there is some confusion here: "coretemp" is a kernel module, and
all applications reading it will probably use the lm_sensors libraries.
(I don't think the hwmon module are related to ACPI)
$ modinfo coretemp
filename: /lib/modules/2.6.25-ARCH/kernel/drivers/hwmon/coretemp.ko
license: GPL
description: Intel Core temperature monitor
author: Rudolf Marek <r.marek@assembler.cz>
depends:
vermagic: 2.6.25-ARCH SMP preempt mod_unload
That said, I have two Core 2 CPUs (one mobile, one desktop) and the
values coretemp reports have not changed compared to earlier kernel
versions (around 60°C when idle on the mobile, much less on the desktop).
> Also, do you see any change with and without kernel built with
CONFIG_THERMAL=y?
The values I see from ACPI thermal are also the same as before (this is
funny: they are always about 15°C cooler than the coretemp values).
So I don't see a regression here, maybe the reporter should try a
vanilla kernel.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2008-04-21 16:11 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 15:37 Linux 2.6.25 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
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 [this message]
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
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=480CBC92.4070502@archlinux.org \
--to=thomas@archlinux.org \
--cc=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;
as well as URLs for NNTP newsgroup(s).