From owner-freebsd-hackers  Fri Jan 26 18:11:25 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA14042
          for hackers-outgoing; Fri, 26 Jan 1996 18:11:25 -0800 (PST)
Received: from emout04.mail.aol.com (emout04.mail.aol.com [198.81.10.12])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA14037
          for <hackers@freebsd.org>; Fri, 26 Jan 1996 18:11:21 -0800 (PST)
From: StevenR362@aol.com
Received: by emout04.mail.aol.com (8.6.12/8.6.12) id VAA01120; Fri, 26 Jan 1996 21:09:59 -0500
Date: Fri, 26 Jan 1996 21:09:59 -0500
Message-ID: <960126210958_207569891@emout04.mail.aol.com>
To: rminnich@sarnoff.com, joe@implode.root.com
cc: hackers@freebsd.org, scrappy@ki.net
Subject: Re: Program getting signal 11 for no obvious reason
Sender: owner-hackers@freebsd.org
Precedence: bulk

In a message dated 96-01-26 09:06:15 EST, rminnich@Sarnoff.COM (Ron G.
Minnich) writes:

>when you add new ram, after a while to me reads as 'to when i fell over 
>into the new bank of ram'. signal 11? any chance you have a ram error and 
>are not running parity ram? this happened here. The symptoms are not 
>obvious ...
>
>ron

   I'd have to agree with this.  When I added an additional 2 Mb 80ns Ram to
a system with 8 MB of 70ns Ram,  I would get sig 11's whenever I did a make
world.  I added an extra wait state and the sig 11's disappeared.  Of course
my
system ran slower but it had more Ram.  I'm not sure if this is a good
tradeoff 
though.

Steve