Subject: esiop(4) problem with Symbios Logic 53c896
To: NetBSD current list <current-users@netbsd.org>
From: Andreas Wrede <andreas@planix.com>
List: current-users
Date: 07/18/2003 21:56:05
I am trying to upgrade an HP Server from NetBSD 1.5.4_ALPHA to
1.6.2_STABLE but the esiop(4) driver has problems probing the attached
SCSI drives. The relevant messages are:

siop0 at pci1 dev 6 function 0: Symbios Logic 53c896 (ultra2-wide scsi)
esiop0: using on-board RAM
esiop0: interrupting at irq 5
scsibus0 at esiop0: 16 targets, 8 luns per target
esiop1 at pci1 dev 6 function 1: Symbios Logic 53c896 (ultra2-wide scsi)
esiop1: using on-board RAM
esiop1: interrupting at irq 5
scsibus1 at esiop1: 16 targets, 8 luns per target

and

scsibus0: waiting 2 seconds for devices to settle...
probe(esiop0:0:0:0): unhandled message 0x4
probe(esiop0:0:0:0): unhandled message 0x3
esiop0: DMA IRQ: Illegal instruction dma fifo empty, DSP=0x720 DSA=0x356f000: T/L/Q=0/0/-1 last msg_in=0x1 status=0xff
esiop0: scsi bus reset
probe(esiop0:0:0:0): command with tag id -1 reset
probe(esiop0:0:0:0): unhandled message 0x4
probe(esiop0:0:0:0): unhandled message 0x3
esiop0: DMA IRQ: Illegal instruction dma fifo empty, DSP=0x720 DSA=0x356f0ec: T/L/Q=0/0/-1 last msg_in=0x1 status=0xff
esiop0: scsi bus reset

which continues 8 more times for the first drive, one the DSA= values
changes. For the other 5 drives I get similar messages.

The machine is running fine with NetBSD 1.5.4. The relevant messages
there are:

siop0 at pci1 dev 6 function 0: Symbios Logic 53c896 (ultra2-wide scsi)
siop0: using on-board RAM
siop0: interrupting at irq 5
scsibus0 at siop0: 16 targets, 8 luns per target
siop1 at pci1 dev 6 function 1: Symbios Logic 53c896 (ultra2-wide scsi)
siop1: using on-board RAM
siop1: interrupting at irq 5
scsibus1 at siop1: 16 targets, 8 luns per target

and

scsibus0: waiting 2 seconds for devices to settle...
siop0: target 0 using 8bit transfers
siop0: target 0 now synchronous at 20.0Mhz, offset 15
siop0: target 0 using tagged queuing
sd0 at scsibus0 target 0 lun 0: <COMPAQ, AB01831AC4, 3A05> SCSI2 0/direct fixed
siop0: target 0 using 16bit transfers
siop0: target 0 now synchronous at 20.0Mhz, offset 15
sd0: 17366 MB, 7001 cyl, 20 head, 254 sec, 512 bytes/sect x 35566000 sectors
siop0: target 1 using 8bit transfers
siop0: target 1 now synchronous at 20.0Mhz, offset 15
siop0: target 1 using tagged queuing
sd1 at scsibus0 target 1 lun 0: <COMPAQ, AB01831AC4, 3A05> SCSI2 0/direct fixed
siop0: target 1 using 16bit transfers
siop0: target 1 now synchronous at 20.0Mhz, offset 15
sd1: 17366 MB, 7001 cyl, 20 head, 254 sec, 512 bytes/sect x 35566000 sectors
siop0: target 2 using tagged queuing
sd2 at scsibus0 target 2 lun 0: <COMPAQ, AB0183346B, 3A05> SCSI2 0/direct fixed
siop0: target 2 using 16bit transfers
siop0: target 2 now synchronous at 20.0Mhz, offset 31
sd2: 17366 MB, 7001 cyl, 20 head, 254 sec, 512 bytes/sect x 35566000 sectors
siop0: target 3 using 8bit transfers
siop0: target 3 now synchronous at 20.0Mhz, offset 31
siop0: target 3 using tagged queuing
sd3 at scsibus0 target 3 lun 0: <COMPAQ, HB01831B95, A195> SCSI2 0/direct fixed
siop0: target 3 using 16bit transfers
siop0: target 3 now synchronous at 20.0Mhz, offset 31
sd3: 17366 MB, 7001 cyl, 20 head, 254 sec, 512 bytes/sect x 35566000 sectors
ses0 at scsibus0 target 5 lun 0: <HP, SAFTE; U160/M BP, 1021> SCSI2 3/processor fixed
ses0: SAF-TE Compliant Device
siop0: target 8 using tagged queuing
sd4 at scsibus0 target 8 lun 0: <IBM, DNES-318350Y, SAH0> SCSI3 0/direct fixed
siop0: target 8 using 16bit transfers
siop0: target 8 now synchronous at 20.0Mhz, offset 31
sd4: 17501 MB, 11474 cyl, 10 head, 312 sec, 512 bytes/sect x 35843670 sectors
scsibus1: waiting 2 seconds for devices to settle...
siop1: target 0 using tagged queuing
sd5 at scsibus1 target 0 lun 0: <QUANTUM, ATLAS10K2-TY184L, DDD6> SCSI3 0/direct fixed
siop1: target 0 using 16bit transfers
siop1: target 0 now synchronous at 20.0Mhz, offset 31
sd5: 17510 MB, 17338 cyl, 5 head, 413 sec, 512 bytes/sect x 35860910 sectors


Note that the siop(4) driver probes the drives at 20Mhz, the esiop(4)
should probe them at 40Mhz.



-- 
    - aew