From: Aman Thakur <r.aman.t.435@gmail.com>
To: users@dpdk.org
Subject: Bond fails to start all slaves
Date: Fri, 4 Apr 2025 19:38:23 +0530 [thread overview]
Message-ID: <CAOUH2--o=L4gN-cKouohf3_fMCZ-tMOgs4eTGtkctV2e983v-g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]
Hi users,
Environment
===========
DPKD Version : 21.11.9
Bond member
slave 1 : Intel e1000e I217 1Gbps "Ethernet Connection I217-LM 153a"
slave 2 : Intel e1000e 82574 1Gbps "82574L Gigabit Network Connection 10d3"
OS :Rocky Linux 8.10 rhel centos fedora
Compiler: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-24)
Steps to reproduce
==================
1. bind ports to dpdk
dpdk-devbind.py -b vfio-pci 0000:b1:00.0 0000:b1:00.1
2. launch testpmd
./dpdk-testpmd -l 0-3 -n 4 -- -i --portmask=0x1 --nb-cores=2
--no-lsc-interrupt --port-topology=chained
3. create bonding device
port stop all
create bonded device 0 0
add bonding slave 0 2
add bonding slave 1 2
port start all
show port info all
Results:
========
the link status of 1 ports is down ( not specific to mode )
In every bond mode link speed of the slave interface 1 Intel e1000e I217
1Gbps "Ethernet Connection I217-LM 153a" is down.
Port 0 Link down
Port 1 Link up at 1 Gbps FDX Autoneg
Port 1: link state change event
Port 2 Link up at 1 Gbps FDX Autoneg
Done
Expected Result:
================
The status of all ports should be normal. Link status of both member/slave
should be up and status of port 0 should not be always down.
In mode 0 with bond mode 0 link speed should be 2 Gbps with 2 members each
1 1Gbps.
*My Questions:*
1. What could be causing one of the slaves to become inactive ?
2. Is there a specific configuration or step I might be missing that's
preventing the bond from utilizing both slaves ?
3. Are there any known compatibility issues or limitations with Intel
e1000e I217 1Gbps "Ethernet Connection I217-LM 153a" that could explain
this behavior?
[-- Attachment #2: Type: text/html, Size: 1983 bytes --]
next reply other threads:[~2025-04-07 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 14:08 Aman Thakur [this message]
2025-04-07 10:05 ` madhukar mythri
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='CAOUH2--o=L4gN-cKouohf3_fMCZ-tMOgs4eTGtkctV2e983v-g@mail.gmail.com' \
--to=r.aman.t.435@gmail.com \
--cc=users@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).