On Sun, Sep 20, 2020 at 10:26:11AM +0200, Rainer Hurling wrote: > Am 20.09.20 um 10:20 schrieb Hans Petter Selasky: > > On 2020-09-20 10:05, Rainer Hurling wrote: > >> Hi monochrome, > >> > >> back to keyboard, it tried newest CURRENT (r365920) on my box and even > >> with newest sources the error occurs. > >> > >> After looking around somewhat more, I found some hints about Virtualbox > >> kernel module having problems with r365488. Unfortunately, I am not able > >> to find the thread again :( > >> > >> What seems to help as a workaround is to disable the loading of > >> VirtualBox in /boot/loader.conf > >> > >> #vboxdrv_load="YES" > >> > >> and in /etc/rc.conf > >> > >> #vboxnet_enable="YES" > >> #vboxguest_enable="YES" > >> > >> > >> So probably, this page fault is not restricted to AMD Ryzen? > >> > > > > Possibly you need to rebuild that kernel module. Maybe the FreeBSD > > version was not bumped correctly. > > > > --HPS > > > > Thanks for the hint. But I did rebuild all kernel modules before > rebooting, in my case vbox*.ko, nvidia*.ko.
Provide backtrace of the panic. _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
