Date: Tue, 2 Nov 2021 18:32:26 -0400 From: Michael Butler via freebsd-emulation <freebsd-emulation@freebsd.org> To: Cy Schubert <Cy.Schubert@cschubert.com>, greg@unrelenting.technology Cc: "freebsd-emulation@freebsd.org" <freebsd-emulation@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: current now panics when starting VBox VM Message-ID: <1ccb6ce3-2cb7-e325-79e3-cda5640f24df@protected-networks.net> In-Reply-To: <202111022148.1A2LmeHX004930@slippy.cwsent.com> References: <d4c79b85-2668-3fe8-7c4a-9304e7fd88d1@protected-networks.net> <36923A7F-23DE-490D-B1FA-A8B064740BD6@unrelenting.technology> <202111022148.1A2LmeHX004930@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/2/21 17:48, Cy Schubert wrote: > In message <36923A7F-23DE-490D-B1FA-A8B064740BD6@unrelenting.technology>, > Greg > V via freebsd-current writes: >> >> >> On November 2, 2021 5:16:35 PM GMT+03:00, Michael Butler via freebsd-current >> <freebsd-current@freebsd.org> wrote: >>> On current as of this morning (I haven't tried to bisect yet) .. >>> >>> .. with either graphics/drm-devel-kmod or graphics/drm-current-kmod, >>> trying to start a VirtualBox VM triggers this panic .. >>> >> >>> #16 0xffffffff80c81fc8 at calltrap+0x8 >>> #17 0xffffffff808b4d69 at sysctl_kern_proc_pathname+0xc9 >> >> something something https://reviews.freebsd.org/D32738 ? sysctl_kern_proc_pat >> hname was touched recently there. >> >> (Also can someone commit https://reviews.freebsd.org/D30174 ? These warning-f >> illed reports are unreadable >_<) > > Usually the first thing to do with virtualbox is rebuild it. That usually > fixes any panics I experience here. Of course, make sure your virtualbox > ports subdirs are fully patched, as it's an opportune time to update it too. Before reporting this, I rebuilt world including kernel, all kmods and virtualbox itself to no avail :-( I agree; most issues I've had in the past have been resolvable using this approach. Not this time, Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1ccb6ce3-2cb7-e325-79e3-cda5640f24df>