From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <users-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 50234A0613
	for <public@inbox.dpdk.org>; Tue, 24 Sep 2019 19:18:11 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id AA3DC2BE9;
	Tue, 24 Sep 2019 19:18:10 +0200 (CEST)
Received: from mail-pf1-f182.google.com (mail-pf1-f182.google.com
 [209.85.210.182]) by dpdk.org (Postfix) with ESMTP id 6B6272BE6
 for <users@dpdk.org>; Tue, 24 Sep 2019 19:18:09 +0200 (CEST)
Received: by mail-pf1-f182.google.com with SMTP id q5so1734393pfg.13
 for <users@dpdk.org>; Tue, 24 Sep 2019 10:18:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=networkplumber-org.20150623.gappssmtp.com; s=20150623;
 h=date:from:to:cc:subject:message-id:in-reply-to:references
 :mime-version:content-transfer-encoding;
 bh=QS6xSbB0Q54i3NSRhzgc14xkb/WZi1FdNP/nE4B3dwE=;
 b=FfC+6iAEbcFIj1IPpIxSaRH7j2QgGJ6K7iDzeTzEulBNEWhRksbvT7w0XwUled6YJ8
 jdguuiH6rQOMfApu1n3R70CMQUZHs2Ls3+HbukBJgTzu0qpGh1rcF4zqEMSC4KXuOIMy
 FdlTw2Kkc9UJb9xYoiN5M2x36gMz8gqiJsZEoXJlLxZBwNEtYs2Fr9sY8CsSoOgCWYD3
 poqqQwcfQKTjgHZsAwb6pHZoE4DonOiijcNLRl0ZDljFDnZ/wOZ/HLM/l4l18imj4eTH
 PpWGsjLckH6bnsFWZbzRqZs22xuZSi0k0BlxuxhZbTAtfOQw+ZQSub7RtFeM3JsTW+0J
 sM0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-transfer-encoding;
 bh=QS6xSbB0Q54i3NSRhzgc14xkb/WZi1FdNP/nE4B3dwE=;
 b=HdoYzqxZsxBmFQXpTG9pLKk6FAOzJhltG5TFiNfUNpaCJ05XcRZ5RAmSWs/Zk6EBbi
 ORAzTJK4lRG2XL9MwXVVW30bL3isC4tklA6yGpI2HQQH1au5nUYsLox3dgTFHE6xd8Ce
 PxLg/RpcGokAmI5W0V32kXNu2XQN9GgukFcUgKStCydtcMbuIMd8r61Lo5Ar+Z4bvyS+
 SuPJpfdF8EgjQPVJfmaMrYHDOvLS61Emnr4a/QGcVvPZ64L1EEhMH9zOroj/x/J54z/O
 8gI+IsDTz//i/mvUQDoECj84WlIkQ6YtUzl3As7aDFQ5OqVYesDMGtneYvgbRZtjN5E/
 JOSQ==
X-Gm-Message-State: APjAAAX8Rf5LDWUkK5Z+0L26l9Kl7nJxqk3lOiDfn+mj0SGXmVAMjL1N
 QkKgeZ4Lacte3vJqnqsn5qzX0STAjY8=
X-Google-Smtp-Source: APXvYqxwihWue3fjJFl19tnAJvi/HJ4hxY1SdtlSk/o9+cOVe1AtU2hTm2wDz3hRNhL3UdEIt/fx1A==
X-Received: by 2002:a17:90a:2464:: with SMTP id
 h91mr1255262pje.9.1569345488385; 
 Tue, 24 Sep 2019 10:18:08 -0700 (PDT)
Received: from hermes.lan (204-195-22-127.wavecable.com. [204.195.22.127])
 by smtp.gmail.com with ESMTPSA id l7sm496592pjy.12.2019.09.24.10.18.08
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Tue, 24 Sep 2019 10:18:08 -0700 (PDT)
Date: Tue, 24 Sep 2019 10:18:02 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Jim Vaigl" <jimv@rockbridgesoftware.com>
Cc: <users@dpdk.org>
Message-ID: <20190924101802.273c25d9@hermes.lan>
In-Reply-To: <004101d572f5$92d479d0$b87d6d70$@com>
References: <004101d572f5$92d479d0$b87d6d70$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [dpdk-users] DPDK on Mellanox BlueField Ref Platform
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
Errors-To: users-bounces@dpdk.org
Sender: "users" <users-bounces@dpdk.org>

On Tue, 24 Sep 2019 12:31:51 -0400
"Jim Vaigl" <jimv@rockbridgesoftware.com> wrote:

> Since no one has chimed in with any build/install/configure suggestion for
> the
> BlueField, I've spent some time debugging and thought I'd share the results.
> Building the l3fwd example application and running it as the docs suggest,
> when
> I try to send it UDP packets from another machine, it dumps core.
> 
> Debugging a bit with gdb and printf, I can see that from inside
> process_packet()
> and processx4_step1() the calls to rte_pktmbuf_mtod() return Nil or
> suspicious
> pointer values (i.e. 0x80).  The sample apps don't guard against NULL
> pointers
> being returned from this rte call, so that's why it's dumping core.
> 
> I still think the problem is related to the driver config, but thought this
> might ring a bell for anyone who's had problems like this.
> 
> The thing that still bothers me is that rather than seeing what I was
> expecting
> at init based on what the documentation shows:
>     [...]
>     EAL: probe driver: 15b3:1013 librte_pmd_mlx5
> 
> ... when rte_eal_init() runs, I'm seeing:
>     [...]
>     EAL:  Selected IOVA mode 'PA'
>     EAL:  Probing VFIO support...
> 
> This still seems wrong, and I've verified that specifying the BlueField
> target ID
> string in the make is causing "CONFIG_RTE_LIBRTE_MLX5_PMD=y" to appear in
> the .config.
> 
> Regards,
> --Jim Vaigl
> 614 886 5999
> 
> 

make sure you have latest version of rdma-core installed (v25).
The right version is not in most distros