From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailfilter01.viettel.com.vn (mailfilter01.viettel.com.vn [125.235.240.53]) by dpdk.org (Postfix) with ESMTP id 85715199B1 for ; Thu, 7 Sep 2017 09:42:11 +0200 (CEST) X-IronPort-AV: E=Sophos;i="5.42,357,1500915600"; d="scan'208";a="54236996" Received: from 125.235.240.45.adsl.viettel.vn (HELO mta2.viettel.com.vn) ([125.235.240.45]) by mailfilter01.viettel.com.vn with ESMTP; 07 Sep 2017 14:42:10 +0700 Received: from localhost (localhost [127.0.0.1]) by mta2.viettel.com.vn (Postfix) with ESMTP id 7973969EA21; Thu, 7 Sep 2017 14:42:07 +0700 (ICT) Received: from mta2.viettel.com.vn ([127.0.0.1]) by localhost (mta2.viettel.com.vn [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id gUpaaLcwHoKr; Thu, 7 Sep 2017 14:42:07 +0700 (ICT) Received: from localhost (localhost [127.0.0.1]) by mta2.viettel.com.vn (Postfix) with ESMTP id 545E069EA20; Thu, 7 Sep 2017 14:42:07 +0700 (ICT) X-Virus-Scanned: amavisd-new at Received: from mta2.viettel.com.vn ([127.0.0.1]) by localhost (mta2.viettel.com.vn [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id TgkldycTP0cr; Thu, 7 Sep 2017 14:42:07 +0700 (ICT) Received: from zimbra.viettel.com.vn (mailbox3.viettel.com.vn [10.30.182.138]) by mta2.viettel.com.vn (Postfix) with ESMTP id 25C6F69EA2D; Thu, 7 Sep 2017 14:42:07 +0700 (ICT) To: users@dpdk.org Cc: keith.wiles@intel.com, skhare@vmware.com Message-ID: <1427594697.75906108.1504770126905.JavaMail.zimbra@viettel.com.vn> In-Reply-To: <1551920177.73501197.1504745506408.JavaMail.zimbra@viettel.com.vn> References: <1551920177.73501197.1504745506408.JavaMail.zimbra@viettel.com.vn> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [27.72.58.160] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - GC60 (Win)/8.0.9_GA_6191) Thread-Topic: vmxnet3_dev_stats_get() segfault when called by pktgen Thread-Index: CWvvYIrUnq59dFO/fb24Hidwrhdunvy0xyjg MilterAction: FORWARD Date: Thu, 7 Sep 2017 14:42:07 +0700 (ICT) From: longtb5@viettel.com.vn Subject: Re: [dpdk-users] [VMXNET3] vmxnet3_dev_stats_get() segfault when called by pktgen 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: Thu, 07 Sep 2017 07:42:12 -0000 Hi, I have tested another app (proc_info) which also uses vmxnet3_dev_stats_get() but it ran just fine. I have found out that this function, which is called inside vmxnet3_dev_stats_get(), causes the kernel to return a SIGSEGV when running pktgen: drivers/net/vmxnet3/vmxnet3_ethdev.c:898 vmxnet3_hw_tx_stats_get(hw, i, &txStats); Should be related to how pktgen called this function? Because the other app didn't crash. Thanks, Long > ----- Original Message ----- > From: longtb5@viettel.com.vn > To: users@dpdk.org > Sent: Thursday, September 7, 2017 7:51:46 AM > Subject: [VMXNET3] vmxnet3_dev_stats_get() segfault when called by pktgen > > Hi, > > I'm running Ubuntu 16.04 on my VM with vmxnet3 as the NIC. I have successfully installed DPDK > and managed to run a few sample apps. However when I tried pktgen the kernel threw a SIGSEGV > without me doing anything yet. > > $ sudo .app/x86_64-native-linuxapp-gcc/pktgen > > Pktgen:/> > ====== Pktgen got a Segment Fault > > 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) [0x46f0f9] > 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] > > # gdb .app/x86_64-native-linuxapp-gcc/pktgen > > Pktgen:/> > Thread 1 "pktgen" received signal SIGSEGV, Segmentation fault. > 0x00000000006c7c70 in vmxnet3_dev_stats_get () > > I tried using older versions of DPDK and pktgen but nothing worked so far. > > Is it a problem on my end? Like, the way I set up the NICs in my VM? Or is it a bug? > > BR, > > Long.