From owner-freebsd-current Sun Aug 8 7:12:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (Postfix) with ESMTP id 44EC214E9E for ; Sun, 8 Aug 1999 07:12:45 -0700 (PDT) (envelope-from freebsd@xaa.iae.nl) Received: from ariel.xaa.iae.nl (ariel.xaa.iae.nl [194.151.75.10]) by esmeralda.xaa.iae.nl (Postfix) with ESMTP id 94E86BA41; Sun, 8 Aug 1999 16:09:55 +0200 (MET DST) Received: by ariel.xaa.iae.nl (Postfix, from userid 1008) id 537265CF0; Sun, 8 Aug 1999 16:09:43 +0200 (CEST) Date: Sun, 8 Aug 1999 16:09:43 +0200 From: Mark Huizer To: Poul-Henning Kamp Cc: Andrzej Bialecki , freebsd-current@FreeBSD.ORG Subject: Re: Arg! MFS broken Message-ID: <19990808160943.A1286@ariel.xaa.iae.nl> References: <47364.932848590@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <47364.932848590@critter.freebsd.dk>; from Poul-Henning Kamp on Sat, Jul 24, 1999 at 10:36:30PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> > I'm sorry, I don't have either in my arsenal currently. > >> I found that trying to build a PicoBSD floppy was a sure way of crashing > >> my current box :-( Perhaps that is a nice testing environment? > > > >Then you should investigate this further, because it looks like some bug > >in vn(4) code - picobsd build doesn't do anything unusual except that... > > I built a release (which also uses vn(4)) yesterday, so to some extent > of the concept vn(4) works. I'm very interested in a traceback of > this panic... > I just redid the disk configuration here so I can get kernel dumps working again... I'll try it out this evening. -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message