Re: -CURRENT kernel panic

On Thu, 4 Mar 2004, Vincent Poy wrote:

> Hello everyone:
>
> 	I'm getting the following -current panic with the latest -current
> since the February 28, 2004 code as a upgrade from September 2003.  My
> latest build is from the March 3, 2004 code.
>
> panic: kmem_malloc (4096): kmem_map too small: 377487360 total allocated
>        at line 341 in file /usr/src/sys/vm/vm_kern.c
> cpuid=0;
> Debugger("panic")
> Stopped at Debugger+0x46: xchgl %ebx, in_Debugger.0
>
> vince_at_bigbang [4:15am][~] >> ident /usr/src/sys/vm/vm_kern.c
> /usr/src/sys/vm/vm_kern.c:
>      $FreeBSD: src/sys/vm/vm_kern.c,v 1.114 2004/02/16 21:36:59 des Exp $
>
> 	Is there a way around this?  maxusers=0 from maxusers=512 in the
> kernel didn't make a difference.  The system does have one pipe under
> ipfw/dummynet with 4 queues but the panic occurs sometime during running
> this:
>
> /sbin/dump -L -f- /usr|restore -rf-
>
> where it's dumping to /mnt/usr - another hard drive

	Just searched the mailing list archives and it's suggested to add
in:

options         VM_KMEM_SIZE_MAX=(768*1048576)
options         VM_KMEM_SIZE_SCALE=2

to the kernel config file to fix this.  Is this eventually going to be
fixed?  I looked at the coverstation between Terry Lambert and David but
I'm still not sure what the number in VM_KMEM_SIZE_SCALE represents since
I know it defaults at 3 but is the 3 like the VM_KMEM_SIZE_MAX divided by
3 or how does it work?


Cheers,
Vince - vince_at_WURLDLINK.NET - Vice President             ________   __ ____
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / |  / |[__  ]
WurldLink Corporation                                  / / / /  | /  | __] ]
San Francisco - Honolulu - Hong Kong                  / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____]
Almighty1_at_IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin