[1742] in linux-scsi channel archive
Re: Timeout problems with Exabyte 8200
daemon@ATHENA.MIT.EDU (Leonard N. Zubkoff)
Wed Apr 23 02:50:51 1997
Date: Tue, 22 Apr 1997 23:48:35 -0700
From: "Leonard N. Zubkoff" <lnz@dandelion.com>
To: skeet@Bridgewater.EDU
CC: linux-scsi@vger.rutgers.edu
In-reply-to: <Pine.HPP.3.93.970422094456.27009D-100000@Titan.bridgewater.edu>
(message from Skeet Fischer on Tue, 22 Apr 1997 10:03:32 -0400 (EDT))
Date: Tue, 22 Apr 1997 10:03:32 -0400 (EDT)
From: Skeet Fischer <skeet@Bridgewater.EDU>
I am new on this list, so I don't know if this issue or a similar one has
been addressed before (I tried to find an archive of this list but I
couldn't).
I am trying to get an Exabyte 8200 SCSI tape drive to work under Linux.
When booting, the kernel recognizes the existence of a SCSI device at the
tape drive's SCSI address, but it times out trying to access the device.
This is what I'm getting in the logfile:
scsi : aborting command due to timeout : pid 19, scsi1, channel 0, id 4,
lun 0 0x00 00 00 00 00 00
scsi1: Aborting CCB #30 to Target 4
scsi1: CCB #30 to Target 4 Aborted
scsi : aborting command due to timeout : pid 19, scsi1, channel 0, id 4,
lun 0 0x00 00 00 00 00 00
scsi1: Aborting CCB #31 to Target 4
scsi1: CCB #31 to Target 4 Aborted
I am running Slackware 3.1 with kernel 2.1.33, all updated libs and utils,
on a 486-DX2 with a EISA bus. I have 2 BusLogic BT-742AH EISA SCSI host
adapters, one controlling a Conner CP31370 hard drive and an NEC CDR-84-1
CD-ROM; the other controlling just the tape drive (Exabyte EXP-8200).
One possibility is that some tape drives will not handle SCSI commands too soon
after a bus reset. If you boot with the kernel command line
"BusLogic= BusLogic=0,0,30"
it will set the Bus Settle Time to 30 seconds on ths second host adapter which
will give the tape drive a better chance of becoming ready.
Leonard
