Atom D525 Inaccurate Temperature Readings

Nonsense

Thanks–not sure all of what I will need to do to apply the patch, but it will likely have to wait until I return from vacation in a few weeks as I am also migrating from a USB drive to a SATA DOM and the latter has not been shipped to me as yet.

Nonsense

If anyone would be so kind as to supply me with detailed instructions (i.e., "Applying the Temperature Patch for Dummies") on how to apply the patch that Stephen refers to in his link, I would greatly appreciate it.

Thanks.

stephenw10

Have you tried a 2.2 snapshot? Those should have the patch included already. Easy way to test it anyway.

Steve

Nonsense

What exactly do you mean by a "snapshot" and how do you obtain it (I am running the most recent version of the software)? Oops! Do you mean to say that version 2.2 will have the fix?–o.k., then I'll just wait until its official release.

stephenw10

Snapshots of the current build of 2.2 (which is still in alpha) are available here:
http://snapshots.pfsense.org
2.2 is built on FreeBSD 10-rel so should include this patch. It will allow you to test it before 2.2 is released to decide if you need to try some other solution.

Steve

BeerCan

I am using the 2.2 snapshot on my home pfsense box and temps are working correctly on my atom d510. The temps did not work correctly on 2.1.x so it looks like the patch made it.

Nonsense

Stephen wrote:

"Have you tried a 2.2 snapshot? Those should have the patch included already."

I downloaded and installed v. 2.2 when it was released last week, but I don't see any difference in CPU temperature reporting. Isn't the patch in the final version?

stephenw10

I don't see it in the source:
https://svnweb.freebsd.org/base/release/10.1.0/sys/dev/coretemp/coretemp.c?revision=274417&view=markup

:(

What does your install report the tjmax as:

[2.2-RELEASE][root@xtm5.localdomain]/root: sysctl -a | grep tjmax
dev.cpu.0.coretemp.tjmax: 85.0C
dev.cpu.1.coretemp.tjmax: 85.0C

Steve

Nonsense

$ sysctl -a | grep tjmax
dev.cpu.0.coretemp.tjmax: 100.0C
dev.cpu.1.coretemp.tjmax: 100.0C
dev.cpu.2.coretemp.tjmax: 100.0C
dev.cpu.3.coretemp.tjmax: 100.0C

stephenw10

Do you see this in the boot logs:
coretemp0: <cpu on-die="" thermal="" sensors="">on cpu0
coretemp0: Can not get Tj(target) from your CPU, using 100C.

The correct tjmax value for the D525 seems to be mostly reported as 100C with some reports of 125C.

Steve</cpu>

mir

If coretemp for some reason is reported wrongly you can adjust the readings. This is what I have in /boot/loader.conf.local:

dev.amdtemp.0.sensor_offset=-6

stephenw10

Unfortunately a similar control doesn't exist in the coretemp driver.

Steve

Nonsense

The only relevant thing I see in the boot log ("general" log tab):

Jan 28 01:42:35 kernel: coretemp3: <cpu on-die="" thermal="" sensors="">on cpu3
Jan 28 01:42:35 kernel: coretemp2: <cpu on-die="" thermal="" sensors="">on cpu2
Jan 28 01:42:35 kernel: coretemp1: <cpu on-die="" thermal="" sensors="">on cpu1
Jan 28 01:42:35 kernel: coretemp0: <cpu on-die="" thermal="" sensors="">on cpu0

By the way, on a different subject, do I have to worry about this other message in the boot log(?):

Jan 28 01:42:35 kernel: iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
Jan 28 01:42:35 kernel: iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.</cpu></cpu></cpu></cpu>

stephenw10

Hmm, looks like it's correctly finding and reading the tjmax value from the CPU then. :-\

Those license warnings are nothing to worry about. You can add the ack values to loader.conf.local to make them go away if you want.

Steve