root@OPNsense:~ # sysctl -a | grep temperaturehw.acpi.thermal.tz0.temperature: 47.1Cdev.cpu.3.temperature: 46.0Cdev.cpu.2.temperature: 46.0Cdev.cpu.1.temperature: 45.0Cdev.cpu.0.temperature: 45.0Croot@OPNsense:~ # sysctl -a | grep temperaturehw.acpi.thermal.tz0.temperature: 47.1Cdev.cpu.3.temperature: 48.0Cdev.cpu.2.temperature: 47.0Cdev.cpu.1.temperature: 46.0Cdev.cpu.0.temperature: 45.0Croot@OPNsense:~ # sysctl -a | grep temperaturehw.acpi.thermal.tz0.temperature: 47.1Cdev.cpu.3.temperature: 47.0Cdev.cpu.2.temperature: 46.0Cdev.cpu.1.temperature: 45.0Cdev.cpu.0.temperature: 47.0Croot@OPNsense:~ # sysctl -a | grep temperaturehw.acpi.thermal.tz0.temperature: 47.1Cdev.cpu.3.temperature: 49.0Cdev.cpu.2.temperature: 48.0Cdev.cpu.1.temperature: 47.0Cdev.cpu.0.temperature: 46.0Croot@OPNsense:~ #root@OPNsense:~ # sysctl -a | grep temperaturehw.acpi.thermal.tz0.temperature: 47.1Cdev.cpu.3.temperature: 48.0Cdev.cpu.2.temperature: 46.0Cdev.cpu.1.temperature: 46.0Cdev.cpu.0.temperature: 46.0C
markus@opnsense:~ % sysctl -a | grep temperature && sysctl dev.cpu | grep temperaturehw.acpi.thermal.tz0.temperature: 27.9Cdev.cpu.3.temperature: 61.0Cdev.cpu.2.temperature: 59.0Cdev.cpu.1.temperature: 58.0Cdev.cpu.0.temperature: 57.0Cdev.cpu.3.temperature: 58.0Cdev.cpu.2.temperature: 58.0Cdev.cpu.1.temperature: 57.0Cdev.cpu.0.temperature: 57.0C
@maxus and @yahyoh: Yes, we know all that. You probably should re-read the thread.Franco already explained in detail what is going on:The difference between the (current) GUI query and a query from the CLI is that the during the processing of the dashboard widgets (which include the temperature readouts), the CPU is being used, which in turn heats it up, resulting in an increased reading. You could probably reduce the difference by de-selecting all but the CPU temperature widget.The granularity of modern CPUs temperature is so high that this matters, because the sensors now reside on the CPU die itself. The temperature can jump a few degrees in a few microseconds.Franco also told you that this could only be fixed if the time of readout is shifted from the point in time that the GUI processes the widgets (so a background process is probably needed which decouples this).
No. There were exactly the same complaints about something being "too high" when compared to not staring at the dashboard. Like here.
but the phenomenon only occurred after the update from 24.1 to 24.7.
Well that simply is not true, as documented by the ticket I linked.Whatever, it shows data returned by the on-die sensors and as read and provided by the kernel. I don't really know why people want to see incorrect readings just because they don't like the data shown. Anyway, this is the current dumpspace of these complaints..
Maybe part of the difference is from the fact that widget evaluation has changed because of the structural changes (like order of evaluation or complexity of other widgets).Maybe you have an RRD database update / maintenance running after the upgrade that caused CPU spikes.Whatever the reason, there is a github issue and probably it will be adressed if no issues exist that have higher priority (of which I know some...).
I think this is worth investigating and patching before anyone has hardware failure as a result.
Quote from: irrenarzt on August 28, 2024, 12:22:42 amI think this is worth investigating and patching before anyone has hardware failure as a result.This is getting borderline absurd. Get a better cooling system if you have such concerns.