From owner-freebsd-stable Wed May 7 10:10:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA02229 for stable-outgoing; Wed, 7 May 1997 10:10:13 -0700 (PDT) Received: from dopey.pathlink.com (dopey.pathlink.com [204.30.237.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA02224 for ; Wed, 7 May 1997 10:10:11 -0700 (PDT) Received: from dvl-1.pathlink.com (dvl-1.pathlink.com [204.30.237.241]) by dopey.pathlink.com (8.8.5/8.8.5) with SMTP id KAA22752 for ; Wed, 7 May 1997 10:20:38 -0700 (PDT) Message-Id: <1.5.4.32.19970507101001.006db218@dopey.pathlink.com> X-Sender: kachun@dopey.pathlink.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 07 May 1997 10:10:01 +0000 To: freebsd-stable@freebsd.org From: Kachun Lee Subject: kern malloc leak in 2.2X ? Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After upgrading to 2.2 (2.2beta thru 2.2-releng-970422), some of our systems would panic with 'kmem_map too small' every ~30 hours - clockwork. Per suggestion of Mr. Greenman, I increased VM_KMEM_SIZE from 32M to 48M. The systems still panic, but now about every 2.5days. That leads me to believe there may be a memory leak in 2.2X. Those systems are all heavy NFS clients over SMC 100 netcards. I wouldn't mind spend sometime to identify the problem, if someone could point me to the right direction. The last time I did any UNIX kernel work was back with UNIX sysIII.5. Any suggestion would be greatly appreicated. Best regards