From owner-freebsd-stable Thu Mar 22 14:58:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from swan.au.en-bio.com (swan.en-bio.COM.AU [203.35.254.3]) by hub.freebsd.org (Postfix) with ESMTP id 74E9037B71D for ; Thu, 22 Mar 2001 14:58:28 -0800 (PST) (envelope-from TMaher@entigen.com) Received: from shad.au.int.en-bio.com (www-cache.au.en-bio.com [203.35.254.2]) by swan.au.en-bio.com (8.9.1a/8.9.1) with ESMTP id JAA00751; Fri, 23 Mar 2001 09:58:26 +1100 Received: (from tonym@localhost) by shad.au.int.en-bio.com (8.9.1b+Sun/8.9.1) id JAA05645; Fri, 23 Mar 2001 09:57:55 +1100 (EST) Date: Fri, 23 Mar 2001 09:57:55 +1100 (EST) From: Tony Maher Message-Id: <200103222257.JAA05645@shad.au.int.en-bio.com> To: cshishid@slip.net, gibbs@scsiguy.com Cc: stable@FreeBSD.ORG Subject: Re: Adaptec 19160 and Data Parity Errors Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Nothing was committed that would affect reported PCI parity errors. > It may be that your chipset just doesn't generate parity correctly. > It may also be that the card edge is dirty or the slot is. Hard > to say. The parity error reporting can be disabled if necessary. > I'll look into adding a device flag for that in the near future. Ok. I dont think its the card since its brand new and works ok in the other box. I'll try cleaning the slots and addtionally installing an older 2940 board (have to retrieve it from another box at home so it will take a couple of days). BTW I believe the motherboard uses VIA chipset (and its obviously old version) thank you tonym To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message