Re: panic: System call lstat returning with 1 locks held

> On Jan 17, 2008 11:40 PM, Scot Hetzel <swhetzel_at_gmail.com> wrote:
> > The panic didn't occur after lock order reversal 4, instead it occured
> > after the system had displayed lock order reversal 2.
> >
> > hp010# /usr/local/etc/cvsup/update.sh &
> > hp010# tail -f /var/log/cvsup.log
> > :
> > <lock order reversal 1>
> > :
> > <lock order reversal 3>
> > :
> > <lock order reversal 1>
> > <lock order reversal 2>
> > :
> > <lock order reversal 4>
> > :
> > <lock order reversal 1>
> > <lock order reversal 2>
> > Edit CVSROOT-ports/modules,v
> > :
> > :
> > Edit ports/audio/sonata/pkg-plist,v
> > panic: System call lstat returning with 1 locks held
> > cpuid = 0
> > KDB: enter: panic
> > [ thread pid 996 tid 10011 ]
> > stopped at kdb_enter+0x3d: movq $0,0x4ad188(%rip)
> > db> show lockedvnods
> > Locked vnodes
> > db>
> >



On 1/18/08, Kip Macy <kip.macy_at_gmail.com> wrote:
> What does:
> Try
>
> ddb> show locks
>
It doesn't show any locks, I also tried show alllocks and nothing was displayed.

When the panic occured this time, lock order reversal 4 didn't occur.

Scot