public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: malahal@us.ibm.com
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: AIC94XX discovery timeout problem details...
Date: Wed, 4 Oct 2006 17:21:16 -0700	[thread overview]
Message-ID: <20061005002116.GA16678@us.ibm.com> (raw)
In-Reply-To: <1158701551.4170.50.camel@mulgrave.il.steeleye.com>

James, Jack Hammer from Adaptec gave us SAS analyser output.  All SMP
commands work fine, but SSP commands are sent on a PHY that is up and
updated (in the DDB0). In response, the expander tries to open
connection on a different PHY that is up but not yet updated in DDB0.
The HBA sends OPEN_REJECT(retry) and the Vitesse expander retries the
same path forever!

Thanks, Malahal.

James Bottomley [James.Bottomley@SteelEye.com] wrote:
> However, SAS specs require us to open connections for SMP and receive
> the responses through the connection we opened.  The target is
> specifically prohibited from responding outside of this protocol
> boundary.  The theory behind this is that the Host controls port
> formation ... until we open multiple connections between the source and
> target ports, the actual connection remains narrow.  All of this should
> support the current discovery model.
> 
> I suppose the only way to confirm what's going on would be with a SAS
> analyser.  Does the host send multiple OPEN's even before the
> PORTE_BYTES_DMAED is responded to?
> 
> James
> 

  reply	other threads:[~2006-10-05  0:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15  7:20 AIC94XX discovery timeout problem details malahal
2006-09-18  7:35 ` Luben Tuikov
2006-09-19 20:59   ` malahal
2006-09-19 21:32     ` James Bottomley
2006-10-05  0:21       ` malahal [this message]
2006-09-20 14:55     ` Luben Tuikov

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=20061005002116.GA16678@us.ibm.com \
    --to=malahal@us.ibm.com \
    --cc=James.Bottomley@SteelEye.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