Re: high value for CPUTIN

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Oct 29, 2012 at 02:00:33AM -0300, Alejandro Jakubi wrote:
> I observe a very high value for CPUTIN, namely 96.5C, far above the
> high limit of 80C, that seems inconsistent with all the other values
> of temperature provided by lm-sensors, in the range of the 30s C.
> And also seems inconsistent with the BIOS values: CPU 37C, MB 33C.
> Besides, I guess that the CPU would no longer work at that
> temperature...
> 
> Find appended below the information requested in the FAQ, as far as I have
> understood it as relevant for this case. Just tell me whether additional
> information is needed.
> 
> So, I wonder whether this is a bug, a weakness of the sensor (diode?) and
> possible solutions or workarounds.
> 
> 
> ======================
> lm-sensors version: 1:3.3.1-2ubuntu1
> 
> Linux Mint Release 13 (maya) 32-bit
> Kernel Linux 3.2.0-23-generic
> GNOME 3.4.2
> 
> Intel Core i7-3820 CPU @ 3.60GHz
> 
> Mother Asus P9X79
> 
> ==================
> sensor:
> 
> coretemp-isa-0000
> Adapter: ISA adapter
> Physical id 0:  +35.0°C  (high = +82.0°C, crit = +100.0°C)
> Core 0:         +34.0°C  (high = +82.0°C, crit = +100.0°C)
> Core 1:         +32.0°C  (high = +82.0°C, crit = +100.0°C)
> Core 2:         +34.0°C  (high = +82.0°C, crit = +100.0°C)
> Core 3:         +33.0°C  (high = +82.0°C, crit = +100.0°C)
> 
> nct6776-isa-0290
> Adapter: ISA adapter
> Vcore:         +0.94 V  (min =  +0.00 V, max =  +1.74 V)
> in1:           +1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> AVCC:          +3.31 V  (min =  +2.98 V, max =  +3.63 V)
> +3.3V:         +3.30 V  (min =  +2.98 V, max =  +3.63 V)
> in4:           +1.00 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> in5:           +2.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> 3VSB:          +3.42 V  (min =  +2.98 V, max =  +3.63 V)
> Vbat:          +3.36 V  (min =  +2.70 V, max =  +3.30 V)  ALARM
> fan1:            0 RPM  (min =    0 RPM)  ALARM
> fan2:         4411 RPM  (min =    0 RPM)  ALARM
> fan3:            0 RPM  (min =    0 RPM)  ALARM
> fan4:            0 RPM  (min =    0 RPM)  ALARM
> fan5:            0 RPM  (min =    0 RPM)  ALARM
> SYSTIN:        +33.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = thermistor
> CPUTIN:        +96.5°C  (high = +80.0°C, hyst = +75.0°C)  ALARM  sensor = diode
> AUXTIN:        +33.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
> PECI Agent 0:  +33.5°C
> cpu0_vid:     +1.708 V
> intrusion0:   OK
> intrusion1:   ALARM
> 

Usage notes from the new prototype driver for NCT6775/NCT6776:

On various ASUS boards with NCT6776F, it appears that CPUTIN is not really
connected to anything and floats, or that it is connected to some non-standard
temperature measurement device. As a result, the temperature reported on CPUTIN
will not reflect a usable value. It often reports unreasonably high
temperatures, and in some cases the reported temperature declines if the actual
temperature increases (similar to the raw PECI temperature value - see PECI
specification for details). CPUTIN should therefore be be ignored on ASUS
boards. The CPU temperature on ASUS boards is reported from PECI 0.

Guenter

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



[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux