From owner-freebsd-bugs@FreeBSD.ORG Tue May 27 09:53:06 2008 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CEC91065687; Tue, 27 May 2008 09:53:06 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C145E8FC16; Tue, 27 May 2008 09:53:05 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <483BDA00.8040207@FreeBSD.org> Date: Tue, 27 May 2008 11:53:04 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: S Roberts References: <200805232326.m4NNQQG4089363@freefall.freebsd.org> <1211876727.24906.1255223109@webmail.messagingengine.com> In-Reply-To: <1211876727.24906.1255223109@webmail.messagingengine.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bugs@FreeBSD.org, vwe@FreeBSD.org Subject: Re: kern/123813: [panic] 7.0-STABLE i386 reboots weekly with panic: kmem_malloc(11186176): kmem_map too small: 315637760 total allocated X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2008 09:53:06 -0000 S Roberts wrote: > Hello, > > On Fri, 23 May 2008 23:26:26 GMT, vwe@FreeBSD.org said: >> Synopsis: [panic] 7.0-STABLE i386 reboots weekly with panic: >> kmem_malloc(11186176): kmem_map too small: 315637760 total allocated >> >> State-Changed-From-To: open->feedback >> State-Changed-By: vwe >> State-Changed-When: Fri May 23 23:23:11 UTC 2008 >> State-Changed-Why: >> >> Stacey, please try increasing vm.kmem_size_max in /etc/loader.conf and >> reboot. > > Is this the procedure for i386? > > I thought that setting this in /etc/loader.conf is only viable for > amd64., First, it's /boot/loader.conf, but it is supported on all architectures. To add some detail, the panic indicates that your kernel ran out of memory because of the workload your system was running on it. Unless you are hitting a memory leak, the solution is to allocate it more memory. Kris