Public bug reported:

Description:    Ubuntu 10.04 LTS  Release:      10.04
apt-cache policy lm-sensors
lm-sensors:
  Installed: 1:3.1.2-2
  Candidate: 1:3.1.2-2
  Version table:
 *** 1:3.1.2-2 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

What I did:
sensors -v
sensors version 3.1.2 with libsensors version 3.1.2
fah...@matrix-27:~$ snmpwalk -c public -v 2c 127.0.0.1 lm
LM-SENSORS-MIB::lmTempSensorsIndex.1 = INTEGER: 0
LM-SENSORS-MIB::lmTempSensorsIndex.2 = INTEGER: 1
LM-SENSORS-MIB::lmTempSensorsDevice.1 = STRING: temp1
LM-SENSORS-MIB::lmTempSensorsDevice.2 = STRING: temp1
LM-SENSORS-MIB::lmTempSensorsValue.1 = Gauge32: 48000
LM-SENSORS-MIB::lmTempSensorsValue.2 = Gauge32: 120000
LM-SENSORS-MIB::lmMiscSensorsIndex.1 = INTEGER: 0
LM-SENSORS-MIB::lmMiscSensorsIndex.2 = INTEGER: 1
LM-SENSORS-MIB::lmMiscSensorsIndex.3 = INTEGER: 2
LM-SENSORS-MIB::lmMiscSensorsIndex.4 = INTEGER: 3
LM-SENSORS-MIB::lmMiscSensorsIndex.5 = INTEGER: 4
LM-SENSORS-MIB::lmMiscSensorsIndex.6 = INTEGER: 5
LM-SENSORS-MIB::lmMiscSensorsIndex.7 = INTEGER: 6
LM-SENSORS-MIB::lmMiscSensorsIndex.8 = INTEGER: 7
LM-SENSORS-MIB::lmMiscSensorsDevice.1 = STRING: Core 0
LM-SENSORS-MIB::lmMiscSensorsDevice.2 = STRING: Core 0
LM-SENSORS-MIB::lmMiscSensorsDevice.3 = STRING: Core 0
LM-SENSORS-MIB::lmMiscSensorsDevice.4 = STRING: Core 0
LM-SENSORS-MIB::lmMiscSensorsDevice.5 = STRING: Core 1
LM-SENSORS-MIB::lmMiscSensorsDevice.6 = STRING: Core 1
LM-SENSORS-MIB::lmMiscSensorsDevice.7 = STRING: Core 1
LM-SENSORS-MIB::lmMiscSensorsDevice.8 = STRING: Core 1
LM-SENSORS-MIB::lmMiscSensorsValue.1 = Gauge32: 41000
LM-SENSORS-MIB::lmMiscSensorsValue.2 = Gauge32: 105000
LM-SENSORS-MIB::lmMiscSensorsValue.3 = Gauge32: 105000
LM-SENSORS-MIB::lmMiscSensorsValue.4 = Gauge32: 0
LM-SENSORS-MIB::lmMiscSensorsValue.5 = Gauge32: 40000
LM-SENSORS-MIB::lmMiscSensorsValue.6 = Gauge32: 105000
LM-SENSORS-MIB::lmMiscSensorsValue.7 = Gauge32: 105000
LM-SENSORS-MIB::lmMiscSensorsValue.8 = Gauge32: 0

What shoud show up is a temp of around 45000 for sensors value .2, but it's 
showing 105000. 
 So, I did this:

sensors -v
sensors version 3.1.2 with libsensors version 3.1.2

sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:       +47.0°C  (crit = +120.0°C)                  
temp2:       +47.0°C  (crit = +120.0°C)                  

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +42.0°C  (high = +105.0°C, crit = +105.0°C)  

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +39.0°C  (high = +105.0°C, crit = +105.0°C)  


This shows that 'sensors' is working correctly.  My history I keep with MRTG 
shows that this incorrect high temp reading started after an update around the 
8th of May or close to it.  Prior to May, lm-sensors was working correctly on 
my laptop.
If you need any other info, please contact me, I'll be glad to help. Dylan 
sends!

** Affects: lm-sensors-3 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
lmTempSensorsValue.2 incorrect
https://bugs.launchpad.net/bugs/597822
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to