Subject: Re: SCSI failure going from 1.5.1 to 1.5Q
To: William O Ferry <woferry@iname.com>
From: Greywolf <greywolf@starwolf.com>
List: port-sparc
Date: 01/19/2001 09:33:47
On Thu, 18 Jan 2001, William O Ferry wrote:

# 	With 1.5Q I get:
# 
# sd1 at scsibus0 target 4 lun 0: <CWS ORB2, -SE U ID 4, D01> SCSI2 0/direct 
# removable
# sd1(esp0:4:0): max sync rate 7.57MB/s
# esp0: unexpected disconnect: sending REQUEST SENSE
# esp0: target didn't send tag: 0 bytes in fifo
# esp0: SCSI bus reset
# 
# 	At this point the machine hangs for a minute or so, then displays:
# 
# sd1(esp0:4:0): esp0: timed out [ecb 0xf02f7000 (flags 0x1, dleft 0, stat 0)], 
# <state 2 nexus 0xf02f7000, phase(l 1, c 101, p 101), resid 0, msg(q 0, o 100) 
# DMA active>
# sd1(esp0:4:0): esp0: timed out [ecb 0xf02f7000 (flags 0x1, dleft 0, stat 0)], 
# <state 2 nexus 0xf02f7000, phase(l 1, c 101, p 101), resid 0, msg(q 0, o 100) 
# DMA active> AGAIN
# esp0: SCSI bus reset

I got this from my CDRW, and my 4mm drive no longer works right :-(.  I had
to put my old EXB-8200 back on.  Yes, it's slow, but it's stable.

It turns out that when you config a kernel you have to give the scsi
adapter some flags (undocumented, by the way) on bits 16-23 corresponding
to target [bit-16] which disable tagged queueing.  I disabled tagged
queueing on my targets 4 and 6 (i.e. flags 0x500000), and my CDRW (6)
and my 8mm drive (4) now seem to be functioning, but I'm still having
some problems dumping stuff out to tape.  This started happening to me
with 1.5Q as well.

Ahh, (b)leading-edge technology.  Isn't it grand?

# 	And that's about as far as it gets.  Switching back to the
# 1.5.1_ALPHA2 kernel it boots just fine.
# 
# 	Does this drive need some sort of quirk entry, or is there
# something else I can do to get this to work under 1.5Q?

Maybe I need to backrev my sources...

# 	Thanks in advance.
#                                           Will Ferry

				--*greywolf;
--
*BSD: Hackers tested, mom approved.