From owner-freebsd-questions Thu Jun 22 14:34: 8 2000 Delivered-To: freebsd-questions@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 9A67C37BA6D for ; Thu, 22 Jun 2000 14:34:04 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id QAA19798; Thu, 22 Jun 2000 16:33:58 -0500 (CDT) (envelope-from dan) Date: Thu, 22 Jun 2000 16:33:58 -0500 From: Dan Nelson To: Hampton Maxwell Cc: freebsd-questions@FreeBSD.ORG Subject: Re: multiple core dumps & crash Message-ID: <20000622163358.B14670@dan.emsphone.com> References: <39528616.9E26B168@101freeway.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.4i In-Reply-To: <39528616.9E26B168@101freeway.com>; from "Hampton Maxwell" on Thu Jun 22 14:33:10 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jun 22), Hampton Maxwell said: > We have a FreeBSD 4.0 Release box running Big Brother and mrtg > monitoring. I went on it last night and noticed a hung process and > checked syslog, finding multiple entries that looked like this: > > Jun 21 23:47:25 gopher /kernel: pid 40433 (head), uid 0: exited on signal 10 (core dumped) > Jun 21 23:52:34 gopher /kernel: pid 42709 (head), uid 0: exited on signal 10 (core dumped) > Jun 21 23:57:42 gopher /kernel: pid 44962 (bbnet), uid 0: exited on signal 11 (core dumped) > Jun 21 23:57:44 gopher /kernel: pid 45428 (grep), uid 0: exited on signal 10 (core dumped) > Jun 21 23:57:45 gopher /kernel: pid 45539 (sh), uid 0: exited on signal 11 (core dumped) > > The machine is a K6-2 450 with 32 megs of ram that had been running > fine for about 11 days prior to the 21st, since it accidentally was > powered off. Prior to that it had been fine for over a month. > Anyone have any idea what sort of hardware problem might be causing > this. I'd rather not pop in a new drive and find out I've got a fried > board or bad ram. Sig10's are usually caused by bad ram or overclocking. Bad disks will usually log errors to the console first. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message