Thermal Sensors pfsense 2.7.0-DEVELOPMENT (amd64)

SuperTypeGuy

Hello,
Just curious if anyone else is experiencing this. The Dashboard Thermal Sensors widget is showing different cpu temperature values than sysctl. For example:

Here is my cpu info:
CPU Type Intel(R) Pentium(R) Silver N6005 @ 2.00GHz
Current: 2528 MHz, Max: 1996 MHz
4 CPUs: 1 package(s) x 4 core(s)
AES-NI CPU Crypto: Yes (active)

I have Advanced Miscellaneous Thermal Sensors set to Intel Core CPU on-die thermal sensor.

From Dashboard Widget:
hw.acpi.thermal.tz0.temperature: 44.1C
dev.cpu.3.temperature: 46.0C
dev.cpu.2.temperature: 45.0C
dev.cpu.1.temperature: 45.0C
dev.cpu.0.temperature: 45.0C

From sysctl:
hw.acpi.thermal.tz0.temperature: 44.1C
dev.cpu.3.temperature: 54.0C
dev.cpu.2.temperature: 54.0C
dev.cpu.1.temperature: 53.0C
dev.cpu.0.temperature: 53.0C

Which one is correct? My guess is sysctl but I am not sure how to tell for sure.

Thanks!
Mark

stephenw10

The dashboard pulls that data from the sysctls so it should be the same. If it's not it suggests the dashboard is not updating.

SuperTypeGuy

@stephenw10 said in Thermal Sensors pfsense 2.7.0-DEVELOPMENT (amd64):

The dashboard pulls that data from the sysctls so it should be the same. If it's not it suggests the dashboard is not updating.

At first I thought the same, however the cpu temp numbers are never close (zone is always the same tho). I can see the dashboard widget numbers updating every so often.

weird.

SuperTypeGuy

I should mention a few additional points:

sysctl cpu temp always higher than dashboard widget
graph or raw numbers are consistent.

tedquade

@supertypeguy "......graph or raw numbers are consistent....." with what?

Ted Quade

SuperTypeGuy

If I change the widget to show graph or raw (no graph) the numbers are the same. meaning the widget numbers are consistent with itself even though they do not jive with sysctl

SuperTypeGuy

testing with sysctl but not sure why the discrepancies. our other systems are fine but not running 2.7.0-DEVELOPMENT
this test unit is our first to test the Intel I226-V 2.5G nics

this is the original sysctl command I used:
sysctl -a | grep 'dev.cpu.*.temperature'
dev.cpu.3.temperature: 59.0C
dev.cpu.2.temperature: 59.0C
dev.cpu.1.temperature: 58.0C
dev.cpu.0.temperature: 57.0C

this sysctl gets temperatures like the dashboard widget:
sysctl dev. | grep 'dev.cpu.*.temperature'
dev.cpu.3.temperature: 51.0C
dev.cpu.2.temperature: 50.0C
dev.cpu.1.temperature: 51.0C
dev.cpu.0.temperature: 51.0C

this sysctl gets even lower temperatures
sysctl dev.cpu. | grep 'dev.cpu.*.temperature'
dev.cpu.3.temperature: 41.0C
dev.cpu.2.temperature: 44.0C
dev.cpu.1.temperature: 43.0C
dev.cpu.0.temperature: 45.0C

tomorrow I will load 2.7.0-DEVELOPMENT on some of our other test hardware that has no current temperature reading issues.
maybe it is this hardware we are testing, not sure yet.

stephenw10

Ah well that looks like you're seeing the spot loading from running the sysctl query itself.
The widget uses:

/sbin/sysctl -q hw.acpi.thermal dev.cpu dev.t5nex dev.armada_thermal dev.cordbuc | /usr/bin/grep 'temperature:'

I note from your first post that you're using a CPU that will support Intel Speed Shift and that is close to instant scaling and associated temperature increases. You may need to tune that:
https://redmine.pfsense.org/issues/14047
It's new in 23.01/2.7

Steve

SuperTypeGuy

Thanks Steve!
This appears to be definitely related. Setting all dev.hwpstate_intel.%d.epp=95 seems to have affected temp readings and brought them within more reasonable levels. I will educate myself more on this.

I am in the lab today and will explore bios settings.

Warm regards,
Mark