From owner-freebsd-stable@FreeBSD.ORG Tue Aug 15 19:32:59 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 9782016A4DA for ; Tue, 15 Aug 2006 19:32:59 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp7.server.rpi.edu (smtp7.server.rpi.edu [128.113.2.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id D922E43D4C for ; Tue, 15 Aug 2006 19:32:58 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp7.server.rpi.edu (8.13.1/8.13.1) with ESMTP id k7FJWuf7015147; Tue, 15 Aug 2006 15:32:56 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <44E1FD81.2070803@oberon.pfi.lt> References: <44E19FF2.9080709@oberon.pfi.lt> <20060815121355.GP490@bunrab.catwhisker.org> <44E1C044.3000104@oberon.pfi.lt> <14989d6e0608150604y1ddabadr9d7e297851e92557@mail.gmail.com> <44E1EF32.10205@oberon.pfi.lt> <44E1FD81.2070803@oberon.pfi.lt> Date: Tue, 15 Aug 2006 15:32:55 -0400 To: "Android Andrew [:]" From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) 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 19:32:59 -0000 At 7:59 PM +0300 8/15/06, Android Andrew [:] wrote: >Yes, nothing changed. > >Problem could be in anything: memory, raid controller, >network adapter, power supply, bios and so on. But to >test it all empirically will take too much time. The >most annoying thing in this situation is absence of >any system/kernel messages or reports that could >explain something. > >Is there any methodology of troubleshooting in similar >situations? It can be very tedious to pin something like this down. I had something like this hit with one system of mine, which would die on 6.x-current (I think it was), but still work fine on 5.x-stable (I think it was. A dual- boot system, but I forget exactly which releases). After trying to pin it down to an update to 6.x, I eventually got all the way back to the exact same snapshot I had been running before the trouble started, but the trouble still existed. I even did a clean- install of the 6.x system, from some original CD's that were *before* the problem started, and yet I still had problems. And then I started to occasionally see the same problem on the 5.x system. And then more frequently. And finally it got to the point that the machine would not boot up at all. Not even 'POST'. It was a dead parrot. It ended up that something had gone wrong with the motherboard itself. It was about two months from the time I first started to see problems to the point where it completely died. It was a very frustrating two months! -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu