From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932433AbVHIHT7 (ORCPT ); Tue, 9 Aug 2005 03:19:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932456AbVHIHT7 (ORCPT ); Tue, 9 Aug 2005 03:19:59 -0400 Received: from 203-217-29-35.perm.iinet.net.au ([203.217.29.35]:55999 "EHLO anu.rimspace.net") by vger.kernel.org with ESMTP id S932433AbVHIHT7 (ORCPT ); Tue, 9 Aug 2005 03:19:59 -0400 From: Daniel Pittman To: linux-kernel@vger.kernel.org Subject: Adaptec AHA-2940U2W "Data Parity Error Dectected" messages Date: Tue, 09 Aug 2005 17:19:47 +1000 Message-ID: <878xzbr2zw.fsf@rimspace.net> User-Agent: Gnus/5.110004 (No Gnus v0.4) XEmacs/21.5-b21 (corn, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org I recently installed a SCSI tape drive and Adaptec AHA-2940U2W SCSI controller into my server to run backups. Since then, the driver issues these warnings on a semi-regular basis while the drive is busy: Aug 9 17:00:26 anu kernel: scsi0: Data Parity Error Detected during address or write data phase Aug 9 17:00:26 anu kernel: scsi0: PCI error Interrupt at seqaddr = 0x8 [...] Aug 9 17:03:34 anu kernel: scsi0: Data Parity Error Detected during address or write data phase [...] Aug 9 17:04:36 anu kernel: scsi0: PCI parity error checking has been disabled. Aug 9 17:04:36 anu kernel: scsi0: Some device on this bus is generating bad parity. Aug 9 17:04:36 anu kernel: scsi0: This is an error *observed by*, not *generated by*, this controller. Aug 9 17:04:36 anu kernel: scsi0: Too many PCI parity errors observed as a target. Aug 9 17:04:36 anu kernel: scsi0: WARNING WARNING WARNING WARNING Now, the log message claims that the SCSI controller is not responsible for these parity errors, so my questions are: * should I panic about this? * should I have seen this before the SCSI controller was installed? * can I do anything about it, or identifying the cause? Thanks, Daniel