[ On Sunday, September 8, 2002 at 20:31:40 (+0200), Manuel Bouyer wrote: ]
> Subject: Re: 1.6 on IPC (tagged queuing bug still there)
>
> All drivers are scsipi-enabled.

I thought so, but I was just being careful!  ;-)

> I agree if the problem is that drives don't support tagged queuing.
> But I think the problem isn't here. It's more a driver issue, in which
> case disabling tagged queuing only for this driver until it's fixed
> is the right thing to do.

Tagged queuing _may_ be a driver issue with ESP100 _only_ -- it is
definitely not a driver issue with ESP200.  The ESP200 report was surely
mistaken to identify a driver issue with tagged queuing.

For example my development machine with an ESP200 has re-built the world
several times, and built many packages many times too, not to mention is
NFS and XFS serving my two diskless clients at the same time.

esp0 at dma0 slot 15 offset 0x800000 level 4: ESP200, 40MHz, SCSI ID 7
scsibus0 at esp0: 8 targets, 8 luns per target
sd0 at scsibus0 target 0 lun 0: <WDIGTL, ENTERPRISE, 1.61> SCSI2 0/direct fixed
sd0: 4157 MB, 5720 cyl, 8 head, 186 sec, 512 bytes/sect x 8515173 sectors
sd0: sync (100.0ns offset 15), 8-bit (10.000MB/s) transfers, tagged queueing
sd1 at scsibus0 target 1 lun 0: <SEAGATE, ST32430N, 0510> SCSI2 0/direct fixed
sd1: 2049 MB, 3992 cyl, 9 head, 116 sec, 512 bytes/sect x 4197405 sectors
sd1: sync (100.0ns offset 15), 8-bit (10.000MB/s) transfers, tagged queueing

I've not tried any drives like these on my SS1 or SS1+ (ESP100)
machines, though at some point I may (the SS1 test machine's old MAXTOR
drive without tagged queuing support (async only, even) is now near death).

> I think we already have most of the buggy drives in the quirk database.

See FreeBSD's list for more.

-- 
								Greg A. Woods

+1 416 218-0098;            <g.a.woods@ieee.org>;           <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>