DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 52] Bonding PMD may fail to accept new slaves in certain conditions
Date: Mon, 28 May 2018 13:38:12 +0000	[thread overview]
Message-ID: <bug-52-3@http.dpdk.org/tracker/> (raw)

https://dpdk.org/tracker/show_bug.cgi?id=52

            Bug ID: 52
           Summary: Bonding PMD may fail to accept new slaves in certain
                    conditions
           Product: DPDK
           Version: 18.05
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: minor
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: radu.nicolau@intel.com
  Target Milestone: ---

When using testpmd to test bonding, the following sequence of commands will
fail as described:

testpmd> port stop all
testpmd> create bonded device 4 0
testpmd> add bonding slave 0 2
testpmd> add bonding slave 1 2

__eth_bond_slave_add_lock_free(352) - Invalid link properties for slave 1 in
bonding mode 4
Failed to add slave 1 to master port = 2


Root cause is a mismatch in port link status caused by testpmd implementation
that does not re-check all ports, but stops at the first port that shows link
down.

To work around the issue insert "show port info all" command after "port stop
all" if using testpmd, or make sure that the application either calls
rte_eth_link_get on all ports that will be bound, or on none of them.

Patch addressing the issue: https://dpdk.org/dev/patchwork/patch/39567/

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

                 reply	other threads:[~2018-05-28 13:38 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-52-3@http.dpdk.org/tracker/ \
    --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).