Date: Tue, 02 Nov 2021 18:37:53 +0300 From: Greg V via freebsd-current <freebsd-current@freebsd.org> To: imb@protected-networks.net, Michael Butler via freebsd-current <freebsd-current@freebsd.org> Cc: "freebsd-emulation@freebsd.org" <freebsd-emulation@freebsd.org> Subject: Re: current now panics when starting VBox VM Message-ID: <36923A7F-23DE-490D-B1FA-A8B064740BD6@unrelenting.technology> In-Reply-To: <d4c79b85-2668-3fe8-7c4a-9304e7fd88d1@protected-networks.net>
index | next in thread | previous in thread | raw e-mail
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_pathname was touched recently there. (Also can someone commit https://reviews.freebsd.org/D30174 ? These warning-filled reports are unreadable >_<)help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36923A7F-23DE-490D-B1FA-A8B064740BD6>