From owner-freebsd-current@FreeBSD.ORG Thu Mar 4 14:14:24 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 589BA16A4CE for ; Thu, 4 Mar 2004 14:14:24 -0800 (PST) Received: from oahu.WURLDLINK.NET (oahu.wurldlink.net [66.193.144.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13DB843D31 for ; Thu, 4 Mar 2004 14:14:24 -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 i24MDXqQ015452; Thu, 4 Mar 2004 12:13:46 -1000 (HST) Received: from localhost (vince@localhost)i24MDXnJ015449; Thu, 4 Mar 2004 12:13:33 -1000 (HST) Date: Thu, 4 Mar 2004 12:13:32 -1000 (HST) From: Vincent Poy To: Andrew Gallatin In-Reply-To: <16455.34987.700107.64116@grasshopper.cs.duke.edu> Message-ID: <20040304120548.U8264-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org 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 22:14:24 -0000 On Thu, 4 Mar 2004, Andrew Gallatin wrote: > > 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. That part I understand but what exactly does the number 2 and 3 mean? > > > > > 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? vince@bigbang [2:07pm][~] >> sysctl vm.kmem_size vm.kmem_size: 209715200 > Try bumping it up via vm.kmem_size=805306368 /boot/loader.conf Just tried that but for some reason, the number doesn't set. vince@bigbang [2:12pm][~] >> sysctl vm.kmem_size vm.kmem_size: 209715200 vince@bigbang [2:12pm][~] >> cat /boot/loader.conf hw.ata.wc="1" snd_ich_load="YES" acpi_dsdt_load="YES" acpi_dsdt_name="/boot/acpi_dsdt.aml agp_load="YES" nvidia_load="YES" vm.kmem_size="805306368" Does it have to be in a certain order? Since I had the same problem when setting kern.ipc.nmbclusters where it didn't work either. 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