All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Metro <tmetro@tommetro.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] coretemp readings are static/constant
Date: Fri, 29 Nov 2013 21:41:37 +0000	[thread overview]
Message-ID: <52990A11.8060001@tommetro.com> (raw)
In-Reply-To: <loom.20131119T072701-70@post.gmane.org>

Hi Jean,

Jean Delvare wrote:
> Tom Metro wrote:
>> % sensors
>> [...]
>> coretemp-isa-0000
>> Adapter: ISA adapter
>> Core 0:       +33.0°C  (high = +105.0°C, crit = +105.0°C)
>> Core 1:       +33.0°C  (high = +105.0°C, crit = +105.0°C)
>>
>> The values reported by coretemp are always 33000 millidegrees:
> 
> You should really stress the CPU and see what happens.

I ran:

% stress --cpu 2 --timeout 7200
stress: info: [14967] dispatching hogs: 2 cpu, 0 io, 0 vm, 0 hdd
stress: info: [14967] successful run completed in 7200s

And just to be sure, I also thew in a couple of these:

% dd bs=10 if=/dev/urandom | bzip2 -z -s -9 -c > /dev/null &

and let the latter run for 8 hours.

I saw some new peaks on the 'acpitz-virtual-0' sensors, but the
'coretemp-isa-0000' sensors didn't budge.


> Another possibility is that this particular incarnation of the sensors
> do not report values below 33°C. 

Right, that was the theory I was going on based on the FAQ entry I
quoted. Apparently not the case here.


So this would appear to be a problem with the coretemp kernel module.
This CPU (Intel Core 2 Duo P8400) is from the right era to be supported
by coretemp. Where is the best place to go to file a bug against that
module?

Thanks for the suggestions.

 -Tom

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2013-11-29 21:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19  6:28 [lm-sensors] coretemp readings are static/constant Tom Metro
2013-11-19  7:57 ` Jean Delvare
2013-11-29 21:41 ` Tom Metro [this message]
2013-11-29 21:56 ` Jean Delvare

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=52990A11.8060001@tommetro.com \
    --to=tmetro@tommetro.com \
    --cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.