public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>,
	Roland Dreier <roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mlx4: kernel 3.4-rc1 breaks libumad
Date: Mon, 2 Apr 2012 17:06:48 +0300	[thread overview]
Message-ID: <4F79B278.10104@mellanox.com> (raw)
In-Reply-To: <4F79AB24.2090200-HInyCGIudOg@public.gmane.org>

On 4/2/2012 4:35 PM, Bart Van Assche wrote:
>
> Some additional info:
> - This issue only occurs if the back-to-back connected system is down,
>    not if it is running.
> - The output I get with the other system down is:
>
> # cat /sys/class/infiniband/mlx4_0/ports/1/link_layer
> InfiniBand
> # dmesg -c>/dev/null
> # cat /sys/class/infiniband/mlx4_0/ports/1/rate
> cat: /sys/class/infiniband/mlx4_0/ports/1/rate: Invalid argument
> # dmesg -c
> ib_link_query_port active_speed 7
> rate_show ret 0 for ib_query_port dev mlx4_0 port 1 link 1
>

So you're getting the same wrong value of seven which I get on my 
systems, I think the patch / way to go here would be to assume some 
fixed speed (SDR?) when the link is down - as when the link is really 
down or down since the "wrong" link layer is assumed, the firmware 
command returns that value of seven which isn't in the speed enum, Roland?

Or.
--
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:[~2012-04-02 14:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02  7:42 mlx4: kernel 3.4-rc1 breaks libumad Bart Van Assche
     [not found] ` <4F795880.4070306-HInyCGIudOg@public.gmane.org>
2012-04-02 10:33   ` Or Gerlitz
     [not found]     ` <4F798069.4030305-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2012-04-02 11:16       ` Bart Van Assche
     [not found]         ` <4F798A9B.7060805-HInyCGIudOg@public.gmane.org>
2012-04-02 11:20           ` Or Gerlitz
     [not found]             ` <4F798B9A.6090309-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2012-04-02 11:48               ` Bart Van Assche
     [not found]                 ` <4F799222.3050306-HInyCGIudOg@public.gmane.org>
2012-04-02 12:51                   ` Or Gerlitz
     [not found]                     ` <4F79A0C5.2030805-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2012-04-02 13:02                       ` Or Gerlitz
     [not found]                         ` <4F79A359.2020204-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2012-04-02 13:25                           ` Hal Rosenstock
     [not found]                             ` <4F79A8C4.5000604-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2012-04-02 14:10                               ` Hal Rosenstock
2012-04-02 14:51                               ` Or Gerlitz
2012-04-03 21:37                               ` Ira Weiny
2012-04-02 13:35                       ` Bart Van Assche
     [not found]                         ` <4F79AB24.2090200-HInyCGIudOg@public.gmane.org>
2012-04-02 14:06                           ` Or Gerlitz [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=4F79B278.10104@mellanox.com \
    --to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=bvanassche-HInyCGIudOg@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=roland-DgEjT+Ai2ygdnm+yROfE0A@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