From owner-freebsd-current Wed Jan 9 3:10:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id 74F8937B405 for ; Wed, 9 Jan 2002 03:10:06 -0800 (PST) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id MAA16479; Wed, 9 Jan 2002 12:08:54 +0100 (CET) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.3/8.8.8) with ESMTP id g09D2Zu00474; Wed, 9 Jan 2002 14:02:35 +0100 (CET) (envelope-from root@nihil) Date: Wed, 9 Jan 2002 14:02:35 +0100 (CET) From: Michael Reifenberger To: Bruce Evans Cc: FreeBSD-Current Subject: Re: panic during fdisk'ing a md(4) device In-Reply-To: <20020109201155.L7824-100000@gamplex.bde.org> Message-ID: <20020109135621.H415-100000@nihil> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 9 Jan 2002, Bruce Evans wrote: ... > This seems to be just another null pointer panic caused by the dk macros > creating half-baked devices with null devswitches. I sent the following > quick fixes for this to the devfs maintainer a couple of weeks ago. They > also fix the non-creation of all minor devices on the disk when the first > one is opened. Applying your patch to a fresh -current tree leads to a page-fault in (swapper) after "mounting root from ..." (I had to apply the second Hunk of subr_disk by hand) Do you know how to enable a dumpdev via the boot loader in order to get a dump? Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message