(https://imgur.com/a/XAH6BwW)
Spurious CPU references etc?
(https://imgur.com/a/XAH6BwW)
(https://nextcloud.gourmetsaint.com.au/index.php/s/tm2pN3J64sXdy3F)
Can you share your output of the following?
# sh -c 'sysctl $(configctl system sensors)'
FreeBSD has a few temperature sensors disguised as thresholds that need to be excluded.
Cheers,
Franco
I'm facing same issue.
Here my output:
dev.cpu.0.temperature: 41.0C
dev.cpu.1.temperature: 33.0C
dev.cpu.2.temperature: 34.0C
dev.cpu.3.temperature: 33.0C
dev.pchtherm.0.ctt: 115.0C
dev.pchtherm.0.pmtemp: 50.0C
dev.pchtherm.0.t0temp: 108.0C
dev.pchtherm.0.t1temp: 111.0C
dev.pchtherm.0.t2temp: 114.0C
dev.pchtherm.0.temperature: 47.0C
hw.acpi.thermal.tz0.temperature: 27.9C
hw.acpi.thermal.tz1.temperature: 29.9C
The values for pchtherm seems too high. I assume there is a calculation failure.
If you translate from F° to C° the values are same to the old ones.
Thanks try this one:
# opnsense-patch https://github.com/opnsense/core/commit/695772d2017
# service configd restart
Perfect, works great.
Thanks a lot
Still looks a bit out of shape, even with the above patch applied. Also what is this AMD 000?
Hardware: DEC750, 1G generation.
AMD is actually the real and only sensor, FreeBSD is scaling this sensor up as a per CPU reading so this is more or less correct, even though "000" looks a bit strange and can be streamlined.
Cheers,
Franco
Thnx for the very quick patch. Initially, 25.1 added a few CPU temps in my interface. Back to normal after apllying the patch.
When will a prod patch be released for this?
Quote from: franco on January 30, 2025, 09:23:28 AMCan you share your output of the following?
# sh -c 'sysctl $(configctl system sensors)'
FreeBSD has a few temperature sensors disguised as thresholds that need to be excluded.
Cheers,
Franco
dev.cpu.0.temperature: 37.0C
dev.cpu.1.temperature: 37.0C
dev.cpu.10.temperature: 40.0C
dev.cpu.11.temperature: 40.0C
dev.cpu.2.temperature: 38.0C
dev.cpu.3.temperature: 38.0C
dev.cpu.4.temperature: 38.0C
dev.cpu.5.temperature: 38.0C
dev.cpu.6.temperature: 41.0C
dev.cpu.7.temperature: 41.0C
dev.cpu.8.temperature: 39.0C
dev.cpu.9.temperature: 39.0C
dev.pchtherm.0.ctt: 120.0C
dev.pchtherm.0.pmtemp: 77.0C
dev.pchtherm.0.t0temp: 108.0C
dev.pchtherm.0.t1temp: 111.0C
dev.pchtherm.0.t2temp: 114.0C
dev.pchtherm.0.temperature: 47.0C
hw.acpi.thermal.tz0.temperature: 27.9C
Yes these were fixed by the proposed patch.
A patch is usually released in a next stable release. The issue is cosmetic.
Cheers,
Franco
Really appreciate the quick fix on this one. :)
Was definitely a bit alarming to see a bunch of 100 C warnings at 2 AM. But since the box wasn't bursting into flames, I figured it was a cosmetic thing.
Thank you for the patch!
On a mostly related note, I've always had these two below show up in my dashboard as zone 1 and zone 2, but the temps never change and are always identical to the below:
hw.acpi.thermal.tz0.temperature: 27.9C
hw.acpi.thermal.tz1.temperature: 29.9C
I'm assuming there's no temp sensors present on my motherboard but as far as I can tell there's no way to exclude them from the dashboard?
Also, I have this platform controller hub temp sensor, which does seem to change and be a genuine temperature reported, but it reports on dashboard as a duplicate cpu0:
dev.pchtherm.0.temperature: 47.0C
Is there any way of modifying naming of these and/or excluding unwanted ones from the dashboard?
# sh -c 'sysctl $(configctl system sensors)'
dev.cpu.0.temperature: 42.0C
dev.cpu.1.temperature: 42.0C
dev.cpu.10.temperature: 39.0C
dev.cpu.11.temperature: 39.0C
dev.cpu.2.temperature: 45.0C
dev.cpu.3.temperature: 45.0C
dev.cpu.4.temperature: 42.0C
dev.cpu.5.temperature: 42.0C
dev.cpu.6.temperature: 46.0C
dev.cpu.7.temperature: 46.0C
dev.cpu.8.temperature: 41.0C
dev.cpu.9.temperature: 41.0C
dev.pchtherm.0.ctt: 120.0C
dev.pchtherm.0.pmtemp: 77.0C
dev.pchtherm.0.t0temp: 100.0C
dev.pchtherm.0.t1temp: 105.0C
dev.pchtherm.0.t2temp: 110.0C
dev.pchtherm.0.temperature: 40.0C
hw.acpi.thermal.tz0.temperature: 27.9C
The above patch fixed "some" weirdness for me, but it seems as if the dashboard display doesn't scale like it used to. A narrow (1 column) window seems to always be exceeded by even green temperatures and the occasional red temperature exceeds 3 column configuration.
Thanks for the confirmation here. I was snooping around hoping to find something like this thread. Not only do the device names look strange, but temps over 100C are generally "unrecoverable critical" (as in, "We should be dead, my friend"), so seeing the box humming along happily with those readings struck me as a red herring.
On the plus side, the updated interface in 25.1 looks great - thank you.