Re: vinum lock panic at startup -current

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_at_[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_at_phk.freebsd.dk> said:
> In message <20030808002310.0C1193959F_at_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_at_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.