Date: Wed, 4 Apr 2018 17:19:03 -0600 From: Cy Schubert <Cy.Schubert@cschubert.com> To: Allan Jude <allanjude@freebsd.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: RE: 11.1-RELEASE virtualbox-ose panic: ncpus is 0 with non-zero map Message-ID: <20180404231857.45A6732A4@spqr.komquats.com>
next in thread | raw e-mail | index | archive | help
I had the same problem on -current last week. Rebuilding the vbox kld resolved the panic. I also rebuilt the GUI for clean and healthy living. --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert <Cy.Schubert@cschubert.com> or <cy@freebsd.org> The need of the many outweighs the greed of the few. --- -----Original Message----- From: Allan Jude Sent: 04/04/2018 16:52 To: freebsd-hackers@freebsd.org Subject: Re: 11.1-RELEASE virtualbox-ose panic: ncpus is 0 with non-zero map On 2018-04-04 18:42, Craig Leres wrote: > On 04/04/18 15:33, Allan Jude wrote: >> So are you loading the virtualbox module from 10.3 into an 11.1 kernel? >> >> You'll need to rebuild the virtualbox-ose-kmod port to match the kernel >> you are runnin > > As part of the upgrade I removed all packages (pkg delete -fya), after I > used enough pkg.freebsd.org packages to be able to run poudriere to > rebuild all of the packages I use. Then I reinstalled all packages from > my pkg server (pkg clean -ay ; pkg upgrade -yf ; pkg clean -ay). > > I just verified that /boot/modules/vbox*.ko match the ones in the > package in > /public/FreeBSD:11:amd64/latest/All/virtualbox-ose-kmod-5.2.8_1.txz on > my server. > > Craig > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" The official packages are built for the GENERIC kernel, I think specifically changing the MAXCPU will change the size of one of the structs used by the module, causing this issue. -- Allan Jude _______________________________________________ freebsd-hackers@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180404231857.45A6732A4>