From owner-freebsd-questions@FreeBSD.ORG  Fri Jun 19 20:21:25 2009
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2C52B1065675
	for <freebsd-questions@freebsd.org>;
	Fri, 19 Jun 2009 20:21:25 +0000 (UTC)
	(envelope-from bruce@cran.org.uk)
Received: from muon.cran.org.uk (brucec-1-pt.tunnel.tserv4.nyc4.ipv6.he.net
	[IPv6:2001:470:1f06:c09::2])
	by mx1.freebsd.org (Postfix) with ESMTP id DBD008FC12
	for <freebsd-questions@freebsd.org>;
	Fri, 19 Jun 2009 20:21:24 +0000 (UTC)
	(envelope-from bruce@cran.org.uk)
Received: from muon.cran.org.uk (localhost [127.0.0.1])
	by muon.cran.org.uk (Postfix) with ESMTP id E54F51900F;
	Fri, 19 Jun 2009 20:21:23 +0000 (GMT)
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on muon
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00,NO_RELAYS
	autolearn=ham version=3.2.5
Received: from gluon.draftnet (unknown
	[IPv6:2a01:348:10f:0:240:f4ff:fe57:9871])
	(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	by muon.cran.org.uk (Postfix) with ESMTPSA;
	Fri, 19 Jun 2009 20:21:23 +0000 (GMT)
Date: Fri, 19 Jun 2009 21:21:20 +0100
From: Bruce Cran <bruce@cran.org.uk>
To: Glen Barber <glen.j.barber@gmail.com>
Message-ID: <20090619212120.531af76a@gluon.draftnet>
In-Reply-To: <4ad871310906191235p3cb3b3c0h1ad61e3904e209b9@mail.gmail.com>
References: <20090619175537.36128909@gluon.draftnet>
	<alpine.BSF.2.00.0906192103360.74610@wojtek.tensor.gdynia.pl>
	<20090619201419.27fcec9b@gluon.draftnet>
	<4ad871310906191221q2aadc509sfbc41eb6e8db00e8@mail.gmail.com>
	<4ad871310906191235p3cb3b3c0h1ad61e3904e209b9@mail.gmail.com>
X-Mailer: Claws Mail 3.7.1 (GTK+ 2.16.2; i386-portbld-freebsd7.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-questions@freebsd.org
Subject: Re: Processes dying with signal 11
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jun 2009 20:21:25 -0000

On Fri, 19 Jun 2009 15:35:09 -0400
Glen Barber <glen.j.barber@gmail.com> wrote:

> On Fri, Jun 19, 2009 at 3:21 PM, Glen Barber<glen.j.barber@gmail.com>
> wrote:
> > I would suspect hardware. =A0Most probably RAM than anything else
> > initially. =A0Can you run memtest86+?
> >
>=20
> Also, for what it's worth, I had this similar scenario a few years
> ago.  After numerous hardware replacements (RAM, motherboard, etc,
> etc) it turned out to the the CPU that was the problem.
>=20
> It was bad enough that I couldn't even do a 'portsnap fetch' because
> the checksum would be incorrectly calculated.
>=20
>=20

Unfortunately memtest86+ runs on x86 hardware and this is a
PowerPC iBook.  Being Apple hardware there's not much swapping of
hardware I can do - I'll run a few more tests but I guess it's probably
time to chuck it away.

--=20
Bruce