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

    2.3.4 update increased CPU temp by 8 degree C

    Scheduled Pinned Locked Moved Hardware
    7 Posts 4 Posters 1.2k Views
    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.
    • Raffi_R
      Raffi_
      last edited by

      Hello,

      I have been running 2.3.3 for a while and my CPU temp was always 47 degrees C. After I updated to 2.3.4 last night, my CPU temp sits at 55 degrees C. The temp before and after the update never seems to change regardless of the CPU load. The CPU load is barely ever a factor since the system never breaks a sweat on my simple network. In fact, I think the CPU load mainly increases when I'm accessing the dashboard which has graphs. Otherwise, it's usually at or close to 0.00. I have attached a screen shot of my system information. 8 degrees C is a noticeable increase in temp and I would like to understand why. I'm sure it's nothing to be concerned about, but in general as temperature increases, the lifespan of electronic components decreases. If I could get that temp back down, it would be ideal.

      Thanks,
      Raffi
      system-info.JPG
      system-info.JPG_thumb

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        Nothing changed that significantly between 2.3.3 and 2.3.4 that would cause a jump of that size.  Especially with 2% CPU usage.

        If it was something in update causing it to run hotter, I'd expect to see a constant higher amount of CPU usage.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • Raffi_R
          Raffi_
          last edited by

          Thanks jimp. Yea, the CPU usage has not gone up at all. If the CPU usage did increase, that would make sense for the higher temp. I guess I have a rare case. Is it possible the temp is not being reported correctly? Or is it possible the temp is now being reported correctly, and the 47 degrees I thought I had before was incorrectly reported? Is there any way to check the temp outside of the GUI?

          1 Reply Last reply Reply Quote 0
          • Raffi_R
            Raffi_
            last edited by

            Aaah haaa… I was poking around with the dashboard. I added the thermal sensors widget. That only showed the 55 degree temp for zone 1 and zone 2, whatever that means. When I clicked on the link in the widget setting, it took me to system>advanced>miscellaneous. I changed the thermal sensor option from None/ACPI to Intel Core CPU on-die thermal sensor. Saved it. Now back on the main system information widget it shows 46 degree C!! That must have been it. The interesting thing though is that when I tried switching it back to None/ACPI, it still displays 46 degrees C. I'm not sure if that's a bug or not. It seems like after the update, the thermal sensor setting was either not getting all the facts or not applying the thermal sensor setting correctly? I'm not sure.

            1 Reply Last reply Reply Quote 0
            • D
              DeLorean
              last edited by

              In your system information, it seems that PowerD is not enabled.
              With PowerD disabled, the CPU runs always at max speed, and with only 1a2% cpu usage, the cpu gets hotter
              then when the CPU runs at lower speed with 1a2% usage.

              Grtz
              DeLorean

              1 Reply Last reply Reply Quote 0
              • Raffi_R
                Raffi_
                last edited by

                I enabled PowerD hiadaptive. I don't think that was my issue, but I figure it can't do any harm.

                The temp is still around 45 degree C. According to the system logs, the problem was that the coretemp thermal monitor module was not loading by default. After I went in and made the changes I mentioned in my previous post, it must have loaded the module and provided the correct readings.

                Jun 7 15:12:25 php-fpm 16181 /system_advanced_misc.php: Loading coretemp thermal monitor module.
                Jun 7 15:12:25 kernel coretemp0: <cpu on-die="" thermal="" sensors="">on cpu0
                Jun 7 15:12:25 kernel coretemp1: <cpu on-die="" thermal="" sensors="">on cpu1</cpu></cpu>

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

                  probably caused by a different driver giving a different reading.

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