[989] in linux-scsi channel archive
Buslogic 445S and iomega jaz drive
daemon@ATHENA.MIT.EDU (Zane Dodson)
Fri Nov 22 01:40:10 1996
From: Zane Dodson <dodson@redwood.mza.com>
To: linux-scsi@vger.rutgers.edu
Date: Thu, 21 Nov 1996 23:40:09 -0700 (MST)
Hello,
I am wondering if anyone has had success using a Buslogic 445S
SCSI host adapter with the iomega jaz drive.
I am getting bus resets and a variety of interesting messages
when I run a find over the entire 1GB disk. I am using the Buslogic
driver by Leonard Zubkoff. Here is an excerpt from the syslog
about the host adapter.
Nov 21 23:07:50 knuth kernel: scsi: ***** BusLogic SCSI Driver Version 2.0.4 of 5 June 1996 *****
Nov 21 23:07:50 knuth kernel: scsi: Copyright 1995 by Leonard N. Zubkoff <lnz@dandelion.com>
Nov 21 23:07:50 knuth kernel: scsi0: Configuring BusLogic Model BT-445S VESA SCSI Host Adapter
Nov 21 23:07:50 knuth kernel: scsi0: Firmware Version: 3.37, I/O Address: 0x234, IRQ Channel: 11/Edge
Nov 21 23:07:50 knuth kernel: scsi0: DMA Channel: None, BIOS Address: 0xDC000, Host Adapter SCSI ID: 7
Nov 21 23:07:50 knuth kernel: scsi0: Scatter/Gather Limit: 128 of 8192 segments, Parity Checking: Disabled
Nov 21 23:07:50 knuth kernel: scsi0: Synchronous Initiation: Enabled, Extended Disk Translation: Disabled
Nov 21 23:07:50 knuth kernel: scsi0: Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled
Nov 21 23:07:50 knuth kernel: scsi0: Total Queue Depth: 30, Mailboxes: 255, Initial CCBs: 64
Nov 21 23:07:51 knuth kernel: scsi0: Tagged Queue Depth: Automatic, Untagged Queue Depth: 3
Nov 21 23:07:51 knuth kernel: scsi0: Error Recovery Strategy: Default
Nov 21 23:07:51 knuth kernel: scsi0: *** BusLogic BT-445S Initialized Successfully ***
Nov 21 23:07:51 knuth kernel: scsi0: Target 0: Synchronous at 10.0 mega-transfers/second, offset 15
Nov 21 23:07:51 knuth kernel: scsi0: Target 4: Synchronous at 10.0 mega-transfers/second, offset 15
Nov 21 23:07:51 knuth kernel: scsi0 : BusLogic BT-445S
Nov 21 23:07:51 knuth kernel: scsi : 1 host.
Nov 21 23:07:51 knuth kernel: Vendor: SEAGATE Model: ST11900N Rev: 8650
Nov 21 23:07:51 knuth kernel: Type: Direct-Access ANSI SCSI revision: 02
Nov 21 23:07:51 knuth kernel: Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Nov 21 23:07:51 knuth kernel: Vendor: iomega Model: jaz 1GB Rev: H.71
Nov 21 23:07:51 knuth kernel: Type: Direct-Access ANSI SCSI revision: 02
Nov 21 23:07:51 knuth kernel: Detected scsi disk sdb at scsi0, channel 0, id 4, lun 0
Nov 21 23:07:51 knuth kernel: scsi : detected 2 SCSI disks total.
Nov 21 23:07:51 knuth kernel: SCSI device sda: hdwr sector= 512 bytes. Sectors= 3320691 [1621 MB] [1.6 GB]
Nov 21 23:07:51 knuth kernel: SCSI device sdb: hdwr sector= 512 bytes. Sectors= 2091050 [1021 MB] [1.0 GB]
Here is what often happens when using the jaz drive. It appears
that after Tagged Queueing is disabled, I don't have any more problems with
the drive, though this could be simply coincidental.
VFS: Disk change detected on device 08:10
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 2091050 [1021 MB] [1.0 GB]
sdb: Write Protect is off
sdb:scsidisk I/O error: dev 08:10, sector 0
unable to read partition table
VFS: Disk change detected on device 08:11
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 2091050 [1021 MB] [1.0 GB]
sdb: Write Protect is off
sdb: sdb1
scsi : aborting command due to timeout : pid 7703, scsi0, channel 0, id 4, lun 0 Read (6) 0f 00 3c 02 00
scsi0: Unable to Abort CCB #11224 to Target 4 - Abort Tag Not Supported
scsi : aborting command due to timeout : pid 7702, scsi0, channel 0, id 4, lun 0 Write (6) 0f 00 32 02 00
scsi0: Unable to Abort CCB #11232 to Target 4 - Abort Tag Not Supported
scsi : aborting command due to timeout : pid 7687, scsi0, channel 0, id 4, lun 0 Write (6) 0b 00 36 04 00
scsi0: Unable to Abort CCB #11240 to Target 4 - Abort Tag Not Supported
scsi : aborting command due to timeout : pid 7709, scsi0, channel 0, id 4, lun 0 Write (6) 11 00 32 02 00
scsi0: Unable to Abort CCB #11248 to Target 4 - Abort Tag Not Supported
scsi : aborting command due to timeout : pid 7710, scsi0, channel 0, id 4, lun 0 Write (6) 12 40 32 02 00
scsi0: Unable to Abort CCB #11256 to Target 4 - Abort Tag Not Supported
scsi : aborting command due to timeout : pid 7711, scsi0, channel 0, id 4, lun 0 Write (6) 12 80 34 02 00
scsi0: Unable to Abort CCB #11264 to Target 4 - Abort Tag Not Supported
scsi : aborting command due to timeout : pid 7712, scsi0, channel 0, id 4, lun 0 Write (6) 14 00 34 04 00
scsi0: Unable to Abort CCB #11272 to Target 4 - Abort Tag Not Supported
scsi : aborting command due to timeout : pid 7713, scsi0, channel 0, id 4, lun 0 Write (6) 14 80 34 02 00
scsi0: Unable to Abort CCB #11280 to Target 4 - Abort Tag Not Supported
scsi : aborting command due to timeout : pid 7714, scsi0, channel 0, id 4, lun 0 Write (6) 14 c0 34 02 00
scsi0: Unable to Abort CCB #11288 to Target 4 - Abort Tag Not Supported
scsi : aborting command due to timeout : pid 7715, scsi0, channel 0, id 4, lun 0 Write (6) 15 40 36 02 00
scsi0: Unable to Abort CCB #11296 to Target 4 - Abort Tag Not Supported
scsi : aborting command due to timeout : pid 7703, scsi0, channel 0, id 4, lun 0 Read (6) 0f 00 3c 02 00
scsi0: Unable to Abort CCB #11224 to Target 4 - Abort Tag Not Supported
SCSI host 0 abort (pid 7703) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
scsi0: Tagged Queuing now disabled for Target 4
scsi0: Sending Bus Device Reset CCB #13782 to Target 4
scsi0: Bus Device Reset CCB #13782 to Target 4 Completed
Unable to handle kernel NULL pointer dereference at virtual address c0000004
current->tss.cr3 = 00d4f000, %cr3 = 00d4f000
*pde = 00102067
*pte = 00000027
Oops: 0000
CPU: 0
EIP: 0010:[<001bbf91>]
EFLAGS: 00010246
eax: 00000000 ebx: 00093118 ecx: 00dbde6c edx: 00000000
esi: 00000806 edi: 00000046 ebp: 00000001 esp: 00dbdec8
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process syslogd (pid: 50, process nr: 11, stackpage=00dbd000)
Stack: 00000000 002128d4 00000806 00212814 00220fb4 0017ea97 00000008 000052ec
00000001 00000002 0017eeef 00220fb4 00212814 00000000 00dbdf60 00000001
00000400 00212844 00000806 0000002a 00000000 00008706 0017f039 00000008
Call Trace: [<0017ea97>] [<0017eeef>] [<0017f039>] [<001596ce>] [<00159822>] [<001599ff>] [<00124aa4>]
[<0010a5e2>]
Code: 8a 40 04 c1 e8 04 83 e0 0f 8b 15 3c e2 1f 00 8d 04 80 8b 44
Disc change detected.
VFS: Disk change detected on device 08:10
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 2091050 [1021 MB] [1.0 GB]
sdb: Write Protect is off
sdb: sdb1
Disc change detected.
VFS: Disk change detected on device 08:10
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 2091050 [1021 MB] [1.0 GB]
sdb: Write Protect is off
sdb: sdb1
Has anyone ran into something similar with this combination of
hardware?
Best regards,
Zane Dodson
dodson@mza.com
