Hey,

This of use to anybody?

db> bt
cpu_Debugger(c040ed4f,c9662a18,0,0,c9662a18) at netbsd:cpu_Debugger+0x4
panic(c040a801,c0409752,c03f1614,c0403078,c047d7e0) at netbsd:panic+0x155
lockdebug_abort(0,c047d7e0,c043beb0,c03f1614,c0403078) at 
netbsd:lockdebug_abort
+0x61
mutex_abort(c047d7e0,c03f1614,c0403078,0,1) at netbsd:mutex_abort+0x3c
mutex_vector_enter(c047d7e0,0,c0839400,c047e460,c9863378) at 
netbsd:mutex_vector
_enter+0x12f
turnstile_wakeup(c8c6ca14,1,1,0,c99d04b0) at netbsd:turnstile_wakeup+0xc4
mutex_vector_exit(c9863378,3f80000,0,32aa00,0) at 
netbsd:mutex_vector_exit+0xff
nfs_doio_write(c9662bf0,0,c9662bec,c02dd4d2,c961d700) at 
netbsd:nfs_doio_write+0
x4a2
nfs_doio(c08a6378,100,c0403e41,0,c0470fe0) at netbsd:nfs_doio+0x1aa
nfssvc_iod(c961d700,0,0,c01001f5,c961d700) at netbsd:nfssvc_iod+0xce
start_nfsio(c961d700,0,c01001e7,c01001df,c01001e7) at netbsd:start_nfsio+0x13
db>
db> reboot
syncing disks... Mutex error: mutex_vector_enter: locking against myself

lock address : 0x00000000c047d7e0
current cpu  :                  0
current lwp  : 0x00000000c961d700
owner field  : 0x0000000000010b00 wait/spin:                0/1

panic: lock error
Stopped in pid 223.1 (nfsio) at netbsd:cpu_Debugger+0x4:        popl    %ebp


It occurred when I redirected some p2p activity to an nfs share ...

NetBSD babylon.internal 4.99.13 NetBSD 4.99.13 (XEN3_DOMU) #3: Tue Feb 27 
15:53:51 EST 2007  
root@spike.internal:/usr/obj/sys/arch/i386/compile/XEN3_DOMU i386

Let me know if there is anything else I can do.

Sarton