Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 1 Mar 2002 04:47:17 -0500 (EST)
From:      "Matthew N. Dodd" <winter@jurai.net>
To:        freebsd-scsi@freebsd.org
Subject:   SCSI driver problem: 'sym' fails, 'ahc' works.
Message-ID:  <20020301042234.N21724-100000@sasami.jurai.net>

next in thread | raw e-mail | index | archive | help
I've got a set of 4 SUN OEM SEAGATE ST410800WD drives in an external
enclosure.

I've got a system with a LSI/Symbios SYM22802 (dual channel HVD scsi)
adapter and is running FreeBSD -CURRENT, no more than a few weeks old:

sym1: <875> port 0xe400-0xe4ff mem 0xffafd000-0xffafdfff,0xffafee00-0xffafeeff irq 15 at device 16.1 on pci0
sym1: Symbios NVRAM, ID 7, Fast-20, HVD, parity checking
sym1: open drain IRQ line driver, using on-chip SRAM
sym1: using LOAD/STORE-based firmware.

The second system has an Adaptec AHA-4944 (quad channel HVD scsi) adapter
and is running FreeBSD 3.4-STABLE:

chip3: <DEC 21050 PCI-PCI bridge> rev 0x02 on pci0.19.0
...
ahc3: <Adaptec 4944 SCSI adapter> rev 0x00 int a irq 18 on pci2.4.0
ahc3: aic7870 Wide Channel A, SCSI Id=7, 16/255 SCBs

(showing relevent channels only)

When the drives are plugged into the 'sym' channel:

(probe0:sym1:0:0:0): extraneous data discarded.
(probe0:sym1:0:0:0): COMMAND FAILED (87 0 1).
(probe0:sym1:0:0:0): ODD transfer in DATA IN phase.
(probe0:sym1:0:0:0): COMMAND FAILED (87 0 10).
... (repeated a few times)

And the drive does not show up on the bus.

When the drives are plugged into the 'ahc' channel:

(probe45:ahc3:0:0:0): data overrun detected in Data-In phase.  Tag == 0xe.
(probe45:ahc3:0:0:0): Have seen Data Phase.  Length = 36.  NumSGs = 1.
...
da2 at ahc3 bus 0 target 0 lun 0
da2: <SEAGATE ST410800WSUN9.0G 0407> Fixed Direct Access SCSI-2 device
da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing  Enabled
da2: 8669MB (17755614 512 byte sectors: 255H 63S/T 1105C)

My read of the 2 drivers indicates that this is the same error condition
but the 'ahc' driver appears to deal with it somehow and continue to
operate.  The 'sym' driver just gives up.

Can anyone explain what is going on?  Is there an easy fix for the 'sym'
driver that I'm missing?

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| winter@jurai.net |       2 x '84 Volvo 245DL        | ix86,sparc,pmax |
| http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020301042234.N21724-100000>