Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 11 submissions in the queue.
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1, Informative) by Anonymous Coward on Thursday April 24, @05:32AM (2 children)

    by Anonymous Coward on Thursday April 24, @05:32AM (#1401350)

    The easiest way to potentially solve it is to issue the command (cpufreq-set -g powersave) or (cpupower frequency-set -g powersave) which will cause the CPU to use only the minimum allowed speed regardless of load. Otherwise, you can use that tool to experiment on a CPU speed that will not overheat. It will slow everything at the cost of almost ensuring no ability to overheat until you next reboot. There are also a number of daemons you can use to control it based on your platform and requirements. Sadly there isn't an easy answer because what works for one system doesn't work for another. And part of the problem is that, since it appears that you have exceeded the maximum temperature before, the overheat protection may not be aggressive enough due to the lower temperature where the processor will fail now.

    And as a frank side note: you'd think a fanless PC manufacturer would have better documentation on how to configure their servers in this manner.

    Starting Score:    0  points
    Moderation   +1  
       Informative=1, Total=1
    Extra 'Informative' Modifier   0  

    Total Score:   1  
  • (Score: 0) by Anonymous Coward on Thursday April 24, @04:36PM (1 child)

    by Anonymous Coward on Thursday April 24, @04:36PM (#1401400)

    Setting CPU governor to powersave is easy but it might not work. During a really long compile the heat will build up and a fanless system can't clear it out. You can't cool a CPU with hot air.

    Lowering the CPU thermal throttle temperature will probably help more, which you can do with the ryzenadj tool.

    Realistically though, a fanless system just isn't a great choice for long sustained workloads. For silent, the best approach is water cooling open loop with a big radiator and fans that can throttle down to silent speed. Not really viable for a laptop but gives you silent 90% of the time and max performance (and still not very loud) the other 10% of the time.

    • (Score: 0) by Anonymous Coward on Thursday April 24, @10:49PM

      by Anonymous Coward on Thursday April 24, @10:49PM (#1401422)

      It is a tradeoff. Lowering the CPU using ryzenadj vs the governor should affect the same settings under load. The difference is powersave is simpler at the expense of not having to do too much tuning and experimentation. Coming up with a complete thermal profile would be best. In the end, the solution will probably include a mix of hardware and kernel tuning. Right now, the APU is cooking itself, which means the throttling is already being exceeded. At a minimum the APU is signaling the platform to shutdown (either hard or soft) and it is a sign that the maximum junction temp is being exceeded and therefore lowered. That means that the built-in cooling profile is unreliable and that the kernel probably needs to get involved by actively cooling through injected idle loops.