From owner-freebsd-current@FreeBSD.ORG  Sat Feb 28 15:02:14 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 421DA16A4D7; Sat, 28 Feb 2004 15:02:14 -0800 (PST)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 264B743D1D; Sat, 28 Feb 2004 15:02:14 -0800 (PST)
	(envelope-from bright@elvis.mu.org)
Received: by elvis.mu.org (Postfix, from userid 1192)
	id 04A6B5C7DD; Sat, 28 Feb 2004 15:02:14 -0800 (PST)
Date: Sat, 28 Feb 2004 15:02:13 -0800
From: Alfred Perlstein <alfred@freebsd.org>
To: Robert Watson <rwatson@freebsd.org>
Message-ID: <20040228230213.GK56622@elvis.mu.org>
References: <20040228124235.GJ56622@elvis.mu.org>
	<Pine.NEB.3.96L.1040228110348.24114E-100000@fledge.watson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.NEB.3.96L.1040228110348.24114E-100000@fledge.watson.org>
User-Agent: Mutt/1.4.2.1i
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 23:02:14 -0000

* Robert Watson <rwatson@freebsd.org> [040228 08:07] wrote:
> 
> On Sat, 28 Feb 2004, Alfred Perlstein wrote:
> 
> > 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? 

Unlikely sir.  But y'know 6 months ago it all worked just fine.

Every peripheral I cared about worked, and hitting power did an orderly
shutdown.

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

How can I do that?

thank you,
-- 
- Alfred Perlstein
- Research Engineering Development Inc.
- email: bright@mu.org cell: 408-480-4684