From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <jeff@vectranetworks.com> Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0144.outbound.protection.outlook.com [157.56.111.144]) by dpdk.org (Postfix) with ESMTP id 518B75A76 for <dev@dpdk.org>; Fri, 17 Jul 2015 05:40:16 +0200 (CEST) Received: from SN1PR08MB1376.namprd08.prod.outlook.com (10.162.1.146) by SN1PR08MB1375.namprd08.prod.outlook.com (10.162.1.145) with Microsoft SMTP Server (TLS) id 15.1.213.14; Fri, 17 Jul 2015 03:40:14 +0000 Received: from SN1PR08MB1376.namprd08.prod.outlook.com ([10.162.1.146]) by SN1PR08MB1376.namprd08.prod.outlook.com ([10.162.1.146]) with mapi id 15.01.0213.000; Fri, 17 Jul 2015 03:40:14 +0000 From: "Jeff Venable, Sr." <jeff@vectranetworks.com> To: "dev@dpdk.org" <dev@dpdk.org> Thread-Topic: processor/core count issue Thread-Index: AdDAQiAZZYngVsjpRvW1qu6gimeBKw== Date: Fri, 17 Jul 2015 03:40:14 +0000 Message-ID: <SN1PR08MB137618A37C4230E03D29A131A0980@SN1PR08MB1376.namprd08.prod.outlook.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: dpdk.org; dkim=none (message not signed) header.d=none; x-originating-ip: [12.226.156.82] x-microsoft-exchange-diagnostics: 1; SN1PR08MB1375; 5:Vz+MKMdsOzFO0XNSM6D6N8bI7FZKB819rRiqrCSc2zNzwmgMEZfQlsLrllmMN6jGVjLO6N4FiWeIm1XJTC+3XYuJE6nwUlucyM1gx5tdh4jmEClPPNDLA01xwWD3vPPOlFheb1lIIb5KcXsVqzLSAA==; 24:ysRYXku1dZ7bk2CWWX2NNUJ0xBqM+Iu7x2lOzIvuwNT4JQ8rQAVaHB9AUD5OiNEa8E0JyVQ1oodiSSZqSM87doWlYEPGVmNg74Mlo924n5Q=; 20:67H7G7hr5BNZOtDLmXLeHNAdI/HMZ7UqoH58dlFCS7382P0xGl1/KG8O5N0npEA32p+ZvQjpDlFNPReU58rXhA== x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR08MB1375; sn1pr08mb1375: X-MS-Exchange-Organization-RulesExecuted x-microsoft-antispam-prvs: <SN1PR08MB13753DCF16E2C93572911DBBA0980@SN1PR08MB1375.namprd08.prod.outlook.com> x-exchange-antispam-report-test: UriScan:(108003899814671); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:SN1PR08MB1375; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1375; x-forefront-prvs: 06400060E1 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(5001960100002)(2351001)(2900100001)(15975445007)(77096005)(19580395003)(87936001)(77156002)(2656002)(19300405004)(74316001)(86362001)(122556002)(16601075003)(92566002)(2501003)(229853001)(50986999)(54356999)(5002640100001)(19617315012)(66066001)(99286002)(5003600100002)(40100003)(102836002)(46102003)(16236675004)(33656002)(15395725005)(62966003)(110136002)(76576001)(19625215002)(450100001)(189998001)(107886002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1375; H:SN1PR08MB1376.namprd08.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; MIME-Version: 1.0 X-OriginatorOrg: vectranetworks.com X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Jul 2015 03:40:14.0756 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: a6cc66bc-f419-45c2-a9c2-8ff4ab685f2d X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1375 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] processor/core count issue X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK <dev.dpdk.org> List-Unsubscribe: <http://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: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Fri, 17 Jul 2015 03:40:16 -0000 In a VM Fusion environment configured with 2 processors with 1 core each I = get the following: PANIC in rte_eal_init(): Cannot init logs 4: [/lib/x86_64-linux-gnu/libc.so<http://libc.so/>.6(__libc_start_main+0xf5= ) [0x7f9fd3bdaec5]] 3: [/usr/lib/dpdk-2.0.0/librte_eal.so<http://librte_eal.so/>.1(rte_eal_init= +0x123a) [0x7f9fd4f462fa]] 2: [/usr/lib/dpdk-2.0.0/librte_eal.so<http://librte_eal.so/>.1(__rte_panic+= 0xc3) [0x7f9fd4f449e8]] 1: [/usr/lib/dpdk-2.0.0/librte_eal.so<http://librte_eal.so/>.1(rte_dump_sta= ck+0x16) [0x7f9fd4f4daa6]] Aborted (core dumped) rte_socket_id() was returning 0xFFFFFFFF here: (gdb) bt #0 0x00007ffff797ae95 in rte_malloc_socket () from /usr/lib/dpdk-2.0.0/lib= rte_malloc.so.1 #1 0x00007ffff797af4e in rte_zmalloc_socket () from /usr/lib/dpdk-2.0.0/li= brte_malloc.so.1 #2 0x00007ffff7573ef8 in rte_ring_create () from /usr/lib/dpdk-2.0.0/librt= e_ring.so.1 #3 0x00007ffff777770d in rte_mempool_xmem_create () from /usr/lib/dpdk-2.0= .0/librte_mempool.so.1 #4 0x00007ffff7777b97 in rte_mempool_create () from /usr/lib/dpdk-2.0.0/li= brte_mempool.so.1 #5 0x00007ffff7b90899 in ?? () from /usr/lib/dpdk-2.0.0/librte_eal.so.1 #6 0x00007ffff7b88d34 in ?? () from /usr/lib/dpdk-2.0.0/librte_eal.so.1 #7 0x00007ffff7b84950 in rte_eal_init () from /usr/lib/dpdk-2.0.0/librte_e= al.so.1 When I reconfigured the VM to 1 processor with 2 cores, everything works as= expected. This was not a problem in 1.6. Jeff