From owner-freebsd-current Wed Jan 9 2:15:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 1A0D637B400 for ; Wed, 9 Jan 2002 02:15:28 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g09ACsU23914; Wed, 9 Jan 2002 11:12:55 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: Michael Reifenberger , FreeBSD-Current Subject: Re: panic during fdisk'ing a md(4) device In-Reply-To: Your message of "Wed, 09 Jan 2002 20:26:59 +1100." <20020109201155.L7824-100000@gamplex.bde.org> Date: Wed, 09 Jan 2002 11:12:54 +0100 Message-ID: <23912.1010571174@critter.freebsd.dk> From: Poul-Henning Kamp 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 In message <20020109201155.L7824-100000@gamplex.bde.org>, Bruce Evans writes: >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. Yeah, I admit I've been sitting on these patches for a bit too long, I'll try to get through my pile and get to them. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message