>> Well, yea, that part I thought might be different too, but I did
>> hear someone saying they had seen the bug on a SS10, so it might
>> be more general than just ESP100.  Just out of curiosity, what are
>> the effects of the bug?  Hang at boot? Panic at boot? Panic on
>> heavy usage of a tagged disk? Random lossage and data corruption?

> I believe I have a problem on an SS10 with an ESP200.

 SS5 with 1.6_BETA3 I saw message below, and system hang. This does not
happen at boot time.

| sd0(esp0:0:3:0): esp0: timed out [ecb 0xf055b0e0 (flags 0x101, dleft 0, stat 0)], <state 1, nexus 0x0, phase(l 10, c 100, p 3), resid 0, msg(q 0,o 0) >

With 1.5.3_RC2, this drive works without problem, and I notice that
there is no "tagged queueing" on dmesg.


NetBSD 1.6_BETA3 (GENERIC) #0: Wed Jun 26 22:14:09 JST 2002
    :
mainbus0 (root): SUNW,SPARCstation-5
cpu0 at mainbus0DVMA coherent : MB86907 @ 170 MHz, on-chip FPU
    :
esp0 at dma0 slot 5 offset 0x8800000 level 4: ESP200, 40MHz, SCSI ID 7
scsibus0 at esp0: 8 targets, 8 luns per target
    :
sd0 at scsibus0 target 3 lun 0: <FUJITSU, M2954E-512, 0155> SCSI2 0/direct fixed
sd0: 4149 MB, 5714 cyl, 9 head, 165 sec, 512 bytes/sect x 8498506 sectors
sd0: sync (100.0ns offset 15), 8-bit (10.000MB/s) transfers, tagged queueing
    :
sd0(esp0:0:3:0): esp0: timed out [ecb 0xf055b0e0 (flags 0x101, dleft 0, stat 0)], <state 1, nexus 0x0, phase(l 10, c 100, p 3), resid 0, msg(q 0,o 0) >



NetBSD 1.5.3_RC2 (FIR1) #0: Fri May 24 16:05:13 JST 2002
    :
esp0 at dma0 slot 5 offset 0x8800000 level 4: ESP200, 40MHz, SCSI ID 7
scsibus0 at esp0: 8 targets, 8 luns per target
    :
probe(esp0:3:0): max sync rate 10.00MB/s
sd0 at scsibus0 target 3 lun 0: <FUJITSU, M2954E-512, 0155> SCSI2 0/direct fixed
sd0: 4149 MB, 5714 cyl, 9 head, 165 sec, 512 bytes/sect x 8498506 sectors

-mochid