From owner-freebsd-questions Thu Jun 22 14:27:22 2000 Delivered-To: freebsd-questions@freebsd.org Received: from vulcan.amcom.net (ns2.101freeway.net [207.13.211.9]) by hub.freebsd.org (Postfix) with ESMTP id CC00637BE81 for ; Thu, 22 Jun 2000 14:27:18 -0700 (PDT) (envelope-from maxwell@101freeway.com) Received: from 101freeway.com (cobar.101freeway.com [207.13.211.6]) by vulcan.amcom.net (Post.Office MTA v3.5.3 release 223 ID# 0-61056U1000L100S0V35) with ESMTP id net for ; Thu, 22 Jun 2000 14:29:43 -0700 Message-ID: <39528616.9E26B168@101freeway.com> Date: Thu, 22 Jun 2000 14:33:10 -0700 From: Hampton Maxwell X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: multiple core dumps & crash Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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