From owner-freebsd-current@FreeBSD.ORG  Sat Feb 28 08:07:23 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 95FA516A4CE; Sat, 28 Feb 2004 08:07:23 -0800 (PST)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 40EEE43D31; Sat, 28 Feb 2004 08:07:23 -0800 (PST)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i1SG6MDL030556;
	Sat, 28 Feb 2004 11:06:22 -0500 (EST)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)i1SG6MkM030553;
	Sat, 28 Feb 2004 11:06:22 -0500 (EST)
	(envelope-from robert@fledge.watson.org)
Date: Sat, 28 Feb 2004 11:06:21 -0500 (EST)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: Alfred Perlstein <alfred@freebsd.org>
In-Reply-To: <20040228124235.GJ56622@elvis.mu.org>
Message-ID: <Pine.NEB.3.96L.1040228110348.24114E-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
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: Sat, 28 Feb 2004 16:07:23 -0000


On Sat, 28 Feb 2004, Alfred Perlstein 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. 

I have one of these at work, or something very similar.  I'll give it a
try on Monday.  That said, I booted a kernel from about two weeks ago on
it with no problems only a week or so ago.  Question: are you running the
most recent BIOS update available from Dell? 

Any chance you have the whole trap message, can figure out what symbol it
is, etc?

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Senior Research Scientist, McAfee Research