From: Andy Warner <andyw@pobox.com>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: Andy Warner <andyw@pobox.com>, Muli Ben-Yehuda <muli@il.ibm.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: aic94xx IO errors with "escb_tasklet_complete: phy0: REQ_TASK_ABORT"
Date: Wed, 4 Oct 2006 14:31:54 -0500 [thread overview]
Message-ID: <20061004143154.A29888@florence.linkmargin.com> (raw)
In-Reply-To: <452415AE.7030202@us.ibm.com>; from djwong@us.ibm.com on Wed, Oct 04, 2006 at 01:12:30PM -0700
Darrick J. Wong wrote:
> Andy Warner wrote:
>
> > So you are seeing legitimate REQ_TASK_ABORT values, but need to look
> > at the remaining data to see what the chip is trying to tell you.
> > For REQ_TASK_ABORT, status_block[1..2] is the transaction context,
> > and status_block[3] is the reason (TC_NO_ERROR etc from aic94xx_sas.h)
>
> Funny, I've been trying to write at least a REQ_TASK_ABORT handler all
> week. I'm having a bit of trouble using the transaction context...
> mostly because the value I'm getting doesn't correspond to any ascb.
> Assuming, of course, that ascb->scb->header.index/ascb->tc_index are
> indeed transaction contexts.
Check you're actually getting REQ_TASK_ABORT, and not
REQ_DEVICE_RESET or SIGNAL_NCQ_ERROR, where the same
field is a connection handle, and not a transaction
context.
--
andyw@pobox.com
Andy Warner Voice: (612) 801-8549 Fax: (208) 575-5634
next prev parent reply other threads:[~2006-10-04 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 16:44 aic94xx IO errors with "escb_tasklet_complete: phy0: REQ_TASK_ABORT" Muli Ben-Yehuda
2006-10-04 18:29 ` Andy Warner
2006-10-04 20:12 ` Darrick J. Wong
2006-10-04 19:31 ` Andy Warner [this message]
2006-10-04 20:56 ` Muli Ben-Yehuda
2006-10-04 21:11 ` James Bottomley
2006-10-05 21:55 ` Muli Ben-Yehuda
2006-10-05 22:11 ` Darrick J. Wong
2006-10-16 19:51 ` Muli Ben-Yehuda
2006-10-16 20:00 ` James Bottomley
2006-10-16 20:47 ` Muli Ben-Yehuda
2006-10-05 0:50 ` Darrick J. Wong
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=20061004143154.A29888@florence.linkmargin.com \
--to=andyw@pobox.com \
--cc=James.Bottomley@SteelEye.com \
--cc=djwong@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=muli@il.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.