From: James Bottomley <James.Bottomley@suse.de>
To: Jeff Johnson <jeff.johnson@aeoncomputing.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Is it possible to issue device reset to PMC PM8388 expander using sg3_utils or smp_utils?
Date: Thu, 09 Dec 2010 12:59:52 -0600 [thread overview]
Message-ID: <1291921192.3002.339.camel@mulgrave.site> (raw)
In-Reply-To: <4D0122BC.8060501@aeoncomputing.com>
On Thu, 2010-12-09 at 10:41 -0800, Jeff Johnson wrote:
> Greetings,
>
> Is it possible to issue a low level device reset to a PMC-Sierra PM8388
> 24x3G SAS expander using either sg3_utils or smp_utils?
>
> I am able to enumerate and read the status of the phys on the PM8388,
> read end device information, etc. I tried sg_reset and it does a bus
> reset but not an expander reset.
>
> Technical documentation on the PM8388 is not readily available so I do
> not know if it has a mode select bit or other special method to get the
> expander to reset itself.
>
> I am looking for an inband method to reset the expander to clear a
> condition where some phys in a wide connection fail to link. A power
> cycle clears the condition and I am looking to mimic a power cycle by
> bouncing the expander at the lowest level possible via the SAS host
> connection.
There's no protocol defined way to reset an expander using SMP
functions, so it's not really possible to do it in-band. It's sort of
like asking if there's an ethernet packet you can send to a switch to
cause it to reset.
If the wide port isn't forming, you could try doing a hard reset of all
the phys in the port.
James
next prev parent reply other threads:[~2010-12-09 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 18:41 Is it possible to issue device reset to PMC PM8388 expander using sg3_utils or smp_utils? Jeff Johnson
2010-12-09 18:59 ` James Bottomley [this message]
2010-12-09 19:05 ` Jeff Johnson
2010-12-09 20:53 ` Douglas Gilbert
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=1291921192.3002.339.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).