From owner-freebsd-hackers  Wed Feb  5 13:21:39 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA12786
          for hackers-outgoing; Wed, 5 Feb 1997 13:21:39 -0800 (PST)
Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA12776
          for <hackers@freebsd.org>; Wed, 5 Feb 1997 13:21:33 -0800 (PST)
Received: from bmcgover-pc.cisco.com (bmcgover@localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.8.2/8.8.2) with ESMTP id QAA00687; Wed, 5 Feb 1997 16:18:53 -0500 (EST)
Message-Id: <199702052118.QAA00687@bmcgover-pc.cisco.com>
To: dg@root.com, support@cyclades.com
cc: hackers@freebsd.org
Subject: Cyclades Parity error (useful info)
Date: Wed, 05 Feb 1997 16:18:53 -0500
From: Brian McGovern <bmcgover@cisco.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I've installed a handful of printf's to see where the parity error is
being caught. In 2.2-GAMMA, it appears to be in /usr/src/sys/pci/cy_pci.c,
in cy_attach, where it states:

/*
 * Enable the "local" interrupt input to generate a
 * PCI interrupt.
 */

outw(ioport + CY_PLX_ICS, inw(CY_PLX_ICS) | 
	CY_PLX_ICS_IENABLE | CY_PLX_ICS_LOCAL_IENABLE);

Unfortunately, I don't have the docs (and haven't dove in to the code far
enough) to see what this is supposed to do, or what its doing wrong. Perhaps,
IMHO, what its trying to do is generate an interrupt, but what its really
doing is either a.) causing a parity interrupt (wouldn't understand why, tho),
or the interrupt its generating looks to the machine like a parity interrupt.


Let me know if this is helpful, or you'd like me to try something else.
	-Brian