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: 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. -- Jean Delvare _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
