Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 08 Aug 2003 09:58:37 -0600
From:      "Aaron Wohl" <freebsd@soith.com>
To:        "Poul-Henning Kamp" <phk@phk.freebsd.dk>
Cc:        freebsd-current@freebsd.org
Subject:   Re: vinum lock panic at startup -current
Message-ID:  <20030808155837.555F037F3B@www.fastmail.fm>
In-Reply-To: <8938.1060349049@critter.freebsd.dk>
References:  <8938.1060349049@critter.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
Its wierd though that it works on intel/p4 but gets taht panic: Giant on
amd... My 2 amd systems panic with vinum start but the P4 works ok built
from the same sources.  All with no vinum volumes, just trying vinum
start t test for this bug.

----- Original message -----
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
To: "Aaron Wohl" <freebsd@soith.com>
Date: Fri, 08 Aug 2003 15:24:09 +0200
Subject: Re: vinum lock panic at startup -current 

In message <20030808130912.A429138CCB@www.fastmail.fm>, "Aaron Wohl"
writes:

>  Panicstring: mutex Giant owned at /usr/src/sys/geom/geom_dev.c:198

Ok, then I think I know what it is.

Vinum appearantly does not go through SPECFS but rather calls into
the disk device drivers directly.  That is a pretty wrong thing to
do, and it seems that vinum does not respect the D_NOGIANT
flag which GEOM recently started setting.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030808155837.555F037F3B>