From owner-freebsd-questions Wed Apr 30 23:13:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA12632 for questions-outgoing; Wed, 30 Apr 1997 23:13:17 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA12627 for ; Wed, 30 Apr 1997 23:13:14 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id XAA25217; Wed, 30 Apr 1997 23:14:31 -0700 (PDT) Message-Id: <199705010614.XAA25217@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Kachun Lee cc: freebsd-questions@freebsd.org Subject: Re: kmem_map full with 2.2beta to 2.2-releng-970422 In-reply-to: Your message of "Tue, 29 Apr 1997 09:14:17 -0000." <1.5.4.32.19970429091417.006d4e64@dopey.pathlink.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 30 Apr 1997 23:14:31 -0700 Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >After upgraded some of our news servers to 2.2, they would panic about every >other days with the kmem_map full (Just for info, they went fine with >2.1.6). I increased NMBCLUSTERS from 3000 to 4000 to 5000 to 6000 and that >did not help. I logged the netstat -m every 15 minutes and the mbufs usage >was in the 2000s when the system crashed. > >Any suggestion, or where or how I should look for the problem? That panic is not related to the mbuf clusters problem. The kmem_map full panic indicates that the kernel has run out of malloc space. The standard default size is 32MB. You can increase it by changing VM_KMEM_SIZE in i386/include/vmparam.h. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project