Tim Rightnour wrote:

> I booted my LX164 alpha with -current as of yesterday to try something out..
> and got the following error out of the siop controller..
> 
> I've never seen this before thorpej-scsipi went in..  just a random glitch?
> 
> 
> 
> siop0 at pci0 dev 9 function 0: Symbios Logic 53c810a (fast scsi)
> siop0: interrupting at eb164 irq 3
> scsibus0 at siop0: 8 targets, 8 luns per target
> scsibus0: waiting 2 seconds for devices to settle...
> sd0 at scsibus0 target 0 lun 0: <IBM, CFA170S       !S, 167A> SCSI2 0/direct
> fixed
> sd0: 163 MB, 2111 cyl, 2 head, 79 sec, 512 bytes/sect x 335270 sectors
> sd0: Sync (100.0ns offset 8), 8-bit (10.000MB/s) transfers
> st0 at scsibus0 target 1 lun 0: <EXABYTE, EXB-8500SMBANXH1, 0458> SCSI2
> 1/sequential removable
> st0: drive empty
> st0: Async, 8-bit transfers
> st0(siop0:0:1:0):  Check Condition on CDB: 0x00 00 00 00 00 00
>     SENSE KEY:  Aborted Command
>      ASC/ASCQ:  Message Error
> 
> sd2 at scsibus0 target 2 lun 0: <IBM, CFA170S       !S, 167A> SCSI2 0/direct
> fixed

Heh, I just sent a message to port-alpha about exabytes on siop.  I see

	st1 at scsibus0 target 6 lun 0: <DEC, TKZ09   90097000, 045H> SCSI2 1/sequential removable
	st1: drive empty
	siop0: target 6 asynchronous
	probe(siop0:6:1):  Check Condition on CDB: 0x00 20 00 00 00 00
	    SENSE KEY:  Aborted Command
	     ASC/ASCQ:  Message Error

on boot, and AFAICR I only get the "Check Condition" message when the
drive is empty.  This is on vanilla 1.5 and not -current.

Simon.
--
Simon Burge                            <simonb@wasabisystems.com>
NetBSD CDs, Support and Service:    http://www.wasabisystems.com/