From owner-freebsd-questions@FreeBSD.ORG Fri Oct 10 23:45:59 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 700A6106568C for ; Fri, 10 Oct 2008 23:45:59 +0000 (UTC) (envelope-from pprocacci@datapipe.com) Received: from fmailhost04.isp.att.net (fmailhost04.isp.att.net [207.115.11.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5AD768FC19 for ; Fri, 10 Oct 2008 23:45:59 +0000 (UTC) (envelope-from pprocacci@datapipe.com) Received: from [10.5.21.122] (adsl-157-36-19.bna.bellsouth.net[70.157.36.19]) by isp.att.net (frfwmhc04) with ESMTP id <20081010234558H040098vr2e>; Fri, 10 Oct 2008 23:45:58 +0000 X-Originating-IP: [70.157.36.19] Message-ID: <48EFE927.6000404@datapipe.com> Date: Fri, 10 Oct 2008 18:45:43 -0500 From: "Paul A. Procacci" User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Bob Johnson References: <54db43990810101357o6f6396cfsb4ec48585a1c99b@mail.gmail.com> In-Reply-To: <54db43990810101357o6f6396cfsb4ec48585a1c99b@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: kernel: Approaching the limit on PV entries... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Oct 2008 23:45:59 -0000 Bob Johnson wrote: > A web server with several jailed copies of Apache is having problems > that seem to be caused by incorrect IPFW rules, but in the process of > working on that, I find in the log the following repeated many times: > > Oct 8 23:29:50 spider kernel: Approaching the limit on PV entries, > consider increasing either the vm.pmap.shpgperproc or the > vm.pmap.pv_entry_max sysctl. > Oct 8 23:30:52 spider kernel: Approaching the limit on PV entries, > consider increasing either the vm.pmap.shpgperproc or the > vm.pmap.pv_entry_max sysctl. > > sysctl gives me: > > # sysctl vm.pmap > vm.pmap.pmap_collect_active: 0 > vm.pmap.pmap_collect_inactive: 0 > vm.pmap.pv_entry_spare: 45818 > vm.pmap.pv_entry_allocs: 595716945 > vm.pmap.pv_entry_frees: 595133939 > vm.pmap.pc_chunk_tryfail: 0 > vm.pmap.pc_chunk_frees: 3543052 > vm.pmap.pc_chunk_allocs: 3546795 > vm.pmap.pc_chunk_count: 3743 > vm.pmap.pv_entry_count: 583006 > vm.pmap.shpgperproc: 200 > vm.pmap.pv_entry_max: 2243305 > > The system: > FreeBSD .... 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Wed Oct 1 > 07:51:58 UTC 2008 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > Can someone briefly explain what this is telling me and how to decide > which sysctl to increase? I have found some old postings that predate > the sysctls that suggested increasing shpgperproc in the kernel > configuration, about 50 at a time until the problem goes away, but I > still have no clue what that is accomplishing. > > Also, the system has been rebooted since I collected those messages, > and they aren't happening any more, but I expect they will reappear > eventually. Until then I probably can't actually test anything. > > Thanks for your time, > > -- Bob Johnson > fbsdlists@gmail.com > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > For what it's worth, I just came across a machine with the same exact problem, except when I do finally run out of entries, I get a kernel panic. FBSD 7-RELEASE-p4 ~Paul