From: Jeremy Higdon <jeremy@sgi.com>
To: "Moore, Eric Dean" <Emoore@lsil.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Masao Fukuchi <fukuchi.masao@jp.fujitsu.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [RFC][PATCH]SCSI signal(I/O) failure causes no response
Date: Thu, 22 Apr 2004 21:44:36 -0700 [thread overview]
Message-ID: <20040423044436.GA881054@sgi.com> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E570442C1B2@exa-atlanta.se.lsil.com>
On Wed, Apr 14, 2004 at 11:56:20AM -0400, Moore, Eric Dean wrote:
> For this particular issue, Mr Masao Fukuchi has a
> scsi bus test analyzer, in which he set the C/D signal
> to low during read operation. The MPT firmware
> returned MPI_IOCSTATUS_SCSI_PROTOCAL_ERROR, which from
> the mpt manual means " An unrecoverable bus protocal error
> as terminated the SCSI I/O" and the driver will
> return DID_RESET.
>
> Here are some of the other cases which return
> DID_RESET, however I doubt were returned with
> Mr Masao Fukuchi's test anaylzer:
>
> MPI_IOCSTATUS_SCSI_TASK_TERMINATED
> MPI_IOCSTATUS_SCSI_IOC_TERMINATED
> MPI_IOCSTATUS_SCSI_EXT_TERMINATED
I think I would return DID_ERROR for things like that as a sort
of generic "something-went-wrong" on the SCSI bus.
jeremy
next prev parent reply other threads:[~2004-04-23 4:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 15:56 [RFC][PATCH]SCSI signal(I/O) failure causes no response Moore, Eric Dean
2004-04-15 5:24 ` Masao Fukuchi
2004-04-23 4:44 ` Jeremy Higdon [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-15 14:51 Moore, Eric Dean
2004-04-16 1:29 ` Masao Fukuchi
2004-04-14 15:23 Moore, Eric Dean
2004-04-14 1:07 Masao Fukuchi
2004-04-14 15:28 ` 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=20040423044436.GA881054@sgi.com \
--to=jeremy@sgi.com \
--cc=Emoore@lsil.com \
--cc=James.Bottomley@SteelEye.com \
--cc=fukuchi.masao@jp.fujitsu.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