From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by dpdk.org (Postfix, from userid 33) id F075C2B96; Mon, 28 May 2018 15:38:12 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Mon, 28 May 2018 13:38:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: ethdev X-Bugzilla-Version: 18.05 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: radu.nicolau@intel.com X-Bugzilla-Status: CONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://dpdk.org/tracker/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 52] Bonding PMD may fail to accept new slaves in certain conditions X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2018 13:38:13 -0000 https://dpdk.org/tracker/show_bug.cgi?id=3D52 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 =3D 2 Root cause is a mismatch in port link status caused by testpmd implementati= on that does not re-check all ports, but stops at the first port that shows li= nk down. To work around the issue insert "show port info all" command after "port st= op 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/ --=20 You are receiving this mail because: You are the assignee for the bug.=