From owner-freebsd-doc@FreeBSD.ORG Thu May 13 14:10:22 2004 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9715216A4CF for ; Thu, 13 May 2004 14:10:22 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA08843D41 for ; Thu, 13 May 2004 14:10:21 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i4DLALFh069105 for ; Thu, 13 May 2004 14:10:21 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i4DLALFr069104; Thu, 13 May 2004 14:10:21 -0700 (PDT) (envelope-from gnats) Resent-Date: Thu, 13 May 2004 14:10:21 -0700 (PDT) Resent-Message-Id: <200405132110.i4DLALFr069104@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Stefan Bethke Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F49A16A4CE for ; Thu, 13 May 2004 14:02:22 -0700 (PDT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFDAF43D48 for ; Thu, 13 May 2004 14:02:21 -0700 (PDT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i4DL2LEQ006273 for ; Thu, 13 May 2004 14:02:21 -0700 (PDT) (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.11/8.12.11/Submit) id i4DL2LVj006272; Thu, 13 May 2004 14:02:21 -0700 (PDT) (envelope-from nobody) Message-Id: <200405132102.i4DL2LVj006272@www.freebsd.org> Date: Thu, 13 May 2004 14:02:21 -0700 (PDT) From: Stefan Bethke To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: docs/66621: Document fix for "kmem_map too small panics" X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 May 2004 21:10:22 -0000 >Number: 66621 >Category: docs >Synopsis: Document fix for "kmem_map too small panics" >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Thu May 13 14:10:21 PDT 2004 >Closed-Date: >Last-Modified: >Originator: Stefan Bethke >Release: 5-current >Organization: >Environment: FreeBSD majestix.tallence.de 5.2-CURRENT FreeBSD 5.2-CURRENT #5: Wed May 12 12:47:06 GMT 2004 root@majestix.tallence.de:/usr/obj/usr/src/sys/MAJESTIX i386 >Description: solution to "kmem_map too small" panics have been requested at least 5 times on -current in the past two months; fix is simple to implement, but hard to find :-) Kris Kennaway graciously provided advice to limit VM_KMEM_SIZE_MAX to 400 MB; that seems to be working for everybody who enquired. >How-To-Repeat: >Fix: Index: book.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/faq/book.sgml,v retrieving revision 1.618 diff -u -C10 -r1.618 book.sgml cvs diff: conflicting specifications of output style *** book.sgml 11 May 2004 13:29:47 -0000 1.618 --- book.sgml 13 May 2004 20:55:09 -0000 *************** *** 3082,3101 **** --- 3082,3125 ---- The boot floppy hangs on a system with an ASUS K7V motherboard. How do I fix this? Go into the BIOS setup and disable the boot virus protection. + + + + My system has more than 1 GB of RAM, and I'm getting panics + with kmem_map too small messages. What is + wrong? + + + + Normally, FreeBSD determines a number of kernel parameters, + such as the maximum number of open files that can be opened + concurrently, from the amount of memory installed in the + system. On systems with one gigabyte of RAM or more, this + auto-sizing mechanism may choose values that are + too large, leading to poor performance, or even to + panics. + In this particular case, the kernel memory allocation map + is too small for the amount of memory the kernel believes it + should be able to allocate, hence the panic. Compile your own + kernel, and add the to your + kernel configuration file. Limiting the maximum size to 400 MB + (). + + Troubleshooting What do I do when I have bad blocks on my hard drive? >Release-Note: >Audit-Trail: >Unformatted: