public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: Len Brown <lenb@kernel.org>, 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, 28 Apr 2008 20:19:44 +0200	[thread overview]
Message-ID: <1209406784.11608.15.camel@localhost> (raw)
In-Reply-To: <200804231143.10875.maximlevitsky@gmail.com>

On Wed, 2008-04-23 at 11:43 +0300, Maxim Levitsky wrote:
> 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.

I too can confirm that it reports incorrect temperatures.

I have a Q9450, and this is my "sensors" output:
it8718-isa-0290
Adapter: ISA adapter
<snip>
temp1:       +44°C  (low  =  +127°C, high =  +127°C)   sensor =
thermistor
temp2:       +22°C  (low  =  +127°C, high =   +60°C)   sensor = diode
temp3:        -2°C  (low  =  +127°C, high =  +127°C)   sensor =
thermistor
vid:      +0.000 V

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +44°C  (high =  +100°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +44°C  (high =  +100°C)

coretemp-isa-0002
Adapter: ISA adapter
Core 2:      +43°C  (high =  +100°C)

coretemp-isa-0003
Adapter: ISA adapter
Core 3:      +41°C  (high =  +100°C)


temp2 is the cpu temperature(matches bios), temp1 is the northbridge(i
think, bios says "system temp").

i have watercooling, and well :P when i touch the "tube", its normal
room temperature, and believe me, i would notice if it was 45.. this is
with my cpu at idle - at full load on all 4 cores, temp2 says 35, and
~60 on coretemp, and THIS i would surely be able to notice over room
temp :)

any progress on this bug?

> 
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-04-28 18:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e85b9d30804180837y39c52e26i588e4b67c87a5e9d@mail.gmail.com>
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-23  8:43   ` Maxim Levitsky
2008-04-28 18:19     ` Kasper Sandberg [this message]
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
     [not found] ` <alpine.LFD.1.00.0804180843150.2879@woody.linux-foundation.org>
     [not found]   ` <20080418193802.GK7674@cvg>
     [not found]     ` <20080418200338.GL7674@cvg>
     [not found]       ` <48096179.4060803@keyaccess.nl>
     [not found]         ` <480964F7.3040701@keyaccess.nl>
     [not found]           ` <20080419061701.GA7688@cvg>
2008-04-19 10:18             ` Linux 2.6.25 Matthew

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=1209406784.11608.15.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=jackdachef@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maximlevitsky@gmail.com \
    --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