From owner-freebsd-questions  Thu Dec 19 19:42:55 1996
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id TAA03384
          for questions-outgoing; Thu, 19 Dec 1996 19:42:55 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA03376
          for <questions@FreeBSD.ORG>; Thu, 19 Dec 1996 19:42:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id TAA16970; Thu, 19 Dec 1996 19:42:05 -0800 (PST)
Message-Id: <199612200342.TAA16970@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: "Brian J. McGovern" <mcgovern@spoon.beta.com>
cc: questions@FreeBSD.ORG, support@cyclades.com
Subject: Re: PCI 16 port Cyclades w/2.2-ALPHA (FreeBSD) 
In-reply-to: Your message of "Thu, 19 Dec 1996 17:11:57 EST."
             <199612192211.RAA00625@spoon.beta.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Thu, 19 Dec 1996 19:42:05 -0800
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>I recently just returned my 32 port ISA Cyclades cards in favor of PCI
>Cyclades 32 port cards. Unfortunately, I can't seem to get them to be
>properly recognized (the machine sees a card, but then gets a parity
>error, and the kernel panics & freezes).
>
>Could someone send me their (working?) kernel config file for these
>cards for FreeBSD 2.2-ALPHA, so I can make sure its just not something stupid
>that I'm doing...
>
>Also, if there is any special procedure thats recommended for setting these
>cards up (ie - using CYTEST or the like), please fill me in on that. The
>FreeBSD handbook seems minimal on the subject. The manpage is great
>for the ISA, but makes no reference to the PCI version, and the Cyclades
>documentation says "see the FreeBSD documentation".

   Is this in a PPro machine? The folks at U of Utah are having a similar
problem. Accessing the shared memory on ports on the second set of 16 ports
sometimes generates a PCI parity error. The problem doesn't happen for them
(or for me) on P5 systems, although there was one report from someone of this
happening about once a day under heavy use on a P5 system. It appears to be
some sort of hardware/timing problem related to the Cyclades PCI interface.
If you haven't already, you might try using cytest.exe to change the card
to be mapped in high memory rather than 640K-1M and see if this makes any
difference.

-DG

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