From owner-aic7xxx Mon Oct 29 12:12:10 2001 Delivered-To: aic7xxx@freebsd.org Received: from galactus.cs.berkeley.edu (galactus.CS.Berkeley.EDU [169.229.62.130]) by hub.freebsd.org (Postfix) with ESMTP id B851A37B405 for ; Mon, 29 Oct 2001 12:12:05 -0800 (PST) Received: from cs.berkeley.edu ([134.6.32.10]) by galactus.cs.berkeley.edu (8.11.0/8.11.0) with ESMTP id f9TKC9h21764 for ; Mon, 29 Oct 2001 12:12:09 -0800 Message-ID: <3BDDB6F1.582FA14@cs.berkeley.edu> Date: Mon, 29 Oct 2001 12:07:13 -0800 From: "J. Robert von Behren" X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.16-22 i586) X-Accept-Language: en MIME-Version: 1.0 To: aic7xxx@freebsd.org Subject: aic7xxx parity error question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Greetings! I've been seeing some some strange behavior from the aic7xxx driver under Linux. The gist is that although I can access my SCSI drive from DOS (and even boot to the drive), the Linux driver consistently gets parity errors. Here are the details of my setup, and what I've tried so far: 1. on-board SCSI controller (aic7899) 2. external SCSI drive (Quantum Atlas 10K) 3. The SCSI bios sees my drive, and I can successfully boot from it into DOS 4. The linux aic7xxx driver gets parity errors upon boot (error message below) 5. I've tried two different external SCSI drives, and two different cables - all permutations give the same results 6. Disabling the parity checking in the SCSI bios allows the aic7xxx driver to load, but I just get bogus data back from the device. (for example, the partition table is out of whack, mounted file systems that should have data are empty, etc.) Performance isn't a concern for this drive - I just need to be able to mount it and copy a few files around every once in a while. Is there some way to force the driver into a "safe but stupid" mode, that is not likely to have problems? (Perhaps have all accesses go through the BIOS, or perhaps dumb down to SCSI 1?) Are there other things I should try? Any suggestions would be most appreciated!! Best regards, -Rob von Behren -----------output from "modprobe aic7xxx"----------------- SCSI subsystem driver Revision: 1.00 PCI: Enabling device 00:05.1 (0116 -> 0117) PCI: Found IRQ 10 for device 00:05.1 PCI: Enabling device 00:05.0 (0116 -> 0117) PCI: Found IRQ 5 for device 00:05.0 scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.1 aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.1 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/255 SCBs Vendor: QUANTUM Model: ATLAS10K2-TY367L Rev: DDD6 Type: Direct-Access ANSI SCSI revision: 03 (scsi0:A:8): 40.000MB/s transfers (20.000MHz, offset 127, 16bit) (scsi0:A:8:1): parity error detected in Data-in phase. SEQADDR(0x75) SCSIRATE(0x95) scsi0:0:8:0: Tagged Queuing enabled. Depth 253 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message