search for: pmap_shpgperproc

Hello List, I know FreeBSD 4.x is old..., but we are using on a production system with postgres and apache. The above message is appearing periodically. I googled for the message but found no recommendation for adjusting it. Any suggestions. Thanks, Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin)

Hi! I've got FreeBSD 8.3-STABLE/i386 server that can be reliably panicked using just 'squid -k rotatelog' command. It seems the system suffers from the problem described here: http://cxsecurity.com/issue/WLB-2010090156 I could not find any FreeBSD Security Advisory containing a fix. My server has 4G physical RAM (about 3.2G available) and runs squid (about 110M VSS) with 500

...(1.3.27) that's causing the problem, or am I wrong? I also believe it is not a load issue as the load does not get much about 2 most of the time. The only special kernel config is that it's an SMP kernel and the following options are set: options NMBCLUSTERS=20000 options PMAP_SHPGPERPROC=600 options IPFIREWALL options DUMMYNET Below is a copy of the panic message I got from a serial console and below that is a dmesg from today. Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 fault virtual address = 0x13 fault cod...