Date: Wed, 25 Jan 2023 13:45:35 +0100 From: Tomek CEDRO <tomek@cedro.info> To: Ka Ho Ng <khng300@gmail.com> Cc: Graham Perrin <grahamperrin@freebsd.org>, VirtualBox on FreeBSD team <vbox@freebsd.org>, Virtualisation on FreeBSD <freebsd-virtualization@freebsd.org>, FreeBSD questions <freebsd-questions@freebsd.org> Subject: Re: 13.1-STABLE vritualbox-ose-kmod panic Message-ID: <CAFYkXjn-=e9qUwPRzOnoM1OAURQ_saoAJ2Lw0oCkuHNyDfDxbQ@mail.gmail.com> In-Reply-To: <CANnchUYtYmnA9pBdo9bDkiK4-4HP0zmDfy_GVt5TFO5LxUS0fQ@mail.gmail.com> References: <CAFYkXjkwYJBx=naj75WbKAGbZv2f-9fVeWu5Bd2bRtpp9W=45A@mail.gmail.com> <3d8f8238-020b-0706-1c48-b17db12891f1@freebsd.org> <CANnchUYtYmnA9pBdo9bDkiK4-4HP0zmDfy_GVt5TFO5LxUS0fQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 25, 2023 at 4:19 AM Ka Ho Ng wrote: > virtualbox-ose-kmod uses non-public kernel interfaces, thus requires rebuild after kernel buildkernel (in this case -STABLE). It is simply irrelevant whether it works on -RELEASE / -CURRENT. > > Further triage is needed only if the virtualbox-ose-kmod after rebuild still panics the kernel. This seems the case o_O service vboxguest onestart <- this one works service vboxservice onestart <- kernel panic here kldload vboxdrv <- kernel panic here I had to disable all vbox stuff in /boot/loader.conf and /etc/rc.conf otherwise boot loop. No dump is stored in /var/crash I only got this picture: https://ibb.co/D51Q1xm Will have to debug it somehow :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFYkXjn-=e9qUwPRzOnoM1OAURQ_saoAJ2Lw0oCkuHNyDfDxbQ>