From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 099CE968 for ; Wed, 6 Sep 2017 15:51:41 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga105.fm.intel.com with ESMTP; 06 Sep 2017 06:51:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,484,1498546800"; d="scan'208";a="1192154494" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by fmsmga001.fm.intel.com with ESMTP; 06 Sep 2017 06:51:41 -0700 Received: from fmsmsx121.amr.corp.intel.com (10.18.125.36) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 6 Sep 2017 06:51:40 -0700 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.18]) by fmsmsx121.amr.corp.intel.com ([169.254.6.85]) with mapi id 14.03.0319.002; Wed, 6 Sep 2017 06:51:40 -0700 From: "Wiles, Keith" To: "longtb5@viettel.com.vn" CC: "users@dpdk.org" Thread-Topic: [dpdk-users] [pktgen] Segfault at cli_start() Thread-Index: M4DIFtofLSHOQYwqwBx8typLUwwvQ6S+dicA Date: Wed, 6 Sep 2017 13:51:39 +0000 Message-ID: <38376A46-3F2E-406B-B2E3-5F7BF8B0BD66@intel.com> References: <1493430108.72087290.1504693110045.JavaMail.zimbra@viettel.com.vn> In-Reply-To: <1493430108.72087290.1504693110045.JavaMail.zimbra@viettel.com.vn> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.254.186.232] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] [pktgen] Segfault at cli_start() X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Sep 2017 13:51:42 -0000 > On Sep 6, 2017, at 5:18 AM, longtb5@viettel.com.vn wrote: >=20 > Hi,=20 >=20 > I'm running a VM on Ubuntu 16.04 with VMXNET3.=20 >=20 > I have managed to compile and successfully run DPDK (v17.11.0-rc0) and th= e sample apps. However, pktgen (v3.40) ran into a segfault without me doing= anything yet. Everything seemed to be OK until the pktgen> prompt showed u= p. Here's the message. This does not appear to be a problem in Pktgen, but in the VMXNET3 driver. = You may want to contact the driver maintainer in the Maintainers file and c= hange the subject to reference the VMXNET3 driver to get others attention i= nstead of Pktgen. One of the first things Pktgen does is start polling the ethernet stats of = the ports and this is why it happens in Pktgen an possibly not other applic= ations that do not poll the stats. >=20 > $ sudo .app/x86_64-native-linuxapp-gcc/pktgen >=20 > Pktgen:/>=20 > =3D=3D=3D=3D=3D=3D Pktgen got a Segment Fault >=20 > Obtained 11 stack frames. > app/x86_64-native-linuxapp-gcc/pktgen() [0x468ba5] > /lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x7f1e618de4b0] > app/x86_64-native-linuxapp-gcc/pktgen() [0x6c7c70] > app/x86_64-native-linuxapp-gcc/pktgen(rte_eth_stats_get+0x79) [0x4a3fe9] > app/x86_64-native-linuxapp-gcc/pktgen(pktgen_process_stats+0xa9) [0x46f0f= 9] > app/x86_64-native-linuxapp-gcc/pktgen(rte_timer_manage+0x526) [0x48ca96] > app/x86_64-native-linuxapp-gcc/pktgen(cli_start+0x26d) [0x71276d] > app/x86_64-native-linuxapp-gcc/pktgen(pktgen_cli_start+0xb) [0x4509bb] > app/x86_64-native-linuxapp-gcc/pktgen(main+0x7a6) [0x447b86] > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f1e618c9830] > app/x86_64-native-linuxapp-gcc/pktgen(_start+0x29) [0x44a639] >=20 > The same problem showed up whether I ran pktgen by the py script, invoked= directly, supplied the basic EAL args, pktgen args or not. >=20 > GDB gave this >=20 > Pktgen:/>=20 > Thread 1 "pktgen" received signal SIGSEGV, Segmentation fault. > 0x00000000006c7c70 in vmxnet3_dev_stats_get () >=20 > Thanks. >=20 > BR. >=20 Regards, Keith