DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 915] [20.11.4-rc1][mlx5] segfault when changing number of rxqs
Date: Wed, 22 Dec 2021 17:01:15 +0000	[thread overview]
Message-ID: <bug-915-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=915

            Bug ID: 915
           Summary: [20.11.4-rc1][mlx5] segfault when changing number of
                    rxqs
           Product: DPDK
           Version: 20.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: alialnu@nvidia.com
  Target Milestone: ---

$ build/app/dpdk-testpmd -n 4  -a
0000:00:07.0,dv_flow_en=1,rxqs_min_mprq=1,mprq_log_stride_num=11,mprq_log_stride_size=8,mprq_en=1
 -a
0000:00:08.0,dv_flow_en=1,rxqs_min_mprq=1,mprq_log_stride_num=11,mprq_log_stride_size=8,mprq_en=1
-- --mbcache=512 -i  --txd=8192 --rxd=8192

> port stop all
> port config all rxq 4
> port start all

Result is a segfault with the following trace:

#0  0x0000555555f76c01 in mlx5_mr_update_mp ()
#1  0x00005555557ecbbf in mlx5_dev_start ()
#2  0x0000555555c5bfaf in rte_eth_dev_start ()
#3  0x0000555555b1aba6 in start_port.part ()
#4  0x0000555555c53f6f in cmdline_parse ()
#5  0x0000555555c52db4 in cmdline_valid_buffer ()
#6  0x0000555555c565eb in rdline_char_in ()
#7  0x0000555555c52e89 in cmdline_in ()
#8  0x0000555555c53050 in cmdline_interact ()
#9  0x0000555555894176 in main ()

OS: Ubuntu 20.04
NIC: ConnectX-5
MLNX_OFED: MLNX_OFED_LINUX-5.5-1.0.3.2
FW: 16.32.1010

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2021-12-22 17:01 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=bug-915-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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).