----- Original Message -----
From: "Kenn Humborg" <[EMAIL PROTECTED]>
To: "Eric Youngdale" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, May 13, 2000 1:21 PM
Subject: Re: DEC RZ55 and Advansys ABP3925
> On Sat, May 13, 2000 at 11:43:38AM -0400, Eric Youngdale wrote:
> >
> > I don't have any good ideas here - are you saying that with the
logging
> > enabled the timeouts don't occur?
>
> With logging enabled, the result code in scan_scsis_done is 0x25040000,
> and no error recovery is performed. Total time to scan one device ID
> is about 0.5secs.
This corresponds to SUGGEST_ABORT | DRIVER_INVALID | DID_BAD_TARGET.
This is a reasonable response given what you have described (although we
shouldn't be trying to abort the command if we actually did get a proper
response back from the host - it looks like we might do the right thing,
however).
> With no (or less) logging, the result code is 26030000, and scsi_error.c
> goes into error recovery mode. Total time to scan is about 5 secs.
And this corresponds to SUGGEST_ABORT | DRIVER_TIMEOUT | DID_TIME_OUT
This doesn't make much sense to me. In the event that logging is turned
off, you should also be getting the DID_BAD_TARGET message, but you are not.
I guess I can suggest tossing some printk in both advansys.c and in
scsi_old_done in scsi_obsolete.c, and try and narrow down more about the
sequence of events. You can reduce the amount of spew by ignoring status
results of 0 - that is what you would get for normal completion of a
command.
-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
