>On Apr  9,  9:15am, Greg Wohletz wrote:
>> Apr  9 08:03:44 lazy /netbsd: asc_get_status: cmdreg 11, fifo cnt 7
>
>  Haven't we been here before?

Yep, got these occasionally under 1.2F and friends, but it has gotten
significantly worse under 1.3.1 for some reason.

>
>> Apr  9 08:03:44 lazy /netbsd: rz0: Illegal request, blk 3452431
>...
>> What does this mean?  I'm quite certain that the drives themselves are OK.
>
>  The first message indicates that the ASC driver got to the status phase
>of a SCSI operation and has 7 bytes of data sitting in the 53c94 chip.
>There should only be 2 - the status byte and the message byte.  The message
>following that would appear to be the results of a request sense in
>response to a "check-condition" status.

Is there any possibility that bad bus termination  could cause this?

>  I would like to see the results on a kernel compiled with DEBUG - that
>includes a trace dump of the ASC driver interrupts up to that point which
>can give me an idea of what the device and driver did up to that point.

Unfortunately the kernel compiled with DEBUG fails in a differant manner
and ends up crashing during fsck...  Here is what it said before it did:

rz0 at asc0 drive 0 slave 0 SEAGATE ST42100 rev 8224
rz0: 1812MB, 2574 cyl, 15 head, 96 sec, 512 bytes/sect x 3711990 sectors
rz1 at asc0 drive 1 slave 0 SEAGATE ST42100 rev 8224
rz1: 1812MB, 2574 cyl, 15 head, 96 sec, 512 bytes/sect x 3711990 sectors
rconsattach: 1 raster consoles
boot device: rz0
root on rz0a dumps on rz1b
mountroot: trying ffs...
root file system type: ffs
init: copying out flags `-s' 3
init: copying out path `/sbin/init' 11
asc_timeout: cmd 0x8011ecc0 drive 1
asc: asc_timeout: cmd 28 bn 732000 cnt 96
asc0 tgt 1 status 81 ss c4 ir 10 cond 18:110 msg 12 resid 1024
asc0 tgt 1 status 93 ss cc ir 10 cond 1:310 msg 90 resid 0
asc0 tgt 1 status 97 ss cc ir 8 cond 7:708 msg 0 resid 0
asc0 tgt 1 status 90 ss cc ir 20 cond 8:20 msg 12 resid 0
asc0 tgt 0 status 0 ss 0 ir 28 cond 0:118 msg c0 resid 8192
asc0 tgt 0 status 91 ss c4 ir 18 cond 0:118 msg c2 resid 8192
asc0 tgt 0 status 93 ss cc ir 10 cond 1:310 msg 90 resid 0
asc0 tgt 0 status 97 ss cc ir 8 cond 7:708 msg 0 resid 0
asc0 tgt 0 status 90 ss cc ir 20 cond 8:20 msg 12 resid 0
asc0 tgt 1 status 0 ss 0 ir 28 cond 0:118 msg c0 resid 49152
asc0 tgt 1 status 97 ss 8c ir 18 cond 0:118 msg c2 resid 0
asc0 tgt 1 status 97 ss 8c ir 8 cond 9:708 msg 4 resid 0
asc0 tgt 1 status 90 ss cc ir 20 cond 15:20 msg 12 resid 0
asc0 tgt -1 status 97 ss 9c ir c cond 16:700 msg 80 resid 0
asc0 tgt 1 status 91 ss c4 ir 10 cond 17:110 msg 12 resid 49152
asc0 tgt 1 status 87 ss 8c ir 10 cond 2:110 msg 90 resid 16164
asc0 tgt 1 status 87 ss 8c ir 8 cond 9:708 msg 2 resid 0
asc0 tgt 1 status 87 ss 8c ir 10 cond 10:710 msg 12 resid 0
asc0 tgt 1 status 87 ss 8c ir 8 cond 9:708 msg 4 resid 0
asc0 tgt 1 status 80 ss cc ir 20 cond 15:20 msg 12 resid 0
asc0 tgt -1 status 87 ss 9c ir c cond 16:700 msg 80 resid 0
asc0 tgt 1 status 81 ss c4 ir 10 cond 18:110 msg 12 resid 16164
asc0 tgt 1 status 87 ss 8c ir 10 cond 2:110 msg 90 resid 13092
asc0 tgt 1 status 87 ss 8c ir 8 cond 9:708 msg 2 resid 0
asc0 tgt 1 status 87 ss 8c ir 10 cond 10:710 msg 12 resid 0
asc0 tgt 1 status 87 ss 8c ir 8 cond 9:708 msg 4 resid 0
asc0 tgt 1 status 80 ss cc ir 20 cond 15:20 msg 12 resid 0
asc0 tgt -1 status 87 ss 9c ir c cond 16:700 msg 80 resid 0
asc0 tgt 1 status 81 ss c4 ir 10 cond 18:110 msg 12 resid 13092
asc0 tgt 1 status 87 ss 8c ir 10 cond 2:110 msg 90 resid 8484
asc0 tgt 1 status 87 ss 8c ir 8 cond 9:708 msg 2 resid 0
asc0 tgt 1 status 87 ss 8c ir 40 cond 10:710 msg 10 resid 0
rebooting...


The errors I get with the not debug kernel don't mention any timeouts.

							--Greg