From owner-freebsd-current@FreeBSD.ORG  Fri Aug  8 06:09:15 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 AC4A537B401
	for <freebsd-current@freebsd.org>;
	Fri,  8 Aug 2003 06:09:15 -0700 (PDT)
Received: from mail.messagingengine.com (out1.smtp.messagingengine.com
	[66.111.4.25])	by mx1.FreeBSD.org (Postfix) with ESMTP id 1998D43F75
	for <freebsd-current@freebsd.org>;
	Fri,  8 Aug 2003 06:09:15 -0700 (PDT)
	(envelope-from freebsd@soith.com)
Received: from www.fastmail.fm (localhost [127.0.0.1])
	by localhost.localdomain (Postfix) with ESMTP
	id B9E5C8B9FC; Fri,  8 Aug 2003 09:09:13 -0400 (EDT)
Received: from 10.202.2.132 ([10.202.2.132] helo=www.fastmail.fm) by
	messagingengine.com  with SMTP; Fri, 08 Aug 2003 09:09:13 -0400
Received: by www.fastmail.fm (Postfix, from userid 99)
	id A429138CCB; Fri,  8 Aug 2003 09:09:12 -0400 (EDT)
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="ISO-8859-1"
MIME-Version: 1.0
X-Mailer: MIME::Lite 1.2  (F2.71; T1.001; A1.51; B2.12; Q2.03)
From: "Aaron Wohl" <freebsd@soith.com>
To: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
Date: Fri, 08 Aug 2003 07:09:12 -0600
X-Epoch: 1060348153
X-Sasl-enc: MAyInYYWtcm2A0azjA9+Mw
References: <7192.1060330926@critter.freebsd.dk>
In-Reply-To: <7192.1060330926@critter.freebsd.dk>
Message-Id: <20030808130912.A429138CCB@www.fastmail.fm>
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 13:09:16 -0000

I tried it this morning on different systems.  So far the two AMD systems
panic with vinum start and the intel/p4 works ok.  All systems have no
vinum volumes currently.

Good dump found on device /dev/ad0s1b
  Architecture: i386
  Architecture version: 1
  Dump length: 1073676288B (1023 MB)
  Blocksize: 512
  Dumptime: Fri Aug  8 05:28:09 2003
  Hostname: [edited]
  Versionstring: FreeBSD 5.1-CURRENT #0: Thu Aug  7 12:02:25 MDT 2003
    root@[edited out]:/usr/obj/usr/src/sys/ROUTER5
  Panicstring: mutex Giant owned at /usr/src/sys/geom/geom_dev.c:198
  Bounds: 3

On Fri, 08 Aug 2003 10:22:06 +0200, "Poul-Henning Kamp"
<phk@phk.freebsd.dk> said:
> 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.