DPDK patches and discussions
 help / color / mirror / Atom feed
From: SANDEEP KUMAR <sandeepkumar2016000@gmail.com>
To: dev@dpdk.org
Subject: Application crash when use dpdk interrupt with virtual function of i40e NIC
Date: Mon, 22 May 2023 12:55:59 +0530	[thread overview]
Message-ID: <CAOy+CXJmSSsK5SUm8hg174oaZqz+BUDTO7T2usrY8ye53Qf_2g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]

Hi,

I am trying to enable DPDK interrupts with the function
rte_eth_dev_rx_intr_enable with a virtual function of i40e NIC then
following segmentation fault coming when the function is called. The same
code does not give a fault when used against the virtual function of the
Intel 82599 NIC. I am using DPDK version dpdk-stable-22.11.1

Program received signal SIGSEGV, *Segmentation fault.*
0x00007fffe72bceb5 in iavf_dev_rx_queue_intr_enable () from
/usr/local/lib64/dpdk/pmds-23.0/librte_net_iavf.so.23.0
Missing separate debuginfos, use: debuginfo-install
bzip2-libs-1.0.6-13.el7.x86_64 elfutils-libelf-0.176-5.el7.x86_64
libacl-2.2.51-15.el7.x86_64 libarchive-3.1.2-14.el7_7.x86_64
libattr-2.4.46-13.el7.x86_64 libpcap-1.5.3-13.el7_9.x86_64
lzo-2.06-8.el7.x86_64
*(gdb) bt*
#0  0x00007fffe72bceb5 in iavf_dev_rx_queue_intr_enable () from
/usr/local/lib64/dpdk/pmds-23.0/librte_net_iavf.so.23.0
#1  0x00007ffff6be98df in rte_eth_dev_rx_intr_enable () from
/usr/local/lib64/librte_ethdev.so.23
#2  0x0000000000624a40 in init_queues ()
#3  0x0000000000410612 in packet_handler_fmwk_init ()
#4  0x0000000000405e23 in main ()
(gdb)

Is there a known issue around this in DPDK ?

Thanks & Regards,
Sandeep Kumar

[-- Attachment #2: Type: text/html, Size: 5773 bytes --]

                 reply	other threads:[~2023-05-22  7:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAOy+CXJmSSsK5SUm8hg174oaZqz+BUDTO7T2usrY8ye53Qf_2g@mail.gmail.com \
    --to=sandeepkumar2016000@gmail.com \
    --cc=dev@dpdk.org \
    /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).