From owner-freebsd-questions  Wed Aug 16 18:30:15 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id SAA09040
          for questions-outgoing; Wed, 16 Aug 1995 18:30:15 -0700
Received: from easy4.easynet.com ([199.2.26.4])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id SAA09034
          for <questions@FreeBSD.org>; Wed, 16 Aug 1995 18:30:13 -0700
Received: (from brian@localhost) by easy4.easynet.com (8.6.11/8.6.9) id BAA05851; Thu, 17 Aug 1995 01:30:47 GMT
From: Brian Litzinger <brian@mediacity.com>
Message-Id: <199508170130.BAA05851@easy4.easynet.com>
Subject: Re: P5/2940W panics system
To: Jeremy@cfs.purdue.edu
Date: Thu, 17 Aug 1995 01:30:47 +0000 ()
Cc: questions@FreeBSD.org
In-Reply-To: <9F9A220B3A@cfs.purdue.edu> from "W. Jeremy Nauck" at Aug 16, 95 02:32:33 pm
X-Mailer: ELM [version 2.4 PL24 ME7a]
Content-Type: text
Content-Length: 638       
Sender: questions-owner@FreeBSD.org
Precedence: bulk

> During the initial boot from floppy before installation (2.0 and 
> 2.0.5) everything begins to boot alright, but immediately after the 
> phase the system panics with RAM parity error.  Probable hardware 
> problem.  I isolated the error to our Adaptec AHA-2940W SCSI card  
> (PCI) by removing it and booting with only a 1.44 3.5" floppy 
> installed.
> 	-Jeremy

I found a similar problem with a board using the adaptec 7850 single
chip SCSI. (I believe the 2940W uses 7870 technology) 

Turning off the motherboard memory parity checking cured
the problem, though I later ran into other problems.

Brian Litzinger
brian@easynet.com