From owner-freebsd-hackers  Thu Jul 10 10:36:24 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA13862
          for hackers-outgoing; Thu, 10 Jul 1997 10:36:24 -0700 (PDT)
Received: from server.local.sunyit.edu (A-V25.rh.sunyit.edu [150.156.211.85])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA13852
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 10 Jul 1997 10:36:18 -0700 (PDT)
Received: from localhost (brightmn@localhost)
	by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id NAA26187;
	Sun, 22 Jun 1997 13:44:54 GMT
Date: Sun, 22 Jun 1997 13:44:54 +0000 (GMT)
From: BRiGHTMN <brightmn@a-v25.rh.sunyit.edu>
To: Robert Shady <rls@mail.id.net>
cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Sig 11 errors...
In-Reply-To: <199707101632.MAA16653@shell.id.net>
Message-ID: <Pine.BSF.3.95q.970622134347.26178B-100000@server.local.sunyit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Sorry to bring this up again, but I've been having a hell of a time with
> my Win95 machine crashing all the time, getting corrupted data, etc.
> 
> Just by coincendance, I happen to install FreeBSD 2.2.2 on it to test
> something else out, and noticed I was getting a large number of 
> core dumped - exit signal 11 messages.. I remember sometime back
> Jordan saying something about these possibly being related to having
> external cache memory installed on the motherboard... Have we narrowed
> this down to be the cause?  What is the effects of running a P200
> with 128MB RAM w/o a COAST module?

i was getting these problems until i told my bios to put a wait state for
the ram, but i P200 shouldn't need that... or it could :)

try some other ram.