From owner-freebsd-hardware  Fri Feb 21 20:27:54 1997
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA19411
          for hardware-outgoing; Fri, 21 Feb 1997 20:27:54 -0800 (PST)
Received: from scruz.net (nic.scruz.net [165.227.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA19403
          for <hardware@freebsd.org>; Fri, 21 Feb 1997 20:27:52 -0800 (PST)
Received: (from speth@localhost)
	by scruz.net (8.7.3/1.34) id UAA14952; Fri, 21 Feb 1997 20:27:49 -0800 (PST)
Message-Id: <199702220427.UAA14952@scruz.net>
From: speth@scruz.net (James G. Speth)
Date: Fri, 21 Feb 1997 20:27:47 -0800
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: hardware@freebsd.org
Subject: problem with 2.1.7-RELEASE #0
Cc: speth@nic.scruz.net, matthew@nic.scruz.net
Sender: owner-hardware@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I installed FreeBSD release 2.1.7 yesterday, and I've been dealing with some
very strange errors since then.

I'm using a Peak 510S single board computer with an on-board Adaptek AIC7880
ultra-wide SCSI controller (BIOS 1.22S2B), and a Quantum VP32170W drive.

The first indication of a problem was during the boot sequence.  When I have
the SCSI controller set for "Initiate Wide Negotiation: On", I get a parity
error during the boot probe.  When I try disabling parity checking I get some
serious data errors during the probe (e.g. "Quaftum"), and a panic when
labelling the disk.

So, I turned off wide negotiation, and turned on parity checking.  This allows
me to boot from the floppy and do a normal install with no problems.  After
the install is complete things get really weird.  When I attempt to compile
some software that compiles cleanly under an identical system running
FreeBSD 2.1.0-RELEASE #4, I get sporadic internal compiler errors.  Every
now and then it will compile cleanly with no errors, but the rest of the
time it gives me errors like these:

cc -g -c billing.c
assertion "fragP->fr_offset >= 0" failed: file "/usr/src/gnu/usr.bin/as/write.c"
, line 529
cc: Internal compiler error: program as got fatal signal 6
*** Error code 1

cc -g -c billing.c
cc: Internal compiler error: program cc1 got fatal signal 11
*** Error code 1

cc -g -c utils.c
/var/tmp/cc000363.s: Assembler messages:
/var/tmp/cc000363.s:6893: Fatal error:Case value 23199812 unexpected at line 380
 of file "/usr/src/gnu/usr.bin/as/write.c"

cc -g -c billing.c
billing.c: In function `undo':
billing.c:3880: internal error--unrecognizable insn:
(jump_insn 155 153 156 (set (pc)
        (UnKnown Unknown)) -1 (nil)
    (nil))
cc: Internal compiler error: program cc1 got fatal signal 6
*** Error code 1

It is very inconsistent, giving different error messages on different
attempts, and sometimes giving no error at all.  That is what makes me think
it is related to the earlier disk problems, or perhaps something in the
caching code.

Have you seen problems like this, or heard any other reports of problems with
this release?  Any help you can give me would be appreciated.

Thanks.

--
Jim Speth
scruz-net engineering