From owner-freebsd-questions@FreeBSD.ORG  Fri Jan 24 19:48:03 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 655B0986
 for <freebsd-questions@freebsd.org>; Fri, 24 Jan 2014 19:48:03 +0000 (UTC)
Received: from nightmare.dreamchaser.org (nightmare.dreamchaser.org
 [12.32.44.142])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2A1681253
 for <freebsd-questions@freebsd.org>; Fri, 24 Jan 2014 19:48:03 +0000 (UTC)
Received: from breakaway.dreamchaser.org (breakaway.dreamchaser.org.
 [12.32.36.73])
 by nightmare.dreamchaser.org (8.13.6/8.13.6) with ESMTP id s0OJlsvx000340;
 Fri, 24 Jan 2014 12:47:55 -0700 (MST)
 (envelope-from freebsd@dreamchaser.org)
Message-ID: <52E2C36A.3070306@dreamchaser.org>
Date: Fri, 24 Jan 2014 12:47:54 -0700
From: Gary Aitken <freebsd@dreamchaser.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130730 Thunderbird/17.0.7
MIME-Version: 1.0
To: Erich Dollansky <erichsfreebsdlist@alogt.com>
Subject: Re: coretemp0: critical temperature detected, suggest system shutdown
References: <20140123223803.3b02c179@X220.alogt.com>
 <52E1731A.1020005@dreamchaser.org> <20140124204523.5ff8e368@X220.alogt.com>
In-Reply-To: <20140124204523.5ff8e368@X220.alogt.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2
 (nightmare.dreamchaser.org [12.32.36.65]);
 Fri, 24 Jan 2014 12:47:55 -0700 (MST)
Cc: freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: freebsd@dreamchaser.org
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 19:48:03 -0000

On 01/24/14 05:45, Erich Dollansky wrote:
> On Thu, 23 Jan 2014 12:52:58 -0700
> Gary Aitken <freebsd@dreamchaser.org> wrote:
>> On 01/23/14 07:38, Erich Dollansky wrote:
>>  
>>> I have seen today for the first time above's message in messages.
>>>
>>> This happened when I compiled some ports. It is normal that the CPU
>>> get then some 96 degrees.
>>
>> I had this problem some time ago.
>> I ended up replacing the stock fan on my system with a better one.
>> However, a good cleaning of the system may remove enough dust,
>> cobwebs, etc. and promote better airflow and thereby solve the
>> problem.
> 
> this is not the problem. The machine has still the same temperatures as
> at the beginning. Only the message appeared with the update.
> 
> It was always normal that the CPU went up to 96 Celsius the moment I was
> compiling the kernel or some larger ports. It does not get hotter now.

Sorry, I misunderstood the original question.
Unfortunately, I can't help you there.