public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: dougg@torque.net
Cc: "Darrick J. Wong" <djwong@us.ibm.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: aic94xx driver woes
Date: Mon, 02 Apr 2007 19:37:32 -0500	[thread overview]
Message-ID: <1175560652.3680.92.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <46119396.3070008@torque.net>

On Mon, 2007-04-02 at 19:36 -0400, Douglas Gilbert wrote:
> > echo 1 > /sys/class/sas_phy/phy-X:3/link_reset
> > 
> > and see if it just produces 
> > 
> > aic94xx: scb:0x80 timed out
> 
> Yes it does.
> 
> > Again?
> 
> It is repeatable.
> 
> Also when I connect to phy 0 it works (both direct
> connect and expander). However phys 1 and 2 react
> like phy 3 shown above.

OK, well, I know what it is, I just don't know how to fix it.

On certain error conditions, whatever controls the phy SCB processing
seems to freeze to a particular phy.  With me, it's externally induced
(an expander->expander->satapi configuration).  I can recover my system
by powering off and on the expander setup.

Whatever this condition is, it blows away all error recovery, since
they're also done via means of ascbs, so any error recovery ascbs also
get stuck until they timeout.  Someone with the specs needs to look and
see if there's a way we can kick the phy queue (or whatever queue it's
stuck in)---I'm assuming it's a phy queue because I can get packets out
via other phys, just nothing via the stuck one.

James



      reply	other threads:[~2007-04-03  0:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-31 16:48 aic94xx driver woes Douglas Gilbert
2007-03-31 17:28 ` James Bottomley
2007-03-31 18:01 ` Darrick J. Wong
2007-03-31 19:05   ` Douglas Gilbert
2007-03-31 23:17     ` James Bottomley
2007-04-01 20:29       ` Douglas Gilbert
2007-04-02 17:52         ` James Bottomley
2007-04-02 23:36           ` Douglas Gilbert
2007-04-03  0:37             ` James Bottomley [this message]

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=1175560652.3680.92.camel@mulgrave.il.steeleye.com \
    --to=james.bottomley@steeleye.com \
    --cc=djwong@us.ibm.com \
    --cc=dougg@torque.net \
    --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