From owner-freebsd-current@FreeBSD.ORG Thu Mar 4 05:23:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D90316A4CE for ; Thu, 4 Mar 2004 05:23:05 -0800 (PST) Received: from oahu.WURLDLINK.NET (oahu.wurldlink.net [66.193.144.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1458E43D46 for ; Thu, 4 Mar 2004 05:23:05 -0800 (PST) (envelope-from vince@oahu.WURLDLINK.NET) Received: from oahu.WURLDLINK.NET (vince@localhost.WURLDLINK.NET [127.0.0.1]) by oahu.WURLDLINK.NET (8.12.9/8.12.9) with ESMTP id i24DMJqQ005467 for ; Thu, 4 Mar 2004 03:22:29 -1000 (HST) Received: from localhost (vince@localhost)i24DMII2005464 for ; Thu, 4 Mar 2004 03:22:18 -1000 (HST) Date: Thu, 4 Mar 2004 03:22:18 -1000 (HST) From: Vincent Poy To: current@freebsd.org In-Reply-To: <20040304021753.I8264-100000@oahu.WURLDLINK.NET> Message-ID: <20040304032033.P8264-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: -CURRENT kernel panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2004 13:23:05 -0000 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@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@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@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin