🚀 go-pugleaf

I have had many problems with the 3/E SCSI/ether board.

No SCSI disk except MD21/Microp works at all.  I get the following
errors: 

Sep 27 13:00
se0:  resetting scsi bus
	last phase= 0x0 ()
	csr= 0x60f  tcr= 0x0  ser= 0x80
	cbsr= 0x6d (STATUS)  cdr= 0x0  mr= 0xa  bsr= 0x90
	target= 0, lun= 0    DMA addr= 0x2000  count= 8192 (8192)
	cdb=    a  c  4d  74  10  0
sd0:  sdtimer: I/O request timeout
	last phase= 0x0 ()
	csr= 0x407  tcr= 0x0  ser= 0x80
	cbsr= 0x0 (DATA_OUT/FREE)  cdr= 0x0  mr= 0x8  bsr= 0x8
	target= 0, lun= 0    DMA addr= 0x2000  count= 8192 (8192)
	cdb=    a  c  4d  74  10  0
sd0:  failed cmd =  a  c  4d  74  10  0  
sd0 error:  sense key(0x6): unit attention,  error code(0x29): reset
           sense = 70  0  6  0  0  0  0  a  0  0  0  0  29  0  

sd0g:  write retry,  blk 591760  (abs blk 806260)
       sense key(0x6): unit attention,  error code(0x29): reset

Even with the "supported configuration" MD21 and Micropolis using the Sun
approved MD21 rev, I still get occasional errors of the form:

sd0:  failed cmd =  8  20  0  0  1  0  
sd1 error:  sense key(0x0): no sense,  error code(0x45): unknown error
           sense = 0  0  0  1  1f  12  0  0  45  4d  55  4c  45  58  

sd1c:  unknown cmd retry
       sense key(0x0): no sense,  error code(0x45): unknown error

Emulex tells me that no such error can be produced by their MD21.

I have never seen either of these problems when attaching either MD21/...
combos or embedded SCSI drive to any other Sun product.  Nor did I see
them when I tried a Sun SCSI-3 interface with the 3/E CPU.

I think that there are serious engineering problems remaining on that
board.  Sun denies this.  Has anyone out there seen these problems?

Can anyone recommend an alternative to the ETHER side of the SCSI/ETHER
board?  (If you try to boot a CPU, SCSI/ETHER and SCSI-3, the proms will
always go to the SCSI/ETHER and not the SCSI-3.  So I would prefer a
straight ether board.)