Date: Thu, 22 May 2003 22:39:02 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Jake Burkholder <jake@locore.ca> Cc: current@freebsd.org Subject: Re: 5.1 PAE testing results: 2 panics Message-ID: <3ECDB3F6.3E391587@mindspring.com> References: <C50AB9511EE59B49B2A503CB7AE1ABD10440E52E@cceexc19.americas.cpqcorp.net> <20030523024041.GA28928@locore.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Jake Burkholder wrote: > Apparently, On Thu, May 22, 2003 at 08:11:33PM -0500, > Cagle, John (ISS-Houston) said words to the effect of; > > panic: kmem_malloc(4096): kmem_map too small: 96624640 total allocated > > > > I tried lowering kern.maxvnodes from 536130 (default) to 200000, > > but that did not alleviate the panic. > > Can you try reducing this by half again to 100,000 and see if that > helps things? Increasing the amount of available kva with options > KVA_PAGES may also work, but finding the right limits for vnodes is > a better solution. Note that the values for KVA_PAGES are doubled > with PAE, eg 512 gives you the standard 3G user/1G kernel split. FWIW... If the auto-sizing code is taking the actual amount of RAM into account to make its decisions, this could easily be the problem. You may want to modify machdep.c to "clamp" the amount of memory used in auto-sizing at 4G or even 3G, to account for the window's impact on available wired pages. Without the original dmesg (specifically, the part where it spits out the memory size information), it's hard to tell if this is likely the problem or not. -- Terry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3ECDB3F6.3E391587>