From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: Unable to run the second DPDK app: Cannot allocate
	memzone list
Date: Tue, 15 May 2018 11:35:45 +0100
Message-ID: <6ed11b93-e1ff-6ea1-bb4b-dd88d33214cc@intel.com>
References: <e246d08b-6b55-693f-46f5-2df1d076714d@solarflare.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Thomas Monjalon <thomas@monjalon.net>
To: Andrew Rybchenko <arybchenko@solarflare.com>, "dev@dpdk.org" <dev@dpdk.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mga04.intel.com (mga04.intel.com [192.55.52.120])
 by dpdk.org (Postfix) with ESMTP id EA3177EE4
 for <dev@dpdk.org>; Tue, 15 May 2018 12:35:47 +0200 (CEST)
In-Reply-To: <e246d08b-6b55-693f-46f5-2df1d076714d@solarflare.com>
Content-Language: en-US
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On 15-May-18 11:24 AM, Andrew Rybchenko wrote:
> Hi,
> 
> starting from last night I cannot run the second DPDK app on the host.
> I definitely have problems on Ubuntu 16.04.4 (Linux 4.4.0-124-generic) and
> RHEL 7.5 (Linux 3.10.0-862.el7.x86_64).
> EAL command line option --file-prefix is used. So, it worked perfectly 
> before.
> Not it fails in the following way:
> 
> EAL: Detected 10 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Probing VFIO support...
> EAL: VFIO support initialized
> EAL: Cannot allocate memzone list
> EAL: Cannot init memzone
> 
> Memzone list allocation fails on flock() with errno "Resource 
> temporarily unavailable".
> 
> Is it know? Any fixes available?
> 
> Andrew.
> 

Hi Andrew,

I'm looking into it.

-- 
Thanks,
Anatoly