Date: Fri, 19 Jun 2009 21:21:20 +0100 From: Bruce Cran <bruce@cran.org.uk> To: Glen Barber <glen.j.barber@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Processes dying with signal 11 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090619212120.531af76a>