On Tue, Aug 13, 2013 at 8:47 PM, Jeff Roberson <jrober...@jroberson.net>wrote:
> On Tue, 13 Aug 2013, Jim Harris wrote: > > >> >> >> On Tue, Aug 13, 2013 at 3:05 PM, Jeff Roberson <jrober...@jroberson.net> >> wrote: >> >> It's not any one commit really, just creeping demand for more pages >> before the VM can get started. I would suggest making boot pages >> scale with MAXCPU. Or just raising it as the panic suggests. We >> could rewrite the way that the vm gets these early pages but it's a >> lot of work and typically people just bump it and forget about it. >> >> >> I ran into this problem today when enabling hyperthreading on my >> dual-socket >> Xeon E5 system. >> >> It looks like r254025 is actually the culprit. Specifically, the new >> mallocinit()/kmeminit() now invoke the new vmem_init() before >> uma_startup2(), which allocates 16 zones out of the boot pages if I am >> reading this correctly. This is all done before uma_startup2() is called, >> triggering the panic. >> >> > I just disabled the quantum caches in vmem which allocate those 16 zones. > This may alleviate the problem for now. > > Thanks, > Jeff > > Yes - this does alleviate the problem. Thanks! -Jim _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
