From owner-freebsd-stable@FreeBSD.ORG Tue Aug 15 16:59: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 D81CB16A4E0 for ; Tue, 15 Aug 2006 16:59:59 +0000 (UTC) (envelope-from android@oberon.pfi.lt) Received: from oberon.pfi.lt (oberon.pfi.lt [193.219.52.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD78543D76 for ; Tue, 15 Aug 2006 16:59:55 +0000 (GMT) (envelope-from android@oberon.pfi.lt) Received: from [10.10.10.1] (82-135-145-2.ip.rygveda.lt [82.135.145.2]) by oberon.pfi.lt (8.13.3/8.13.3) with ESMTP id k7FHF5R7055078; Tue, 15 Aug 2006 20:15:06 +0300 (EEST) (envelope-from android@oberon.pfi.lt) Message-ID: <44E1FD81.2070803@oberon.pfi.lt> Date: Tue, 15 Aug 2006 19:59:45 +0300 From: "Android Andrew [:]" User-Agent: Thunderbird 1.5.0.5 (X11/20060731) MIME-Version: 1.0 To: Alexey Karagodov 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> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 16:59:59 -0000 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? Alexey Karagodov wrote: > you mean "nothing changed" ? :) > try replace some hardware, memory first >