From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <robertx.wojciechowicz@intel.com>
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24])
 by dpdk.org (Postfix) with ESMTP id 1B5302904
 for <users@dpdk.org>; Mon, 12 Sep 2016 11:32:14 +0200 (CEST)
Received: from orsmga001.jf.intel.com ([10.7.209.18])
 by orsmga102.jf.intel.com with ESMTP; 12 Sep 2016 02:32:14 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.30,322,1470726000"; d="scan'208";a="1028661281"
Received: from irsmsx107.ger.corp.intel.com ([163.33.3.99])
 by orsmga001.jf.intel.com with ESMTP; 12 Sep 2016 02:32:13 -0700
Received: from irsmsx103.ger.corp.intel.com ([169.254.3.204]) by
 IRSMSX107.ger.corp.intel.com ([169.254.10.204]) with mapi id 14.03.0248.002;
 Mon, 12 Sep 2016 10:30:54 +0100
From: "Wojciechowicz, RobertX" <robertx.wojciechowicz@intel.com>
To: Sergey Matov <smatov@mirantis.com>
CC: users <users@dpdk.org>
Thread-Topic: [dpdk-users] OpenVSwitch with DPDK causes pmd segfault
Thread-Index: AdIM14TwxFRFzvzASFyPES7Q9zra6g==
Date: Mon, 12 Sep 2016 09:30:53 +0000
Message-ID: <ED71EE0C15B44E41B8FA814D7EFD5CA8C1DF92@IRSMSX103.ger.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [163.33.239.181]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-users] OpenVSwitch with DPDK causes pmd segfault
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: usage discussions <users.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Sep 2016 09:32:15 -0000

On Mon, Jun 27, 2016 at 06:53:05PM +0300, Sergey Matov wrote:
> Hello dear community.
>=20
> I've faced unexpected segmentation fault running Open vSwitch with DPDK
> using OpenStack.
>=20
> On the Ubuntu 14.04 with 3.13 kernel we are having Open vSwitch ml2 neutr=
on
> accelerated with DPDK. Running VM with 3 interfaces and vCPU pinning goes
> ok. VM got all pings and SSH successfully.
>=20
> Host related configuration:
>=20
> Hugepages:
> HugePages_Total:   39552
> HugePages_Free:    31360
> HugePages_Rsvd:        0
> HugePages_Surp:        0
> Hugepagesize:       2048 kB
>=20
> NUMA topology:
> root at node-1:~# lscpu | grep NUMA
> NUMA node(s):          4
> NUMA node0 CPU(s):     0-4,20-24
> NUMA node1 CPU(s):     5-9,25-29
> NUMA node2 CPU(s):     10-14,30-34
> NUMA node3 CPU(s):     15-19,35-39
>=20
> OpenStack release: stable/Mitaka
> OVS version: 2.4.1 (bit patched for DPDK 2.1 support)
> DPDK: 2.1
> QEMU: 2.3
> Libvirt: 1.2.9.3

just for the record in case somebody else faced this issue.
I discussed that with Sergey and the conclusion looks as follows:

"""
I've discovered that the actual behavior, it's described here:
http://dpdk.org/ml/archives/dev/2016-July/043104.html.
So I just updated packages and it works fine for me.
Now I am running dpdk 16.07 with ovs 2.5, qemu 2.5 and lbvirt 1.3.1.
Seems problem is gone.
"""

Br,
Robert