From owner-freebsd-questions Thu Jun 22 15:30:40 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.alpha.net.au (mail2.alpha.net.au [203.41.44.8]) by hub.freebsd.org (Postfix) with ESMTP id 7ECD637BD7F for ; Thu, 22 Jun 2000 15:30:36 -0700 (PDT) (envelope-from dannyh@idx.com.au) Received: from dannyh.freebsd.org (surry-pool-164.alpha.net.au [203.41.44.164] (may be forged)) by mail.alpha.net.au (8.9.3/8.9.3) with SMTP id IAA14496; Fri, 23 Jun 2000 08:32:01 +1000 From: Danny To: Hampton Maxwell , freebsd-questions@FreeBSD.ORG Subject: Re: multiple core dumps & crash Date: Sat, 24 Jun 2000 08:38:46 +1000 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain References: <39528616.9E26B168@101freeway.com> MIME-Version: 1.0 Message-Id: <00062408393905.00297@dannyh.freebsd.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG - Try swapping something like your RAM On Fri, 23 Jun 2000, Hampton Maxwell wrote: > 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) > > I killall'ed head and a runaway copy of perl and the machine went > down. The machine went back up after an fsck, but almost immediately > after going from single to multi-user all the processes on the box > begin core dumping, including repeatedly killing getty. After about a > minute the machine panics on some sort of mem_swp error (didn't get > the whole error). > 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. > > Thanks, > Hampton Maxwell > -- > Network Administration - 101freeway.com > maxwell@101freeway.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message