From owner-freebsd-current@freebsd.org Sat Oct 20 01:09:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F3BAFEDD9E for ; Sat, 20 Oct 2018 01:09:39 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4384B75C6A; Sat, 20 Oct 2018 01:09:39 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (unknown [76.212.85.177]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: truckman) by smtp.freebsd.org (Postfix) with ESMTPSA id AF24822192; Sat, 20 Oct 2018 01:09:38 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Date: Fri, 19 Oct 2018 18:09:36 -0700 (PDT) From: Don Lewis Subject: Re: virtualbox 5.2.20 triggers panic with FreeBSD 12.0-ALPHA10 r339432 To: "Matthew D. Fuller" cc: freebsd-current@freebsd.org In-Reply-To: <20181020004607.GP32731@over-yonder.net> Message-ID: References: <20181020004607.GP32731@over-yonder.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Sat, 20 Oct 2018 01:09:39 -0000 On 19 Oct, Matthew D. Fuller wrote: > On Fri, Oct 19, 2018 at 03:47:40PM -0700 I heard the voice of > Don Lewis, and lo! it spake thus: >> >> The first is that when I attempt to start a Virtualbox VM, the >> system panics. > > Perhaps https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230460 Thanks, that appears to be it. I'm kind of wondering why I didn't run into this before my last upgrade. I was worried about this before my previous upgrade, but didn't encounter any problems. Since I hadn't seen any discussion of this in a while, I thought the problem had been resolved already ...