Overheating attributed to Freebsd --sysctl variables not available--

C. Ulrich dincht at securenym.net
Mon Nov 3 18:15:54 PST 2003

On Mon, 2003-11-03 at 17:38, nw1 wrote:
> The problem can be viewed @:
> Basically, the machine is overheating (I believe) because the cpu's aren't cycling down.
> Previously I was able to cycle the processors down with the following sysctl variables:
> machdep.apm_suspend_delay:
> machdep.apm_standby_delay:
> however, for some reason those variables currently, aren't any where to be found by the
> up_and_running system.  Please use the hyperlink above for details.
> Thanks for reading.  All feedback is welcome.

Okay, this piqued my curiosity enough that I took a look at the message
in the URL above. 

Conclusion: FreeBSD doesn't even enter into it. The ONLY good solution
to this is to get better physical cooling of the CPUs (or the entire box
if you have to). Otherwise, you're still going to run into problems
whenever there's a full system load. Chances are, they're still running
way too hot even if they're not crashing the system. This will only
result in premature failure of the processors. Take it from the close
friend of an overclocker. :) If the machine is crashing (you only say
"overheating", which could mean either crashing or just getting
dangerously hot), then I would even go so far as to say that there's a
possibility that the stability of the processors is already decreasing,
leading to the more recent crashes.

Charles Ulrich

More information about the freebsd-questions mailing list