Fatal trap 9: general protection fault while in kernel mode VBoxDrvFreeBSDIOCtl

Bernhard Fröhlich decke at bluelife.at
Fri Nov 8 07:29:27 UTC 2013


Am 08.11.2013 04:23 schrieb <am00406 at surrey.ac.uk>:
>
> Hi,
> After update from freebsd 9.1 to freebsd 9.2 (Virtual Box was rebuilt)
VirtualBox started crash the system.
>
> Nov  8 00:15:30 xbsdhost kernel: Fatal trap 9: general protection fault
while in kernel mode
> Nov  8 00:15:30 xbsdhost kernel: cpuid = 7; apic id = 07
> Nov  8 00:15:30 xbsdhost kernel: instruction pointer =
0x20:0xffffffff81b90de6
> Nov  8 00:15:30 xbsdhost kernel: stack pointer        =
0x28:0xffffff88a5948720
> Nov  8 00:15:30 xbsdhost kernel: frame pointer        =
0x28:0xffffff88a5948790
> Nov  8 00:15:30 xbsdhost kernel: code segment = base 0x0, limit 0xfffff,
type 0x1b
> Nov  8 00:15:30 xbsdhost kernel: = DPL 0, pres 1, long 1, def32 0, gran 1
> Nov  8 00:15:30 xbsdhost kernel: processor eflags = interrupt enabled,
resume, IOPL = 0
> Nov  8 00:15:30 xbsdhost kernel:
> Nov  8 00:15:30 xbsdhost kernel: current process = 85225 (VBoxHeadless)
> Nov  8 00:15:30 xbsdhost kernel: Fatal trap 9: general protection fault
while in kernel mode
> Nov  8 00:15:30 xbsdhost kernel: Fatal trap 9: general protection fault
while in kernel mode
> Nov  8 00:15:30 xbsdhost kernel: trap number = 9
> Nov  8 00:15:30 xbsdhost kernel: panic: general protection fault
> Nov  8 00:15:30 xbsdhost kernel: cpuid = 7
> Nov  8 00:15:30 xbsdhost kernel: KDB: stack backtrace:
> Nov  8 00:15:30 xbsdhost kernel: #0 0xffffffff80947986 at
kdb_backtrace+0x66
> Nov  8 00:15:30 xbsdhost kernel: #1 0xffffffff8090d9ae at panic+0x1ce
> Nov  8 00:15:30 xbsdhost kernel: #2 0xffffffff80cf20d0 at trap_fatal+0x290
> Nov  8 00:15:30 xbsdhost kernel: #3 0xffffffff80cf28e1 at trap+0x241
> Nov  8 00:15:30 xbsdhost kernel: #4 0xffffffff80cdbd13 at calltrap+0x8
> Nov  8 00:15:30 xbsdhost kernel: #5 0xffffffff81b8b0bd at g_aUnits+0xb0fd
> Nov  8 00:15:30 xbsdhost kernel: #6 0xffffffff81b97dc6 at g_aUnits+0x17e06
> Nov  8 00:15:30 xbsdhost kernel: #7 0xffffffff818717fd at
supdrvIOCtlFast+0x7d
> Nov  8 00:15:30 xbsdhost kernel: #8 0xffffffff8187d8ce at
VBoxDrvFreeBSDIOCtl+0x4e
> Nov  8 00:15:30 xbsdhost kernel: #9 0xffffffff807f4afb at
devfs_ioctl_f+0x7b
> Nov  8 00:15:30 xbsdhost kernel: #10 0xffffffff8095a3d6 at
kern_ioctl+0x106
> Nov  8 00:15:30 xbsdhost kernel: #11 0xffffffff8095a61d at sys_ioctl+0xfd
> Nov  8 00:15:30 xbsdhost kernel: #12 0xffffffff80cf187a at
amd64_syscall+0x5ea
> Nov  8 00:15:30 xbsdhost kernel: #13 0xffffffff80cdbff7 at
Xfast_syscall+0xf7
> Nov  8 00:15:30 xbsdhost kernel: Uptime: 1d22h1m25s
>
> As far as I remember before update, the system was more stable.
>
> There are 2 virtual machines with OpenBSD on it, the network adapter is
in bridged mode.
> I am planning to remove the FreeBSD and use Linux or something else until
the FreeBSD hypervisor will be released, so if you need any information I
can provide you with it but in limited time. Also I can upload full crash
dump if needed.
>
> Kind Regards,
> Alexander Morozov
> FHEQ5 Computer Science
> UofS

Are the panics immediately after starting the VM and are they reproducible?
Did you also update the virtualbox-ose-kmod port and reboot after that?


More information about the freebsd-emulation mailing list