From owner-freebsd-stable  Sat Sep 23  9:37:52 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from hawk.prod.itd.earthlink.net (hawk.prod.itd.earthlink.net [207.217.120.22])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8EAB837B424; Sat, 23 Sep 2000 09:37:50 -0700 (PDT)
Received: from veager.siteplus.net (1Cust192.tnt10.chattanooga.tn.da.uu.net [63.22.145.192])
	by hawk.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id JAA28845;
	Sat, 23 Sep 2000 09:37:34 -0700 (PDT)
Date: Sat, 23 Sep 2000 12:37:32 -0400 (EDT)
From: Jim Weeks <jim@siteplus.net>
To: Brad Knowles <blk@skynet.be>
Cc: Kai Voigt <k@123.org>, Kris Kennaway <kris@FreeBSD.ORG>,
	freebsd-stable@FreeBSD.ORG
Subject: Re: 4.1-STABLE, make world problems, funny case
In-Reply-To: <v0422080bb5f230dfb505@[10.0.1.2]>
Message-ID: <Pine.BSF.4.21.0009231227460.470-100000@veager.siteplus.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Sat, 23 Sep 2000, Brad Knowles wrote:
 
> 	Note that ECC RAM usually helps in this case, but it is possible 
> for there to be so many errors that even ECC can't save you.

An interesting observation.  

I have a couple of machines running ECC chips that produce this
error on occasion.

(httpd), uid 65534: exited on signal 11

No other process has ever exited on signal 11.  I realize that signal 11
is usually memory related but make build/installworlds never fail, at
least for this reason.

--
Jim 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message