> On Mon, Oct 18, 1999 at 08:28:25AM -0400, D'Arcy J.M. Cain wrote:
> Dunno.  My HP is three days old, so I _think_ it should work.  And it works
> just fine unless some kind of an error occurs.  This time, I had just
> inserted a tape into the drive and the drive wasn't ready yet - and I
> tried to access it.  It returned an error - and after that, every SCSI
> command to the drive is failing.  Other SCSI units (a QIC drive and two
> disks) are still fine.
> 
> Could it be that the DAT and the ncr driver got "out of sync" somehow and
> the driver is now sending out crippled commands?  The drive worked just
> fine for hours, so I tend to think that "any error condition confuses the
> ncr driver until rebooted" :-I

Similar conditions work flawlesly for me, but I have about 1+ year old Sony 
drive. So in ncr-driver seems to know what it is doing.

NetBSD 1.4.1 (POLY) #2: Tue Sep 14 23:05:00 EEST 1999
...
ncr0 at pci0 dev 13 function 0: ncr 53c815 fast10 scsi
ncr0: interrupting at irq 11
ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo
ncr0: single-ended, open drain IRQ driver
ncr0: restart (scsi reset).
...
st0 at scsibus0 targ 6 lun 0: <SONY, SDT-5000, 3.30> SCSI2 1/sequential 
removable
st0: st0(ncr0:6:0): 5.0 MB/s (200 ns, offset 8)
drive empty
...
st0(ncr0:6:0):  Check Condition on CDB: 0x00 00 00 00 00 00
    SENSE KEY:  Not Ready
     ASC/ASCQ:  Logical Unit Is in Process Of Becoming Ready
...
polykoira[3]%mt status
SCSI tape drive, residual=0
ds=3<Mounted>
er=6<>
blocksize: 0 (0, 0, 0, 0)
density: 19 (0, 0, 0, 0)