Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Jan 2007 15:48:36 GMT
From:      Bill Moran<wmoran@collaborativefusion.com>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   kern/108121: pmap.c panic message references a sysctl that doesn't exist
Message-ID:  <200701191548.l0JFmal4087933@www.freebsd.org>
Resent-Message-ID: <200701191550.l0JFoKbx057902@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         108121
>Category:       kern
>Synopsis:       pmap.c panic message references a sysctl that doesn't exist
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jan 19 15:50:20 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator:     Bill Moran
>Release:        Tested on both 6.1 and 6.2
>Organization:
Collaborative Fusion Inc.
>Environment:
FreeBSD db00.lab00 6.2-RELEASE FreeBSD 6.2-RELEASE #1: Thu Jan 18 17:19:48 EST 2007     root@db00.lab00:/usr/obj/usr/src/sys/DB-2850-amd64  amd64
>Description:
See the following thread on -questions@ for some information:
http://lists.freebsd.org/pipermail/freebsd-questions/2007-January/140286.html

It appears as if pmap.c contains an error message suggesting the user
increase a sysctl that doesn't exist:
panic("no pv entries: increase vm.pmap.shpgperproc");

This panic string exists in the alpha, amd64, i386, and ia64 versions of
pmap.c.  It does not exist in the arm version.

`sysctl -a | grep pmap` does not list any sysctls.

The usual answer to this is to rebuild a kernel with PMAP_SHPGPERPROC
set to a higher value.

Not sure why the sysctl isn't available.
>How-To-Repeat:
Not sure how to reliably create the panic situation, but I don't believe that's the real issue.  grepping the sysctl and the source should provide the rest of the information.
>Fix:
My preference would be to actually make the value tunable via sysctl,
but I have no idea how difficult that would be.

If it can no be made available via sysctl, the message should probably
be changed to recommend rebuilding the kernel, as is done in
sys/vm/vm_pageout.c
>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200701191548.l0JFmal4087933>