From owner-freebsd-current@FreeBSD.ORG  Mon May 10 12:09:19 2004
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 6BBAF16A4CE
	for <current@freebsd.org>; Mon, 10 May 2004 12:09:19 -0700 (PDT)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3A0B143D46
	for <current@freebsd.org>; Mon, 10 May 2004 12:09:19 -0700 (PDT)
	(envelope-from bright@elvis.mu.org)
Received: by elvis.mu.org (Postfix, from userid 1192)
	id 347F05C811; Mon, 10 May 2004 12:09:19 -0700 (PDT)
Date: Mon, 10 May 2004 12:09:19 -0700
From: Alfred Perlstein <alfred@freebsd.org>
To: current@freebsd.org
Message-ID: <20040510190919.GP22547@elvis.mu.org>
References: <20040228124235.GJ56622@elvis.mu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040228124235.GJ56622@elvis.mu.org>
User-Agent: Mutt/1.4.2.1i
Subject: Re: worst FreeBSD EVAR. (crash on boot)
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: Mon, 10 May 2004 19:09:19 -0000

FYI:

This bug went away with recent current.

* Alfred Perlstein <alfred@freebsd.org> [040228 03:42] wrote:
> So I'm updating from a Dec 5th kernel to today's so as to hopefully
> restore the cool pre-Dec 5th ACPI behaviour which was:
>   Hitting the power button did an orderly shutdown.
> 
> Instead of Dec 5th's behaviour which is:
>   Randomly (well mostly when I fat finger ^A-n to switch screens)
>     failing to suspend to disk and then completely locking up.
>   Hitting power button does an immediate shutdown.. like power OFF,
>     no orderly shutdown, fsck at boot required, baby jesus cries etc.
> 
> Well now I have a kernel that won't even boot, here's the dmesg
> from the Dec 5th kernel with a marker where the panic happens on
> the newer kernel (noted by: <<<PANIC HERE ON NEW KERNEL>>) any
> help would be appreciated.
> 
> Machine is an old laptop, a Dell Latitude, celeron 300, 128 megs
> of ram.  It seems to crash both with and without ACPI loaded now.