Bug 1394747 - sensors reports wrong temperatures
Summary: sensors reports wrong temperatures
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: lm_sensors
Version: 24
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Jaromír Cápík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-14 11:37 UTC by Pierre Blavy
Modified: 2017-08-08 19:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 19:15:47 UTC
Type: Bug


Attachments (Terms of Use)
dmidecode (full) (7.84 KB, text/plain)
2016-11-14 11:37 UTC, Pierre Blavy
no flags Details

Description Pierre Blavy 2016-11-14 11:37:58 UTC
Created attachment 1220365 [details]
dmidecode (full)

Description of problem:
The temperatures reported by sensors are wrong



Version-Release number of selected component (if applicable):
sensors --version
sensors version 3.4.0 with libsensors version 3.4.0

uname -a
Linux xxxx.xxx 4.8.6-201.fc24.x86_64 #1 SMP Thu Nov 3 14:38:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux



How reproducible: always



Steps to Reproduce:
1. type sensors in a terminal

Actual results:
sensors
nct6776-isa-0290
Adapter: ISA adapter
Vcore:          +1.26 V  (min =  +0.00 V, max =  +1.74 V)
in1:            +0.19 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC:           +3.20 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:          +3.18 V  (min =  +2.98 V, max =  +3.63 V)
in4:            +0.46 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:            +1.71 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:            +1.86 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.63 V)
fan1:          1481 RPM  (min =    0 RPM)
fan2:             0 RPM  (min =    0 RPM)
fan3:             0 RPM  (min =    0 RPM)
fan4:             0 RPM  (min =    0 RPM)
fan5:             0 RPM  (min =    0 RPM)
SYSTIN:         +27.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = thermistor
CPUTIN:         +27.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN:         -29.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
PCH_CHIP_TEMP:   +0.0°C  
PCH_CPU_TEMP:    +0.0°C  
PCH_MCH_TEMP:    +0.0°C  
intrusion0:    OK
intrusion1:    OK
beep_enable:   disabled

radeon-pci-0008
Adapter: PCI adapter
temp1:         -2.0°C  (crit = +120.0°C, hyst = +90.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:         +0.0°C  (high = +70.0°C)
                       (crit = +70.0°C, hyst = +69.0°C)


Expected results:
- The temp1 temperatures should be around 40°C, not around 0.
- No temperature should be below 0°C, as it's more than 16°C in my flat, and there is no heat pump in the PC (only fans).



Additional info: 
- Temperatures in the UEFI are OK
- I suspect a Kelvin to degree conversion that's done twice.


dmidecode -t 2
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: ASRock
	Product Name: FM2A88X Pro3+
	Version:                       
	Serial Number: M80-57006400989
	Asset Tag:                       
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis:                       
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

Comment 1 Fedora End Of Life 2017-07-25 23:52:52 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-08-08 19:15:47 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.