From: Mike Anderson <andmike@us.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Tarte, Robert" <Robert_Tarte@adaptec.com>,
"Hammer, Jack" <Jack_Hammer@adaptec.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Need help with another aic94xx sequencer problem
Date: Tue, 22 Aug 2006 16:58:20 -0700 [thread overview]
Message-ID: <20060822235820.GA19794@us.ibm.com> (raw)
In-Reply-To: <1156286656.21487.0.camel@mulgrave.il.steeleye.com>
James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> On Tue, 2006-08-22 at 13:53 -0700, Mike Anderson wrote:
> > Does this help any? While Alexis and I where working on a expander timeout
> > issue the abort was never working for us. I compared the adp abort and the
> > aic94xx abort code and made these changes. This appears to make the abort
> > work for us now. A few lines of the changes are not related to the abort.
> > YMMV, a better solution would be to know the exact format of the abort.
>
> Actually, no. I still seem to get the same problem (at least it BUGs in
> the same place ... I haven't dug down to see if I'm getting the same
> return value).
Well the adp driver had a comment that the 0x1D error code means that it
cannot find the command in its execution queue as it already has sent the
command to the target(if I mapped this right between the two drivers).
What looks odd is in the adp driver that move to a higher level of
recovery (i.e., lun reset) if they receive this code, but in the aic94xx
we mark the task TMF_RESP_FUNC_COMPLETE which appears wrong as you found
out with the BUG_ON.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2006-08-22 23:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 20:28 Need help with another aic94xx sequencer problem James Bottomley
2006-08-22 20:44 ` Tarte, Robert
2006-08-22 20:53 ` Mike Anderson
2006-08-22 22:44 ` James Bottomley
2006-08-22 23:58 ` Mike Anderson [this message]
2006-08-24 9:08 ` Luben Tuikov
2006-08-24 8:58 ` Luben Tuikov
2006-08-24 14:22 ` James Bottomley
2006-08-28 3:26 ` James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060822235820.GA19794@us.ibm.com \
--to=andmike@us.ibm.com \
--cc=Jack_Hammer@adaptec.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Robert_Tarte@adaptec.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox