From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Alexander Feigl <Alexander.Feigl@gmx.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: aic7xxx SCSI system hangs
Date: Thu, 11 Oct 2001 13:15:21 -0600 [thread overview]
Message-ID: <200110111915.f9BJFLY97700@aslan.scsiguy.com> (raw)
In-Reply-To: Your message of "11 Oct 2001 14:58:13 +0200." <1002805093.3593.9.camel@PowerBox.MysticWorld.de>
>Hi
>
>Sorry for my incomplete console output yesterday.
Not a problem.
Here's the interesting part...
>scsi0:0:2:0: Attempting to queue an ABORT message
>scsi0: Dumping Card State in Command phase, at SEQADDR 0xbf
The sequencer believes that the last, REQ qualified, phase was
the command phase.
>ACCUM = 0x80, SINDEX = 0xa0, DINDEX = 0xe4, ARG_2 = 0x0
>HCNT = 0xa
We're setup to send a 10byte cdb(command) to the target. No bytes of
the cdb have yet been transfered.
>SCSISEQ = 0x12, SBLKCTL = 0xa
> DFCNTRL = 0x24, DFSTATUS = 0x80
The data fifo is all set to send data...
>LASTPHASE = 0x80, SCSISIGI = 0x44, SXFRCTL0 = 0x80
^^^^
But what's this? The target has us in data-in phase.
>SSTAT0 = 0x0, SSTAT1 = 0x3
But this phase, according to the hardware, was never qualified by
a REQ, so we never see this change and fall out of the loop that is
trying to process the command phase.
To sum up, from time to time, the controller sees the first REQ for
the data-in phase that follows the command phase, prior to seeing the
phase lines change to data-in. This is either caused by the plextor
not allowing the proper bus-settle time for the phase change to be
seen prior to asserting REQ *OR* your cabling is poor (too long,
marginal/bent pin, incorrect termination, etc.) giving a similar
result.
As for why you cannot talk to the device after a while, the device
has been set offline. The controller was unable to talk to it
successfully, so the SCSI layer decided to ignore it.
--
Justin
next prev parent reply other threads:[~2001-10-11 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 14:03 Alexander Feigl
2001-10-10 16:22 ` Justin T. Gibbs
2001-10-10 19:36 ` Alexander Feigl
2001-10-10 20:27 ` Justin T. Gibbs
2001-10-11 12:58 ` Alexander Feigl
2001-10-11 19:15 ` Justin T. Gibbs [this message]
2001-10-11 19:44 ` Alexander Feigl
2001-10-11 19:59 ` Justin T. Gibbs
2001-10-10 17:47 ` Cliff Albert
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=200110111915.f9BJFLY97700@aslan.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=Alexander.Feigl@gmx.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®