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-curr...@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
