From: Maxim Levitsky <maximlevitsky@gmail.com>
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: Wed, 23 Apr 2008 11:43:10 +0300 [thread overview]
Message-ID: <200804231143.10875.maximlevitsky@gmail.com> (raw)
In-Reply-To: <200804182151.49021.lenb@kernel.org>
On Saturday, 19 April 2008 04:51:48 Len Brown wrote:
> On Friday 18 April 2008, Matthew wrote:
> > Hi everyone, hi Linus,
> >
> > congratulations on this new great kernel-release :)
> >
> > I've another "regression" to report for 2.6.25:
> >
> > it's concerning much higher temperatures being read out by the
> > "coretemp" kernel-module in comparison to 2.6.24* series
> >
> > e.g. where temperatures were around 40-47°C they are now constantly
> > jumping around 55-70°C (even in idle !)
I just updated from 2.6.24 to 2.6.25
(I usually follow whole development cycle, but I was very busy, so I skipped 2.6.25 cycle)
I confirm this.
I *know* that temperatures reported now are wrong.
The reason is that bios did report same temperatures as coretemp in 2.6.24,
moreover some time ago I have run a cpu tool (don't remember its name) on windows
which similar to coretemp reads from each core directly, sensor data ,
and I noticed that temperature that bios reports is exactly the average
temperature of both cores
(I had to run this on windows - intel haven't released
drivers for their QST for temperature monitoring from bios - very sad)
And the driver did say in kernel log that TJMAX is 85C
Lets at least make a kernel option to override tjmax?
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2008-04-23 8:43 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
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 [this message]
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=200804231143.10875.maximlevitsky@gmail.com \
--to=maximlevitsky@gmail.com \
--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).