Sorry, this is overdue on being reported.
I've encountered a panic with VIMAGE from a patched build of current
from around mid September. I tracked the problem to the second call
to refcount_release in kern_vimage.c:vi_td_ioctl(). Just for clarity
I determined this by making 3 refcount_re
Happy New Year!
I've been encountering a problem with packets going where they're not
supposed to regardless of static routes and ipfw rules meant to block
said miss routed packets. My vimage setup is fairly complex and may
well be the actual cause of the problem so haven't wanted to say
