[2953] in linux-scsi channel archive
Re: BusLogic problems...
daemon@ATHENA.MIT.EDU (Leonard N. Zubkoff)
Wed Dec 17 17:47:13 1997
Date: Wed, 17 Dec 1997 14:43:03 -0800
From: "Leonard N. Zubkoff" <lnz@dandelion.com>
To: rstagg@csc.com
CC: linux-scsi@vger.rutgers.edu
In-reply-to: <8525656F.00655B45.00@csc.com> (rstagg@csc.com)
From: rstagg@csc.com
Date: Wed, 17 Dec 1997 08:46:15 +0000
Alles,
I imagine that this is a fairly common query, but my researches have turned
up nothing.
Today, I removed an Adaptec 2940 from my Linux box and replaced it with a
BT958. This, primarily, was because the Adaptec was screwing any attempts
at CD writing.
Now, any prolonged hard-disc accesses are repeatedly and time-consumingly
interrupted with:
scsi: aborting command due to timeout : pid xx, scsi0, channel 0, id 0, lun
0 Read (10) 00 00 2a b4 ee 00 00 10 00 (or some such)
scsi0: Aborting CCB#107 to Target 0
SCSI host 0 abort (pid 95) timed out - resetting
SCSI bus is now being reset for host 0 channel 0.
scsi0: Tagged Queueing now disabled for Target 0
scsi0: Sending Bus Device Reset CCB #108 to Target 0
SCSI host 0 channel 0 reset (pid 95) timed out - trying harder
SCSI bus is being reset for host 0 channel 0.
scsi0: Resetting BusLogic BT-958 due to Target 0
scsi0: *** BusLogic BT-958 Initialised Successfully ***
The above messages look like a SCSI bus hang, with the driver recovering
successfully.
Obviously with varying PIDs and CCBs. And this happens LOADS - even during
fscking, which is unnerving to say the least!
My system:
Kernel: 20.0.32. Pentium 200. SpeedEasy motherboard. 256Mb.
2 x Quantum Fireball ST4.3S hdds
Matshita CD-506 cdrom
Yamaha CDR100 cd-writer
I'm running Buslogic driver 2.0.10 (11/8/97).
Buslogic SCSI firmware is v5.07B.
My hard discs both detect at Syncronous 20.0 Mtransfers/sec (offset 15)
Both CD drives come up as Asyncronous.
Can anybody suggest 1) what's wrong and 2) how to put it right?!
Thanks VERY much...
The problem is most likely due to the Quantum Stratus disk drives. Even with
the latest firmware (see http://www.dandelion.com/Linux/Quantum.html), they
still seem to be buggy. If you have the BusLogic driver compiled into your
kernel, you can boot with the command line "BusLogic=0,7" to limit the queue
depth to 7, which should make this problem either go away completely or become
much less frequent. The next release of the BusLogic driver will support
setting the queue depth on a per-target basis as well as allow passing options
to the driver from insmod.
Another possibility is that there have been a few reports of problems with the
5.07B BT-958 firmware. You might try using 5.06J if there are any remaining
problems after limiting the queue depth.
I'm beginning to think we should just blacklist the Quantum Tempest and Stratus
drives.
Leonard
