From owner-freebsd-current  Mon Feb 17 11:38:52 2003
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 660FD37B401; Mon, 17 Feb 2003 11:38:50 -0800 (PST)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 72E8943F85; Mon, 17 Feb 2003 11:38:49 -0800 (PST)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.12.6/8.12.6) with ESMTP id h1HJcm8I023476
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 17 Feb 2003 14:38:48 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h1HJchL43193;
	Mon, 17 Feb 2003 14:38:43 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15953.14915.548457.683546@grasshopper.cs.duke.edu>
Date: Mon, 17 Feb 2003 14:38:43 -0500 (EST)
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: alpha@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: top-of-tree alpha kernel panics during boot
In-Reply-To: <xzplm0e4sui.fsf@flood.ping.uio.no>
References: <xzpn0l0v119.fsf@flood.ping.uio.no>
	<xzpk7fz58r0.fsf@flood.ping.uio.no>
	<xzpfzqn57pi.fsf@flood.ping.uio.no>
	<15952.60850.445423.454870@grasshopper.cs.duke.edu>
	<xzp7kbz571q.fsf@flood.ping.uio.no>
	<15952.61478.809737.101419@grasshopper.cs.duke.edu>
	<xzplm0e4sui.fsf@flood.ping.uio.no>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG


Dag-Erling Smorgrav writes:
 > Andrew Gallatin <gallatin@cs.duke.edu> writes:
 > > You might be able to get some idea of what's happening by enabling KTR
 > > and tracing everything, then dumping the trace buffer at your
 > > breakpoint.
 > 
 > Of course, the KTR-enabled kernel fails to crash.
 > 
 > *sigh*
 > 
 > but I bet it'll segfault like nobody's business if I let it boot to
 > multiuser, so I'm stuck with my Jan 9 kernel.

Ugh.

About the only thing I can suggest is to pepper the startup code with
Debugger() calls, and do something of a binary search.  Having just
done that to track some vm faults before vm is setup, I know that's
about as much fun as eating dirt.  But I can't think of a better
idea.

Drew

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message