Bug 2131580

Summary: temperatures displayed by sensors program are strange
Product: [Fedora] Fedora Reporter: pgaltieri <pgaltieri>
Component: lm_sensorsAssignee: Hans de Goede <hdegoede>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 35CC: aegorenkov.91, hdegoede, jaromir.capik, jorton, olysonek-foss, pknirsch
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 18:09:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description pgaltieri 2022-10-02 16:05:34 UTC
Description of problem:
I ran sensors-detect to detect the sensors on my laptop and the ran sensors to display the data.  Here is the output

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +49.0°C  

pch_cometlake-virtual-0
Adapter: Virtual device
temp1:        +52.0°C  

ucsi_source_psy_USBC000:002-isa-0000
Adapter: ISA adapter
in0:           0.00 V  (min =  +0.00 V, max =  +0.00 V)
curr1:         3.00 A  (max =  +0.00 A)

nvme-pci-6c00
Adapter: PCI adapter
Composite:    +41.9°C  (low  = -20.1°C, high = +81.8°C)
                       (crit = +83.8°C)
Sensor 1:     +41.9°C  (low  = -273.1°C, high = +65261.8°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +64.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +64.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +61.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:        +63.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:        +61.0°C  (high = +100.0°C, crit = +100.0°C)

dell_smm-isa-0000
Adapter: ISA adapter
fan1:        3194 RPM  (min =    0 RPM, max = 4800 RPM)
fan2:        3485 RPM  (min =    0 RPM, max = 4800 RPM)
temp1:        +61.0°C  
temp2:        +47.0°C  
temp3:        +51.0°C  
temp4:        +54.0°C  
temp5:        +43.0°C  
temp6:        +36.0°C  
temp7:        +41.0°C  
temp8:        +44.0°C  
temp9:        +50.0°C  

ucsi_source_psy_USBC000:003-isa-0000
Adapter: ISA adapter
in0:           5.00 V  (min =  +5.00 V, max =  +5.00 V)
curr1:         0.00 A  (max =  +1.50 A)

ucsi_source_psy_USBC000:001-isa-0000
Adapter: ISA adapter
in0:          15.00 V  (min = +26.55 V, max = +20.00 V)
curr1:         4.50 A  (max =  +4.50 A)

BAT0-acpi-0
Adapter: ACPI interface
in0:          12.55 V  
curr1:       1000.00 uA 

You will notice the following:

nvme-pci-6c00
Adapter: PCI adapter
Composite:    +41.9°C  (low  = -20.1°C, high = +81.8°C)
                       (crit = +83.8°C)
Sensor 1:     +41.9°C  (low  = -273.1°C, high = +65261.8°C)

The composite temperature show a low temperature of -20.1 C. This is not possible.  You will also notice that Sensor 1 shows a low of -273.1 C this is absolute 0 Kelvin which is -273.15 C and a maximum of 65261.8 C.  I think if my laptop had a sensor that got this high a temperature it would be in serious trouble.


Version-Release number of selected component (if applicable):
3.6

How reproducible:
Always


Steps to Reproduce:
1.run sensors-detect
2.run sensors
3.

Actual results:
Temperatures showing in the negative range and excessively high.

Expected results:
Reasonable temperature values

Additional info:
This is Dell Model XPS 15 9500 with Intel(R) Core(TM) i5-10300H CPU @ 2.50GHz.

Comment 1 Ben Cotton 2022-11-29 19:01:24 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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
'version' of '35'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Ben Cotton 2022-12-13 18:09:23 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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