[SOLVED] Sensors output

Mantra · 09-11-2023, 02:23 PM

Hi, I noticed the output from sensors looks... strange. Is there anything here to be worried about - especially the voltages where it says 'alarm'? (Some of the temperatures don't make sense, there isn't anything below 0C in my computer, I'm sure of that much!)

Quote:

nct6796-isa-0290
Adapter: ISA adapter
Vcore: 1.34 V (min = +0.00 V, max = +1.74 V)
in1: 1.86 V (min = +0.00 V, max = +0.00 V) ALARM
AVCC: 3.46 V (min = +2.98 V, max = +3.63 V)
+3.3V: 3.34 V (min = +2.98 V, max = +3.63 V)
in4: 1.69 V (min = +0.00 V, max = +0.00 V) ALARM
in5: 296.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in6: 216.00 mV (min = +0.00 V, max = +0.00 V) ALARM
3VSB: 3.46 V (min = +2.98 V, max = +3.63 V)
Vbat: 3.18 V (min = +2.70 V, max = +3.63 V)
in9: 0.00 V (min = +0.00 V, max = +0.00 V)
in10: 200.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in11: 224.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in12: 232.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in13: 216.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in14: 1.70 V (min = +0.00 V, max = +0.00 V) ALARM
fan1: 1288 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)
fan7: 0 RPM (min = 0 RPM)
SYSTIN: +39.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
CPUTIN: +32.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
AUXTIN0: +88.5°C sensor = thermistor
AUXTIN1: +95.0°C sensor = thermistor
AUXTIN2: +93.0°C sensor = thermistor
AUXTIN3: -14.0°C sensor = thermistor
PCH_CHIP_CPU_MAX_TEMP: +0.0°C
PCH_CHIP_TEMP: +0.0°C
PCH_CPU_TEMP: +0.0°C
PCH_MCH_TEMP: +0.0°C
intrusion0: ALARM
intrusion1: ALARM
beep_enable: disabled

acpitz-acpi-0
Adapter: ACPI interface
temp1: +38.0°C (crit = +95.0°C)

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

business_kid · 09-12-2023, 02:49 PM

Is your question about a computer? You've told us nothing at all about your machine, OS, age, etc.

metaed · 09-12-2023, 02:55 PM

Quote:

Originally Posted by business_kid

Is your question about a computer?

Code:

$ which sensors
/usr/bin/sensors

Mantra · 09-12-2023, 03:57 PM

Sorry, yes!

Desktop PC, running Ubuntu jammy. Asrock J5040-ITX motherboard with integrated Pentium silver CPU.

Sensors binary from lm-sensors version 1:3.6.0-7ubuntu1.

It's the voltages that I'm puzzled by, it's showing voltages on several sensors which (according to the output) should be zero. What does that mean, and should I do anything about it?

obobskivich · 09-12-2023, 09:36 PM

More likely its either erroneous reads or a lack of support on sensors' part for whatever is being scraped. If something isn't running right you may want to investigate further, but unfortunately this is often the reality of sensors - its imperfect.

kilgoretrout · 09-13-2023, 09:38 AM

Agree that it's probably a problem with lm-sensors support rather than anything wrong with your hardware. You may want to check sensor readings in the bios setup.

business_kid · 09-13-2023, 01:09 PM

Quote:

Originally Posted by Mantra

Sorry, yes!

Desktop PC, running Ubuntu jammy. Asrock J5040-ITX motherboard with integrated Pentium silver CPU.

Sensors binary from lm-sensors version 1:3.6.0-7ubuntu1.

It's the voltages that I'm puzzled by, it's showing voltages on several sensors which (according to the output) should be zero. What does that mean, and should I do anything about it?

Have you ever run 'sensors-detect'? It should be run and detects the sensor stuff you should pay attention to. A lot of that stuff might be nonsense, as others have said.

Mantra · 09-14-2023, 11:43 AM

Ok thanks for the replies. I checked the bios, and that only shows about half the sensors, and none of the ones that are showing alarms. So I guess those are spurious as suggested. sensors-detect runs fine and detects these chips, but I suppose there's something about the output which makes it "detect" more outputs than are actually on the chip.