linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: "Moore, Eric" <Eric.Moore@lsi.com>
Cc: James Bottomley <James.Bottomley@suse.de>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"kay.sievers@vrfy.org" <kay.sievers@vrfy.org>,
	Greg KH <greg@kroah.com>, Tom Coughlan <coughlan@redhat.com>
Subject: Re: mpt2sas logged messages
Date: Tue, 18 Aug 2009 13:47:51 -0400	[thread overview]
Message-ID: <4A8AE947.5060403@redhat.com> (raw)
In-Reply-To: <660360F4F2570145BD872F298951B17AE303DB55@cosmail03.lsi.com>

On 08/18/2009 01:02 PM, Moore, Eric wrote:
> On Tuesday, August 18, 2009 10:13 AM,  James Bottomley wrote:
>>> The code (0x12) means PL_LOGINFO_CODE_ABORT
>>> The sub_code(0x102) means
>> PL_LOGINFO_SUB_CODE_OPEN_FAILURE_PATHWAY_BLOCKED
>>
>> To translate this according to the SAS 1.1 specification, a
>> pathway open
>> failed because a timeout fired before the path could be established.
>>
>> You can mitigate this by increasing the expander partial
>> pathway timeout
>> value. (or just move to a more efficient configuration).
>>
>
> I was telling Ric it was something else in seperate email.  The pathway was blocked due to two initiors establishing a connection to single port. That woudl be the case if he wasn't using a sata multiplexor.
>
>
> anyways, if the pathway timeout is the issue, then I believe you can set the pathway timeout value using Dougs smp tools, smp_phy_control , setting the --pptv command line option.
>
> http://sg.danny.cz/sg/smp_utils.html

Thanks, I will give that a try,

ric


      reply	other threads:[~2009-08-18 17:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18 13:18 mpt2sas logged messages Ric Wheeler
2009-08-18 13:25 ` Greg KH
2009-08-18 13:55   ` James Bottomley
2009-08-18 13:59   ` Ric Wheeler
2009-08-18 14:57     ` Greg KH
2009-08-18 15:53       ` Ric Wheeler
2009-08-18 16:09         ` James Bottomley
2009-08-18 17:44           ` Ric Wheeler
2009-08-18 20:14             ` James Bottomley
2009-08-18 20:33               ` Ric Wheeler
2009-08-18 16:40         ` Greg KH
2009-08-18 17:45           ` Ric Wheeler
2009-08-18 18:37           ` Kay Sievers
2009-08-18 18:41             ` Ric Wheeler
2009-08-19 19:30               ` Kay Sievers
2009-08-19 19:36                 ` Ric Wheeler
2009-08-20 15:18                 ` Ric Wheeler
2009-08-20 15:20                   ` Kay Sievers
2009-08-20 15:30                     ` Ric Wheeler
2009-08-18 13:26 ` Ric Wheeler
2009-08-18 15:39 ` Moore, Eric
2009-08-18 16:13   ` James Bottomley
2009-08-18 17:02     ` Moore, Eric
2009-08-18 17:47       ` Ric Wheeler [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=4A8AE947.5060403@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=Eric.Moore@lsi.com \
    --cc=James.Bottomley@suse.de \
    --cc=coughlan@redhat.com \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --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).