> >knowing the value of p->p_locks and lockcount at this point will be
> >useful (just to verify that something was left locked, as opposed to
> >something extra being unlocked); also, in a DEBUG kernel, try calling
> >printlockedvnodes() at this point..
> 
> A few printf()s later and with a -current kernel, I got
> 
> [hauke@elmo] ~ > ../../../../nfs/nfs_syscalls.c, line 618: p->p_locks = 1,
> lockc
> ount = 0 !
> Locked vnodes
> printlockedvnodes() says -266950656 ...
> nfsd: locking botch in op 3
> 
> -- printlockedvnodes() may be bogus, I don't know what it returns (I
> used %d).

It's supposed to print out info about locked vnodes to the console.

this looks suspiciously like something other than a vnode lock is
being left locked..

					- Bill