Re: amd64 current kernel crashes w/ rw_vector_enter: locking against myself

[Kurt Schreiner <ks%ub.uni-mainz.de@localhost>]

On Wed, Aug 19, 2009 at 11:14:09PM +0200, David Laight wrote:
> On Wed, Aug 19, 2009 at 10:52:02PM +0200, Kurt Schreiner wrote:
> > Hi,
> > 
> > trying to boot a kernel compiled from -current sources cvs updated
> > Aug 19 20:57 MEST results in an early crash. Doesn't matter if I
> > try booting a GENERIC kernel (as shown below) or a customized one.
> > This is on a Sun Ultra24 w/ an Intel Q6600 and 8GB Ram...
> 
> I'd try building a kernel with 'tail-call' optimisation disabled.
> It might give a better looking traceback.
Just added -fno-optimize-sibling-calls to COPTS. Crash is the same,
but trace looks slightly "better".

Kurt

> boot netbsd.gen_090819
booting hd0a:netbsd.gen_090819
10720224+543680+722240 [764040+501597]=0xda48e8
Reader / writer lock error: rw_vector_enter: locking against myself

lock address : 0xffffffff80d0d368
current cpu  :                  0
current lwp  : 0xffffffff80c9c940
owner/count  : 0xffffffff80c9c940 flags    : 0x0000000000000004

panic: lock error
fatal breakpoint trap in supervisor mode
trap type 1 code 0 rip ffffffff8022dc95 cs 8 rflags 246 cr2  ffff80000f6dcf8c 
cpl 8 rsp ffffffff80ea86d0
Stopped in pid 0.1 (system) at  netbsd:breakpoint+0x5:  leave
db{0}> bt
breakpoint() at netbsd:breakpoint+0x5
cpu_Debugger() at netbsd:cpu_Debugger+0x9
panic() at netbsd:panic+0x29e
lockdebug_abort() at netbsd:lockdebug_abort+0x3a
rw_abort() at netbsd:rw_abort+0x22
rw_vector_enter() at netbsd:rw_vector_enter+0x25b
vm_map_lock_read() at netbsd:vm_map_lock_read+0xf
uvm_fault_internal() at netbsd:uvm_fault_internal+0xc9
trap() at netbsd:trap+0x68e
--- trap (number 0) ---
0:
db{0}>