Date: Thu, 4 Mar 2004 14:51:07 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Vincent Poy <vince@oahu.WURLDLINK.NET> Cc: current@freebsd.org Subject: Re: -CURRENT kernel panic Message-ID: <16455.34987.700107.64116@grasshopper.cs.duke.edu> In-Reply-To: <20040304093201.X8264-100000@oahu.WURLDLINK.NET> References: <16455.33748.860265.157572@grasshopper.cs.duke.edu> <20040304093201.X8264-100000@oahu.WURLDLINK.NET>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16455.34987.700107.64116>