pfSense » pfSense Plus

This is not true for all pchtherm devices though. For example:

[23.05-RC][admin@m470.stevew.lan]/root: sysctl dev.pchtherm.0.temperature
dev.pchtherm.0.temperature: 35.5C

Specifically the 1541 and 1537 return higher values than expected:

[23.05-RELEASE][root@XG-1537-DUT-1.test.netgate.com]/root: sysctl dev.pchtherm.0.temperature
dev.pchtherm.0.temperature: 75.5C

This command doesn't appear to work on Cordoba-based platforms, but I believe there is a PCH for the NVME interfaces, so not sure why it wouldn't have a readout here unless there isn't a temp sensor present.

Tested on 23.09 with result:
sysctl: unknown oid 'dev.pchtherm.0.temperature'

PCH isn't there on dev snaps because of #14727

getting unknown oid in the latest build 23.09.a.20230929.2350

This is probably what I am experiencing on a Xeon D-1736NT (Ice Lake) on 23.09-RC (23.09.r.20231027.0151)

sysctl: unknown oid 'dev.pchtherm.0.temperature'

Indeed, there are no temperature values at from PCH / PCIe with only CPU related temp values or limits available.

For example:

dev.coretemp.7.%domain: 0
dev.coretemp.7.%parent: cpu7
dev.coretemp.7.%pnpinfo: 
dev.coretemp.7.%location: 
dev.coretemp.7.%driver: coretemp

dev.cpu.7.temperature: 45.0C
dev.cpu.7.coretemp.throttle_log: 0
dev.cpu.7.coretemp.tjmax: 100.0C
dev.cpu.7.coretemp.resolution: 1
dev.cpu.7.coretemp.delta: 55