From owner-freebsd-stable@FreeBSD.ORG Thu Jun 5 01:55:04 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5846437B401 for ; Thu, 5 Jun 2003 01:55:04 -0700 (PDT) Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3787F43FB1 for ; Thu, 5 Jun 2003 01:55:03 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from fishballoon.org ([81.104.195.199]) by mta02-svc.ntlworld.com (InterMail vM.4.01.03.37 201-229-121-137-20020806) with ESMTP id <20030605085501.YBMB9882.mta02-svc.ntlworld.com@fishballoon.org>; Thu, 5 Jun 2003 09:55:01 +0100 Received: from tuatara.fishballoon.org (tuatara [192.168.1.6]) by fishballoon.org (8.12.8p1/8.12.8) with ESMTP id h558sJ4o035552; Thu, 5 Jun 2003 09:54:19 +0100 (BST) (envelope-from scott@tuatara.fishballoon.org) Received: (from scott@localhost) by tuatara.fishballoon.org (8.12.9/8.12.9/Submit) id h558sJMY037214; Thu, 5 Jun 2003 09:54:19 +0100 (BST) (envelope-from scott) Date: Thu, 5 Jun 2003 09:54:19 +0100 From: Scott Mitchell To: Noor Dawod Message-ID: <20030605085419.GA36987@tuatara.fishballoon.org> References: <20030604154549.A68164@ns.museum.rain.com> <000701c32b2f$66de5550$b655fea9@dawodhome> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000701c32b2f$66de5550$b655fea9@dawodhome> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.8-STABLE i386 cc: freebsd-stable@freebsd.org Subject: Re: Sudden and unexplained reboots X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2003 08:55:04 -0000 On Thu, Jun 05, 2003 at 08:55:03AM +0200, Noor Dawod wrote: > Hi again, > > I must say that I believe I forgot to mention four main factors that > might aid in finding the cause of the panic: > > 1) I use ipfw to limit allowed connections to the machine. I > specifically limit connections to (ftpd) all along, which means that for > some weird reason, the kernel panic'ed in (ftpd) while it shouldn't have > been running at all. > > 2) the machine is based on a server motherboard and case, manufactured > by Intel, and its hardware is highly appreciated. I had no problem with > it at all ever. > > 3) Apache is failing to start on few occasions with sudden 'Signal 4' or > 'Signal 11' exit codes. Restarting it would work most of the times. Random sig 11's are a classic sign of dodgy RAM (especially) or other hardware. Take a look at http://www.bitwizard.nl/sig11/ for much more information than you ever wanted... > 4) kernel is built using "-O2 -pipe" make options. > > The above information is the currently used ones. I am building a new > kernel now without the "-O2 -pipe" options, using a newly built world. This is a good idea, but I'd be tempted to install a kernel & world built on another machine if possible, in case some part of your toolchain is damaged. It'll be interesting to see how things work out with the new world. Scott -- =========================================================================== Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" scott at fishballoon.org | 0xAA775B8B | -- Anon