Hello: I've written here before about some AIC7xxx driver problems encountered on a Dell Poweredge 2200 system running Linux 2.1.127pre1 (which is basically 2.1.126 with minor patches.) The symptoms were that, once every one or two weeks, some messages like the following: Dec 2 00:49:06 press kernel: (scsi0:0:0:0) Parity error during Data-In phase. Dec 8 09:08:40 press kernel: (scsi0:0:0:0) Parity error during Message-In phase. Dec 8 09:08:55 press kernel: scsi : aborting command due to timeout : pid 16061190, scsi0, channel 0, id 0, lun 0 Read (6) 1e f5 6d 02 00 Dec 8 09:08:55 press kernel: scsi : aborting command due to timeout : pid 16061191, scsi0, channel 0, id 1, lun 0 Read (6) 06 00 0e 02 00 Dec 8 09:08:56 press kernel: SCSI host 0 abort (pid 16061190) timed out - resetting Dec 8 09:08:56 press kernel: SCSI bus is being reset for host 0 channel 0. Dec 8 09:08:56 press kernel: (scsi0:0:1:0) Synchronous at 40.0 Mbyte/sec, offset 8. Dec 8 09:08:57 press kernel: (scsi0:0:0:0) Synchronous at 40.0 Mbyte/sec, offset 8. Dec 8 09:40:45 press kernel: (scsi0:0:0:0) Parity error during Data-In phase. Dec 8 09:42:15 press kernel: (scsi0:0:0:0) Parity error during Data-In phase. Dec 8 09:50:09 press kernel: (scsi0:0:0:0) Parity error during Data-In phase. Dec 10 04:41:55 press kernel: (scsi0:0:0:0) Parity error during Data-In phase. *** crash here *** Dec 10 10:57:34 press kernel: (scsi0:0:0:0) Parity error during Message-In phase. Dec 10 10:57:34 press kernel: (scsi0:0:0:-1) Unexpected busfree, LASTPHASE = 0xa0, SEQADDR = 0x155 Dec 10 10:57:38 press kernel: (scsi0:0:0:0) Parity error during Message-In phase. Dec 10 10:57:38 press kernel: (scsi0:0:0:-1) Unexpected busfree, LASTPHASE = 0xa0, SEQADDR = 0x155 Dec 10 11:08:34 press kernel: (scsi0:0:0:0) Parity error during Data-In phase. Dec 10 11:08:34 press kernel: (scsi0:0:0:0) Parity error during Data-In phase. Dec 10 11:08:34 press kernel: (scsi0:0:0:0) Synchronous at 40.0 Mbyte/sec, offset 8. Dec 11 09:01:05 press kernel: (scsi0:0:0:0) Parity error during Data-In phase. appear in the kern.log file. I have annotated once where the system actually locked up hard. I haven't gotten any answer to my previous query, so I gather it's not a common problem. On the first chance I got after the crash, I took down the machine and checked the SCSI BIOS. One thing I noticed is that our SCSI controllers were configured for 'parity enabled' and the AIC7xxx driver defaults to 'parity disabled'. I checked the source code and found a comment to the effect that PCI parity checking is 'dubious at best.' My question is: why? I did disable parity checking in the SCSI BIOS in hopes that will solve the random error messages and make the machine stable again. I would appreciate any insights anyone might have about this problem. Thanks! --- Roy Bixler The University of Chicago Press [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED]
