From owner-freebsd-stable@FreeBSD.ORG Tue Jul 22 21:04:03 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 667C61065678 for ; Tue, 22 Jul 2008 21:04:03 +0000 (UTC) (envelope-from royce@alaska.net) Received: from malik.acsalaska.net (malik.acsalaska.net [209.112.173.227]) by mx1.freebsd.org (Postfix) with ESMTP id 3B7D18FC12 for ; Tue, 22 Jul 2008 21:04:02 +0000 (UTC) (envelope-from royce@alaska.net) Received: from [10.0.102.101] (209-112-156-43-adslb0fh.acsalaska.net [209.112.156.43]) by malik.acsalaska.net (8.14.1/8.14.1) with ESMTP id m6ML41Qr072415; Tue, 22 Jul 2008 13:04:01 -0800 (AKDT) (envelope-from royce@alaska.net) Message-ID: <48864B41.50300@alaska.net> Date: Tue, 22 Jul 2008 13:04:01 -0800 From: Royce Williams User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.14) Gecko/20080421 Thunderbird/2.0.0.14 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: Kris Kennaway References: <488638DA.7010005@alaska.net> <48863F23.9020504@FreeBSD.org> In-Reply-To: <48863F23.9020504@FreeBSD.org> X-Enigmail-Version: 0.95.6 OpenPGP: url=http://www.tycho.org/royce/royce@alaska.net.asc X-Face: ">19[ShfDD9'g", GrH$'v:=qBVZdg.kXSBR6*ZC$am:D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-ACS-Spam-Status: no X-ACS-Scanned-By: MD 2.63; SA 3.2.3; spamdefang 1.122 Cc: freebsd-stable@FreeBSD.org Subject: Re: 6.3-RELEASE-p3 recurring panics on multiple SM PDSMi+ X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2008 21:04:03 -0000 Kris Kennaway wrote, on 7/22/2008 12:12 PM: > Royce Williams wrote: > >> db> trace >> Tracing pid 71182 tid 100325 td 0xcc08b180 >> kdb_enter(c095f294) at kdb_enter+0x2b >> panic(c09768ad,1000,14000000,c145bc88,1000,...) at panic+0x127 >> kmem_malloc(c14680c0,1000,102,eba6a8cc,c07e3fa5,...) at kmem_malloc+0x89 > > You forgot to include the panic Is there is a way to get the panic after dropping into the debugger? This serial console setup has no scrollback, so I couldn't see the preceding text. > but this is probably the "kmem_map too small" panic. Ah, I see this now, at faq/book.html#KMEM-MAP-TOO-SMALL: "Compile your own kernel, and add the VM_KMEM_SIZE_MAX to your kernel configuration file, increasing the maximum size to 400 MB (options VM_KMEM_SIZE_MAX=419430400). 400 MB appears to be sufficient for machines with up to 6 GB of memory." > It says that your kernel ran out of memory, and the > solution is to fix that situation by giving more memory to the kernel. > Increase the vm.kmem_size tunable until your system stops running out of > memory on your workload. Comparing the FAQ, kern_malloc.c and your mentioning it as tunable, please clarify: is the Right Thing to do to use vm.kmem_size, or vm.kmem_size_max? I tried vm.kmem_size_max, which yields: # sysctl -a | grep kmem vm.kmem_size: 419430400 vm.kmem_size_max: 419430400 vm.kmem_size_scale: 3 Should I contribute some additional language to the FAQ, saying that the vm.kmem_size[_max] tunable can be used without recompiling the kernel? Royce -- Royce D. Williams - http://royce.ws/ Reproof should not exhaust its power upon petty failings. - S. Johnson