[lm-sensors] sensors show hdd temp instead of cpu temp using coretemp in acer d250

vajorie vajorie at gmail.com
Thu Jan 7 06:07:28 CET 2010


On Wed, Jan 6, 2010 at 8:59 PM, Huaxu Wan <huaxu.wan at linux.intel.com> wrote:
> On 19:51 Mon 04 Jan, vajorie wrote:
...
>> sensors output:
>>
>> coretemp-isa-0000
>> Adapter: ISA adapter
>> Core 0:      +45.0°C  (crit = +90.0°C)
>>
>> coretemp-isa-0001
>> Adapter: ISA adapter
>> Core 1:      +45.0°C  (crit = +90.0°C)
>>
>> acpitz-virtual-0
>> Adapter: Virtual device
>> temp1:       +26.8°C  (crit = +100.0°C)
>>
>
> You can get the hdd temperature through hddtemp[1].
>
> Coretemp get CPU temperature data from MSR directly. The data in
> MSR is reported by the on-die DTS (Digital Temperature Sensor), it
> reflects the delta between the current temperature and the maximum
> junction temperature of the die(Tj).
>
>
> [1] http://savannah.nongnu.org/projects/hddtemp/
>
> Thanks
> Huaxu
>


Hi,

Thanks for your response (and it's truly great to hear from intel, as
a side note). If I got your message right, unfortunately, I'm not
literate at all about the internal mechanisms of hardware monitoring
:( All I know is that the temperature that is reported as cpu's by
coretemp / sensors is actually (I'm pretty sure) that of the hdd. The
crit temps that sensors report (90C) is accurate according to intel's
specs for N280, but the temperature is too low for this cpu (right
now, it's 29C) and it corresponds almost perfectly to hdd temperature
reported in Windows (checked with a reboot from Linux to Windows). The
average cpu temp reported in Windows is 50C+...

Is it possible that what coretemp thinks is MSR is actually not it (I
don't know what I'm saying at this point)?

This may be related to how Acer set (wrongly?) things up with Aspire
One D250 (via their bios??), but I'm not sure about that. Their bios
(?) already has other problems with this cpu[1].

I opened yet another bug report in linux kernel about this:
http://bugzilla.kernel.org/show_bug.cgi?id=14991 which has one other
user reporting similar experience on the D250. That bug report also
has my output of acpidump, if relevant here.

Thanks again for your reply.
Is there any way I can help debug this?

[1] https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/422858




More information about the lm-sensors mailing list