From owner-freebsd-current Sat Jan 4 10:51:46 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 51C1537B401; Sat, 4 Jan 2003 10:51:45 -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 A740E43E4A; Sat, 4 Jan 2003 10:51:44 -0800 (PST) (envelope-from hrs@eos.ocn.ne.jp) Received: from mail.allbsd.org (p14087-adsao12honb4-acca.tokyo.ocn.ne.jp [219.161.234.87]) by smtp.eos.ocn.ne.jp (Postfix) with ESMTP id 9B4592462; Sun, 5 Jan 2003 03:51:43 +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 h04IpIB2012907; Sun, 5 Jan 2003 03:51:18 +0900 (JST) (envelope-from hrs@eos.ocn.ne.jp) Date: Sun, 05 Jan 2003 03:49:40 +0900 (JST) Message-Id: <20030105.034940.18284223.hrs@eos.ocn.ne.jp> To: phk@FreeBSD.ORG Cc: wjw@withagen.nl, current@FreeBSD.ORG Subject: Re: panic with panic: kmem_malloc(4096): kmem_map too small... From: Hiroki Sato In-Reply-To: <7651.1041670679@critter.freebsd.dk> References: <03a701c2b38c$8e3ad990$471b3dd4@dual> <7651.1041670679@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 Hi, phk@FreeBSD.ORG wrote in <7651.1041670679@critter.freebsd.dk>: phk> In message <03a701c2b38c$8e3ad990$471b3dd4@dual>, "Willem Jan Withagen" writes: phk> >Which seems a problem sticking up it's head once so often. phk> >I had it happen to me now 3 times over the last day. It just drops into the debugger. phk> >And I've foun little extra info in the archive. phk> > phk> >What dows this actually mean? Is something leaking in the kernel. phk> >IF so how do I help it go away. phk> > phk> >I'm copy 100G from a W2K system to my vinum file server with a 170G raid5. phk> >Current is as of 28 dec... phk> phk> Please try to move up to current as of today. On Dec 29th I commited phk> code to make the desiredvnodes a limit rather than a vague suggestion phk> and that should solve your problem I hope. I also had "kmem_malloc(4096): kmem_map too small: 275378176 total allocated" several times on -current as of Jan 4th. My -current box has 3GB memory, but when the memory size is explicitly specified as 2GB via MAXMEM option, the panic disappears (but I don't know why...). -- | Hiroki SATO To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message