public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Alan Cook <acook-osxm6dDZNBBZx8iatJs59jGjJy/sRE9J@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Unable to Connect Using Active Speed 2.5 Gbps and Active Width of 1
Date: Mon, 28 Mar 2011 15:19:20 -0400	[thread overview]
Message-ID: <4D90DF38.1060407@dev.mellanox.co.il> (raw)
In-Reply-To: <loom.20110328T210350-244-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>

On 3/28/2011 3:07 PM, Alan Cook wrote:
> Hal Rosenstock<hal@...>  writes:
>>
>> What does smpquery portinfo say for both sides of that link ?
>>
>
> What specifically would be I be looking for in this data to determine if their
> is an issue?

The various LinkSpeed/Width components to see if they make sense.

> For card 1 I have:
>
> # Port info: DR path slid 65535; dlid 65535; 0 port 1
> Mkey:............................0x0000000000000000
> GidPrefix:.......................0xfe80000000000000
> Lid:.............................2
> SMLid:...........................1
> CapMask:.........................0x2510868
>                                  IsTrapSupported
>                                  IsAutomaticMigrationSupported
>                                  IsSLMappingSupported
>                                  IsSystemImageGUIDsupported
>                                  IsCommunicatonManagementSupported
>                                  IsVendorClassSupported
>                                  IsCapabilityMaskNoticeSupported
>                                  IsClientRegistrationSupported
> DiagCode:........................0x0000
> MkeyLeasePeriod:.................0
> LocalPort:.......................1
> LinkWidthEnabled:................1X or 4X
> LinkWidthSupported:..............1X or 4X
> LinkWidthActive:.................1X
> LinkSpeedSupported:..............2.5 Gbps or 5.0 Gbps or 10.0 Gbps
> LinkState:.......................Active
> PhysLinkState:...................LinkUp
> LinkDownDefState:................Polling
> ProtectBits:.....................0
> LMC:.............................0
> LinkSpeedActive:.................2.5 Gbps
> LinkSpeedEnabled:................2.5 Gbps
> NeighborMTU:.....................2048
> SMSL:............................0
> VLCap:...........................VL0-7
> InitType:........................0x00
> VLHighLimit:.....................4
> VLArbHighCap:....................8
> VLArbLowCap:.....................8
> InitReply:.......................0x00
> MtuCap:..........................2048
> VLStallCount:....................0
> HoqLife:.........................31
> OperVLs:.........................VL0-7
> PartEnforceInb:..................0
> PartEnforceOutb:.................0
> FilterRawInb:....................0
> FilterRawOutb:...................0
> MkeyViolations:..................0
> PkeyViolations:..................0
> QkeyViolations:..................0
> GuidCap:.........................128
> ClientReregister:................0
> SubnetTimeout:...................18
> RespTimeVal:.....................16
> LocalPhysErr:....................8
> OverrunErr:......................8
> MaxCreditHint:...................0
> RoundTrip:.......................0
>
>
> For card 2 I have:
>
> # Port info: DR path slid 65535; dlid 65535; 0 port 1
> Mkey:............................0x0000000000000000
> GidPrefix:.......................0xfe80000000000000
> Lid:.............................1
> SMLid:...........................1
> CapMask:.........................0x251086a
>                                  IsSM
>                                  IsTrapSupported
>                                  IsAutomaticMigrationSupported
>                                  IsSLMappingSupported
>                                  IsSystemImageGUIDsupported
>                                  IsCommunicatonManagementSupported
>                                  IsVendorClassSupported
>                                  IsCapabilityMaskNoticeSupported
>                                  IsClientRegistrationSupported
> DiagCode:........................0x0000
> MkeyLeasePeriod:.................0
> LocalPort:.......................1
> LinkWidthEnabled:................1X or 4X
> LinkWidthSupported:..............1X or 4X
> LinkWidthActive:.................1X
> LinkSpeedSupported:..............2.5 Gbps or 5.0 Gbps or 10.0 Gbps
> LinkState:.......................Active
> PhysLinkState:...................LinkUp
> LinkDownDefState:................Polling
> ProtectBits:.....................0
> LMC:.............................0
> LinkSpeedActive:.................2.5 Gbps
> LinkSpeedEnabled:................2.5 Gbps
> NeighborMTU:.....................2048
> SMSL:............................0
> VLCap:...........................VL0-7
> InitType:........................0x00
> VLHighLimit:.....................4
> VLArbHighCap:....................8
> VLArbLowCap:.....................8
> InitReply:.......................0x00
> MtuCap:..........................2048
> VLStallCount:....................0
> HoqLife:.........................31
> OperVLs:.........................VL0-7
> PartEnforceInb:..................0
> PartEnforceOutb:.................0
> FilterRawInb:....................0
> FilterRawOutb:...................0
> MkeyViolations:..................0
> PkeyViolations:..................0
> QkeyViolations:..................0
> GuidCap:.........................128
> ClientReregister:................0
> SubnetTimeout:...................18
> RespTimeVal:.....................16
> LocalPhysErr:....................8
> OverrunErr:......................8
> MaxCreditHint:...................0
> RoundTrip:.......................0

LinkWidthEnabled is 1X or 4X and not just 1X. That's because there's no 
force_link_width option in OpenSM so I think the width you set is 
getting overwritten much like the speed was earlier until you discovered 
force_link_speed 0.

Also, is this b2b HCAs or is there a switch in the topology ?

-- Hal
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2011-03-28 19:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 18:01 Unable to Connect Using Active Speed 2.5 Gbps and Active Width of 1 Alan Cook
     [not found] ` <loom.20110328T194956-774-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-03-28 18:55   ` Hal Rosenstock
2011-03-28 19:07     ` Alan Cook
     [not found]       ` <loom.20110328T210350-244-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-03-28 19:19         ` Hal Rosenstock [this message]
2011-03-28 19:26           ` Alan Cook
     [not found]             ` <loom.20110328T212117-950-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-03-28 19:41               ` Jason Gunthorpe
2011-03-28 20:41                 ` Alan Cook
     [not found]                   ` <loom.20110328T220853-101-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2011-03-29 17:37                     ` Hal Rosenstock
2011-03-29 18:01                       ` Alan Cook
2011-03-28 20:18               ` Hal Rosenstock

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=4D90DF38.1060407@dev.mellanox.co.il \
    --to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=acook-osxm6dDZNBBZx8iatJs59jGjJy/sRE9J@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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