Re: 5.99.42/i386 crash (backtrace + core available)

[David Holland <dholland-current%netbsd.org@localhost>]

On Tue, Dec 28, 2010 at 05:37:43PM +0100, Dennis den Brok wrote:
 > rw_abort(df829668,c06548f2,c0654902,c0330da3,df20b830,df0ed540,df20b6cc,c05b1424,0,0)
 >  at 0xc0330c90
 > rw_vector_enter(df829668,1,1,c059ba97,0,0,df20b7e8,df8295c8,2,1) at 
 > 0xc0330ea0
 > genfs_lock(df20b7e8,2,df20b76c,c049dcd0,cd7e2180,0,80,df20b7ec,c0581be5,df20b830)
 >  at 0xc02125fc
 > layer_bypass(df20b7e8,0,df0ed540,c0325558,0,0,ffffffff,1,0,c0690998) at 
 > 0xc0363294
 > VOP_LOCK(e15c2170,2,df20b82c,c05a7d17,df0ed540,0,df0ed540,1000,1,0) at 
 > 0xc05c7249
 > vclean(e15c2170,8,4,c0534cc4,df8295c8,0,df20b87c,c05a5f78,e15c2170,c06d2638) 
 > at 0xc05a7de7
 > getcleanvnode(0,0,df20b90c,0,0,0,df20b90c,c01fa2cd,1,df20c000) at 0xc05a5b27
 > getnewvnode(1,df20c000,cc24fe40,df20b8f4,0,0,df20b85c,df20b84e,800,0) at 
 > 0xc05a6052

What was the panic message?

-- 
David A. Holland
dholland%netbsd.org@localhost