Date: Thu, 5 Apr 2018 21:04:07 -0700 From: Craig Leres <leres@freebsd.org> To: Eugene Grosbein <eugen@grosbein.net>, Allan Jude <allanjude@freebsd.org>, freebsd-hackers@freebsd.org Subject: Re: 11.1-RELEASE virtualbox-ose panic: ncpus is 0 with non-zero map Message-ID: <7c0a41c4-01a2-140f-2628-6aa7e1da976f@freebsd.org> In-Reply-To: <5AC5A2D4.2080202@grosbein.net> References: <f769bfc5-b76e-49df-db15-e5cfb565554e@freebsd.org> <3fd9fbd1-26ef-c176-2c4b-cf02f89ea680@freebsd.org> <a10e62c3-9f93-758e-a5f4-4f66c8138253@freebsd.org> <5AC5A2D4.2080202@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/04/18 21:15, Eugene Grosbein wrote:
> 05.04.2018 5:42, Craig Leres wrote:
>
>> 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.
>
> This is known problem that was raised multiple times in several mailing lists.
Thanks for that; once I went looking I found this PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219913
Due to ABI difference (vboxdrv passes cpuset_t parameter (bitfield
with CPU_SETSIZE -> MAXCPU bits) into smp_rendezvous_cpus())
kernel panics with "ncpus is 0 with non-zero map" message.
Part of my normal FreeBSD upgrade process was to raise MAXCPU to 64. As
it turns out that is already the default for 10 and the default was
*raised* to 256 for 11.
So the solution is: don't mess with MAXCPU.
Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7c0a41c4-01a2-140f-2628-6aa7e1da976f>