Re: Gigabyte MA785GMT-UD2H

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

 



> > lm90-i2c-2-4c
> > Adapter: NVIDIA i2c adapter 
> > temp1:       +29.0°C  (low  =  +0.0°C, high = +105.0°C)  
> >                       (crit = +127.0°C, hyst = +117.0°C)  
> > temp2:       +19.6°C  (low  = -11.0°C, high = +94.0°C)  
> >                       (crit = +127.0°C, hyst = +117.0°C)  
> > 
> > 
> > Verified that these go up when the graphics card is busy.
> 
> The values are surprising. temp1 is on the sensor chip itself, so it's
> the graphics adapter's temperature. Sounds reasonable. temp2 OTOH is a
> remote sensors, which typically monitors the GPU. It should be much
> hotter, and can anyway not be cooler than the board.
> 
> Are you sure sensors-detect found an LM90 chip and not an LM99? The
> LM99 has a 16 degrees offset on temp2, 35°C would see more reasonable.

Ran sensors-detect again and it was LM99.  So tried this instead:

echo lm99 0x4c > /sys/bus/i2c/devices/i2c-2/new_device
sensors
lm99-i2c-2-4c
Adapter: NVIDIA i2c adapter 
temp1:       +27.0°C  (low  =  +0.0°C, high = +105.0°C)  
                      (crit = +127.0°C, hyst = +117.0°C)  
temp2:       +34.9°C  (low  =  +5.0°C, high = +110.0°C)  
                      (crit = +143.0°C, hyst = +133.0°C)  

but that doesn't agree with the nvidia tools either:

nvidia-smi --query-gpu-info -a

GPU 0:
        Product Name            : Quadro FX 1400
        PCI ID                  : ce10de
        Temperature             : 38 C

Ran a graphics intensive program and did this again and both went up 5C,
so it looks like lm99 reads 3C below the actual temp fairly
consistently.  For whatever it is worth speedfan showed 40C when "idle",
but idle on W7 is probably not the same as idle on linux.  Is there a
way to add 3C to the lm99 reading in the sensors.conf file?

<SNIP>

> This is expected. As I understand it, the K8 sensor was per-core (or
> even 2 sensors per core) while the K10 sensor is per CPU package.

I thought these CPUs had both per core sensors and a package sensor. 
Why report only the last one?  Maybe because some of Brisbane chips had
broken core sensors?  This is Regor though, hopefully with working core
sensors.

Thanks,

David Mathog
mathog@xxxxxxxxxxx
Manager, Sequence Analysis Facility, Biology Division, Caltech

_______________________________________________
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