Date: Mon, 10 Jun 2002 13:33:34 -0400 From: "Robert Blayzor" <rblayzor@inoc.net> To: "'Matthew Dillon'" <dillon@apollo.backplane.com> Cc: "'Valery G. Utkin'" <uvg@niiefa.spb.su>, <freebsd-stable@FreeBSD.ORG> Subject: RE: RE: FW: RE: Swap_pager error Message-ID: <000b01c210a4$f2a18db0$6f00000a@z0.inoc.net> In-Reply-To: <200206101725.g5AHPLTa009107@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000b01c210a4$f2a18db0$6f00000a>