All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
Date: Sat, 28 Apr 2012 14:43:24 +0000	[thread overview]
Message-ID: <20120428144324.GA23747@ericsson.com> (raw)
In-Reply-To: <CAGqf2i+bMvvWyELKn5ApTL+XUQ_s7x-eMCSV4DdNGhpfuHy6nA@mail.gmail.com>

On Sat, Apr 28, 2012 at 04:55:09AM -0400, Jean Delvare wrote:
> On Sat, 28 Apr 2012 06:43:53 +0000, P.B. V wrote:
> > w83627ehf and nct6775 (Apr 27, 2012) driver modules both show a
> > seemingly incorrect value for PECI. I am running a Maximus IV Extreme
> > Revision 1.0 motherboard (NCT6776F), with an i5-2550K CPU, on kernel
> > 3.3.
> > 
> > The coretemp module and my BIOS reports my idle temperatures at around
> > 33-35C, while PECI in Linux reports in at 23-25. It looks to be 10
> > degrees off. Under load it scales with coretemp, always staying 10
> > degrees under the average coretemp values.
> > 
> > Unless I'm not understanding something correctly, PECI should not be
> > used and doing so may lead to hardware damage.
> > 
> > coretemp:
> >  Physical id 0:  +36.0 C  (high = +80.0 C, crit = +101.0 C)
> >  Core 0:         +36.0 C  (high = +80.0 C, crit = +101.0 C)
> >  Core 1:         +32.0 C  (high = +80.0 C, crit = +101.0 C)
> >  Core 2:         +34.0 C  (high = +80.0 C, crit = +101.0 C)
> >  Core 3:         +30.0 C  (high = +80.0 C, crit = +101.0 C)
> > 
> > w83627ehf: (nct6775 values are identical)
> >  PECI Agent 0:  +24.0 C
> 
> PECI values are reported (at the hardware level) relative from an
> arbitrary maximum. The coretemp driver uses 101°C as the maximum, your
> results suggests that the w83627ehf and nct6775 drivers use 91°C (or
> maybe 90°C) instead. This isn't going to cause any hardware damage, and
> you can even fix the problem in user-space with a compute formula like:
> 
The maximum should be set by the BIOS. On my system (ASUS mainboard) it
is correctly set to the critical CPU temperature (99 degrees C in my case).
Guess the Maximum board doesn't do that.

> chip "nct6776-*"
> 
>    compute tempN @ + 10, @ - 10
> 
> Guenter, is there a way to know what the NCT6776F thinks the maximum
> temperature is? Maybe we can read it from registers 0x709 or 0x70A? If
> we could present this value as tempN_crit, this would help understand
> the difference of absolute temperatures between coretemp and nct6776.
> 

Good idea. I added that to the nct6775 driver (I don't really want to mess
with the w83627ehf driver - it is getting too complicated).
Output for NCT6776F on my board (i5-2400) is now:

PECI Agent 0:   +39.0°C  (high = +80.0°C, hyst = +75.0°C)
                         (crit = +99.0°C)

and for NCT6775F (i7-2600):

PECI Agent 0:   +32.0°C  (high = +80.0°C, hyst = +75.0°C)
                         (crit = +98.0°C)

The attribute is writable.

Thanks,
Guenter

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

  parent reply	other threads:[~2012-04-28 14:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-14 13:09 [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus iv e Martin Suchanek
2012-04-14 21:58 ` [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus Guenter Roeck
2012-04-20 10:47 ` Martin Suchanek
2012-04-20 15:22 ` Guenter Roeck
2012-04-21  9:38 ` Martin Suchanek
2012-04-21 14:49 ` Guenter Roeck
2012-04-21 15:04 ` Martin Suchanek
2012-04-28  4:30 ` Guenter Roeck
2012-04-28  6:43 ` P.B. V
2012-04-28  8:55 ` Jean Delvare
2012-04-28 10:08 ` Martin Suchanek
2012-04-28 10:22 ` Jean Delvare
2012-04-28 10:48 ` Martin Suchanek
2012-04-28 14:43 ` Guenter Roeck [this message]
2012-04-28 15:00 ` Guenter Roeck
2012-04-28 15:36 ` Guenter Roeck
2012-04-28 19:30 ` Guenter Roeck
2012-04-28 23:18 ` Martin Suchanek
2012-04-28 23:41 ` Guenter Roeck
2012-04-29  9:42 ` Martin Suchanek

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=20120428144324.GA23747@ericsson.com \
    --to=guenter.roeck@ericsson.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.