Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Atom D525 Inaccurate Temperature Readings

    General pfSense Questions
    4
    18
    3.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      Nonsense
      last edited by

      pfSense (latest embedded version) is displaying my CPU and motherboard temperatures ca. 18 degrees below what my BIOS and motherboard utilities display them as being.  I have searched the forums and found some old posts about this matter, but I had assumed the problem had been corrected in the current versions of pfSense.  I have already tried changing the one advanced, misc. setting in the console to "none" to no avail–doing so results in no temperature being displayed).  I don't know how long this situation has existed, as it seemed that the display was correct at one time.  Can anyone explain to me in detail how to correct this situation (i.e., "Temperature Error Compensation for Dummies")?

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        The actual value reported by the CPU is given as the temperature below the maximum junction temperature (Tj-max). The usual cause of offset readings is the Tj-max value is wrong. This is usually a BIOS issue. I think you can see the Tj-max value in the sysctls. You may be able to override it if it's not corect. No idea whay it mght have changed though. Are you using ACPI or Coretemp in your settings?

        Steve

        1 Reply Last reply Reply Quote 0
        • N
          Nonsense
          last edited by

          Thanks, Stephen, for your help.  I am using "coretemp" as "ACPI/none" yields no results.

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            You should be able to check the Tjmax syscyl then.
            I doubt this patch made it into 8.3:
            http://lists.freebsd.org/pipermail/freebsd-bugs/2012-September/049951.html

            Steve

            1 Reply Last reply Reply Quote 0
            • N
              Nonsense
              last edited by

              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.

              1 Reply Last reply Reply Quote 0
              • N
                Nonsense
                last edited by

                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.

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

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

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • N
                    Nonsense
                    last edited by

                    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.

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      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

                      1 Reply Last reply Reply Quote 0
                      • B
                        BeerCan
                        last edited by

                        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.

                        1 Reply Last reply Reply Quote 0
                        • N
                          Nonsense
                          last edited by

                          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?

                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            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

                            1 Reply Last reply Reply Quote 0
                            • N
                              Nonsense
                              last edited by

                              $ 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

                              1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator
                                last edited by

                                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>

                                1 Reply Last reply Reply Quote 0
                                • M
                                  mir
                                  last edited by

                                  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

                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

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

                                    Steve

                                    1 Reply Last reply Reply Quote 0
                                    • N
                                      Nonsense
                                      last edited by

                                      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>

                                      1 Reply Last reply Reply Quote 0
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

                                        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

                                        1 Reply Last reply Reply Quote 0
                                        • First post
                                          Last post
                                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.