Date: Wed, 08 Aug 2018 16:26:06 +0000 From: bugzilla-noreply@freebsd.org To: vbox@FreeBSD.org Subject: maintainer-feedback requested: [Bug 230460] emulators/virtualbox-ose panic on CURRENT Message-ID: <bug-230460-26505-qNyXNYnr5g@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230460-26505@https.bugs.freebsd.org/bugzilla/> References: <bug-230460-26505@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Bugzilla Automation <bugzilla@FreeBSD.org> has asked vbox@FreeBSD.org for maintainer-feedback: Bug 230460: emulators/virtualbox-ose panic on CURRENT https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230460 --- Description --- Virtualbox is causing a kernel panic during VM start. I'm using a recent CURRENT: $ uname -a FreeBSD capeta 12.0-CURRENT FreeBSD 12.0-CURRENT #10 r337378M: Mon Aug 6 11:06:26 -03 2018=20=20=20=20 danilo@capeta:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 I'm not using the binary module, I built it from ports. The system panics immediately and doesn't drop me to the debugger. The message is: Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0x28 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff80c7e806 stack pointer =3D 0x28:0xfffffe009c0b84c0 frame pointer =3D 0x28:0xfffffe009c0b84f0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 3505 (VBoxNetAdpCtl) I've built the kernel module with and without VIMAGE to test, same problem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230460-26505-qNyXNYnr5g>