Subject: lock panic
To: None <current-users@netbsd.org>
From: Patrick Welche <prlw1@newn.cam.ac.uk>
List: current-users
Date: 11/13/2007 12:47:34
With this morning's i386 CVS (Nov 13 10:37 GMT), I just got the following, but
sadly no coredump...
Cheers,
Patrick
Reader / writer lock error: lockdebug_wantlock: locking against myself
lock address : 0x00000000d749ad54 type : sleep/adaptive
shared holds : 0 exclusive: 1
shares wanted: 1 exclusive: 0
current cpu : 0 last held: 0
current lwp : 0x00000000d7087a80 last held: 0x00000000d7087a80
last locked : 0x00000000c02c8a07 unlocked : 0x00000000c02c8bca
initialized : 0x00000000c02d088c
owner/count : 0x00000000d7087a80 flags : 0x0000000000000004
Turnstile chain at 0xc0621d40.
=> No active turnstile for this lock.
panic: LOCKDEBUG
Stopped in pid 795.1 (sh) at netbsd:breakpoint+0x1: ret
bt/l
breakpoint(c052caf2,cca61858,0,0,cca61858) at netbsd:breakpoint+0x1
panic(c052bd04,c0359ad9,c052baac,c052babf,d3280000) at netbsd:panic+0xd1
lockdebug_abort1(d32874b8,c063bac0,c052baac,c052babf,1) at netbsd:lockdebug_abort1+0x6e
lockdebug_wantlock(319f2,c02bf4bf,1,cca619f0,c03522bd) at netbsd:lockdebug_wantlock+0xea
rw_vector_enter(d749ad54,0,700005c,cca61930,c0352284) at netbsd:rw_vector_enter+0x69
vm_map_lock_read(d749ad50,c063bb00,7,cca61950,c03522bd) at netbsd:vm_map_lock_read+0x55
uvmfault_lookup(cca61ad8,0,1,cca61980,c0352251) at netbsd:uvmfault_lookup+0x63
uvm_fault_internal(d749ad50,0,1,0,28) at netbsd:uvm_fault_internal+0x81
trap() at netbsd:trap+0xa19
--- trap (number 6) ---
?(0,0,0,0,0) at 0
db{0}> c
syncing disks... Kernel lock error: _kernel_lock: spinout
lock address : 0x00000000c061ed64 type : spin
shared holds : 0 exclusive: 1
shares wanted: 0 exclusive: 1
current cpu : 1 last held: 0
current lwp : 0x00000000d7087380 last held: 0x00000000d7087a80
last locked : 0x00000000c03f9346 unlocked : 0x00000000c03f84b6
initialized : 0x00000000c03053c0
curcpu holds : 0 wanted by: 0x00000000d7087380
panic: LOCKDEBUG
Stopped in pid 2522.1 (rm) at netbsd:breakpoint+0x1: ret
db{1}> reboot 0x104
dumping to dev 4,9 offset 21951
..which failed