Thanks!
Alex.
PS. Does it support Synch Tx of 20mb on bt-956c?
----------
From: Michael B Herf[SMTP:herf+@cmu.edu]
Sent: Sunday, April 21, 1996 10:06 AM
To: linux-kernel@vger.rutgers.edu
Cc: linux-kernel@vger.rutgers.edu
Subject: Re: I try BusLogic driver 1.3.2, ( in 1.3.9[12].)
Excerpts from internet.computing.linux-kernel: 21-Apr-96 Re: I try
BusLogic driver 1.. by "Leonard N. Zubkoff"@dan
> If we get further reports of problems with this model disk, it should
probably
> be blacklisted then.
>
I'm having a slightly different problem. The problem arose when I added
a new CD-ROM, the Toshiba XM-5401. I do have a Quantum Empire 1080S,
but I've never had any problems with it. The setup is this:
[internal term]-[Quantum 1080S] <-> [Toshiba 5401] <-> [DEC 5400S] <-> [bt946]
<-> [Conner CTMS3200]-[external term]
Here's the startup of Leonard's driver:
--------
Apr 21 14:16:16 vivarin kernel: scsi0: Firmware Version: 4.22, I/O
Address: 0x334, IRQ Channel: 15/Level
Apr 21 14:16:16 vivarin kernel: scsi0: DMA Channel: None, BIOS
Address: 0xDC000, Host Adapter SCSI ID: 7
Apr 21 14:16:16 vivarin kernel: scsi0: Scatter/Gather Limit: 8192
segments, Synchronous Initiation: Enabled
Apr 21 14:16:16 vivarin kernel: scsi0: SCSI Parity Checking: Enabled,
Extended Disk Translation: Enabled
Apr 21 14:16:16 vivarin kernel: scsi0: Disconnect/Reconnect: Enabled,
Tagged Queuing: Enabled
Apr 21 14:16:16 vivarin kernel: scsi0: Error Recovery: Default,
Mailboxes: 64, Initial CCBs: 32
Apr 21 14:16:16 vivarin kernel: scsi0: Driver Scatter/Gather Limit:
128 segments, Concurrency: 7
Apr 21 14:16:16 vivarin kernel: scsi0: *** BusLogic BT-946C Initialized
Successfully ***
Apr 21 14:16:16 vivarin kernel: scsi0: Target 0: Synchronous at 10.0
mega-transfers/second, offset 15
Apr 21 14:16:16 vivarin kernel: scsi0: Target 1: Synchronous at 10.0
mega-transfers/second, offset 15
Apr 21 14:16:16 vivarin kernel: scsi0: Target 4: Synchronous at 4.55
mega-transfers/second, offset 15
Apr 21 14:16:16 vivarin kernel: scsi0: Target 5: Asynchronous
Apr 21 14:16:16 vivarin kernel: scsi0 : BusLogic BT-946C
---------------------
And then the errors look like these:
Apr 19 23:21:02 vivarin kernel: SCSI host 0 abort (pid 35059) timed out
- resetting
Apr 19 23:21:02 vivarin kernel: SCSI bus is being reset for host 0.
Apr 19 23:21:02 vivarin kernel: scsi0: Unable to Reset Command to Target
0 - Reset Pending
Apr 19 23:21:02 vivarin kernel: scsi : aborting command due to timeout :
pid 35063, scsi0, channel 0, id 1, lun 0 0x0a 14 00 57 02 00
Apr 19 23:21:02 vivarin kernel: scsi0: Unable to Abort CCB #35142 to Target 1 -
Abort Tag Not Supported
Apr 19 23:21:02 vivarin kernel: SCSI host 0 abort (pid 35063) timed out
- resetting
Apr 19 23:21:02 vivarin kernel: SCSI bus is being reset for host 0.
Apr 19 23:21:02 vivarin kernel: scsi0: Resetting BusLogic BT-946C due to Target
1
Apr 19 23:21:02 vivarin kernel: scsi0: *** BusLogic BT-946C Initialized
Successfully ***
Apr 19 23:21:59 vivarin kernel: scsi0: Tagged Queuing now active for Target 1
Apr 19 23:35:01 vivarin kernel: scsi : aborting command due to timeout :
pid 36507, scsi0, channel 0, id 1, lun 0 0x0a 04 27 2d f4 00
Apr 19 23:35:01 vivarin kernel: scsi0: Unable to Abort CCB #36604 to Target 1 -
Abort Tag Not Supported
Apr 19 23:35:01 vivarin kernel: scsi : aborting command due to timeout :
pid 36508, scsi0, channel 0, id 1, lun 0 0x0a 04 28 21 f4 00
Apr 19 23:35:01 vivarin kernel: scsi0: Unable to Abort CCB #36605 to Target 1 -
Abort Tag Not Supported
Apr 19 23:35:01 vivarin kernel: scsi : aborting command due to timeout :
pid 36509, scsi0, channel 0, id 1, lun 0 0x0a 04 29 15 f4 00
Apr 19 23:35:01 vivarin kernel: scsi0: Unable to Abort CCB #36606 to Target 1 -
Abort Tag Not Supported
Apr 19 23:35:01 vivarin kernel: scsi : aborting command due to timeout :
pid 36510, scsi0, channel 0, id 1, lun 0 0x0a 04 2a 09 f4 00
Apr 19 23:35:01 vivarin kernel: scsi0: Unable to Abort CCB #36607 to Target 1 -
Abort Tag Not Supported
Apr 19 23:35:06 vivarin kernel: scsi : aborting command due to timeout :
pid 36527, scsi0, channel 0, id 1, lun 0 0x0a 04 00 4f 02 00
------------
Eventually, it gets the bus reset, and things work for quite a while. I
get these errors about once a day. Everything locks and you just have
to wait for the kernel to reset the bus.
Actually, NT does the same thing, so I think it's probably a problem
with the controller or one of the devices.
mike