2.0.32-3985W (fwd)

[Doug Ledford]

On 04-Dec-97 Michael Leodolter wrote:
>On Wed, 3 Dec 1997, Mike Bilow wrote:
>
>> The RAID controller chip is an AIC-7810.
>
>Thanks!
>
>Back to the REAL problem:
>Can anyone of you tell me if the following messages com from
>1) Disk (there are 5 other disk w/o problems).
>2) Cable
>3) Controller
>4) Memory
>5) Kernel/Driver
>6) ???
>...
>Dec  4 04:23:21 lab1 kernel: (scsi0:0:1:0) Parity error during phase
>Data-In.
>Dec  4 04:23:21 lab1 kernel: (scsi0:0:1:0) Parity error during phase
>Data-In.
>Dec  4 04:23:21 lab1 kernel: (scsi0:0:1:0) Underflow - Wanted at least
>17408, got 12800, residual SG count 1.
>Dec  4 04:23:21 lab1 kernel: (scsi0:0:1:0) Parity error during phase
>Data-In.
>Dec  4 04:23:21 lab1 kernel: (scsi0:0:1:0) Underflow - Wanted at least
>17408, got 8704, residual SG count 1.
>Dec  4 04:23:26 lab1 kernel: scsi0 channel 0 : resetting for second half of
>retries.
>Dec  4 04:23:27 lab1 kernel: (scsi0:0:1:0) Reset called, no scb, flags 0x1
>Dec  4 04:23:27 lab1 kernel: (scsi0:0:-1:-1) Channel reset
>Dec  4 04:23:27 lab1 kernel: (scsi0:0:0:0) Using 16 bit (Wide)transfers.
>Dec  4 04:23:27 lab1 kernel: (scsi0:0:0:0) Synchronous at 10.0MHz, offset
>8.
>Dec  4 04:23:27 lab1 kernel: (scsi0:0:1:0) Using 16 bit (Wide)transfers.
>Dec  4 04:23:27 lab1 kernel: (scsi0:0:1:0) Synchronous at 10.0MHz, offset
>8.
>Dec  4 04:23:27 lab1 kernel: (scsi0:0:1:0) Parity error during phase
>Command.

I would guess that you are using the Nov-05 version of my patch (this is the
one where I updated the printk headers to the style noted above).  I would
first guess that your problem is cable related.  Either termination or a bad
cable period.  The SCSI parity errors are hardware flagged by the card and
not directly controlled by the driver (other than we tell the card to let us
know when they occur).

----------------------------------
E-Mail: Doug Ledford <dledford at dialnet.net>
Date: 04-Dec-97
Time: 14:26:40
----------------------------------