From owner-freebsd-stable@FreeBSD.ORG Tue Aug 15 11:41:19 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 2AC0E16A4DF for ; Tue, 15 Aug 2006 11:41:19 +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 076CA43D4C for ; Tue, 15 Aug 2006 11:41:16 +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 k7FBuRm9053792; Tue, 15 Aug 2006 14:56:27 +0300 (EEST) (envelope-from android@oberon.pfi.lt) Message-ID: <44E1B2D4.4080901@oberon.pfi.lt> Date: Tue, 15 Aug 2006 14:41:08 +0300 From: "Android Andrew [:]" User-Agent: Thunderbird 1.5.0.5 (X11/20060731) MIME-Version: 1.0 To: Dennis Melentyev References: <44E19FF2.9080709@oberon.pfi.lt> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Alexey Karagodov 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 11:41:19 -0000 Dennis Melentyev wrote: > Don't take it personally, but could it just power-off the monitor? > What does show the disk activity led? :) No, monitor shows there's no signal... Disk activity led and power led are off. Keyboard leds are off too. There is no network activity, no ping-reply... > > AFAIR, if you have to power-off manually (long pressing power button) > before power-on, it does will make FS dirty. Instead of real correct > power-off case. > > Try to make a simple script appending some log/file with timestamps, > wait untill your issue occurs, then check the time, wait for, say, 5 > more minutes and then cold-start system again. > > I bet, the script will still be logging messages into the file while > system looks like "sleeping". Ok, I'll try it.