From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Mason Subject: Re: dl2k: PCI parity error Date: Wed, 17 May 2006 15:27:18 -0500 Message-ID: <20060517202718.GB22817@us.ibm.com> References: <20060513165715.GA21243@cm.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netdev@vger.kernel.org Return-path: Received: from e32.co.us.ibm.com ([32.97.110.150]:7315 "EHLO e32.co.us.ibm.com") by vger.kernel.org with ESMTP id S1751095AbWEQU2o (ORCPT ); Wed, 17 May 2006 16:28:44 -0400 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e32.co.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k4HKShQi024761 for ; Wed, 17 May 2006 16:28:43 -0400 Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k4HKShRI266914 for ; Wed, 17 May 2006 14:28:43 -0600 Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id k4HKSgSc031569 for ; Wed, 17 May 2006 14:28:42 -0600 To: Shane Content-Disposition: inline In-Reply-To: <20060513165715.GA21243@cm.nu> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Sat, May 13, 2006 at 09:57:15AM -0700, Shane wrote: > Hello list, > > Not sure if this is the best place to report this. I seem > to be having a conflict of sorts and believe it may be a > dl2k issue. The card is a Dlink 550t gigabit pci-64 card. > When connected to the pci-64 slot on the mb which shares an > IRQ with the onboard SCSI controller, the SCSI subsystem > starts reporting PCI parity errors. If I move the NIC to a > pci-32 slot, the errors go away. Do you have any other 64bit slots? > scsi0: PCI error Interrupt at seqaddr = 0x9 > scsi0: Data Parity Error Detected during address or write data phase > scsi1: PCI error Interrupt at seqaddr = 0x9 > scsi1: Data Parity Error Detected during address or write data phase > scsi1: PCI error Interrupt at seqaddr = 0x9 > scsi1: Data Parity Error Detected during address or write data phase > scsi0: PCI error Interrupt at seqaddr = 0x8 > scsi0: Data Parity Error Detected during address or write data phase > scsi0: WARNING WARNING WARNING WARNING > scsi0: Too many PCI parity errors observed as a target. > scsi0: Some device on this bus is generating b ad parity. > scsi0: This is an error *observed by*, not *generated by*, this controller. > scsi0: PCI parity error checking has been disabled. > > This is using a 2.6.15.4 kernel but I can certainly update > if that will help. Is this likely a dl2k issue? The > driver does seem a bit dated. The driver is mostly unmaintained. I did a fix a month or so ago which fixed a DMA free issue, but that doesn't sound like the problem you have here. There is another error I am seeing that I haven't had time to track down, where the adapter appears to be DMA'ing somewhere its not supposed to. I would be suprised if either of these caused a SCSI data parity error. Thanks, Jon > > Tia, > Shane > > -- > http://www.cm.nu/~shane/ > - > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html