From owner-freebsd-bugs@FreeBSD.ORG Tue Jan 30 01:10:04 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8512816A401; Tue, 30 Jan 2007 01:10:04 +0000 (UTC) (envelope-from ade@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 60DBE13C471; Tue, 30 Jan 2007 01:10:04 +0000 (UTC) (envelope-from ade@FreeBSD.org) Received: from freefall.freebsd.org (ade@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l0U1A43c008742; Tue, 30 Jan 2007 01:10:04 GMT (envelope-from ade@freefall.freebsd.org) Received: (from ade@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l0U1A3ZT008738; Tue, 30 Jan 2007 01:10:03 GMT (envelope-from ade) Date: Tue, 30 Jan 2007 01:10:03 GMT From: Ade Lovett Message-Id: <200701300110.l0U1A3ZT008738@freefall.freebsd.org> To: wmoran@collaborativefusion.com, ade@FreeBSD.org, freebsd-bugs@FreeBSD.org, ade@FreeBSD.org Cc: Subject: Re: kern/108121: [pmap] pmap.c panic message references a sysctl that doesn't exist 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, 30 Jan 2007 01:10:04 -0000 Synopsis: [pmap] pmap.c panic message references a sysctl that doesn't exist State-Changed-From-To: open->closed State-Changed-By: ade State-Changed-When: Tue Jan 30 01:04:41 UTC 2007 State-Changed-Why: The message is correct. However, it is *NOT* a sysctl, rather it is a tunable that can be set in /boot/loader.conf eg: vm.pmap.shpgperproc=1000 Making this a sysctl, with the ability to dynamically change it whilst the system is running would be Exceptionally Hard[tm]. One could possibly make a case for providing a read-only sysctl, though it is likely to be of very limited use, since pv exhaustion is not by any means a typical occurance. Responsible-Changed-From-To: freebsd-bugs->ade Responsible-Changed-By: ade Responsible-Changed-When: Tue Jan 30 01:04:41 UTC 2007 Responsible-Changed-Why: Since I provided the specific "fix" (in terms of an appropriate panic, rather than letting the kernel wander off into la-la land as was the case previously), I'll assume (some of ;) the responsibility... http://www.freebsd.org/cgi/query-pr.cgi?pr=108121