Re: timeout during sas discovery (aic94xx)

[Mike Anderson <andmike@us.ibm.com>]

James Bottomley <James.Bottomley@SteelEye.com> wrote:
> On Tue, 2006-08-29 at 09:03 -0700, Mike Anderson wrote:
> > I think this failure mode is a different path than what your patch tries to
> > address. We sending a inquiry to the device and coming through the
> > standard IO path and not through sas_execute_task.
> > 
> > I still think for these cases that we need to be running the patch I
> > previous sent to the list to try and get the abort to work (this patch is
> > not in the git tree so one needs to add this on top of the git source).
> > This will not solve the timeout, but would at least address the tmf time
> > out.
> 
> OK ... I was waiting for Adaptec to comment on that one since it's
> messing with undocumented sequencer bits.  However, prove it works in
> this case and I can put it in.

ok, yes it would be good for Adaptec to comment on the proper format for
the abort_hscb as add I did was set the values to match what the adp
driver was doing as the aic94xx abort_task always timed out for our cases.

> 
> > We need to also address the first issue of the inquiry timeout. Previous
> > runs showed that we where hitting this error a lot on the inquiry to the
> > Vitesse SES device which the adp driver has created a work around (unclear
> > if the work around solves the issue or not).
> 
> What is the work around?

Link reset wait 4 seconds and then retry. Since this is a timeout on a
scan inquiry getting a retry to happen in scsi_probe_lun once the error
handler has started up will not be easy.

-andmike
--
Michael Anderson
andmike@us.ibm.com