Re: current now panics when starting VBox VM
Date: Tue, 02 Nov 2021 21:48:40 UTC
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 > <email@example.com> 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. -- Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: https://FreeBSD.org NTP: <firstname.lastname@example.org> Web: https://nwtime.org The need of the many outweighs the greed of the few.