> For the two crashes that I've been able to capture some output
> from (one from an IP KVM, one from /var/log/messages after setting
> ddb.panic=0), I've seen:
>
>
> uvm_fault(0xffffffff81cf2b20, 0xffff800000cef000, 0, 2) -> e
> kernel: page fault trap, code=0
> Stopped at memmove+0x16: repe movsq (%rsi),%es:(%rdi)
>
> and
>
> reboot after panic: trap type 8, code=0, pc=ffffffff81292dff
Whoops - the hosting company caught some of the panic message before
it rebooted this morning (retyped from a screenshot):
VOP_FSYNC() at VOP_FSYNC+0x2f
ffs_sync_vnode() at ffs_sync_vnode+0x77
vfs_mount_foreach_vnode() at vfs_mount_foreach_vnode+0x38
ffs_sync() at ffs_sync+0x83
sys_sync() at sys_sync+0xa1
vfs_syncwait() at vfs_syncwait+0x50
vfs_shutdown() at vfs_shutdown+0x32
boot() at boot+0x17f
panic() at panic+0xf6
trap() at trap+0x7f1
--- trap (number 8) ---
ffs_update() at ffs_update+0x19f
ufs_inactive() at ufs_inactive+0xd3
VOP_INACTIVE() at VOP_INACTIVE+0x28
vrele() at vrele+0x61
proc_zap() at proc_zap+0xa1
dowait4() at dowait4+0x2ca
sys_wait4() at sys_wait4+0x38
syscall() at syscall+0x249
--- syscall (number 11) ---
end of kernel
end trace frame: 0xd6f3ca35c0, count: 215
0xd6f3cebaea:
End of stack trace.
--
"No matter how tempted I am with the prospect of unlimited power, I
will not consume any energy field bigger than my head."
-- #22 on Peter Anspach's Evil
Overlord list
