Re: -CURRENT kernel panic

From: Andrew Gallatin <gallatin_at_cs.duke.edu>
Date: Thu, 4 Mar 2004 14:30:28 -0500 (EST)
Vincent Poy writes:
 > On Thu, 4 Mar 2004, Andrew Gallatin wrote:
 > 
 > > Just add vm.kmem_size=VALUE to /boot/loader.conf.  That way you don't
 > > need to rebuild a kernel.   I run with vm.kmem_size=429391872
 > 
 > 	Does that actually work since I thought unless you alter the
 > kernel, it won't use more than 200KB for the kmem_map?

Sure.. read the code (kern/kern_malloc.c:kmeminit) The
VM_KMEM_SIZE_MAX comes first, then the tunable from the loader.

 > > Even after bumping the limits, I'm seeing a repeatable panic when
 > > allocating a large amount of kernel memory ("panic: pmap_enter:
 > > attempted pmap_enter on 4MB page").  See yesterday's message
 > > with that subject for details..
 > 
 > 	Just checked the archives and yours seems to jhave more variables
 > than mines from the panic message.

Can you describe the panic you see?

Drew
Received on Thu Mar 04 2004 - 10:30:35 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:46 UTC