From owner-freebsd-emulation@freebsd.org  Fri Aug  5 00:10:36 2016
Return-Path: <owner-freebsd-emulation@freebsd.org>
Delivered-To: freebsd-emulation@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id C76F1BAE0E6
 for <freebsd-emulation@mailman.ysv.freebsd.org>;
 Fri,  5 Aug 2016 00:10:36 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id A93BF1D67
 for <freebsd-emulation@FreeBSD.org>; Fri,  5 Aug 2016 00:10:36 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
 by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id u750ATJ7016450
 for <freebsd-emulation@FreeBSD.org>; Thu, 4 Aug 2016 17:10:33 -0700 (PDT)
 (envelope-from truckman@FreeBSD.org)
Message-Id: <201608050010.u750ATJ7016450@gw.catspoiler.org>
Date: Thu, 4 Aug 2016 17:10:29 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
Subject: kernel panic caused by virtualbox
To: freebsd-emulation@FreeBSD.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
X-BeenThere: freebsd-emulation@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Development of Emulators of other operating systems
 <freebsd-emulation.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-emulation>, 
 <mailto:freebsd-emulation-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-emulation/>
List-Post: <mailto:freebsd-emulation@freebsd.org>
List-Help: <mailto:freebsd-emulation-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-emulation>, 
 <mailto:freebsd-emulation-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2016 00:10:36 -0000

I just got a kernel panic when I started up a CentOS 7 VM in virtualbox.
The host is:
	FreeBSD 12.0-CURRENT #17 r302500 GENERIC amd64
The virtualbox version is:
	virtualbox-ose-5.0.26
	virtualbox-ose-kmod-5.0.26_1

The panic message is:

panic: Unregistered use of FPU in kernel
cpuid = 1
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe085a55d030
vpanic() at vpanic+0x182/frame 0xfffffe085a55d0b0
kassert_panic() at kassert_panic+0x126/frame 0xfffffe085a55d120
trap() at trap+0x7ae/frame 0xfffffe085a55d330
calltrap() at calltrap+0x8/frame 0xfffffe085a55d330
--- trap 0x16, rip = 0xffffffff827dd3a9, rsp = 0xfffffe085a55d408, rbp = 0xfffffe085a55d430 ---
g_pLogger() at 0xffffffff827dd3a9/frame 0xfffffe085a55d430
g_pLogger() at 0xffffffff8274e5c7/frame 0x3
KDB: enter: panic

Since g_pLogger is a symbol in vboxdrv.ko, it looks like virtualbox is
the trigger.

There are no symbols for the virtualbox kmods, possibly because I
installed them as an upgrade using packages (built with the same source
tree version) instead of by using PORTS_MODULES in make.conf, so ports
kgdb didn't have anything useful to say about what happened before the
trap.

This panic is very repeatable.  I just got another one when starting the
same VM., but this time the two calls before the trap were
null_bug_bypass().

I don't see this with a Windows 7 VM.