From: Amiya Mohakud <amohakud@paloaltonetworks.com>
To: dev@dpdk.org
Cc: Sachin Kanoje <skanoje@paloaltonetworks.com>,
Megha Punjani <mpunjani@paloaltonetworks.com>,
Sharad Saha <ssaha@paloaltonetworks.com>,
Eswar Sadaram <esadaram@paloaltonetworks.com>
Subject: Re: DPDK:20.11.1: net/ena crash while fetching xstats
Date: Mon, 18 Apr 2022 20:48:48 +0530 [thread overview]
Message-ID: <CAC6kMfMhL9mWhDL1EHKCA=SUSaemEvjTOLMO5PYAFqT01oxD5A@mail.gmail.com> (raw)
In-Reply-To: <CAC6kMfP=incDD-W1K-bNBjXt1U_jknVySzPGgG51EMXj8Rg6Ew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2103 bytes --]
+ 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
>
[-- Attachment #2: Type: text/html, Size: 6887 bytes --]
next prev parent reply other threads:[~2022-04-18 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 8:33 Amiya Mohakud
2022-04-18 15:18 ` Amiya Mohakud [this message]
2022-04-19 12:10 ` Michał Krawczyk
2022-04-19 15:01 ` Stephen Hemminger
2022-04-19 20:27 ` Michał Krawczyk
2022-04-19 22:25 ` Stephen Hemminger
2022-04-19 23:09 ` Stephen Hemminger
2022-04-20 8:37 ` Amiya Mohakud
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC6kMfMhL9mWhDL1EHKCA=SUSaemEvjTOLMO5PYAFqT01oxD5A@mail.gmail.com' \
--to=amohakud@paloaltonetworks.com \
--cc=dev@dpdk.org \
--cc=esadaram@paloaltonetworks.com \
--cc=mpunjani@paloaltonetworks.com \
--cc=skanoje@paloaltonetworks.com \
--cc=ssaha@paloaltonetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).