Still problems with SCSI scanning...

Justin T. Gibbs gibbs at scsiguy.com
Mon Nov 26 13:09:19 PST 2001


>The last time it took a plunge, the loghost received this message:
>---
>messages:Nov 26 19:33:35 lev8 kernel: (scsi0:A:0:0): parity error
>detected in Message-in phase. SEQADDR(0x1a6) SCSIRATE(0x95)

I haven't found out the model number yet, but supposedly many of
HP's newer scanners do not properly generate parity.  This is
the likely cause of your problem.

I'll look into the parity error handling in the driver to see how I
might recover better, but the above log gives me very little to go
on.  Is that really all that was generated by the run?

>While I'm at it, I know for a fact that the Atlas V is 80 mb/s. Why is
>it reported as 40mb/s in dmesg? Normal behaviour, or signs of other
>problems? dmesg and other stuff included below.

There may be two reasons for this.  One is that some other device
on that chain is a Single Ended device.  40MHz sync rates are only
available if the bus is in LVD mode, and that can only happen
if all devices are LVD capable.  Also, your active terminator will
force the bus into single ended mode.  You need an LVD terminator
on that chain.

--
Justin

To Unsubscribe: send mail to majordomo at FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message




More information about the aic7xxx mailing list