From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 01:42:10 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1743D16A422 for ; Thu, 16 Mar 2006 01:42:10 +0000 (UTC) (envelope-from ogautherot@vtr.net) Received: from lp01.vtr.net (relay.vtr.net [200.83.1.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F8AB43D4C for ; Thu, 16 Mar 2006 01:42:07 +0000 (GMT) (envelope-from ogautherot@vtr.net) Received: from [192.168.10.3] (200.83.72.41) by lp01.vtr.net (7.1.026) (authenticated as ogautherot) id 439EFA43003AA581 for freebsd-hardware@freebsd.org; Wed, 15 Mar 2006 21:42:01 -0400 From: Olivier Gautherot To: freebsd-hardware@freebsd.org Date: Wed, 15 Mar 2006 21:41:46 -0400 User-Agent: KMail/1.9.1 References: <1142469789.15888@swaggi.com> In-Reply-To: <1142469789.15888@swaggi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603152141.47518.ogautherot@vtr.net> Subject: Re: FreeBSD shutting down unexpectedly X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: olivier@gautherot.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 01:42:10 -0000 Hi Yuri! Good to see you solved your problem. Just keep in mind that if your CPU overheated for some time, it is likely to die prematurely. I would strongly recommend to check the CPU temperature and, if you figure out that it is starting to heat up more than usual, be it by a couple of degrees, make sure you get quickly a replacement: it is usually the first sign of an agony... I had one die this way. Cheers Olivier On Wednesday 15 March 2006 20:43, Yuri Lukin wrote: > >soralx@cydem.org wrote .. > > This is a problem indeed. > > In any case, this is getting off-topic now. Hopefully, this discussion > > succeeded in pointion out the quality problem that exists with current > > consumer-grade hardware, and suggested some ways to solve it (whether > > globally -- by 'boycotting' bad manufacturers, or locally -- by > > modifying already purchased hardware). > > Just to give everyone an update on my situation: > > It turned out I had a bad fan on the CPU, apparently the motor seized. I > ordered a replacement and finally installed it earlier today. Everything > appears to be running fine even the CPU utilization goes up. I also > installed ports/sysutils/mbmon to monitor the voltage and fan RPMs. I > must say, this is a very handy tool. > > Thanks to all for the help! > > -Yuri -- Olivier Gautherot olivier@gautherot.net