On Mon, Dec 01, 2003 at 03:20:12PM +0100, Frank van der Linden wrote:
> On Mon, Dec 01, 2003 at 03:15:14PM +0100, Nicolas Joly wrote:
> > panic: lockmgr: processor 0, not exclusive lock holder 1 unlocking
> > Stopped at      netbsd:cpu_Debugger+0x1:
> > db{0}> bt
> > cpu_Debugger() at netbsd:cpu_Debugger+0x1
> > kernel: page fault trap, code=0
> > Faulted in DDB; continuing...
> > 
> > This is a GENERIC.MP kernel with the following 2 lines for the kernel
> > debugger :
> > 
> > options DDB
> > options DDB_ONPANIC=1
> 
> Could you try two things for me:
> 
> 1) use -fno-omit-frame-pointer in the makeoptions in the kernel config
>    file (there's a commented line right by the DDB option that must
>    be used, or backtraces won't work).
> 2) Try switching on LOCKDEBUG, this should catch the problem earlier.

Ok, i've make a new kernel with (1)+(2). And it really looks better
...

panic: lockmgr: processor 1, not exclusive lock holder 0 unlocking
Stopped at      netbsd:cpu_Debugger+0x5:
db{1}> bt
cpu_Debugger() at netbsd:cpu_Debugger+0x5
panic() at netbsd:panic+0x1c8
_lockmgr() at netbsd:_lockmgr+0xa35
exit1() at netbsd:exit1+0x369
sys_exit() at netbsd:sys_exit+0x30
netbsd32_exit() at netbsd:netbsd32_exit+0x28
netbsd32_syscall_plain() at netbsd:netbsd32_syscall_plain+0x96

-- 
Nicolas Joly

Biological Software and Databanks.
Institut Pasteur, Paris.