From owner-freebsd-current@FreeBSD.ORG  Fri Jan 28 17:22:38 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id ACB8916A4CE; Fri, 28 Jan 2005 17:22:38 +0000 (GMT)
Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 25F6443D2D; Fri, 28 Jan 2005 17:22:38 +0000 (GMT)
	(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
	by dan.emsphone.com (8.13.1/8.13.1) id j0SHMbdi006017;
	Fri, 28 Jan 2005 11:22:37 -0600 (CST)
	(envelope-from dan)
Date: Fri, 28 Jan 2005 11:22:36 -0600
From: Dan Nelson <dnelson@allantgroup.com>
To: Sergey Matveychuk <sem@freebsd.org>
Message-ID: <20050128172236.GC70503@dan.emsphone.com>
References: <41FA67B0.5000602@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <41FA67B0.5000602@FreeBSD.org>
X-OS: FreeBSD 5.3-STABLE
X-message-flag: Outlook Error
User-Agent: Mutt/1.5.6i
cc: freebsd-current@freebsd.org
Subject: Re: unwanted shutdowns
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jan 2005 17:22:38 -0000

In the last episode (Jan 28), Sergey Matveychuk said:
> My CURRENT box has random shutdowns time to time. No panic. Just
> clean shutdown with common messages on console.
> 
> I've updated yesterday, but the symptom I've seen with previous
> sources too (updated two or three weeks ago).

I'm suspecting ACPI.  I had two similar occurences on my 5.3 machine. 
One was a clean sutdown&poweroff in the middle of the night, and
another one just logged this in /var/log/messages:

Dec 27 16:13:44 <0.2> dan kernel: acpi0: Sleep state S3 not supported by BIOS
Dec 27 16:13:49 <0.2> dan kernel: acpi: suspend request ignored (not ready yet)

According to "sysctl hw.acpi", none of my case buttons are set to S3 so
it's not caused by someone bumping the machine and accidentally
triggering it.

-- 
	Dan Nelson
	dnelson@allantgroup.com