2 Systems, identical hardware, one shows CPU temp, one does not?

[rcfa]

I have two hardware wise identical systems. In the past, they both used to properly display CPU temperatures.
One, for whatever reason seems to have stopped.

Similar results at the shell level:

/root: sysctl -a | grep temperature
dev.cpu.3.temperature: -1
dev.cpu.2.temperature: -1
dev.cpu.1.temperature: -1
dev.cpu.0.temperature: -1

and

/root: sysctl -a | grep temperature
dev.cpu.3.temperature: 25.0C
dev.cpu.2.temperature: 25.0C
dev.cpu.1.temperature: 26.0C
dev.cpu.0.temperature: 26.0C

Anyone has an idea what could change the behavior of the one system? Or is this an early warning sign of a failing CPU?

Thanks!

[MikeV7896]

Check in the advanced settings (I think on the Miscellaneous tab, but not certain) and make sure that Coretemp is enabled for Intel processors… it may have gotten disabled somehow.

[stephenw10]

Not sure the D510 uses coretemp, it may rely on the ACPI passed info. In which case I'd check the BIOS versions and settings.

Steve

Edit: Looks like it does use Coretemp and we have discussed this before.  ::)

Does the coretemp driver report attaching to the cores at boot?

[rcfa]

@virgiliomi:

Check in the advanced settings (I think on the Miscellaneous tab, but not certain) and make sure that Coretemp is enabled for Intel processors… it may have gotten disabled somehow.

Thanks for the hint, unfortunately, both have the settings enabled, but only one shows.

The puzzling things is, they both used to show the temp. So either I'm looking at some subtle settings corruption due to some software update or something like that, or a CPU that is starting to fail, or who knows what.

The two machines are twin systems: bought together, same model, same SSD, same amount of RAM, etc.

PS: for what it's worth, just noticed the regular temperature from the System Information which sits between "MBUF Usage" and "Load average" isn't showing either on the one system in question, while the other system shows it.

[stephenw10]

That value coems from the same place if the coretemp driver is in use.
I would suggest that there may have been some BIOS change. Perhaps the BIOS battery has gone flat on that one system and it's gone back to default settings?
It's hard to explain what the difference might be but you should see the coretemp driver attaching to the hardware in the boot log. Check for differences between the systems in the log.

Steve