Date: Wed, 25 Jan 2023 02:38:21 +0100 From: Tomek CEDRO <tomek@cedro.info> To: Graham Perrin <grahamperrin@freebsd.org> Cc: FreeBSD questions <freebsd-questions@freebsd.org>, VirtualBox on FreeBSD team <vbox@freebsd.org>, Virtualisation on FreeBSD <freebsd-virtualization@freebsd.org> Subject: Re: 13.1-STABLE vritualbox-ose-kmod panic Message-ID: <CAFYkXjndd5psJE6E3jJXRRXT0kww22GW2qbg8qm5dw=sE1hcmg@mail.gmail.com> In-Reply-To: <7fe27024-d794-d808-c2f4-371c533eb2e4@freebsd.org> References: <CAFYkXjkwYJBx=naj75WbKAGbZv2f-9fVeWu5Bd2bRtpp9W=45A@mail.gmail.com> <3d8f8238-020b-0706-1c48-b17db12891f1@freebsd.org> <7fe27024-d794-d808-c2f4-371c533eb2e4@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 25, 2023 at 12:14 AM Graham Perrin wrote: > On 24/01/2023 22:06, Tomek CEDRO wrote: > > =E2=80=A6 The first time I noticed that problem was beginning of January = 2023. Before I was able to use virtualbox-ose(-kmod) on STABLE with no prob= lem. > > How can I make things work again? > > Will virtualbox-ose-kmod work only with a RELEASE and not with STABLE? > > It works here with CURRENT. Hmm I guess it works on RELEASE and CURRENT.. why it kernel panics STABLE? = o_O > Do I need to rebuild both virtualbox-ose and virtualbox-ose-kmod from por= ts? =E2=80=A6 > Tomek, please check that your copy of the ports tree is up-to-date. > If you build from source, build (and install) the kernel module alone. fresh git pull of the ports tree, port built and reinstalled from ports. :-( --=20 CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFYkXjndd5psJE6E3jJXRRXT0kww22GW2qbg8qm5dw=sE1hcmg>