Subject: Re: Locking against myself
To: Martin Husemann <martin@duskware.de>
From: Bill Studenmund <wrstuden@netbsd.org>
List: tech-kern
Date: 12/12/2006 14:42:36
--4Ckj6UjgE2iN1+kY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 12, 2006 at 10:57:02PM +0100, Martin Husemann wrote:
> I can reproduce this with a LOCKDEBUG kernel, /usr/src on NFS, /mnt on
> NFS, and then doing:
>=20
> setenv DESTDIR /mnt
> setenv INSTALLWORLDDIR /
> setenv USETOOLS never
> cd /usr/src
> make installworld |& tee /tmp/log
>=20
> As soon as pax starts to copy sets, I get:
>=20
> panic: lockmgr: locking against myself
> Stopped in pid 1269.1 (pax) at  netbsd:cpu_Debugger+0x6:        unlk    a6
> db> bt                                                                   =
=20
> cpu_Debugger(2,0,4f2edac,5bd2d54,5bd2d84) + 6
> panic(187cb5,20002,5b91c7c,5,0) + 118       =20
> _lockmgr(4f2edac,10002,4f2ed20,190e14,135) + c8a
> genfs_lock(5bd2dac,19073c,4f2ed20,10002,5bd2dd0) + 20
> VOP_LOCK(4f2ed20,10002) + 26                        =20
> vn_lock(4f2ed20,20002) + 94=20
> namei(5bd2ec4) + a66      =20
> sys___stat30(5b91c7c,5bd2f38,5bd2f78) + 30
> syscall_plain(183,5b91c7c,5bd2fb4,ffffffff,ffffb627) + c0
> syscall(183) + 62                                       =20
> trap0() + e     =20
>=20
> Chuck, is this related to your latest changes? Anything particular I shou=
ld
> dig?

Can you figure out the path that was being stat'd?

Take care,

Bill

--4Ckj6UjgE2iN1+kY
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)

iD8DBQFFfzBcWz+3JHUci9cRAttRAJ9VDpaOXWqBxPlikp5npJlvgHHNhACgg7KM
t91kVEHgGa9HCyjK9H0MeVI=
=EOUP
-----END PGP SIGNATURE-----

--4Ckj6UjgE2iN1+kY--