Scanning problems persist, even with Justin's SCSI driver.

[Wirschell, Tom]

K, I'll up the logging level to its maximum (assuming it's done the same way
as with Doug's driver. If not, let me know) and let you know if anything
pops up. As for ideas you've given:
1. Termination problem with the scanner.
I've attached a known-good terminator to it to no avail.
2. Cable quality/length
The shortest external 50-pin HD SCSI cable you can buy in the shops is 1.8
meters. The one I got with the scanner was that length and the one I
replaced it with once these problems became really annoying was also that
length. I believe both to be/have been of good quality and the old one
didn't appear to have been bent or twisted in direction it didn't agree
with.
I didn't consider replacing the internal SCSI cable yet, so I guess that'll
be next on the list. Maybe something sharp in the case nicked it or
whatever. I probably still have one back home, so it shouldn't be much of a
problem. I will however try to get some decent logging of a crash due to
this problem so you might be able to figure out why you can't recover.

The crash the way it is now is reliably reproducable given a little effort.
Most recent one was after 106 scans. New record :) Just too bad that one
didn't even bother to write anything in the logs/on the console...

-----Oorspronkelijk bericht-----
Van: Justin T. Gibbs [mailto:gibbs at scsiguy.com]
Verzonden: zaterdag 17 maart 2001 19:08
Aan: Wirschell, Tom
CC: AIC7xxx at FreeBSD.ORG
Onderwerp: Re: Scanning problems persist, even with Justin's SCSI
driver. 


>I was working on roughly my 65th scan when the scanner stopped. I
>brought up the xconsole window which read:
>
>kernel: (scsi0:A:0:0): parity error detected in Message-in

I'd have to have more complete logs to know why we didn't
recover, but the moral of the story is that your bus is not
up to snuff.  Perhaps your scanner has a sub-par terminator.
Perhaps your cable going to your scanner is too long or just
not of high quality.  Perhaps the combined length of your
internal and external cables is too long.  Whatever the
reason, you won't have a reliable bus until this problem is
fixed.

--
Justin

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