From owner-freebsd-hackers  Tue Oct 17 10:43:40 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id KAA01509
          for hackers-outgoing; Tue, 17 Oct 1995 10:43:40 -0700
Received: from peter.cs.andrews.edu (root@peter.cs.andrews.edu [143.207.1.4])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id KAA01502
          for <freebsd-hackers@freebsd.org>; Tue, 17 Oct 1995 10:43:37 -0700
Received: from edmund (edmund.cs.andrews.edu) by peter.cs.andrews.edu (5.x/SMI-SVR4)
	id AA02540; Tue, 17 Oct 1995 13:43:31 -0400
From: gillham@andrews.edu (Andrew Gillham)
Received: by edmund (5.x) id AA14344; Tue, 17 Oct 1995 13:43:31 -0400
Message-Id: <9510171743.AA14344@edmund>
Subject: Re: Stability questions...
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Tue, 17 Oct 1995 13:43:30 -0400 (EDT)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <27826.813944006@time.cdrom.com> from "Jordan K. Hubbard" at Oct 17, 95 08:33:26 am
X-Mailer: ELM [version 2.4 PL24]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
Precedence: bulk

> > by signal 11" or similar when I am trying to compile a kernel.
> > Restarting make will eventually get it all built though.  Is this a
> > known problem with 2.0.5-RELEASE, or is my hardware flakey?
> 
> This has been a sign of hardware flakeyness or misconfiguration
> in every instance I've ever seen, that's all I can really say.
> 
> 					Jordan

So... What do you suggest?  Disabling the hardware cache?
Why would the 2.2-CURRENT and NetBSD kernels not have the problem?
I'm fairly sure that 2.2-CURRENT (as of saturday) _doesn't_ have
the SEGV problem, just the biodone problem.
I am willing to accept that it is my ASUS if nobody else has seen the
problem.  I will try it after disabling my cache, etc. (i.e. load BIOS
default)

-Andrew