Date: Sun, 20 Sep 2020 10:26:11 +0200 From: Rainer Hurling <rhurlin@gwdg.de> To: Hans Petter Selasky <hps@selasky.org>, monochrome <monochrome@twcny.rr.com> Cc: <freebsd-current@freebsd.org> Subject: Re: Fwd: Re: r365488 page faults on AMD Ryzen 9 3950X Message-ID: <2bbfb4b3-92e9-b3ca-9c31-6c513cee2f2d@gwdg.de> In-Reply-To: <b6d7aa27-948a-b820-76b9-1f91a1df0471@selasky.org> References: <69ff9432-fc8f-b0ab-8ad2-8e3daa77f8e1@twcny.rr.com> <1a88773b-d2fa-a790-c7e2-868d3884ba8b@twcny.rr.com> <865D6BF0-9F1E-4125-81D3-FB9A369FED8D@gwdg.de> <88af31d4-9ed9-172a-d48f-1780f19841e3@twcny.rr.com> <11d27d41-029a-d7f5-eccc-0ba3a3fcfe97@gwdg.de> <b6d7aa27-948a-b820-76b9-1f91a1df0471@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Best wishes, Rainer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2bbfb4b3-92e9-b3ca-9c31-6c513cee2f2d>