+ Megha, Sharad and Eswar.

On Mon, Apr 18, 2022 at 2:03 PM Amiya Mohakud <amohakud@paloaltonetworks.com>
wrote:

> Hi Michal/DPDK-Experts,
>
> I am facing one issue in net/ena driver while fetching extended stats
> (xstats). The DPDK seems to segfault with below backtrace.
>
> DPDK Version: 20.11.1
> ENA version: 2.2.1
>
>
> Using host libthread_db library "/lib64/libthread_db.so.1".
>
> Core was generated by `/opt/dpfs/usr/local/bin/brdagent'.
>
> Program terminated with signal SIGSEGV, Segmentation fault.
>
> #0  __memmove_avx_unaligned_erms () at
> ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:232
>
> 232             VMOVU   %VEC(0), (%rdi)
>
> [Current thread is 1 (Thread 0x7fffed93a400 (LWP 5060))]
>
>
> Thread 1 (Thread 0x7fffed93a400 (LWP 5060)):
>
> #0  __memmove_avx_unaligned_erms () at
> ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:232
>
> #1  0x00007ffff3c246df in ena_com_handle_admin_completion () from
> ../lib64/../../lib64/libdpdk.so.20
>
> #2  0x00007ffff3c1e7f5 in ena_interrupt_handler_rte () from
> ../lib64/../../lib64/libdpdk.so.20
>
> #3  0x00007ffff3519902 in eal_intr_thread_main () from
> /../lib64/../../lib64/libdpdk.so.20
>
> #4  0x00007ffff510714a in start_thread (arg=<optimized out>) at
> pthread_create.c:479
>
> #5  0x00007ffff561ff23 in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
>
>
>
>
> *Background:*
>
>    - This used to work fine with DPDK-19.11.3 , that means there was no
>    crash observed with the 19.11.3 DPDK version, but now after upgrading to
>    DPDK 20.11.1, DPDK is crashing with the above trace.
>    - It looks to me as a DPDK issue.
>    - I could see multiple fixes/patches in the net/ena area, but not able
>    to identify which patch would exactly fix this issue.
>
> For example:
> http://git.dpdk.org/dpdk/diff/?h=releases&id=aab58857330bb4bd03f6699bf1ee716f72993774
>
> https://inbox.dpdk.org/dev/20210430125725.28796-6-mk@semihalf.com/T/#me99457c706718bb236d1fd8006ee7a0319ce76fc
>
>
> Could you please help here and let me know what patch could fix this issue.
>
>
> Regards
> Amiya
>