From owner-freebsd-current Sat Jan 11 3:12:21 2003 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 A427437B401; Sat, 11 Jan 2003 03:12:20 -0800 (PST) Received: from smtp.eos.ocn.ne.jp (eos.ocn.ne.jp [211.6.83.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0509E43EB2; Sat, 11 Jan 2003 03:12:20 -0800 (PST) (envelope-from hrs@eos.ocn.ne.jp) Received: from mail.allbsd.org (p44077-adsao12honb4-acca.tokyo.ocn.ne.jp [219.114.51.77]) by smtp.eos.ocn.ne.jp (Postfix) with ESMTP id 7995C39DA; Sat, 11 Jan 2003 20:12:18 +0900 (JST) Received: from localhost (alph.allbsd.org [192.168.0.10]) by mail.allbsd.org (8.12.3/3.7W/DomainMaster) with ESMTP id h0BAjXB2044926; Sat, 11 Jan 2003 19:45:33 +0900 (JST) (envelope-from hrs@eos.ocn.ne.jp) Date: Sat, 11 Jan 2003 19:45:07 +0900 (JST) Message-Id: <20030111.194507.130543329.hrs@eos.ocn.ne.jp> To: phk@FreeBSD.ORG Cc: tlambert2@mindspring.com, current@FreeBSD.ORG Subject: Re: panic with panic: kmem_malloc(4096): kmem_map too small... From: Hiroki Sato In-Reply-To: <2303.1041706799@critter.freebsd.dk> References: <20030105.034940.18284223.hrs@eos.ocn.ne.jp> <2303.1041706799@critter.freebsd.dk> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 2.2 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG phk@FreeBSD.ORG wrote in <2303.1041706799@critter.freebsd.dk>: phk> I only have 2G ram and that's what I have tested (extensively). If we're phk> still broken for >2G ram, somebody needs to revist this. phk> phk> One thing you can try is reduce the value of the phk> sysctl kern.maxvnodes phk> phk> If you set it to the same value as used for 2G (appros 130000), I phk> think your machine should survive with 3G RAM. Thank you for the clarification. I notice that the panic happens when numvnodes becomes more than about 185000. When kern.maxvnodes=130000 (198799 by default) is specified, the system works fine under heavy loads during this week. Is anyone else suffering from it? If it happens on all of >2GB systems, I think it should be solved (or described in relnotes) before the release. -- | Hiroki SATO To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message