Subject: Re: -current amd64 panic, _kernel_unlock: assertion failed: olocks == 1
To: Andrew Doran <email@example.com>
From: Nicolas Joly <firstname.lastname@example.org>
Date: 02/20/2007 18:01:10
On Tue, Feb 20, 2007 at 04:38:05PM +0000, Andrew Doran wrote:
> On Tue, Feb 20, 2007 at 03:39:30PM +0100, Nicolas Joly wrote:
> > Since a few days, i'm experiencing kernel hard lockup. The problem
> > arise when the Symantec (was Veritas) NetBackup server tries to backup
> > my up-to-date -current NetBSD/amd64 workstation using linux 32-bits
> > binaries (which worked perfectly during the last 5 monthes).
> > Kernel lock error: _kernel_unlock: assertion failed: olocks == 1
> > lock address : 0xffffffff80ce4ea0 type : spin
> > shared holds : 0 exclusive: 1
> > shares wanted: 0 exclusive: 183
> > current cpu : 1 last held: 1
> > current lwp : 0xffff80004c93a900 last held: 0xffff80004c93a900
> > last locked : 0xffffffff807d6801 unlocked : 0xffffffff807d682d
> > curcpu holds : 2 wanted by: 000000000000000000
> > panic: LOCKDEBUG
> > Stopped in pid 360.1 (bpcd) at netbsd:breakpoint+0x5: leave
> I think this one should be fixed now, sorry. I also fixed an issue with
> LOCKDEBUG kernels, where lots of file system activity would eventually
> provoke a panic.
I confirm, i cannot panic/hang my kernel anymore, with telnet on bpcd
Thanks a lot for your prompt reply, and fix.
Biological Software and Databanks.
Institut Pasteur, Paris.