panic: System call old.recv returning with 1 locks held

[Pawel Jakub Dawidek]

On Sun, Sep 10, 2006 at 05:15:56PM -0400, Kris Kennaway wrote:
> On Sun, Sep 10, 2006 at 11:00:03PM +0200, Alexander Leidinger wrote:
> > Quoting Kris Kennaway <kris at obsecurity.org> (Sun, 10 Sep 2006 14:43:59 -0400):
> > 
> > > Enable DEBUG_LOCKS and DEBUG_VFS_LOCKS then run 'show lockedvnods'
> > > from DDB to find out where the lockmgr lock was acquired.
> > 
> > I've enabled them (and WITNESS, INVARIANTS and DIAGNOSTICS) and rebuild
> > the kernel. Not much files where rebuild.
> 
> That's a warning sign; almost every file in the kernel should have
> been rebuilt when you turned on WITNESS and INVARIANTS.  Perhaps you
> didn't run 'make depend'?
> 
> > show lockedvnods did not show any locks.
> 
> Odd, I thought your initial panic was from a held lockmgr lock, so it
> should have showed up here.

In HEAD (not sure if it was MFCed) jhb@ added code to track number of
mutexes/sx-locks acquired/released. So bascially this panic can happen
when you leak a lock of any kind.

'show alllocks' has to show them when the kernel (and modules) is
compiled with WITNESS.

-- 
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd at FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20060911/373e50e0/attachment.pgp