Re: dl2k: PCI parity error

[Jon Mason <jdmason@us.ibm.com>]

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