From owner-freebsd-current  Wed Mar 19 22:52:22 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA29346
          for current-outgoing; Wed, 19 Mar 1997 22:52:22 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29339
          for <freebsd-current@FreeBSD.ORG>; Wed, 19 Mar 1997 22:52:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id WAA00973; Wed, 19 Mar 1997 22:53:14 -0800 (PST)
Message-Id: <199703200653.WAA00973@root.com>
X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol
To: Jaye Mathisen <mrcpu@cdsnet.net>
cc: Tom Samplonius <tom@uniserve.com>, freebsd-current@FreeBSD.ORG,
        "Justin T. Gibbs" <gibbs@freefall.freebsd.org>
Subject: Re: ahc problems with 2.2+ 
In-reply-to: Your message of "Wed, 19 Mar 1997 21:53:39 PST."
             <Pine.NEB.3.95.970319215218.29913H-100000@mail.cdsnet.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Wed, 19 Mar 1997 22:53:14 -0800
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>I don't know specifically about your case, but on one motherboard I had,
>turning off the allow_memio fixed my problems completely.  Apparently on
>the 3940, some MB BIOS's don't initialize the PCI bridge correctly.  Or
>ast least, I think that was a simplification of what Justin once told me.
>
>In any case, since I stopped using MEMIO for this particular MB, it's
>worked fine.

   ...and if I _don't_ turn on AHC_ALLOW_MEMIO on wcarchive, the machine
dies regularly with a PCI bus parity error during the PIO instruction. This
seems to happen on some (especially P6) machines.
   With Justin's latest stuff, wcarchive has been quite stable.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project