From owner-freebsd-questions Tue Sep 5 13:38:43 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mx6.screaming.net (mx6.screaming.net [212.49.224.21]) by hub.freebsd.org (Postfix) with ESMTP id 109DA37B423 for ; Tue, 5 Sep 2000 13:38:40 -0700 (PDT) Received: from merlin.onsea.com (dyn64-ras50.screaming.net [212.188.145.64]) by mx6.screaming.net (8.9.3/8.9.3) with ESMTP id VAA09039 for ; Tue, 5 Sep 2000 21:35:29 +0100 (BST) Received: from localhost (dozprompt@localhost) by merlin.onsea.com (8.9.3/8.9.3) with ESMTP id VAA87139 for ; Tue, 5 Sep 2000 21:41:09 +0100 (BST) (envelope-from dozprompt@onsea.com) X-Authentication-Warning: merlin.onsea.com: dozprompt owned process doing -bs Date: Tue, 5 Sep 2000 21:41:09 +0100 (BST) From: Cliff Rowley To: freebsd-questions@freebsd.org Subject: PMAP Question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I have scoured the -hackers and -questions mailing list archives for answers, and among a fair amount of messages directing questions back to the archives I've only found a few little tidbits of information. Basically I am trying to debug a FreeBSD 4.1-STABLE server that is acting very ill. It was occasionally hanging shortly after complaining: pmap_collect: collecting pv entries -- suggest increasing PMAP_SHPGPERPROG Feeling a little bit sheepish, I took on board what I'd read from the archives, and doubled the default value of 200 to 400, and although the machine has not yet frozen, the messages still appear periodically. Instead getting myself into the spiral of increasing it until it breaks, I would like to know exactly what I am doing. I've looked around for information on what 'PMAP' is, but I'm not finding much at all. If someone could point me in the right direction I would be most grateful. I would rather spend time reading and learning about the problem and make an accurate assumption as to a solution, than to wildly guess and risk breaking something else. The main problem is that Apache is regularly crawling up it's own backside. I've managed to cure that once by increasing kern.maxfiles, but that was a different problem that has now gone away. Thanks in advance. Cliff Rowley The reader this message encounters not failing to understand is cursed. - while (!asleep) { code(); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message