The vgonel panic happens very often on a production machine we have here.
Is there anyone that knows more about this area of the kernel that can
give me some hints about what to search for?

-- Ragge

> 
> --- trap (number 6) ---
> (null)(df43c7b4,8,df2d6c9c) at 0xe1
> vgonel(df43c7b4,df2d6c9c) at vgonel+0x3b
> getnewvnode(1,c054c000,c0520100,df4d4cf0,cf386900) at getnewvnode+0x1b9
> ffs_vget(c054c000,3beda,df4d4d80,df4d4eb4,c05a4c00) at ffs_vget+0x51
> ufs_lookup(df4d4e90,ffffffff,df4df4e90,df4d4eb4,df2599f8) at ufs_lookup+0xbfe
> lookup(df4d4e90,df4d4f88,df2d6c8c,df4d4f88,df4d4eb4) at lookup+0x26b
> namei(df4d4e90,df4d4f88,df2d6c8c,df4d4f80,8054840) at namei+0x4bf
> sys___lstat13(df2d6c8c,df4d4f88,df4d4f80,480e9efc,8054840) at sys_lstat13+0x44
> 
> 
> syscall() at syscall+0x1e7
> --- syscall (number 280) ---
> 0x480da71f:
> 
> btw, ddb is very cpu unfriendly (especially for laptops)
> 
>