public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: Jeff Johnson <jeff.johnson@aeoncomputing.com>,
	Linux SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Suggestions for testing SAS cables via sg3_utils
Date: Wed, 18 Mar 2015 16:14:01 -0400	[thread overview]
Message-ID: <5509DC89.9030506@interlog.com> (raw)
In-Reply-To: <5509D10F.2020601@aeoncomputing.com>

On 15-03-18 03:25 PM, Jeff Johnson wrote:
> Greetings,
>
> Does anyone have an effective way of testing SAS cabling in a Linux
> environment without using a block storage device?
>
> Something like reading/writing to a buffer in an expander (LSI). Something
> that could stress all four lanes of a multilane cable. Like a SAS equivalent of
> a floodping between a SAS initiator and a SAS expander to stress the cable.

Jeff,
For SAS targets you could use sg_senddiag (sg3_utils)
to put one or more phys in test/training mode. In
the sg3_utils examples directory there are some
templates (e.g. sdiag_sas_p0_cjtpat.txt). [See
spl4r02.pdf section 9.2.9.2]

For expander phys you might use smp_phy_test to put one
or more in test/training mode. I'm not aware of a SCSI
loopback test in which the remote end is an expander ***.
[See spl4r02.pdf section 9.4.3.29]

On a 4 wide cable between a HBA and an expander with a
SAS disk beyond you might put 3 of those expander phys in
training mode then to to use READ BUFFER on the echo buffer
in the disk. The SCSI command should squeeze through on
the remaining path. Then rotate which phy is the "clear"
path.

My guess is initiator phys can also be put in training mode.
If so that would involve some LLD specific action.

Doug Gilbert


*** checked two LSI expanders (one SAS-2, the other SAS-3)
     and they don't support the SCSI READ BUFFER command on
     the SES target that is connected to a virtual expander
     phy. Might be useful if they did.



      reply	other threads:[~2015-03-18 20:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 19:25 Suggestions for testing SAS cables via sg3_utils Jeff Johnson
2015-03-18 20:14 ` Douglas Gilbert [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=5509DC89.9030506@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=jeff.johnson@aeoncomputing.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