From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: ltuikov@yahoo.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: Thu, 24 Aug 2006 09:22:49 -0500 [thread overview]
Message-ID: <1156429369.1024.14.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20060824085841.27630.qmail@web31810.mail.mud.yahoo.com>
On Thu, 2006-08-24 at 01:58 -0700, Luben Tuikov wrote:
> The sequencer response is correct but incomplete. The interpretation
> is a bad compromize between SSP and STP.
>
> TF_TMF_NO_CTX should be interpreted as TMF_RESP_FUNC_ESUPP to get
> "best of both worlds", and then upper layers would do the proper
> thing depending on the protocol.
OK ... I can do that easily; that should cause the error handler to try
with a bigger hammer.
The next problem is that this actual issue is occurring in
sas_execute_task() which takes no further action if an abort fails. I
can easily wire in a next level ... would you recommend CLEAR_TASK_SET,
or move straight on to LOGICAL_UNIT_RESET?
James
> Of course your version of my code and my version of my code differ
> somewhat.
>
> The fix in the sequencer is messy as is the fix in software.
>
next prev parent reply other threads:[~2006-08-24 14:22 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
2006-08-24 9:08 ` Luben Tuikov
2006-08-24 8:58 ` Luben Tuikov
2006-08-24 14:22 ` James Bottomley [this message]
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=1156429369.1024.14.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@hansenpartnership.com \
--cc=Jack_Hammer@adaptec.com \
--cc=Robert_Tarte@adaptec.com \
--cc=linux-scsi@vger.kernel.org \
--cc=ltuikov@yahoo.com \
/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