From owner-freebsd-stable@FreeBSD.ORG Tue Aug 15 20:05:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2211916A4FF for ; Tue, 15 Aug 2006 20:05:18 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail.secureworks.net (mail.secureworks.net [65.114.32.155]) by mx1.FreeBSD.org (Postfix) with SMTP id 87E0D43D49 for ; Tue, 15 Aug 2006 20:05:17 +0000 (GMT) (envelope-from mike@jellydonut.org) Received: (qmail 90112 invoked from network); 15 Aug 2006 20:05:16 -0000 Received: from unknown (HELO ?192.168.14.135?) (63.239.86.253) by 0 with SMTP; 15 Aug 2006 20:05:16 -0000 Message-ID: <44E228FB.4030406@jellydonut.org> Date: Tue, 15 Aug 2006 16:05:15 -0400 From: Michael Proto User-Agent: Thunderbird 1.5.0.5 (X11/20060730) MIME-Version: 1.0 To: "Android Andrew [:]" References: <44E19FF2.9080709@oberon.pfi.lt> <20060815143308.GC31257@voodoo.schug.net> <44E1E291.1010707@oberon.pfi.lt> <44E20FB1.3040506@yahoo.gr> <20060815185704.GB720@turion.vk2pj.dyndns.org> <44E221DF.8000301@oberon.pfi.lt> In-Reply-To: <44E221DF.8000301@oberon.pfi.lt> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1-STABLE: Unexplained power off X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Aug 2006 20:05:18 -0000 Android Andrew [:] wrote: > > > Peter Jeremy wrote: >> On Tue, 2006-Aug-15 21:17:21 +0300, Apatewna wrote: >>> O/H Android Andrew [:] ??????: >>>> I've checked supply voltages by digital multimeter, >> >> This won't show a noisy supply rail (eg due to high ESR capacitors). >> If you suspect power, check the rails under load (eg lots of disk >> seeks and I/O) using an oscilloscope. > I've checked voltages on MB contacts exactly under load (during port > compilation). I have no oscilloscope, so I can't control voltage > impulse, especially on multiple channels. > In this case I could only replace PSU for testing. I would recommend this based on my own personal experience. PSUs are the single most-replaced component in both my desktops and servers (white-box servers anyway), and I've spent countless hours trying to track down similar issues only to have the problem disappear when the power supply was replaced. I keep a collection of various spare PSUs at my site just for this purpose, as its often not a case of IF a power supply will start going out, but WHEN. Your mileage may vary of course, but if it were me I'd try replacing the PSU first and see if the situation improves. -Proto