From owner-freebsd-hackers  Tue Oct 17 08:12:30 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id IAA27857
          for hackers-outgoing; Tue, 17 Oct 1995 08:12:30 -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 IAA27852
          for <freebsd-hackers@freebsd.org>; Tue, 17 Oct 1995 08:12:27 -0700
Received: from edmund (edmund.cs.andrews.edu) by peter.cs.andrews.edu (5.x/SMI-SVR4)
	id AA16313; Tue, 17 Oct 1995 11:12:23 -0400
From: gillham@andrews.edu (Andrew Gillham)
Received: by edmund (5.x) id AA24607; Tue, 17 Oct 1995 11:12:22 -0400
Message-Id: <9510171512.AA24607@edmund>
Subject: Stability questions...
To: freebsd-hackers@freebsd.org
Date: Tue, 17 Oct 1995 11:12:21 -0400 (EDT)
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


Apologies if this is the wrong mailing list.

I installed FreeBSD 2.0.5-RELEASE over the weekend, and I have
been having problems with it.  What I am seeing is "cc1 interrupted
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?
My hardware:
	ASUS SP3G w/AMD DX4/100
	32MB
	NCR PCI SCSI
	Micropolis MC2217
	3c509 (not a 'b')
	ATI GUP ISA

I have been running NetBSD on this box without any problems.

Also, I supped freebsd-current onto my NetBSD NFS server, and tried
building it.  I was able to build a kernel and /sbin/* (by restarting
make whenever cc1 got a SEGV), and rebooted with the new kernel.  This
new kernel didn't appear to have the SEGV problem, but I'm not 100%
sure, as something else broke.  After a few minutes of compiling (on the
NFS mount) the kernel says "Biodone: buffer already done" or something
and hangs my compile.  (sorry for the not exact errors, but I'm at
work, and the PCs are at home)  Accessing the NFS mountpoint will hang
my shell, but I can still halt the box from another console.

Any ideas?  Should I be trying to update to 2.1-current instead of
2.2-current? (how would I do that? I just ask for 'current' via sup.)

Thanks for any assistance.

-Andrew