From owner-freebsd-bugs@FreeBSD.ORG Wed Dec 26 15:40:02 2007 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C714A16A418 for ; Wed, 26 Dec 2007 15:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C530913C44B for ; Wed, 26 Dec 2007 15:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id lBQFe2jB066061 for ; Wed, 26 Dec 2007 15:40:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id lBQFe2pj066060; Wed, 26 Dec 2007 15:40:02 GMT (envelope-from gnats) Date: Wed, 26 Dec 2007 15:40:02 GMT Message-Id: <200712261540.lBQFe2pj066060@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Kris Kennaway Cc: Subject: Re: kern/118955: googleearth causes panic in 7.0-BETA4/i386 - kmem_malloc/kmem_map too small X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kris Kennaway List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Dec 2007 15:40:02 -0000 The following reply was made to PR kern/118955; it has been noted by GNATS. From: Kris Kennaway To: Martin Etteldorf Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/118955: googleearth causes panic in 7.0-BETA4/i386 - kmem_malloc/kmem_map too small Date: Wed, 26 Dec 2007 16:36:14 +0100 Martin Etteldorf wrote: > Kris, > >> Your kernel ran out of memory. Increase the vm.kmem_size tunable in >> /boot/loader.conf (it usually defaults to 300*1024*1024 = 314572800) >> until the problem goes away. If the problem persists even with a large >> kmem_map there might be a memory leak in the kernel. > > Thanks for your help. I increased the vm.kmem_size gradually in 25% steps > and after I reached 200% of the default value (671088640), the problem went > away. > > Shouldn't I modify vm.kmem_size_max as well? It's currently still at its > default value, which is 335544320. That is just used for auto-tuning and is overridden when you set kmem_size by hand, I think. Kris