Date: Wed, 4 Apr 2018 16:18:40 -0700 From: Craig Leres <leres@freebsd.org> To: 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: <aecf62a4-36e4-61a1-4428-f5eac1484130@freebsd.org> In-Reply-To: <1288458d-d0dd-40d8-eaf9-32fcd0ca6137@freebsd.org> References: <f769bfc5-b76e-49df-db15-e5cfb565554e@freebsd.org> <3fd9fbd1-26ef-c176-2c4b-cf02f89ea680@freebsd.org> <a10e62c3-9f93-758e-a5f4-4f66c8138253@freebsd.org> <1288458d-d0dd-40d8-eaf9-32fcd0ca6137@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/04/18 15:51, Allan Jude wrote: > 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. I'm not so sure about that. I believe MAXCPU changes some data structure sizes and allows for kernels that have up to that many cores. I don't believe loadable drivers care what it is. They system I built the virtualbox-ose-kmod package on was running the same 64 MAXCPU kernel at the time (I built and booted the custom kernel before building packages). Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aecf62a4-36e4-61a1-4428-f5eac1484130>