Data Parity Error w/aic7xxxx 6.2.8, 2940u2w, quantum drives

[Chris Boylan]

I'm running redhat 2.4.2 with the aic7xxx 6.2.3 driver sucessfully. via 
chipset, amd k6-2/300.  Attempting to upgrade redhat.  New driver is 
6.2.8.  Can't read my file system.  Badness as follows:  

<6>PCI: Found IRQ 5 for device 00:0a.0
<6>IRQ routing conflict for 00:0a.0, have irq 11, want irq 5
<6>scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
<4>        <Adaptec 2940 Ultra2 SCSI adapter>
<4>        aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs
<4>        
<4>blk: queue dfce2614, I/O limit 4095Mb (mask 0xffffffff)
<4>  Vendor: QUANTUM   Model: QM318000TD-SW     Rev: N495
<4>  Type:   Direct-Access                      ANSI SCSI revision: 02
<4>blk: queue dfce2814, I/O limit 4095Mb (mask 0xffffffff)
<4>  Vendor: QUANTUM   Model: QM318000TD-SW     Rev: N495
<4>  Type:   Direct-Access                      ANSI SCSI revision: 02
<4>blk: queue dfce2c14, I/O limit 4095Mb (mask 0xffffffff)
<4>  Vendor: QUANTUM   Model: QM318000TD-SW     Rev: N495
<4>  Type:   Direct-Access                      ANSI SCSI revision: 02
<4>blk: queue de837014, I/O limit 4095Mb (mask 0xffffffff)
<4>  Vendor: QUANTUM   Model: QM318000TD-SW     Rev: N495
<4>  Type:   Direct-Access                      ANSI SCSI revision: 02
<4>blk: queue de837414, I/O limit 4095Mb (mask 0xffffffff)
<4>  Vendor: QUANTUM   Model: QM318000TD-SW     Rev: N495
<4>  Type:   Direct-Access                      ANSI SCSI revision: 02
<4>blk: queue de837814, I/O limit 4095Mb (mask 0xffffffff)
<4>  Vendor: QUANTUM   Model: QM318000TD-SW     Rev: N495
<4>  Type:   Direct-Access                      ANSI SCSI revision: 02
<4>blk: queue de837c14, I/O limit 4095Mb (mask 0xffffffff)
<4>  Vendor: QUANTUM   Model: QM318000TD-SW     Rev: N495
<4>  Type:   Direct-Access                      ANSI SCSI revision: 02
<4>blk: queue de829014, I/O limit 4095Mb (mask 0xffffffff)
<4>  Vendor: QUANTUM   Model: QM318000TD-SW     Rev: N495
<4>  Type:   Direct-Access                      ANSI SCSI revision: 02
<4>blk: queue de829414, I/O limit 4095Mb (mask 0xffffffff)
<4>scsi0:A:0:0: Tagged Queuing enabled.  Depth 253
<4>scsi0:A:1:0: Tagged Queuing enabled.  Depth 253
<4>scsi0:A:2:0: Tagged Queuing enabled.  Depth 253
<4>scsi0:A:3:0: Tagged Queuing enabled.  Depth 253
<4>scsi0:A:4:0: Tagged Queuing enabled.  Depth 253
<4>scsi0:A:5:0: Tagged Queuing enabled.  Depth 253
<4>scsi0:A:6:0: Tagged Queuing enabled.  Depth 253
<4>scsi0:A:8:0: Tagged Queuing enabled.  Depth 253
<4>Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
<4>Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
<4>Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0
<4>Attached scsi disk sdd at scsi0, channel 0, id 3, lun 0
<4>Attached scsi disk sde at scsi0, channel 0, id 4, lun 0
<4>Attached scsi disk sdf at scsi0, channel 0, id 5, lun 0
<4>Attached scsi disk sdg at scsi0, channel 0, id 6, lun 0
<4>Attached scsi disk sdh at scsi0, channel 0, id 8, lun 0
<4>(scsi0:A:0): 80.000MB/s transfers (40.000MHz, offset 31, 16bit)
<4>SCSI device sda: 35566500 512-byte hdwr sectors (18210 MB)
<6> sda: sda1
<4>(scsi0:A:1): 80.000MB/s transfers (40.000MHz, offset 31, 16bit)
<4>SCSI device sdb: 35566500 512-byte hdwr sectors (18210 MB)
<6> sdb: sdb1
<4>(scsi0:A:2): 80.000MB/s transfers (40.000MHz, offset 31, 16bit)
<4>SCSI device sdc: 35566500 512-byte hdwr sectors (18210 MB)
<6> sdc: sdc1
<4>(scsi0:A:3): 80.000MB/s transfers (40.000MHz, offset 31, 16bit)
<4>SCSI device sdd: 35566500 512-byte hdwr sectors (18210 MB)
<6> sdd: sdd1
<4>(scsi0:A:4): 80.000MB/s transfers (40.000MHz, offset 31, 16bit)
<4>SCSI device sde: 35566500 512-byte hdwr sectors (18210 MB)
<6> sde: sde1
<4>(scsi0:A:5): 80.000MB/s transfers (40.000MHz, offset 31, 16bit)
<4>SCSI device sdf: 35566500 512-byte hdwr sectors (18210 MB)
<6> sdf: sdf1
<4>(scsi0:A:6): 80.000MB/s transfers (40.000MHz, offset 31, 16bit)
<4>SCSI device sdg: 35566500 512-byte hdwr sectors (18210 MB)
<6> sdg: sdg1
<4>(scsi0:A:8): 80.000MB/s transfers (40.000MHz, offset 31, 16bit)
<4>SCSI device sdh: 35566500 512-byte hdwr sectors (18210 MB)
<6> sdh: sdh1
<6>md: raid0 personality registered as nr 2
<6>md: raid1 personality registered as nr 3
<6>raid5: measuring checksumming speed
<4>   8regs     :   512.000 MB/sec
<4>   32regs    :   317.600 MB/sec
<4>   8regs_prefetch:   512.000 MB/sec
<4>   32regs_prefetch:   320.800 MB/sec
<4>   pII_mmx   :   712.800 MB/sec
<4>   p5_mmx    :   676.800 MB/sec
<4>raid5: using function: pII_mmx (712.800 MB/sec)
<6>md: raid5 personality registered as nr 4
<6>Journalled Block Device driver loaded
<6>LVM version 1.0.5+(22/07/2002) module loaded
<6>parport0: PC-style at 0x378 [PCSPP(,...)]
<7>ISO 9660 Extensions: RRIP_1991A
<7>ISO 9660 Extensions: RRIP_1991A
<7>ISO 9660 Extensions: RRIP_1991A
<7>ISO 9660 Extensions: RRIP_1991A
<7>ISO 9660 Extensions: RRIP_1991A
<4>scsi0: PCI error Interrupt at seqaddr = 0x8
<4>scsi0: Data Parity Error Detected during address or write data phase
<4>scsi0: PCI error Interrupt at seqaddr = 0x9
<4>scsi0: Data Parity Error Detected during address or write data phase
<4>scsi0: PCI error Interrupt at seqaddr = 0x8
<4>scsi0: Data Parity Error Detected during address or write data phase
<4>scsi0: PCI error Interrupt at seqaddr = 0x8
<4>scsi0: Data Parity Error Detected during address or write data phase

Repeats until it gets around to whining about being unable to read the
superblock and that the raid file system is probably unformatted.  Not.

I've got current firmware on the controller and drives and I've led a 
chaste life with plenty of pray, entirely in the computer room.
What's my problem from?  Thanks.


I've tried booting with:

linux text aic7xxx=verbose,tag_info{{7,7,7,7,7,7,7,7,7}} based on a note 
I found elsewhere without joy.  I don't think it gets passed to the 
driver successfully.
    Chris Boylan
    Actual Software, Inc.
    651-665-0035
    651-265-3100 (f)
    boylan at actualsoftware.com