Hello, guest. We have noticed that you are not registered at this bug tracker. Your experience will be greatly enhanced if you log in. To do so, you first must register by clicking on the Register tab at the top. If you are already registered, you can login at the Login tab.
Syndicate Syndicate Listing Display Search Login/Register
Bug Id ?
Reporter ?
bobtfish
Product/Version ?
HardInfo / 0.5.1
Status ?
Unconfirmed
Severity ?
Minor
Duplicate Of ?
- none -
Summary ?
Repeated and missing temperatures
Report Time ?
August 15, 2010 12:09:53 PM
Assignment ?
- none -
Resolution ?
Open
Priority ?
Normal
Dependencies ?
- none -


Votes
For: 0 (0%)
Against: 0 (0%)
Total: 0

August 15, 2010 12:09:53 PM bobtfish
In Devices->Sensors, the first temperature result is repeated 3 times. The others only appear once, but some other temperatures are missing, but do appear in other programs, so are available (both cores, and GPU).
Using Ubuntu 10.04, what hardware information would be useful? I'm afraid I'm a bit clueless, but according to lshw:
description: Motherboard - product: G31M-ES2L - vendor: Gigabyte Technology Co., Ltd.
and processor: Pentium(R) Dual-Core CPU E5300 @ 2.60GHz

August 16, 2010 01:25:54 PM bobtfish
As per a discussion on the Ubuntu forums, I ran "sensors", with the following output:
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +37.0°C (high = +76.0°C, crit = +100.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +32.0°C (high = +76.0°C, crit = +100.0°C)

it8718-isa-0290

... lots of voltages that are reported correctly in HardInfo...

fan2: 2721 RPM (min = 0 RPM)
temp1: -55.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
temp2: -2.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
temp3: +20.0°C (low = +127.0°C, high = +127.0°C) sensor = thermal diode
cpu0_vid: +3.300 V

Now, stupid results for the temp1 and temp2 aside, the last 3 temperatures listed do appear in HardInfo, but with temp1 repeated 3 times.
The first 2 core temperatures do not appear in HardInfo at all.

December 15, 2010 11:09:04 AM Leandro Pereira
I've never been able to reproduce this bug, so fixing it is pretty complicated. I've looked through the sensors code a lot of times and it seems to be just fine.