Created attachment 161780 [details] sudo dmidecode >/tmp/dmidecode SUMMARY Upon adding CPU temp to the system monitor it always hows 0.0 C STEPS TO REPRODUCE 1. open system monitor 2. add cpu temp to cpu monitor (group or single core does not matter) 3. read cpu temp provided OBSERVED RESULT Fails to show CPU temp EXPECTED RESULT See real CPU temp SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-5-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Pentium® CPU N3710 @ 1.60GHz Memory: 3.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 405 Manufacturer: ASUSTeK COMPUTER INC. Product Name: X541SA System Version: 1.0 ADDITIONAL INFORMATION $ cat /sys/class/thermal/thermal_zone*/temp 45000 45000 20000 43000 36000 37000 $ sensors asus-isa-0000 Adapter: ISA adapter cpu_fan: 2300 RPM temp1: +6280.4°C soc_dts0-virtual-0 Adapter: Virtual device temp1: +35.0°C BAT0-acpi-0 Adapter: ACPI interface in0: 10.80 V coretemp-isa-0000 Adapter: ISA adapter Core 0: +39.0°C (high = +90.0°C, crit = +90.0°C) Core 1: +39.0°C (high = +90.0°C, crit = +90.0°C) Core 2: +40.0°C (high = +90.0°C, crit = +90.0°C) Core 3: +40.0°C (high = +90.0°C, crit = +90.0°C) soc_dts1-virtual-0 Adapter: Virtual device temp1: +35.0°C drivetemp-scsi-0-0 Adapter: SCSI adapter temp1: +19.0°C acpitz-acpi-0 Adapter: ACPI interface temp1: +35.0°C (crit = +95.0°C) temp2: +35.0°C (crit = +94.0°C) $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 76 model name : Intel(R) Pentium(R) CPU N3710 @ 1.60GHz stepping : 4 microcode : 0x411 cpu MHz : 480.002 cache size : 1024 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp tpr_shadow flexpriority ept vpid tsc_adjust smep erms dtherm ida arat vnmi md_clear vmx flags : vnmi preemption_timer invvpid ept_x_only flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest bugs : cpu_meltdown spectre_v1 spectre_v2 mds msbds_only mmio_unknown bogomips : 3200.00 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management:
Created attachment 161781 [details] screenshot of issue
Can you try applying the patch from bug 438318, and then seeing if "Hardware Sensors/coretemp-isa-0000/Core 0" shows you the correct temperature?
that says it was fixed it version 5.23, this but is present on 5.27.10-0ubuntu1 on the daily kubuntu ISO from yesterday I have only seen this issue on this asus intel laptop (model X541S; w/ a N3710 CPU) at this time (no issue on any of my AMD based desktop) also able to reproduce this on a Intel J2900 (acer axc-603g-uw15) no issues with a Intel i3-2100 (old dell box)
The "Remove blacklist in lmsensors plugin" patch is different from that bug's solution – it's was not merged into the code. If you could check that with this patch you can get the correct temperatures, it would give us another argument in favor of merging the patch.
oh... i am not experienced with compiling (i try to avoid it cause is usually does not work whenever i try...), can i get some instructions for any distro i can boot a live for
I don't know about setting up compilation environment in a live distro; let's drop that idea, it will be more hassle than it's worth. Instead, can you post the output of the following two commands? $ sensors | awk '/^coretemp/,/^$/' $ kstatsviewer cpu/cpu0/temperature
all sensors command was in the 1st post, the other command just hangs and gives nothing... sensors coretemp-* would do the same thing BTW kubuntu@kubuntu:~$ sensors coretemp-* coretemp-isa-0000 Adapter: ISA adapter Core 0: +33.0°C (high = +90.0°C, crit = +90.0°C) Core 1: +33.0°C (high = +90.0°C, crit = +90.0°C) Core 2: +35.0°C (high = +90.0°C, crit = +90.0°C) Core 3: +35.0°C (high = +90.0°C, crit = +90.0°C) kubuntu@kubuntu:~$ kstatsviewer cpu/cpu0/temperature ^C kubuntu@kubuntu:~$ kstatsviewer -details cpu/cpu0/temperature kstatsviewer: Unknown options: d, e, t, a, i, l, s. kubuntu@kubuntu:~$ kstatsviewer --details cpu/cpu0/temperature cpu/cpu0/temperature Name: Core 1 Current Temperature Short Name: Temperature Description: Unit: °C Minimum: 0 Maximum: 0 ^C kubuntu@kubuntu:~$ kstatsviewer --details --remain cpu/cpu0/temperature cpu/cpu0/temperature Name: Core 1 Current Temperature Short Name: Temperature Description: Unit: °C Minimum: 0 Maximum: 0
A possibly relevant merge request was started @ https://invent.kde.org/plasma/ksystemstats/-/merge_requests/76
Git commit 1dcc0d4a1fb80c3ecd7986012fe6d54bbc3497d4 by Arjen Hiemstra. Committed on 07/02/2024 at 14:57. Pushed by ahiemstra into branch 'master'. cpu: Store physical ID with core ID when looking up coretemp sensors If there are multiple CPUs, we would only consider the last CPU. Additionally, if there is no sensors with a physical ID, we'd never match any sensors. Now we assume we start at physical ID 0 and only change that if we encounter a different physical ID sensor. M +6 -8 plugins/cpu/linuxcpuplugin.cpp https://invent.kde.org/plasma/ksystemstats/-/commit/1dcc0d4a1fb80c3ecd7986012fe6d54bbc3497d4
Git commit 5ab4ae0f82afbffd8d1a00ff8f1822e92ff9ba1b by Arjen Hiemstra. Committed on 20/03/2024 at 10:52. Pushed by ahiemstra into branch 'Plasma/6.0'. cpu: Store physical ID with core ID when looking up coretemp sensors If there are multiple CPUs, we would only consider the last CPU. Additionally, if there is no sensors with a physical ID, we'd never match any sensors. Now we assume we start at physical ID 0 and only change that if we encounter a different physical ID sensor. (cherry picked from commit 1dcc0d4a1fb80c3ecd7986012fe6d54bbc3497d4) M +6 -8 plugins/cpu/linuxcpuplugin.cpp https://invent.kde.org/plasma/ksystemstats/-/commit/5ab4ae0f82afbffd8d1a00ff8f1822e92ff9ba1b
*** Bug 484019 has been marked as a duplicate of this bug. ***
My other bug report was marked as a duplicate of this but I'm not sure if they are the same issue. I still have this problem in 6.0.3 My CPU temps are not shown at all anywhere, k10temp is not shown still under hardware sensors. sensors shows my CPU temps without issue, as does KsysGuard Not sure if I missed something. sensors ucsi_source_psy_11_00081-i2c-11-08 Adapter: NVIDIA GPU I2C adapter in0: 0.00 V (min = +0.00 V, max = +0.00 V) curr1: 0.00 A (max = +0.00 A) nct6779-isa-0290 Adapter: ISA adapter Vcore: 624.00 mV (min = +0.00 V, max = +1.74 V) in1: 1.08 V (min = +0.00 V, max = +0.00 V) ALARM AVCC: 3.33 V (min = +2.98 V, max = +3.63 V) +3.3V: 3.33 V (min = +2.98 V, max = +3.63 V) in4: 1.83 V (min = +0.00 V, max = +0.00 V) ALARM in5: 1.13 V (min = +0.00 V, max = +0.00 V) ALARM in6: 1.35 V (min = +0.00 V, max = +0.00 V) ALARM 3VSB: 3.47 V (min = +2.98 V, max = +3.63 V) Vbat: 3.30 V (min = +2.70 V, max = +3.63 V) in9: 0.00 V (min = +0.00 V, max = +0.00 V) in10: 800.00 mV (min = +0.00 V, max = +0.00 V) ALARM in11: 824.00 mV (min = +0.00 V, max = +0.00 V) ALARM in12: 1.67 V (min = +0.00 V, max = +0.00 V) ALARM in13: 928.00 mV (min = +0.00 V, max = +0.00 V) ALARM in14: 808.00 mV (min = +0.00 V, max = +0.00 V) ALARM fan1: 2220 RPM (min = 0 RPM) fan2: 759 RPM (min = 0 RPM) fan3: 3020 RPM (min = 0 RPM) fan4: 2253 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) SYSTIN: +34.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor CPUTIN: +36.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor AUXTIN0: +8.0°C sensor = thermistor AUXTIN1: +37.0°C sensor = thermistor AUXTIN2: +36.0°C sensor = thermistor AUXTIN3: +36.0°C sensor = thermistor SMBUSMASTER 0: +67.0°C 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 PCH_DIM0_TEMP: +0.0°C TSI0_TEMP: +67.4°C intrusion0: ALARM intrusion1: ALARM beep_enable: disabled k10temp-pci-00c3 Adapter: PCI adapter Tctl: +67.4°C Tdie: +40.4°C Tccd1: +66.8°C nvme-pci-0800 Adapter: PCI adapter Composite: +40.9°C (low = -273.1°C, high = +84.8°C) (crit = +84.8°C) Sensor 1: +40.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +50.9°C (low = -273.1°C, high = +65261.8°C) enp3s0-pci-0300 Adapter: PCI adapter PHY Temperature: +62.7°C MAC Temperature: +62.1°C iwlwifi_1-virtual-0 Adapter: Virtual device temp1: N/A k10temp-pci-00cb Adapter: PCI adapter Tctl: +67.0°C Tdie: +40.0°C nvme-pci-4100 Adapter: PCI adapter Composite: +36.9°C (low = -273.1°C, high = +84.8°C) (crit = +84.8°C) Sensor 1: +36.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +42.9°C (low = -273.1°C, high = +65261.8°C)
Note as the original reporter this only affected my older intel systems, my ryzen 3600 and 5600G AM4 based systems were not affected, i do not have any of the newer Intel platforms to test here, maybe i could test it on a ancient dual cpu xeon system BTW you can do this with the sensors command: sensors k10temp-* Maybe this is related to you having 2 of them is there a distro that has the latest patches yet i can test on a live session?
sensors k10temp-* k10temp-pci-00c3 Adapter: PCI adapter Tctl: +70.4°C Tdie: +43.4°C Tccd1: +61.0°C k10temp-pci-00cb Adapter: PCI adapter Tctl: +64.4°C Tdie: +37.4°C The thing is I need both, as one is for one CPU die and one is for the other. Each has 8 cores/16 threads. So they are different temp sensors. But k10temp doesn't appear at all in System Monitor
The orignal bug report was about an issue with coretemp, which is for Intel chips. k10temp is for AMD chips, so please make a new issue for that.
I did, and it was closed for no reason. https://bugs.kde.org/show_bug.cgi?id=484019 this one too https://bugs.kde.org/show_bug.cgi?id=452763
Bug 452763 was marked as fixed in 6.0.
It was not fixed in 6.0, as I said in the other thread. https://bugs.kde.org/show_bug.cgi?id=452763#c31 If you don't want to fix it just tell me so I can stop wasting my time here.
If it's not fixed, we should re-open the bug report claiming that it was, not some other one, and not with a new bug report. Let me sort out the status here.
Oh I see, in that bug report I told you to open a new one! Yeah, I can see how this is frustrating. Sorry for giving you the run-around. Let's focus on Bug 484019.
Thank Nate, sorry not trying to be a pain here.
Nah it's cool, the frustration is understandable.