From owner-freebsd-questions@FreeBSD.ORG Fri Oct 31 14:52:47 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 3B32216A4CE for ; Fri, 31 Oct 2003 14:52:47 -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 56D9343FBD for ; Fri, 31 Oct 2003 14:52:46 -0800 (PST) (envelope-from whizkid@ValueDJ.com) Received: by ns1.valuedj.com (Postfix, from userid 80) id 19307611B; Fri, 31 Oct 2003 14:52:30 -0800 (PST) Received: from 67.119.190.158 (SquirrelMail authenticated user whizkid) by ns1.valuedj.com with HTTP; Fri, 31 Oct 2003 14:52:30 -0800 (PST) Message-ID: <1353.67.119.190.158.1067640750.squirrel@ns1.valuedj.com> In-Reply-To: <4113380000.1067636556@aslan.btc.adaptec.com> References: <30572.208.253.246.93.1067628638.squirrel@ns1.valuedj.com> <4087260000.1067634243@aslan.btc.adaptec.com> <58233.208.253.246.93.1067635323.squirrel@ns1.valuedj.com> <4113380000.1067636556@aslan.btc.adaptec.com> Date: Fri, 31 Oct 2003 14:52:30 -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 22:52:47 -0000 here are the errors from the messages log. This ONLY happened when A) a device was connected to the Adaptec 29160N and B) when the device was being used by dump. According the the replies I am afraid the problem may be related to the MB.. And ideas on how to trouble shoot it? For some reason this error no longer occurs with the AHA-2940. Could it be some IRQ conflict? I know that the SCSI controller used IRQ 11, as do alot of the other devices on the system.. ns1 kernel: ahc0: PCI error Interrupt at seqaddr = 0x16b ns1 kernel: ahc0: Data Parity Error Detected during address or write data phase ns1 kernel: ahc0: PCI error Interrupt at seqaddr = 0x16b ns1 kernel: ahc0: Data Parity Error Detected during address or write data phase ns1 kernel: ahc0: PCI error Interrupt at seqaddr = 0x8 ns1 kernel: ahc0: Data Parity Error Detected during address or write data phase ns1 kernel: ahc0: PCI error Interrupt at seqaddr = 0x9 ns1 kernel: ahc0: Data Parity Error Detected during address or write data phase ns1 kernel: ahc0: PCI error Interrupt at seqaddr = 0x82 ns1 kernel: ahc0: Data Parity Error Detected during address or write data phase ns1 kernel: ahc0: PCI error Interrupt at seqaddr = 0x16b ns1 kernel: ahc0: Data Parity Error Detected during address or write data phase ns1 kernel: ahc0: WARNING WARNING WARNING WARNING ns1 kernel: ahc0: Too many PCI parity errors observed as a target. ns1 kernel: ahc0: Some device on this bus is generating bad parity. ns1 kernel: ahc0: This is an error *observed by*, not *generated by*, this controller. ns1 kernel: ahc0: PCI parity error checking has been disabled. ns1 kernel: ahc0: WARNING WARNING WARNING WARNING