From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 00:40:46 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 C2B6416A423 for ; Thu, 16 Mar 2006 00:40:46 +0000 (UTC) (envelope-from freebsd@swaggi.com) Received: from swaggi.com (c-24-131-179-91.hsd1.ma.comcast.net [24.131.179.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70E2B43D45 for ; Thu, 16 Mar 2006 00:40:46 +0000 (GMT) (envelope-from freebsd@swaggi.com) Received: from localhost ([127.0.0.1] helo=swaggi.com) by swaggi.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FJga6-00048L-0X for freebsd-hardware@freebsd.org; Wed, 15 Mar 2006 19:43:10 -0500 Received: (from freebsd@localhost) by swaggi.com (8.13.4/8.13.4/Submit) id k2G0h9kt015890; Wed, 15 Mar 2006 19:43:09 -0500 (EST) (envelope-from freebsd@swaggi.com) Date: Wed, 15 Mar 2006 19:43:09 -0500 (EST) From: "Yuri Lukin" To: freebsd-hardware@freebsd.org Cc: X-Originating-IP: 204.56.88.53 X-Mailer: Usermin 1.190 In-Reply-To: <200603082338.02237.soralx@cydem.org> Message-Id: <1142469789.15888@swaggi.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1142469789" Subject: Re: FreeBSD shutting down unexpectedly X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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 00:40:46 -0000 This is a multi-part message in MIME format. --bound1142469789 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit >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 --bound1142469789--