From owner-cvs-all Sun Aug 13 14:26:43 2000 Delivered-To: cvs-all@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 38A8237B790; Sun, 13 Aug 2000 14:26:26 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13O5Gw-000Bh9-00; Sun, 13 Aug 2000 21:26:22 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id XAA00931; Sun, 13 Aug 2000 23:26:20 +0200 (CEST) (envelope-from wkb) Date: Sun, 13 Aug 2000 23:26:20 +0200 From: Wilko Bulte To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: John Hay , Peter Wemm , cvs-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/release/scripts dokern.sh Message-ID: <20000813232620.A907@freebie.demon.nl> References: <200007290922.e6T9Mqc78590@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from groudier@club-internet.fr on Sun, Aug 13, 2000 at 07:45:30PM +0200 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by freebie.demon.nl id XAA00931 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 13, 2000 at 07:45:30PM +0200, G=E9rard Roudier wrote: >=20 > On Sat, 29 Jul 2000, John Hay wrote: >=20 > > > > * Remove the `ncr' driver in the Alpha case -- the `sym' driver= works with > > > > every known Alpha. > > >=20 > > > I think it is time to switch -current to sym-only. No disrespect t= owards the > > > ncr driver writer intended, but the sym driver is well maintained, = robust, > > > up-to-date, not implicated in the recurring fxp+ncr bugs, and suppo= rts all > > > the hardware. > >=20 > > It does not support all hardware yet. I have an old 810 card that don= 't > > even want to boot using the sym driver. It just go into a loop of pri= nting > > errors at the stage where it should probe the disks. The same machine > > works just fine with the ncr driver. >=20 > The PCI status reported by the device indicates a PCI parity error.=20 >=20 > > sym0: PCI STATUS =3D 0x8100 > ^bit 0x8000 -> Signaled PCI parity error. >=20 > On the other hand, the chip reported a MASTER DATA PARITY ERROR detecte= d. >=20 > > sym0:0: ERROR (c0:0) (8-0-0) (0/3) @ (scripta 170:720d0000). > ^DSTAT bit 0x40 -> Master Data Parity Error. >=20 > It means that the NCR device detected such an error when acting as a > master, either in some data it tried to read, or the error has been > signaled by the PCI target while the NCR was writing data to that PCI > target. >=20 > So, it is not the driver that failed, but the PCI hardware, given that = PCI > parity checking is mandatory for PCI-SCSI controllers as we know. Be careful. While this is true, there are combinations of Alpha hardware with specific PCI exp cards where DEC/CPQ recommends/insists on disabling PCI parity checking via the SRM console. I don't remember ever having seen this requirement for the ncr/sym 810s though YMMV.. --=20 Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message