From owner-freebsd-current@FreeBSD.ORG Wed Sep 3 10:41:08 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B97D16A4BF for ; Wed, 3 Sep 2003 10:41:08 -0700 (PDT) Received: from hotmail.com (law10-oe21.law10.hotmail.com [64.4.14.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B1A14400B for ; Wed, 3 Sep 2003 10:41:07 -0700 (PDT) (envelope-from segr@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 3 Sep 2003 10:41:07 -0700 Received: from 205.206.101.61 by law10-oe21.law10.hotmail.com with DAV; Wed, 03 Sep 2003 17:41:07 +0000 X-Originating-IP: [205.206.101.61] X-Originating-Email: [segr@hotmail.com] From: "Stephane Raimbault" To: "Bosko Milekic" , Date: Wed, 3 Sep 2003 11:43:44 -0600 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: X-OriginalArrivalTime: 03 Sep 2003 17:41:07.0342 (UTC) FILETIME=[8E116AE0:01C37242] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Re: FreeBSD 5.1-R kernel panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2003 17:41:08 -0000 Hi Bosko, Well a couple weeks ago I re-cvsup'd to current since I had missed one = of your updates it would seem by a day. I still had the panic occur... = so I did as suggested and upped my KVA. I did the following: In the kernel options KVA_PAGES=3D400 options NMBCLUSTERS=3D8192 In the loader.conf kern.vm.kmem.size=3D"400000000" This seems to have helped, since I am no longer panic'ng. I have = identified a php script that slowly builds to 100% cpu usage in a couple = days which we believe was a culprit in our problems. The guys who made = the php script that runs on this box is having a close look at it to = figure out why it's behaving this way... however I did have some = questions. 1. Should the panic occur in the first place? 2. Is there a way to monitor how much kva is currently being used so = that I can monitor this value so I can have something alert me if I'm = running out of this memory... I'm sure we would of caught this months = ago if I was monitoring for this? Thanks again for everything you have done to assist me thru this = problem. Stephane Raimbault. bmilekic@technokratis.com (Bosko Milekic) wrote in message = news:... > On Thu, Aug 14, 2003 at 10:57:07AM -0600, Stephane Raimbault wrote: > > Hi Bosko, > >=20 > > This is the output of sysctl vm.zone about 2 minutes before the = crash > > occured. let me know if there is anything else I can provide you = for this > > crashing problem. >=20 > Hmmmm. I don't know, maybe you really do have a machine too loaded > for the KVA you have configured... >=20 > I have to re-iterate that it's extremely important that you > double-check that you are in fact in sync with the latest -current = and > _NOT_ RELENG_5_1. Make sure you're building at least version 1.73 = of > src/sys/vm/uma_core.c (grep FBSDID src/sys/vm/uma_core.c). >=20 > With that said, you can try the following: >=20 > options KVA_PAGES=3D400 >=20 > in your kernel configuration file. >=20 > Following that, you can do this: >=20 > kern.vm.kmem.size=3D400000000 >=20 > In your /boot/loader.conf >=20 > Make sure to not set NMBCLUSTERS too high. Around 8K is probably = more > than enough, but you should look at how much you're using on average > with `netstat -m' and then set the number to roughly 3 times that. >=20 > If following this your crash persists, even if after a longer time, > then I would suspect (another?) race. Again, I have to re-iterate > that you really need to make sure you're supping to HEAD: >=20 > *default release=3Dcvs tag=3D. >=20 > Regards,