/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
)
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
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/MYKNL
Panic String: no pv entries: increase
)
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
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/MYKNL
Panic String: no pv entries: increase vm.pmap.shpgperproc
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
Hostname: myhost.mydomain.com
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 6.0-RELEASE #0: Tue Apr 25 15:07:33 CST 2006
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/MYKNL
Panic String: no pv entries: increase vm.pmap.shpgperproc
Dump Parity: 2383301964
Bounds: 49
Dump Status: good