Date: Tue, 15 May 2018 11:01:08 +0200 From: "Jose G. Juanino" <jjuanino@gmail.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Upgrade to 11.2-BETA1: vboxdrv kernel modulo load leads to panic unless vbox ports be rebuilt Message-ID: <20180515090058.p5xxd3i6ddrwry4k@riemann> In-Reply-To: <CAN6yY1s-WeCvoNLNZwyXB8aUVY3qkZMX=M-K4xLVmj1jnpkBKQ@mail.gmail.com> References: <20180513135328.k56hsaww7nb55o4v@riemann> <20180513194134.b2nzuwyusdwtxuov@riemann> <CAN6yY1s-WeCvoNLNZwyXB8aUVY3qkZMX=M-K4xLVmj1jnpkBKQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, May 14 at 05:39:33 CEST, Kevin Oberman wrote: > > Kernel modules are NOT guaranteed to work between kernels. It is > recommended that all kernel modules from ports and lsof be added to > PORTS_MODULES so they are re-built after each kernel update. Rebuild > virtualbox-ose-kmod, unload all vbox modules and reload them. That > should fix he problem. Sorry for the late reply. I was assuming that kernel modules are not guaranteed to work between *major* upgrades, but I was wrong, thanks for clarifying that. Regards. -- Jose G. Juanino
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180515090058.p5xxd3i6ddrwry4k>