Hi all,

I've recently replaced the drive in my Axil 320 (SS20 clone) running NetBSD
2.0.2. The new disk is a Seagate ST34572W with a 68-to-50 pin converter
(the Axil has regular 50-pin narrow SCSI rather than the SS20's SCA).

After the replacement I got a few kernel panics like the following:
Apr 29 11:43:52 sign /netbsd: esp0: illegal command: 0x0 (state 2, phase 4, prevphase 0)
Apr 29 11:43:53 sign /netbsd: sd0: async, 8-bit transfers
Apr 29 11:49:10 sign /netbsd: esp0: unexpected bus phase; resetting
Apr 29 11:50:35 sign /netbsd: esp0: unexpected bus phase; resetting
Apr 29 11:54:43 sign last message repeated 2 times
Apr 29 12:00:04 sign last message repeated 16 times
Apr 29 12:00:05 sign /netbsd: esp0: invalid state: 7 [intr 10, phase(c 7, p 7)]
Apr 29 12:00:07 sign /netbsd: esp0: unexpected bus phase; resetting
Apr 29 12:00:55 sign last message repeated 4 times
Apr 29 12:02:28 sign last message repeated 9 times
Apr 29 12:02:39 sign /netbsd: esp0: invalid state: 7 [intr 10, phase(c 7, p 7)]
Apr 29 12:02:41 sign /netbsd: esp0: unexpected bus phase; resetting
Apr 29 12:02:44 sign /netbsd: esp0: unexpected bus phase; resetting
Apr 29 12:02:44 sign /netbsd: esp0 at line 1934: unexpected MESSAGE OUT phase
Apr 29 12:02:45 sign /netbsd: esp0: unexpected bus phase; resetting
Apr 29 12:02:59 sign last message repeated 4 times
Apr 29 12:02:59 sign /netbsd: esp0 at line 1934: unexpected MESSAGE OUT phase
Apr 29 12:03:04 sign /netbsd: esp0: unexpected bus phase; resetting
Apr 29 12:03:30 sign last message repeated 5 times
Apr 29 12:03:31 sign /netbsd: esp0: invalid state: 7 [intr 10, phase(c 7, p 7)]
Apr 29 12:03:33 sign /netbsd: esp0: unexpected bus phase; resetting
Apr 29 12:03:37 sign /netbsd: esp0 at line 1934: unexpected MESSAGE OUT phase
Apr 29 12:03:37 sign /netbsd: esp0: unexpected bus phase; resetting
Apr 29 12:04:01 sign last message repeated 8 times
Apr 29 12:04:02 sign /netbsd: esp0: invalid state: 7 [intr 10, phase(c 7, p 7)]
Apr 29 12:04:32 sign /netbsd: esp0: unexpected bus phase; resetting
Apr 29 12:04:33 sign /netbsd: esp0 at line 1934: unexpected MESSAGE OUT phase
Apr 29 12:04:34 sign /netbsd: esp0: unexpected bus phase; resetting
Apr 29 12:04:55 sign last message repeated 4 times
Apr 29 12:05:03 sign /netbsd: esp0 at line 1934: unexpected MESSAGE OUT phase
Apr 29 12:05:05 sign /netbsd: sd0(esp0:0:0:0):  Check Condition on CDB: 0x2a 00 00 53 eb 10 00 00 04 00
Apr 29 12:05:05 sign /netbsd:     SENSE KEY:  Illegal Request
Apr 29 12:05:07 sign /netbsd:      ASC/ASCQ:  Illegal Field in CDB
Apr 29 12:05:08 sign /netbsd:      FRU CODE:  0x1
Apr 29 12:05:12 sign /netbsd:          SKSV:  Error in CDB, Offset 5, bit 7
Apr 29 12:05:16 sign /netbsd: 
Apr 29 12:05:16 sign /netbsd: esp0: unexpected bus phase; resetting
Apr 29 12:05:19 sign /netbsd: esp0: unexpected bus phase; resetting
Apr 29 12:05:19 sign /netbsd: esp0 at line 1934: unexpected MESSAGE OUT phase
Apr 29 12:05:21 sign /netbsd: esp0: unexpected bus phase; resetting
Apr 29 12:05:23 sign last message repeated 8 times
Apr 29 12:05:23 sign /netbsd: esp0: invalid state: 7 [intr 10, phase(c 7, p 7)]
Apr 29 12:05:23 sign /netbsd: esp0: unexpected bus phase; resetting

dmesg snippet:
dma0 at sbus0 slot 15 offset 0x400000: DMA rev 2
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: <SEAGATE, ST34572W, 0718> disk fixed
sd0: 4340 MB, 6300 cyl, 8 head, 176 sec, 512 bytes/sect x 8888924 sectors
sd0: sync (100.00ns offset 15), 8-bit (10.000MB/s) transfers, tagged queueing

This happened a few times, but since I disabled parity on the drive, the
machine seems to be running fine. I'm just a little worried that disabling
parity is a Bad Thing(tm). Any thoughts on this? Is it OK to leave the
drive with parity disabled, or should I rather dig out a narrow drive and
use that instead (not sure if the 68-to-50 converter is causing trouble).

-mj
-- 
Michael-John Turner | http://mj.turner.org.za/
mj@turner.org.za    | Open Source in WC ZA - http://www.clug.org.za/