I am also experiencing this problem after updating to beta 3. It is a hard lockup and no keys will respond. It requires the computer to be turned off via the power button. But it definitely looks like an issue with the virtualbox driver. Normally I disable the drivers from loading before I do an update but this time I forgot to.
So I rebuilt both virtualbox-ose and virtualbox-ose-kmod and the driver successfully loaded in my system updated to beta 3, but I haven't tested virtualbox yet to see if it actually works, although I have no reason to believe it won't. I suppose the issue really is if you forget to disable loading vboxdrv.ko like I did, it can result in a hard lockup. I know I had to lookup how to mount ZFS from a live cd to fix loader.conf, it's been a few years since the last time I've had to do it. On Tue, Sep 29, 2020, 16:14 Jeremy <jeremy.m.cox at gmail.com> wrote:> I am also experiencing this problem after updating to beta 3. It is a hard > lockup and no keys will respond. It requires the computer to be turned off > via the power button. But it definitely looks like an issue with the > virtualbox driver. Normally I disable the drivers from loading before I do > an update but this time I forgot to. >
On 9/30/20 10:35 PM, Jeremy wrote:> So I rebuilt both virtualbox-ose and virtualbox-ose-kmod and the driver > successfully loaded in my system updated to beta 3, but I haven't tested > virtualbox yet to see if it actually works, although I have no reason to > believe it won't. > > I suppose the issue really is if you forget to disable loading vboxdrv.ko > like I did, it can result in a hard lockup. I know I had to lookup how to > mount ZFS from a live cd to fix loader.conf, it's been a few years since > the last time I've had to do it. > > On Tue, Sep 29, 2020, 16:14 Jeremy <jeremy.m.cox at gmail.com> wrote: > >> I am also experiencing this problem after updating to beta 3. It is a hard >> lockup and no keys will respond. It requires the computer to be turned off >> via the power button. But it definitely looks like an issue with the >> virtualbox driver. Normally I disable the drivers from loading before I do >> an update but this time I forgot to. >>Maybe you can jump into the loader command line and then give "unset vboxdrv_load" a try. I think I've done something similar in the past by I don't remember the details. Regards, Mateusz Piotrowski