Bug #14467
openTemperature sensor reading is abnormally high on some systems
0%
Description
The temperature reading dev.pchtherm.0.temperature
was introduced in 23.01 and it seems to be incorrect. It fluctuates between 170-178F (seen on the dashboard widget).
Updated by Marcos M about 1 year ago
- Subject changed from Incorrect temperature reading to Temerature sensor reading is abnormally high
Updated by Steve Wheeler about 1 year ago
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
Updated by Marcos M about 1 year ago
- Subject changed from Temerature sensor reading is abnormally high to Temperature sensor reading is abnormally high on some systems
Updated by Kris Phillips 10 months ago
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'
Updated by Jim Pingle 10 months ago
PCH isn't there on dev snaps because of #14727
Updated by Rob A 8 months ago
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