Date: Wed, 25 Jan 2023 17:54:07 +0000 From: Amar Takhar <verm@darkbeer.org> To: questions@freebsd.org Subject: Re: 13.1-STABLE vritualbox-ose-kmod panic Message-ID: <20230125175407.GA55292@darkbeer.org> In-Reply-To: <CAFYkXj=5hu1iYaDsT9eA5wy3WE%2B=rFTdXpVLvZZWdqrJd6AaBw@mail.gmail.com> References: <CAFYkXjkwYJBx=naj75WbKAGbZv2f-9fVeWu5Bd2bRtpp9W=45A@mail.gmail.com> <3d8f8238-020b-0706-1c48-b17db12891f1@freebsd.org> <7fe27024-d794-d808-c2f4-371c533eb2e4@freebsd.org> <CAFYkXjndd5psJE6E3jJXRRXT0kww22GW2qbg8qm5dw=sE1hcmg@mail.gmail.com> <20230125014222.GA27891@darkbeer.org> <CAFYkXj=5hu1iYaDsT9eA5wy3WE%2B=rFTdXpVLvZZWdqrJd6AaBw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2023-01-25 04:21 +0100, Tomek CEDRO wrote: > On Wed, Jan 25, 2023 at 2:42 AM Amar Takhar wrote: > > Did you remember to unload the old kernel module? Also be sure you're using the > > same kernel source as your running kernel I take the hash from a uname -a just > > to be sure. > > yes sir :-) Anytime I have issues with VirtualBox I delete all the packages unload the kmods and check for anything dangling in /usr/local/ and remove that as well. I know you're having panics I've had the boot loop issue before just last year after updating from 13-RELEASE to 13.1-RELEASE instant panic with no dumps. Just last week I was having issues with VMs not booting after a Qt update rebuilding all the ports fixed the issue. I always rebuild every port and never use packages VirtualBox can be really touchy but once it's running it's rock solid, I would try to go and carefully check everything again and do a rebuild from ports no packages at all and see what happens. For good measure before rebuilding make sure you update all your packages. Amar.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230125175407.GA55292>