From owner-freebsd-stable Mon Jun 10 10:33:50 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx0.inoc.net (mx0.inoc.net [64.246.130.30]) by hub.freebsd.org (Postfix) with ESMTP id 30D7337B400 for ; Mon, 10 Jun 2002 10:33:45 -0700 (PDT) Received: from nimbus (unverified [10.0.0.111]) by mx0.inoc.net (Vircom SMTPRS 5.2.204) with ESMTP id ; Mon, 10 Jun 2002 13:33:35 -0400 From: "Robert Blayzor" To: "'Matthew Dillon'" Cc: "'Valery G. Utkin'" , Subject: RE: RE: FW: RE: Swap_pager error Date: Mon, 10 Jun 2002 13:33:34 -0400 Organization: INOC, LLC Message-ID: <000b01c210a4$f2a18db0$6f00000a@z0.inoc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <200206101725.g5AHPLTa009107@apollo.backplane.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Robert, if you haven't already I would recommend that you > re-enable all > your cron stuff, *except* for the ipfw and ip6fw related > elements, and > see if your boxes remain stable. > > If they do, try reenabling ipfw but leaving ip6fw > disabled. If the > continue to work, try reenabling ip6fw (to be sure that is causing > the crash). > > It is beginning to sound like either ipfw or ip6fw is > either causing > corruption in the kernel or is causing something (in > kernel or userland > running as root) to exhaust physical memory and lock the > machine up. Ok, well if this one makes *ANY* sense; the only box we see doing this is the only FreeBSD mutli-CPU box we have. We have several other single processor boxes that have never crashed, although they are a lot less busy. I remember we thought that this could have been a hard drive controller, however, we have several other boxes that run /etc/security just fine every night with the same hard drive controller. (PERC3). We also thought maybe it was bad memory, but we did extensive testing, and never found a problem. -- Robert Blayzor, BOFH INOC, LLC rblayzor@inoc.net Logic: The art of being wrong with confidence... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message