[dpdk-users] [VMXNET3] vmxnet3_dev_stats_get() segfault when called by pktgen

[Wiles, Keith]

> On Sep 7, 2017, at 7:58 AM, Stephen Hemminger <stephen at networkplumber.org> wrote:
> 
> On Thu,  7 Sep 2017 07:51:46 +0700 (ICT)
> longtb5 at viettel.com.vn wrote:
> 
>> 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.
> 
> If you modify the Makefiles for pktgen, ethdev, and vmxnet3 to have -g flag
> then you will get more symbolic data which makes better backtrace.

I use the option EXTRA_CFLAGS on the command line to improve debug.

make install T=x86_64-native-linuxapp-gcc EXTRA_CFLAGS=“-g -O0”

Using -O0 for gdb is good for non-performance testing.


Regards,
Keith