From owner-freebsd-current@freebsd.org Mon Aug 8 17:28:42 2016 Return-Path: Delivered-To: freebsd-current@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 3B29BBB29E4 for ; Mon, 8 Aug 2016 17:28:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1CFC71857; Mon, 8 Aug 2016 17:28:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 367D3B97E; Mon, 8 Aug 2016 13:28:40 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Cc: Don Lewis , freebsd-current@freebsd.org Subject: Re: kernel panic caused by virtualbox(?) Date: Mon, 08 Aug 2016 10:22:44 -0700 Message-ID: <2743385.seuRjyAMVA@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.3-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <201608050132.u751WE75016607@gw.catspoiler.org> References: <201608050132.u751WE75016607@gw.catspoiler.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 08 Aug 2016 13:28:40 -0400 (EDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2016 17:28:42 -0000 On Thursday, August 04, 2016 05:10:29 PM Don Lewis wrote: > Reposted to -current to get some more eyes on this ... > > 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(). Hmn, that symbol is in nullfs ... > > I don't see this with a Windows 7 VM. > > All of the virtualbox kmod files are compiled with -mno-mmx -mno-sse > -msoft-float -mno-aes -mno-avx I suspect head packages are quite likely built against the a "wrong" KBI and are too fragile to use for kmods vs compiling from ports. :-/ I would try a built-from-ports kmod to see if the panics go away. -- John Baldwin