From owner-freebsd-doc@FreeBSD.ORG Tue Jul 13 16:10:07 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 5A67F16A4CE; Tue, 13 Jul 2004 16:10:07 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DAE243D41; Tue, 13 Jul 2004 16:10:07 +0000 (GMT) (envelope-from roam@FreeBSD.org) Received: from freefall.freebsd.org (roam@localhost [127.0.0.1]) i6DGA7Q3016117; Tue, 13 Jul 2004 16:10:07 GMT (envelope-from roam@freefall.freebsd.org) Received: (from roam@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i6DGA6Ok016113; Tue, 13 Jul 2004 16:10:06 GMT (envelope-from roam) Date: Tue, 13 Jul 2004 16:10:06 GMT From: Peter Pentchev Message-Id: <200407131610.i6DGA6Ok016113@freefall.freebsd.org> To: stb@lassitu.de, roam@FreeBSD.org, freebsd-doc@FreeBSD.org, roam@FreeBSD.org Subject: Re: 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: Tue, 13 Jul 2004 16:10:07 -0000 Synopsis: Document fix for "kmem_map too small panics" State-Changed-From-To: open->feedback State-Changed-By: roam State-Changed-When: Tue Jul 13 16:06:41 GMT 2004 State-Changed-Why: Does this also apply to 4.x-STABLE? Both the VM_KMEM_SIZE_MAX option and autosizing support (maxusers 0) are present in -STABLE, too. In this case - or actually, in any case - wouldn't it be better if your excellent explanation replaced the current question 5.11, 'panic-kmemmap-too-small', which seems to pertain to pre-maxusers kernels? Responsible-Changed-From-To: freebsd-doc->roam Responsible-Changed-By: roam Responsible-Changed-When: Tue Jul 13 16:06:41 GMT 2004 Responsible-Changed-Why: I'll take care of this. http://www.freebsd.org/cgi/query-pr.cgi?pr=66621