From owner-freebsd-current@FreeBSD.ORG  Fri Aug  8 01:22:09 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 8CF1F37B401
	for <freebsd-current@freebsd.org>;
	Fri,  8 Aug 2003 01:22:09 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 918AB43F93
	for <freebsd-current@freebsd.org>;
	Fri,  8 Aug 2003 01:22:08 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h788M61f007193;
	Fri, 8 Aug 2003 10:22:07 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: "Aaron Wohl" <freebsd@soith.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 07 Aug 2003 18:23:10 MDT."
             <20030808002310.0C1193959F@www.fastmail.fm> 
Date: Fri, 08 Aug 2003 10:22:06 +0200
Message-ID: <7192.1060330926@critter.freebsd.dk>
cc: freebsd-current@freebsd.org
Subject: Re: vinum lock panic at startup -current 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Aug 2003 08:22:09 -0000

In message <20030808002310.0C1193959F@www.fastmail.fm>, "Aaron Wohl" writes:
>I just cvsuped -current this afternoon to get about 1 weeks updates. 
>After that the kernel panics booting starting vinum.  I removed the one
>vinum volume (reformated as UFS2) I had for testing. And it still panics.
> I changed the /etc/rc.conf 
>start_vinum="YES"  to NO and can start ok now.

What was the actual panic message ?

-- 
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.