You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2024-06-18 15:12:10
- evilch3n
- Member
- Registered: 2020-04-12
- Posts: 15
[SOLVED]single sensor being very high
Hi, i know there are plenty of sensor threads but i couldn't find a fitting one.
i noticed several sensor tools show a high temperatur 79-80°C on "Thermistor 0" or sometimes called "nct6683/temp6"
system is complete idle htop showing nothing.
using a amd 7800x3d cpu with a MSI PRO B650-P WIFI board
my question is: is it a display issue or is my system slowly burning deep down somewhere? the worrying part is that the temp is moving from 79 to 80
sensors output:
mt7921_phy0-pci-0f00
Adapter: PCI adapter
temp1: +36.0°C
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +49.6°C
Tccd1: +36.9°C
nvme-pci-1200
Adapter: PCI adapter
Composite: +25.9°C (low = -273.1°C, high = +84.8°C)
(crit = +84.8°C)
Sensor 1: +25.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +26.9°C (low = -273.1°C, high = +65261.8°C)
amdgpu-pci-0300
Adapter: PCI adapter
vddgfx: 405.00 mV
fan1: 0 RPM (min = 0 RPM, max = 3200 RPM)
edge: +29.0°C (crit = +100.0°C, hyst = -273.1°C)
(emerg = +105.0°C)
junction: +35.0°C (crit = +110.0°C, hyst = -273.1°C)
(emerg = +115.0°C)
mem: +40.0°C (crit = +108.0°C, hyst = -273.1°C)
(emerg = +113.0°C)
PPT: 13.00 W (cap = 339.00 W)
nct6687-isa-0a20
Adapter: ISA adapter
VIN0: 992.00 mV (min = +0.00 V, max = +0.00 V)
VIN1: 1.01 V (min = +0.00 V, max = +0.00 V)
VIN2: 1.30 V (min = +0.00 V, max = +0.00 V)
VIN3: 624.00 mV (min = +0.00 V, max = +0.00 V)
VIN4: 1.09 V (min = +0.00 V, max = +0.00 V)
VIN5: 240.00 mV (min = +0.00 V, max = +0.00 V)
VIN6: 800.00 mV (min = +0.00 V, max = +0.00 V)
VIN7: 1.54 V (min = +0.00 V, max = +0.00 V)
VCC: 3.36 V (min = +0.00 V, max = +0.00 V)
fan1: 718 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)
fan6: 0 RPM (min = 0 RPM)
fan7: 0 RPM (min = 0 RPM)
fan8: 0 RPM (min = 0 RPM)
fan9: 0 RPM (min = 0 RPM)
fan10: 0 RPM (min = 0 RPM)
AMD TSI Addr 98h: +50.0°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = AMD AMDSI
Diode 0 (curr): +35.5°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermal diode
Thermistor 15: +33.5°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermistor
Thermistor 1: +37.0°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermistor
Thermistor 16: +31.5°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermistor
Thermistor 0: +80.0°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermistor
Thermistor 15: +33.5°C (low = +0.0°C)
(high = +125.0°C, hyst = +35.0°C)
(crit = +0.0°C) sensor = thermistor
intrusion0: ALARM
beep_enable: disabled
nvme-pci-0400
Adapter: PCI adapter
Composite: +43.9°C (low = -5.2°C, high = +89.8°C)
(crit = +93.8°C)
amdgpu-pci-1300
Adapter: PCI adapter
vddgfx: 1.10 V
vddnb: 1.30 V
edge: +39.0°C
PPT: 43.22 W Last edited by evilch3n (2024-06-22 13:44:47)
Offline
#2 2024-06-18 17:43:08
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 75,277
Re: [SOLVED]single sensor being very high
https://bbs.archlinux.org/viewtopic.php … 7#p2126297 has that sensor and similar temperatures for "PCIe x1" but that value shows up more reasonable in https://github.com/Fred78290/nct6687d and many other posts involving that sensor do not have isolated hot values.
Do you have anything slotted into the PCIe x1 port and/or does it feel hot (be careful! 80°C can cause burns through materials with high thermal conductivity, ie. metal)
Offline
#3 2024-06-19 06:21:34
- evilch3n
- Member
- Registered: 2020-04-12
- Posts: 15
Re: [SOLVED]single sensor being very high
hey thanks for the response.
i tried to see if anything is in the PCIe-x1 but there is nothing, also no hot areas were found (also the gpu is blocking 80% of the space but its complete idle and not running hot)
then i tried to install the linked nct-module but it seems its already inside the 6.9.1 kernel.
output from the installer-script:
nct6687.ko.zst:
Running module version sanity check.
Module version for nct6687.ko.zst
exactly matches what is already found in kernel 6.9.1-arch1-1.
DKMS will not replace this module.then i tried to figure if its properly loaded or something and looked into dmesg
output from sudo dmesg | grep nct6
[ 9.421890] nct6683: Found NCT6687D or compatible chip at 0x4e:0xa20
[ 9.425596] nct6683 nct6683.2592: NCT6687D EC firmware version 0.0 build 09/27/22
[ 751.410908] nct6683: Found NCT6687D or compatible chip at 0x4e:0xa20
[ 751.414609] nct6683 nct6683.2592: NCT6687D EC firmware version 0.0 build 09/27/22
[ 2132.688751] nct6687: loading out-of-tree module taints kernel.
[ 2132.688756] nct6687: module verification failed: signature and/or required key missing - tainting kernel
[ 2133.699987] nct6687: Found NCT6687D or compatible chip at 0x004e:0x0a20
[ 2133.705785] nct6687 nct6687.2592: NCT6687D EC firmware version 0.0 build 09/27/22i dont know what it means with tainting kernel but i guess i have to read upon that later today
Offline
#4 2024-06-19 07:55:57
- jl2
- Member
- From: 47° 18' N 8° 34' E
- Registered: 2022-06-01
- Posts: 1,318
Re: [SOLVED]single sensor being very high
If you are sure that the value is wrong, you can adjust the values as described in https://wiki.archlinux.org/title/Lm_sen … ing_values
or simply ignore it.
A tainted kernel is a kernel that has loaded out of tree modules, e.g. the ones made by dkms. nothing to worry about.
Last edited by jl2 (2024-06-19 07:56:10)
Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...
Offline
#5 2024-06-19 08:02:58
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 75,277
Re: [SOLVED]single sensor being very high
I only posted the github link to illustrate the sensor condition.
The taint is just a flag that you loaded an out of tree module, it's otherwise meaningless and will just show up when reporting kernel bugs.
But the kernel (6.9.5) "only" has
usr/lib/modules/6.9.5-arch1-1/kernel/drivers/hwmon/nct6683.ko.zst
usr/lib/modules/6.9.5-arch1-1/kernel/drivers/hwmon/nct6775-core.ko.zst
usr/lib/modules/6.9.5-arch1-1/kernel/drivers/hwmon/nct6775-i2c.ko.zst
usr/lib/modules/6.9.5-arch1-1/kernel/drivers/hwmon/nct6775.ko.zst
usr/lib/modules/6.9.5-arch1-1/kernel/drivers/hwmon/nct7802.ko.zst
usr/lib/modules/6.9.5-arch1-1/kernel/drivers/hwmon/nct7904.ko.zstNo nct6687.ko.zst and you also seem to be able to load it - might be the same code on a different name, though.
https://github.com/Fred78290/nct6687d/issues/72 and https://github.com/Fred78290/nct6687d/issues/96 are MSI boards w/ similar results on the PCIx1 slot
Can you disable it or, maybe even better, do you have a PCIe x1 card to put there to test the behavior?
Offline
#6 2024-06-19 13:53:34
- cryptearth
- Member
- Registered: 2024-02-03
- Posts: 2,112
Re: [SOLVED]single sensor being very high
I run a 5600 on a MSI B550-A pro and also use the nct6687d because whatever sensors-detect wants to load causes issues.
As I also have liquid cooling (monitored by liquidctl) and my new 7700xt uses its own curve I not rely on lm_sensors or fancontrol. But every once in a while my nvme-ssd also reports a high temp until I call it with sudo once which sometimes trigger some SMART warning at cold boot. But I confirmed that tge reported hotspot temp is wrong and the real value doesn't exceed the recommended max temp.
TLDR: could be a faulty sensor. Unless your system is a closed hot cell and really gets up to 80c I would ignore it.
Offline
#7 2024-06-22 13:44:19
- evilch3n
- Member
- Registered: 2020-04-12
- Posts: 15
Re: [SOLVED]single sensor being very high
busy week - i've checked everything physically on my board it seems to be a faulty reporting, also i don't have something to put into the PCIx1 Slot to test it any further right now,
i think the case can be closed/is solved only thing i will check is why the nct6687 installer claims to already be installed when seth confirmed its not in the kernel, but that's another issue.
thank you for your support everyone
Offline
#8 2024-06-22 14:41:12
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 75,277
Re: [SOLVED]single sensor being very high
The in-tree module is nct6683 and if we trust dkms it's currently equivalent to the out-of-tree module nct6687
Offline
#9 2024-06-22 19:43:12
- cryptearth
- Member
- Registered: 2024-02-03
- Posts: 2,112
Re: [SOLVED]single sensor being very high
The in-tree module is nct6683 and if we trust dkms it's currently equivalent to the out-of-tree module nct6687
at least for my msi b550a-pro there's quite a different output
in-tree 6683
nct6687-isa-0a20
Adapter: ISA adapter
VIN0: 1.01 V (min = +0.00 V, max = +0.00 V)
VIN1: 1.01 V (min = +0.00 V, max = +0.00 V)
VIN2: 1.10 V (min = +0.00 V, max = +0.00 V)
VIN3: 656.00 mV (min = +0.00 V, max = +0.00 V)
VIN4: 592.00 mV (min = +0.00 V, max = +0.00 V)
VIN5: 800.00 mV (min = +0.00 V, max = +0.00 V)
VIN6: 720.00 mV (min = +0.00 V, max = +0.00 V)
VIN7: 1.52 V (min = +0.00 V, max = +0.00 V)
VCC: 3.34 V (min = +0.00 V, max = +0.00 V)
VTT: 1.81 V (min = +0.00 V, max = +0.00 V)
VSB: 3.36 V (min = +0.00 V, max = +0.00 V)
AVSB: 3.34 V (min = +0.00 V, max = +0.00 V)
VTT: 1.81 V (min = +0.00 V, max = +0.00 V)
VBAT: 0.00 V (min = +0.00 V, max = +0.00 V)
fan1: 0 RPM (min = 0 RPM)
fan2: 1246 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
fan5: 0 RPM (min = 0 RPM)
fan6: 0 RPM (min = 0 RPM)
fan7: 0 RPM (min = 0 RPM)
fan8: 0 RPM (min = 0 RPM)
fan9: 0 RPM (min = 0 RPM)
fan10: 0 RPM (min = 0 RPM)
AMD TSI Addr 98h: +35.0°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = AMD AMDSI
Diode 0 (curr): +36.0°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermal diode
Thermistor 15: +41.0°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermistor
Thermistor 1: +41.5°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermistor
Thermistor 16: +35.0°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermistor
Thermistor 0: +37.0°C (low = +0.0°C)
(high = +0.0°C, hyst = +0.0°C)
(crit = +0.0°C) sensor = thermistor
Thermistor 15: +0.0°C (low = +0.0°C)
(high = +126.0°C, hyst = +30.0°C)
(crit = +0.0°C) sensor = thermistor
intrusion0: ALARM
beep_enable: disabled6687d dkms
nct6687-isa-0a20
Adapter: ISA adapter
+12V: 12.10 V (min = +12.10 V, max = +12.10 V)
+5V: 5.04 V (min = +5.04 V, max = +5.04 V)
+3.3V: 3.36 V (min = +3.36 V, max = +3.36 V)
CPU Soc: 1.11 V (min = +1.11 V, max = +1.11 V)
CPU Vcore: 1.01 V (min = +1.01 V, max = +1.02 V)
CPU 1P8: 1.82 V (min = +1.82 V, max = +1.82 V)
CPU VDDP: 0.00 V (min = +0.00 V, max = +0.00 V)
DRAM: 1.34 V (min = +1.34 V, max = +1.34 V)
Chipset: 788.00 mV (min = +0.79 V, max = +0.79 V)
CPU SA: 728.00 mV (min = +0.73 V, max = +0.73 V)
Voltage #2: 1.54 V (min = +1.54 V, max = +1.54 V)
AVCC3: 3.35 V (min = +3.35 V, max = +3.35 V)
AVSB: 3.36 V (min = +3.36 V, max = +3.36 V)
VBat: 1.82 V (min = +1.82 V, max = +1.82 V)
CPU Fan: 0 RPM (min = 0 RPM, max = 0 RPM)
Pump Fan: 1246 RPM (min = 1246 RPM, max = 1250 RPM)
System Fan #1: 0 RPM (min = 0 RPM, max = 0 RPM)
System Fan #2: 0 RPM (min = 0 RPM, max = 0 RPM)
System Fan #3: 0 RPM (min = 0 RPM, max = 0 RPM)
System Fan #4: 0 RPM (min = 0 RPM, max = 0 RPM)
System Fan #5: 0 RPM (min = 0 RPM, max = 0 RPM)
System Fan #6: 0 RPM (min = 0 RPM, max = 0 RPM)
CPU: +40.0°C (low = +40.0°C, high = +40.0°C)
System: +37.0°C (low = +36.0°C, high = +37.0°C)
VRM MOS: +43.5°C (low = +43.0°C, high = +43.5°C)
PCH: +41.5°C (low = +41.0°C, high = +41.5°C)
CPU Socket: +37.0°C (low = +37.0°C, high = +37.0°C)
PCIe x1: +38.0°C (low = +38.0°C, high = +38.0°C)
M2_1: +0.0°C (low = +0.0°C, high = +0.0°C)There's also quite a different when running pwmconfig: With the in-tree 6683 the additional fan headers (no matter they're not connected) are not even detected. With the dkms 6687d one they get detected and at least the script tries to modify them - but as nothing is connected it fails as the change in pwm input isn't reflected in any change in the sense output. Current I don't have any 4-pin pwm fans to test the headers.
I'm not sure if this is again one of these "the chips don't do what thier datasheets say" (see the recent issues with ASMedia SATA controllers I "forced" to get revereted (as one of the devs replied: waiting for unconnected ports is less a pain than drives not found)) - or if there're just so many different chips out there that it's not feasible to have them all upstream - and in difference to windows where hardware vendors provide drivers the linux community has to come up with thier own
Offline
#10 2024-06-22 21:18:31
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 75,277
Re: [SOLVED]single sensor being very high
Seems dkms is prone to yelling false positives here, https://github.com/dell/dkms/issues/384 & https://github.com/dell/dkms/issues/311
Offline
Pages: 1