From owner-freebsd-current  Wed Jan  7 19:24:07 1998
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id TAA18222
          for current-outgoing; Wed, 7 Jan 1998 19:24:07 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA18137
          for <current@FreeBSD.org>; Wed, 7 Jan 1998 19:23:55 -0800 (PST)
          (envelope-from gibbs@narnia.plutotech.com)
Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id UAA11189; Wed, 7 Jan 1998 20:21:30 -0700 (MST)
Date: Wed, 7 Jan 1998 20:21:30 -0700 (MST)
From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>
Message-Id: <199801080321.UAA11189@narnia.plutotech.com>
To: dk+@ua.net
Subject: Re: RAM parity error
Newsgroups: pluto.freebsd.current
In-Reply-To: <199801060852.AAA04597@dog.farm.org>
cc: current@FreeBSD.org
User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386))
Sender: owner-freebsd-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <199801060852.AAA04597@dog.farm.org> you wrote:
> In article <199712310100.RAA03280@vader.cs.berkeley.edu> you wrote:
>> I have been seeing a "RAM parity error" in one of our machines lately.

...

This is caused by an errata in the P6 having to do with PIO.  The
aic7xxx driver does a lot of PIO unless you tell it to use memory
mapped register access instead.

Try the AHC_ALLOW_MEMIO option in your kernel.

I also thought there was some discussion in the current or hackers
list a while back about putting some code in our trap handlers to
work around this problem.

-- 
Justin T. Gibbs
===========================================
  FreeBSD - Turning PCs into workstations
===========================================