From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] high value for CPUTIN
Date: Wed, 31 Oct 2012 03:58:45 +0000 [thread overview]
Message-ID: <20121031035845.GA25948@roeck-us.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1210290159070.3309@cosmos>
On Tue, Oct 30, 2012 at 11:18:00PM -0300, Alejandro Jakubi wrote:
> >No. Problem is that PECI does not report an absolute temperature, but the
> >difference to Tjmax, which is the maximum CPU temperature (reported as critical
> >temperature by coretemp). The NCT6776F has a register which needs to be programmed
> >to that value. Usually that is done in the BIOS. Looks like the BIOS did not
> >program the correct value on your board.
>
> I see. However, if this NCT6776F register were wrongly programed, it seems
> to me like there should be a systematic error in the reported temperature.
> However, this is not what I am observing. For instance, the value of PECI 0 in
> my first post (showing the complete output) was 33.5C, with all the other
> temperatures (except CPUTIN) in a close range. Now its value is about 30C (+/-
> 1C, I am following it with xsensors), again in close agreement with the other
> readings.
>
> So, it seems to me like something else caused yesterday that PECI 0 had
> reported a value over 10C below "normal". Two things come to my mind: an
> erratic failure of this device, or that previously to the reported low
> reading, I had booted to Win 7 and installed SpeedFan 4.47 (as a check about
> the high value reported for the CPU).
>
> I will keep looking at the PECI 0 value as summer comes here shortly...
>
PECI is actually _very_ inaccurate for low temperatures, so this is not really
surprising.
> In any case, are the values reported by Core 0 to 3 more reliable?
>
Good question. I don't really know; those are also known to be inaccurate
for low temperatures.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2012-10-31 3:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 5:00 [lm-sensors] high value for CPUTIN Alejandro Jakubi
2012-10-31 2:18 ` Alejandro Jakubi
2012-10-31 3:58 ` Guenter Roeck [this message]
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=20121031035845.GA25948@roeck-us.net \
--to=linux@roeck-us.net \
--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.