From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: Mellanox PMD failure w/DPDK-2.1.0 and MLNX_OFED-3.1-1.0.3 Date: Fri, 16 Oct 2015 13:01:58 -0700 Message-ID: <20151016130158.02055ce1@xeon-e3> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" , Moshe Lazer To: "Bill O'Hara" Return-path: Received: from mail-pa0-f50.google.com (mail-pa0-f50.google.com [209.85.220.50]) by dpdk.org (Postfix) with ESMTP id 728985A53 for ; Fri, 16 Oct 2015 22:01:49 +0200 (CEST) Received: by pacfv9 with SMTP id fv9so31408797pac.3 for ; Fri, 16 Oct 2015 13:01:48 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, 16 Oct 2015 12:11:14 -0700 "Bill O'Hara" wrote: > Hi Olga, > > Sorry for slow response. Initially, raw_ethernet_bw and raw_ethernet_lat > were not working. > > * we clean installed some boxes, rather than upgrading from previous ofed > etc and now the raw_ethernet_bw and raw_ethernet_lat work. (This is on > ubuntu14.04 with most recent mellanox ofed release). > > * dpdk-2.1 still did not work. We clean installed the build box, to clear > any possibility of mismatches due to upgrade process. Still not working. > > * at the suggestion of one of our developers, we switched from statically > linking dpdk and libibverbs to static dpdk and dynamic libibverbs. Now the > dpdk test programs work. > > * at this point, we've switched back to our own kernel build (with > patches), our own dpdk programs, and everything appears to be correct. > > Apologies for the firedrill -- we do not yet know the exact root cause, but > it appears to be related to having done an upgrade of mellanox ofed on the > ubuntu14.04 boxes AND building with static linking of libibverbs (though we > double checked that the correct .a file was being linked). I will let you > know if we have a more satisfactory answer -- we're also more highly > prioritizing hermetic builds at this point. > > thanks for your help and hints! > bill Sounds like a case where the application was not linked with proper LDFLAGS to enable constructors.