Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 31 Mar 2014 14:08:09 -0400
From:      "illoai@gmail.com" <illoai@gmail.com>
To:        Walter Hurry <walterhurry@gmail.com>
Cc:        "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   Re: CPU Overheating?
Message-ID:  <CAHHBGkpGHesjzjLao3tjcHjcas8afDCWS5Zew0A8yP-mKUJOBg@mail.gmail.com>
In-Reply-To: <lhabru$3o1$1@ger.gmane.org>
References:  <lhabru$3o1$1@ger.gmane.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 30 March 2014 20:11, Walter Hurry <walterhurry@gmail.com> wrote:
> I have a bog-standard Acer laptop with FreeBSD 9.2 (amd64).
>
> CPU is  AMD Athlon(tm) 64 X2 Dual-Core Processor TK-42 (1596.09-MHz K8-cl=
ass CPU) per dmsg.
>
> From time to time, it shuts off without warning, as if the power cable ha=
s been pulled out. Nothing in any of the logs, and when I power up again it=
 starts normally after replaying the journal.
>
> The shut-off is invariably when it is doing a compile of a big port. I th=
erefore suspect that the CPU is overheating and that the BIOS is causing th=
e shutdown.
>
> To investigate the problem, I have done a 'kldload coretemp' and am perio=
dically running:
>  'sysctl hw.acpi.thermal.tz0.temperature'. So far (only 6 runs) this is r=
eporting temperatures between 76C and 84C.
>
> Question 1: Is this the canonical way to monitor CPU temperature?
> Question 2: Is this too hot?
> Question 3: I plan to load the module in /boot/loader.conf and set up a c=
ron job to run every minute and log the result to a file. Is this sensible,=
 or overkill?
>

amdtemp.ko should give you a bunch of new sysctls under
'dev.amdtemp' to monitor

84=B0C is too hot for a desktop processor, & pretty close to too hot
for a laptop.  With decent airflow I only rarely get above 75=B0C
on my laptop.  Things do have to be disassembled & cleaned
from time to time, though.

It's not such a bad idea to run a script to log those values every
minute or so if you suspect overheating.  You'll probably lose
the last value or two when your machine shuts off, though.
Maybe write the output to a file on an nfs server?  Or get an
old dot-matrix printer & log to that?

--=20
--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHHBGkpGHesjzjLao3tjcHjcas8afDCWS5Zew0A8yP-mKUJOBg>