From owner-freebsd-questions@FreeBSD.ORG Fri Oct 31 13:22:19 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F76216A4CE for ; Fri, 31 Oct 2003 13:22:19 -0800 (PST) Received: from ns1.valuedj.com (adsl-216-100-130-21.dsl.snfc21.pacbell.net [216.100.130.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9476B43F3F for ; Fri, 31 Oct 2003 13:22:18 -0800 (PST) (envelope-from whizkid@ValueDJ.com) Received: by ns1.valuedj.com (Postfix, from userid 80) id 2C389611A; Fri, 31 Oct 2003 13:22:03 -0800 (PST) Received: from 208.253.246.93 (proxying for unknown) (SquirrelMail authenticated user whizkid) by ns1.valuedj.com with HTTP; Fri, 31 Oct 2003 13:22:03 -0800 (PST) Message-ID: <58233.208.253.246.93.1067635323.squirrel@ns1.valuedj.com> In-Reply-To: <4087260000.1067634243@aslan.btc.adaptec.com> References: <30572.208.253.246.93.1067628638.squirrel@ns1.valuedj.com> <4087260000.1067634243@aslan.btc.adaptec.com> Date: Fri, 31 Oct 2003 13:22:03 -0800 (PST) From: whizkid@ValueDJ.com To: "Justin T. Gibbs" User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal cc: freebsd-questions@freebsd.org Subject: Re: Adaptec 29160N errors X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2003 21:22:19 -0000 > The controller is complaining that some device in your system is > generating > PCI transactions that cannot be safely decoded because they contain parity > errors. Just moving the 160 card won't make this situation go away. You > need to find the source of these errors. Otherwise, you might as well > live with the message in your dmesg log and go on with life. > At the time of the errors there was and still is only 1 device on the controller. I have tried 2 different devices 1 internal 1 external as well as a handful of different cables. > Again, this has nothing to do with the SCSI controller, the devices > attached to it, or anything SCSI specific. Some other PCI device is > causing the problem. > the only other PCI device in the machine is the NIC. > > The BIOS for this card may be configuring it to ignore PCI parity > errors. > That was my guess as well. The 29160N has parity set to Auto, the AHA-2940 has no such option. But I have read about this issue and the 29160N cards with any NIX system, or some BSD system. Most of the issues were resolved by moving the card from one PCI slot to another. My MAIN concern is that the card controlls my Tape Backup Drive sa0... The last thing I want to have happen is all my data on the tapes be corrupt and/or un-Readable due to the parity errors