Vincent Poy writes: > On Thu, 4 Mar 2004, Andrew Gallatin wrote: > > Interesting. I'm still wondering what the VM_KMEM_SIZE_SCALE > number represents. It tries to autoscale the kmem size, so that you don't need to hard code it. Hardcoding it could be bad if you change the amount of ram in the box. > > > > 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? > > Everything including buildworld doesn't cause the panic except at > 4AM at night when I do a dump | restore of the /usr partition which shows > just this: > > panic: kmem_malloc (4096): kmem_map too small: 377487360 total allocated > at line 341 in file /usr/src/sys/vm/vm_kern.c According to this, your kmem map size is too small. (360MB). What does sysctl vm.kmem_size show? 377487360? Try bumping it up via vm.kmem_size=805306368 /boot/loader.conf DrewReceived on Thu Mar 04 2004 - 10:51:14 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:46 UTC