From owner-freebsd-current Mon Jan 15 3: 5:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 9402137B400 for ; Mon, 15 Jan 2001 03:05:15 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0FB4vY01616; Mon, 15 Jan 2001 03:04:57 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101151104.f0FB4vY01616@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Newton, Harry" Cc: "'Gerhard Sittig '" , "'freebsd-current@freebsd.org'" Subject: Re: Crash dumps during initialisation In-Reply-To: Date: Mon, 15 Jan 2001 03:04:56 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Newton, Harry" wrote: > I think we might be talking at cross-purposes here. What does the kernel do > if it panics before the /etc/rc script is run ? (i.e. before the dumpon > command is issued ). I can't believe that it reads /etc/rc.conf and locates > the dump_dev entry to determine where it should put the crash dump. In > 4.4BSD one could specify: > > config kernel root on swap on dump on > > but this no longer exists in FreeBSD ? Is this right, and why ? We are missing some infrastructure to get this to work really early in the boot sequence - how early do you need? It should be possible to come up with some tweaks so that we can dump right after the device that we want to dump to has probed its disk label to get the partition sizes etc. Exactly when this happens is something I am not yet sure of. With some tweaks it should be moderately easy to get dumps enabled at the point where boot -v says "Creating DISK xxx" and your dump device is shown.. at least for drivers that use the minidisk layer. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message