From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cos-us-iron01k.cos.keysight.com (cos-us-iron01k.cos.keysight.com [192.25.5.35]) by dpdk.org (Postfix) with ESMTP id 046D16A44 for ; Fri, 19 Aug 2016 10:28:24 +0200 (CEST) X-IPAS-Result: A2CRAACrwrZXfRYYjJxeGgEBAQGEf40mpgaEOIF9hh0CghsUAQEBAQEBAQEBEwEBFisvhF8BAQEDJxNPAgEIIhQQMiUBAQQBGogpvT8BAQEBAQUBAQEBAQEBAR+KeIRCgyqCLwWIJIV6gTeJcp5qSI9tHoJFAxyBTIceAX4BAQE X-IronPort-AV: E=Sophos;i="5.28,544,1464674400"; d="scan'208";a="36652515" Received: from wcosexch03k.cos.is.keysight.com (HELO 2k10hubs.keysight.com) ([156.140.24.22]) by cos-us-iron01k.cos.keysight.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Aug 2016 02:28:23 -0600 Received: from wcosexch02k.cos.is.keysight.com ([169.254.2.97]) by wcosexch03k.cos.is.keysight.com ([156.140.24.22]) with mapi id 14.03.0279.002; Fri, 19 Aug 2016 02:28:22 -0600 From: To: , Thread-Topic: segfault with dpdk 16.07 in rte_mempool_populate_phys Thread-Index: AdH4kORR/4kmue64QRuvda8Df4kUXwBTgvEAAASWNaA= Date: Fri, 19 Aug 2016 08:28:21 +0000 Message-ID: <22C95CA62CBADB498D32A348F0F073BC20AE28CB@wcosexch02k.cos.is.keysight.com> References: <22C95CA62CBADB498D32A348F0F073BC20AE2583@wcosexch02k.cos.is.keysight.com> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [156.140.13.70] x-tm-as-product-ver: SMEX-11.0.0.4283-8.000.1202-22522.006 x-tm-as-result: No--38.817000-8.000000-31 x-tm-as-matchedid: 147014-150567-701625-704425-700685-700107-702020-121270-7 01618-700752-707788-708310-708218-188019-709823-700264-704465-703399-703179 -701177-708712-851788-708060-863916-703523-701445-700104-701588-701223-7016 04-703283-700693-701594-702609-701236-709584-105250-705167-710272-704410-14 8004-148133-42000-42003 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] segfault with dpdk 16.07 in rte_mempool_populate_phys X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2016 08:28:25 -0000 Hi Shreyansh, Thanks for your reply,=20 Hmmm, I had wondered if the debug output from 16.7 was reduced compared to = 2.2.0, but perhaps this is what I should have been concentrating on, rather= than the core later On a vm running our app using 2.2.0 at startup, I see: dpdk: In dpdk_init_eal core_mask is 79, master_core_id is 0 EAL: Detected lcore 0 as core 0 on socket 0 EAL: Detected lcore 1 as core 0 on socket 0 EAL: Detected lcore 2 as core 0 on socket 0 EAL: Detected lcore 3 as core 0 on socket 0 EAL: Detected lcore 4 as core 0 on socket 0 EAL: Detected lcore 5 as core 0 on socket 0 EAL: Detected lcore 6 as core 0 on socket 0 EAL: Support maximum 32 logical core(s) by configuration. EAL: Detected 7 lcore(s) EAL: Setting up physically contiguous memory... EAL: Ask a virtual area of 0x40000000 bytes EAL: Virtual area found at 0x7f2735600000 (size =3D 0x40000000) EAL: Requesting 512 pages of size 2MB from socket 0 EAL: TSC frequency is ~2094950 KHz EAL: WARNING: cpu flags constant_tsc=3Dyes nonstop_tsc=3Dno -> using unreli= able clock cycles ! EAL: Master lcore 0 is ready (tid=3D9a11c720;cpuset=3D[0]) EAL: Failed to set thread name for interrupt handling EAL: Cannot set name for lcore thread EAL: Cannot set name for lcore thread EAL: Cannot set name for lcore thread EAL: Cannot set name for lcore thread EAL: lcore 4 is ready (tid=3D33ff7700;cpuset=3D[4]) EAL: lcore 3 is ready (tid=3D349f8700;cpuset=3D[3]) EAL: lcore 6 is ready (tid=3D32bf5700;cpuset=3D[6]) EAL: lcore 5 is ready (tid=3D335f6700;cpuset=3D[5]) EAL: PCI device 0000:00:07.0 on NUMA socket -1 EAL: probe driver: 8086:1521 rte_igb_pmd EAL: Not managed by a supported kernel driver, skipped EAL: PCI device 0000:00:08.0 on NUMA socket -1 EAL: probe driver: 8086:1572 rte_i40e_pmd EAL: PCI memory mapped at 0x7f27319f5000 EAL: PCI memory mapped at 0x7f279a33c000 PMD: eth_i40e_dev_init(): FW 5.0 API 1.5 NVM 05.00.02 eetrack 8000224e However on my vm running our app but with 16.7 I see much less EAL output, = the other stuff is printf output I put in the dpdk code to try and figure o= ut where it was going wrong dpdk: In dpdk_init_eal core_mask is 79, master_core_id is 0 EAL: Detected 7 lcore(s) EAL: WARNING: cpu flags constant_tsc=3Dyes nonstop_tsc=3Dno -> using unreli= able clock cycles ! dpdk_init_memory_pools position 1 dpdk_init_memory_pools position 2 dpdk_init_memory_pools position 3 about to call ret_mempool_create name Error Ind Mempool number 8 element size 256 cache size 4 private data size 4 mp_init 1158173360 mp_init_arg 0 obj_init 1158173120 obj_init_arg 0 socket_id 4294967295 flags 0 at start of rte_mempool_create at start of rte_mempool_populate_default at start of rte_mempool_populate_phys Is this just down to a change of the debug output from within the EAL , or = is something going fundamentally wrong. There is output about the individual detected lcores, there is no output ab= out the setting up physically contiguous memory.. etc However if my call to rte_eal_init hadn't worked, I shouldn't have to as f= ar as trying to call rte_mempool_create We check for a return of rte_eal_init of < 0 and if so, we rte_exit. I'll have a look over the newer documentation for the debug output Thanks Martin