Date: Fri, 19 Jan 2007 10:58:32 -0500 From: Bill Moran <wmoran@collaborativefusion.com> To: Bill Moran <wmoran@collaborativefusion.com> Cc: freebsd-questions@freebsd.org, peter <peter@topcomtech.com.cn> Subject: Re: no pv entries: increase vm.pmap.shpgperproc Message-ID: <20070119105832.268e18bd.wmoran@collaborativefusion.com> In-Reply-To: <20070119091339.6a0229f1.wmoran@collaborativefusion.com> References: <003b01c73b71$b1e5a930$560ea8c0@rzcpei> <20070119091339.6a0229f1.wmoran@collaborativefusion.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In response to Bill Moran <wmoran@collaborativefusion.com>: > In response to "peter" <peter@topcomtech.com.cn>: > > Hi, > > My freebsd box runs the apache httpd2.0 server, postgresql8.1server, > > Recently, I got the below info in /var/crash. > > “Dump header from device /dev/da0s1b > > Architecture: i386 > > Architecture Version: 2 > > Dump Length: 1073127424B (1023 MB) > > Blocksize: 512 > > Dumptime: Wed Jan 17 16:39:08 2007 > > Hostname: myhost.mydomain.com > > Magic: FreeBSD Kernel Dump > > Version String: FreeBSD 6.0-RELEASE #0: Tue Apr 25 15:07:33 CST 2006 > > peter@myhost.mydomain.com:/usr/src/sys/i386/compile/MYKNL > > Panic String: no pv entries: increase vm.pmap.shpgperproc > > Dump Parity: 2383301964 > > Bounds: 49 > > Dump Status: good” > > I had searched in google, but I didn’t know how to do. > > You _should_ be able to raise the vm.pmap.shpgperproc sysctl to prevent > the problem -- but there doesn't seem to be any such sysctl. I'm not sure > what's going on here, but it seems to me that a PR is in order. http://www.freebsd.org/cgi/query-pr.cgi?pr=108121 -- Bill Moran Collaborative Fusion Inc.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070119105832.268e18bd.wmoran>