From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from www6.g1.pair.com (www6.g1.pair.com [66.39.3.166]) by dpdk.org (Postfix) with ESMTP id 273663F9 for ; Wed, 17 Dec 2014 05:12:37 +0100 (CET) Received: by www6.g1.pair.com (Postfix, from userid 8138) id A5ACB17060; Tue, 16 Dec 2014 23:12:36 -0500 (EST) Date: Tue, 16 Dec 2014 23:12:36 -0500 From: Rick LaMont To: dev@dpdk.org Message-ID: <20141217041236.GB15643@www6.g1.pair.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [dpdk-dev] Segmentation fault in rte_eal_hugepage_attach X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Dec 2014 04:12:37 -0000 My DPDK application works fine when it's the primary process but crashes whenever --proc-type=secondary. The segmentation fault occurs in this call to mmap() within rte_eal_hugepage_attach(): /* * fdzero is mmapped to get a contiguous block of virtual * addresses of the appropriate memseg size. * use mmap to get identical addresses as the primary process. */ base_addr = mmap(mcfg->memseg[s].addr, mcfg->memseg[s].len, PROT_READ, MAP_PRIVATE | MAP_FIXED, fd_zero, 0); I've confirmed that addr and len match the values in rte_eal_hugepage_init() of the primary process (1 gigabyte). The target platform is a 32-bit embedded system running a Yocto distribution. I've confirmed that other applications such as mp_simple work as both primary and secondary on the same platform. The problem only occurs with a larger application to which I'm adding DPDK capabilities. Any advice on how to troubleshoot this? I've been looking at it for a week already and am running out of ideas for things to test. Thanks, Rick LaMont | The storm that I thought would blow over Dot C Software, Inc. | Clouds the light of the love that I found