All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 618] [mlx5] secondary process fails to start
Date: Thu, 14 Jan 2021 14:09:27 +0000	[thread overview]
Message-ID: <bug-618-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 618
           Summary: [mlx5] secondary process fails to start
           Product: DPDK
           Version: 18.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: alialnu@nvidia.com
  Target Milestone: ---

Primary process starts fine:

"""
$ symmetric_mp -n 4 -w 0000:00:05.0,dv_flow_en=0 -w 0000:00:06.0,dv_flow_en=0
-l 1 --proc-type=primary -- -p 0x3 --num-procs=2 --proc-id=0

EAL: Detected 8 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable
clock cycles !
EAL: PCI device 0000:00:05.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15b3:1019 net_mlx5
EAL: PCI device 0000:00:06.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15b3:1019 net_mlx5
# Initialising port 0... # Initialising port 1...
Checking link statusdone
Port0 Link Up. Speed 10000 Mbps - full-duplex
Port1 Link Up. Speed 10000 Mbps - full-duplex
APP: Finished Process Init.
Lcore 1 using ports 0 1
lcore 1 using queue 0 of each port
"""

The secondary process fails to start.
"""
$ symmetric_mp -n 4 -w 0000:00:05.0,dv_flow_en=0 -w 0000:00:06.0,dv_flow_en=0
-l 2 --proc-type=secondary -- -p 0x3 --num-procs=2 --proc-id=1

EAL: Detected 8 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_20671_9af0b0dac948
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable
clock cycles !
EAL: PCI device 0000:00:05.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15b3:1019 net_mlx5
net_mlx5: port 0 mmap failed for BF reg of txq 1
net_mlx5: probe of PCI device 0000:00:05.0 aborted after encountering an error:
No such device or address
EAL: Requested device 0000:00:05.0 cannot be used
EAL: PCI device 0000:00:06.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15b3:1019 net_mlx5
net_mlx5: port 1 mmap failed for BF reg of txq 1
net_mlx5: probe of PCI device 0000:00:06.0 aborted after encountering an error:
No such device or address
EAL: Requested device 0000:00:06.0 cannot be used
EAL: Error - exiting with code: 1
  Cause: No Ethernet ports - bye
"""


NIC: ConnectX-5
OFED: MLNX_OFED_LINUX-5.2-1.0.4.0 (Issue doesn't reproduce with 5.1-2.5.8.0)
Firmware version: 16.29.1016

OS: RHEL 7.4
Kernel: 3.10.0-693.el7.x86_64
gcc: 4.8.5

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

             reply	other threads:[~2021-01-14 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 14:09 bugzilla [this message]
2021-01-20 11:21 ` [dpdk-dev] [Bug 618] [mlx5] secondary process fails to start bugzilla

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-618-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.