From mboxrd@z Thu Jan 1 00:00:00 1970 From: Or Gerlitz Subject: Re: can't get IB link with the for-next branch / IBoE patches Date: Tue, 26 Oct 2010 11:33:05 +0200 Message-ID: <4CC6A051.3010703@Voltaire.com> References: <20101024075835.GA11359@mtldesk30> <20101024160018.GA32499@mtldesk30> <4CC54D4E.7050203@Voltaire.com> <4CC5604D.2080803@Voltaire.com> <20101025161730.GA9335@mtldesk30> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Roland Dreier Cc: Eli Cohen , RDMA list List-Id: linux-rdma@vger.kernel.org Roland Dreier wrote: >> Yep, looks like that's where my cleanup broke things. I rolled this in >> and pushed it out; I'm testing it myself now. > My IB port comes to active now, I think that fixed things. same here, I have IB port coming to active and basic IPoIB, opensm working okay on the node with the current for-next/IBoE bits 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