From mboxrd@z Thu Jan 1 00:00:00 1970 From: Or Gerlitz Subject: Re: mlx4: kernel 3.4-rc1 breaks libumad Date: Mon, 2 Apr 2012 17:06:48 +0300 Message-ID: <4F79B278.10104@mellanox.com> References: <4F795880.4070306@acm.org> <4F798069.4030305@mellanox.com> <4F798A9B.7060805@acm.org> <4F798B9A.6090309@mellanox.com> <4F799222.3050306@acm.org> <4F79A0C5.2030805@mellanox.com> <4F79AB24.2090200@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F79AB24.2090200-HInyCGIudOg@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Bart Van Assche , Roland Dreier Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-rdma@vger.kernel.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