From owner-freebsd-current@FreeBSD.ORG Thu Mar 4 06:53:12 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 5E23E16A4CE for ; Thu, 4 Mar 2004 06:53:12 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C82A43D1F for ; Thu, 4 Mar 2004 06:53:12 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i24ErBF6003319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Mar 2004 09:53:11 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i24Er5Vu082061; Thu, 4 Mar 2004 09:53:05 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16455.17105.820332.248316@grasshopper.cs.duke.edu> Date: Thu, 4 Mar 2004 09:53:05 -0500 (EST) To: Vincent Poy In-Reply-To: <20040304032033.P8264-100000@oahu.WURLDLINK.NET> References: <20040304021753.I8264-100000@oahu.WURLDLINK.NET> <20040304032033.P8264-100000@oahu.WURLDLINK.NET> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid 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 14:53:12 -0000 Vincent Poy writes: > > 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 Just add vm.kmem_size=VALUE to /boot/loader.conf. That way you don't need to rebuild a kernel. I run with vm.kmem_size=429391872 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.. Drew