Hello

Could anyone familiar with that code give me ideas of how to track down
the root of this problem? The machine is both a NFS client and a NFS
server, is this panic server-side related or client-side related? I'd
bet for client side but I'm not sure.

It has been crashing randomly for a week, and this continue after I made
a dump/restore on the filesystems and I removed the whole hardware (no
more underlying hardware: it's now a Xen domU on another machine).
Before it started crashing, it worked for years without a hitch.

panic: kernel debugging assertion "(vp->v_flag & VONWORKLST)" failed:
file "/home/builds/ab/netbsd-3/src/sys/miscfs/genfs/genfs_vnops.c", line
1322
Begin traceback...
__assert(c03f386f,c0420e20,52a,c03fb3a1,cb42fd40) at
netbsd:__assert+0x2e
genfs_putpages(cb573dd4,cb637208,1,0,c03e3ae0) at
netbsd:genfs_putpages+0x8bb
VOP_PUTPAGES(cb5d0ddc,0,0,0,0) at netbsd:VOP_PUTPAGES+0x42
nfs_flush(cb5d0ddc,ca280dc8,1,cb55a330,0) at netbsd:nfs_flush+0x3b
nfs_close(cb573e74,cb2a8000,cb573e9c,c0318d48,c03e3020) at
netbsd:nfs_close+0x7f
VOP_CLOSE(cb5d0ddc,3,ca280dc8,cb55a330,cb51eb34) at
netbsd:VOP_CLOSE+0x36
vn_close(cb5d0ddc,3,ca280dc8,cb55a330,ff) at netbsd:vn_close+0x45
vn_closefile(cb51eb34,cb55a330,2,cb573f04,40) at
netbsd:vn_closefile+0x29
closef(cb51eb34,cb55a330,cb573f5c,cb55a330,ffffffff) at
netbsd:closef+0x127
syscall_plain() at netbsd:syscall_plain+0x19b
--- syscall (number 6) ---
0xbdb341f7:
End traceback...
syncing disks... done

dumping to dev 142,1 offset 261392
dump device bad


rebooting...

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@netbsd.org