Subject: Re: panic: lockmgr: release of unlocked lock
To: Manuel Bouyer <>
From: Bill Studenmund <>
List: tech-kern
Date: 01/10/2005 13:35:51
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jan 08, 2005 at 01:25:23PM +0100, Manuel Bouyer wrote:
> Hi,
> I just got this on a 2.0/alpha system doing a bulk build:
> panic: lockmgr: release of unlocked lock!
> db> tr
> cpu_Debugger() at netbsd:cpu_Debugger+0x4
> panic() at netbsd:panic+0x1f8
> lockmgr() at netbsd:lockmgr+0x308
> layer_unlock() at netbsd:layer_unlock+0x98
> VOP_UNLOCK() at netbsd:VOP_UNLOCK+0x3c
> vput() at netbsd:vput+0x5c
> lookup() at netbsd:lookup+0x44c

Can you get a line number for the above?

> Just before the panic there is:
> vnode: table is full - increase kern.maxvnodes or NVNODE
> I don't know if it's related or not.

It might be. Please also put a diagnostic printf() near line 473 of=20
layerfs_lookup(), in the if (error) case just after layer_node_create().=20
There may be an inconsistency in how we handle an error in case that=20
create fails.

Take care,


Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.3 (NetBSD)