Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Nov 2013 01:29:09 +0000
From:      <am00406@surrey.ac.uk>
To:        <vbox@FreeBSD.org>
Subject:   Fatal trap 9: general protection fault while in kernel mode VBoxDrvFreeBSDIOCtl
Message-ID:  <e81a1de51b424601a802c1259a1cfc59@DB4PR06MB221.eurprd06.prod.outlook.com>

next in thread | raw e-mail | index | archive | help
Hi,
After update from freebsd 9.1 to freebsd 9.2 (Virtual Box was rebuilt) Virt=
ualBox started crash the system.

Nov  8 00:15:30 xbsdhost kernel: Fatal trap 9: general protection fault whi=
le in kernel mode
Nov  8 00:15:30 xbsdhost kernel: cpuid =3D 7; apic id =3D 07
Nov  8 00:15:30 xbsdhost kernel: instruction pointer =3D 0x20:0xffffffff81b=
90de6
Nov  8 00:15:30 xbsdhost kernel: stack pointer        =3D 0x28:0xffffff88a5=
948720
Nov  8 00:15:30 xbsdhost kernel: frame pointer        =3D 0x28:0xffffff88a5=
948790
Nov  8 00:15:30 xbsdhost kernel: code segment =3D base 0x0, limit 0xfffff, =
type 0x1b
Nov  8 00:15:30 xbsdhost kernel: =3D DPL 0, pres 1, long 1, def32 0, gran 1
Nov  8 00:15:30 xbsdhost kernel: processor eflags =3D interrupt enabled, re=
sume, IOPL =3D 0
Nov  8 00:15:30 xbsdhost kernel:
Nov  8 00:15:30 xbsdhost kernel: current process =3D 85225 (VBoxHeadless)
Nov  8 00:15:30 xbsdhost kernel: Fatal trap 9: general protection fault whi=
le in kernel mode
Nov  8 00:15:30 xbsdhost kernel: Fatal trap 9: general protection fault whi=
le in kernel mode
Nov  8 00:15:30 xbsdhost kernel: trap number =3D 9
Nov  8 00:15:30 xbsdhost kernel: panic: general protection fault
Nov  8 00:15:30 xbsdhost kernel: cpuid =3D 7
Nov  8 00:15:30 xbsdhost kernel: KDB: stack backtrace:
Nov  8 00:15:30 xbsdhost kernel: #0 0xffffffff80947986 at kdb_backtrace+0x6=
6
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+0=
x7d
Nov  8 00:15:30 xbsdhost kernel: #8 0xffffffff8187d8ce at VBoxDrvFreeBSDIOC=
tl+0x4e
Nov  8 00:15:30 xbsdhost kernel: #9 0xffffffff807f4afb at devfs_ioctl_f+0x7=
b
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+0x=
5ea
Nov  8 00:15:30 xbsdhost kernel: #13 0xffffffff80cdbff7 at Xfast_syscall+0x=
f7
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 t=
he FreeBSD hypervisor will be released, so if you need any information I ca=
n provide you with it but in limited time. Also I can upload full crash dum=
p if needed.

Kind Regards,
Alexander Morozov
FHEQ5 Computer Science
UofS



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e81a1de51b424601a802c1259a1cfc59>