From: Saurabh Mishra <saurabh.globe@gmail.com>
To: users@dpdk.org, dev@dpdk.org
Subject: [dpdk-dev] DPDK bnx2x driver link problem
Date: Wed, 27 Jan 2016 17:49:41 -0800 [thread overview]
Message-ID: <CAMnwyJ30f1arOR6kg_j+_bwxD5NYf_cr-1-gsWdFpui8WxY9Uw@mail.gmail.com> (raw)
Looks like bnx2x has link problem…sometime it sees link up and most of the
time it see link down even though the RX/TX counters are going up.
Has anybody seen this type of problem? If I don't use DPDK then I don't see
this type of link related problem.
The counter shows that it’s receiving and transmitting packets.
I tried with –n1, -n2 and –n4.
*1st Time:*
[root@ ~]# ./symmetric_mp fakeelf -c 2 -m2048 -n4 --proc-type=primary -- -p
3 --num-procs=2 --proc-id=0
PMD: bnx2x_print_adapter_info(): Switch : 0
PMD: bnx2x_print_adapter_info(): ===================================
Checking link
status..........................................................................................done
Port 0 Link Up - speed 10000 Mbps - full-duplex
Port 1 Link Down
APP: Finished Process Init.
Lcore 1 using ports 0 1
lcore 1 using queue 0 of each port
^C
Exiting on signal 2
Port 0: RX - 3, TX - 27, Drop - 0
Port 1: RX - 27, TX - 3, Drop - 0
*Second time:*
[root@ ~]# ./symmetric_mp fakeelf -c 2 -m2048 -n4 --proc-type=primary -- -p
3 --num-procs=2 --proc-id=0
PMD: bnx2x_print_adapter_info(): Switch : 0
PMD: bnx2x_print_adapter_info(): ===================================
Checking link
status..........................................................................................done
Port 0 Link Down
Port 1 Link Down
APP: Finished Process Init.
Lcore 1 using ports 0 1
lcore 1 using queue 0 of each port
^C
Exiting on signal 2
Port 0: RX - 3, TX - 17, Drop - 0
Port 1: RX - 17, TX - 3, Drop - 0
[root@ ~]#
*Third time:*
[root@ ~]# ./symmetric_mp fakeelf -c 2 -m2048 -n4 --proc-type=primary -- -p
3 --num-procs=2 --proc-id=0
Checking link
status..........................................................................................done
Port 0 Link Down
Port 1 Link Down
APP: Finished Process Init.
Lcore 1 using ports 0 1
lcore 1 using queue 0 of each port
^C
Exiting on signal 2
Port 0: RX - 8, TX - 84, Drop - 0
Port 1: RX - 84, TX - 8, Drop - 0
[root@~]#
*4th time:*
Checking link
status..........................................................................................done
Port 0 Link Down
Port 1 Link Down
APP: Finished Process Init.
Lcore 1 using ports 0 1
lcore 1 using queue 0 of each port
^C
Exiting on signal 2
Port 0: RX - 2, TX - 14, Drop - 0
Port 1: RX - 14, TX - 2, Drop - 0
[root@ ~]#
reply other threads:[~2016-01-28 1:49 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=CAMnwyJ30f1arOR6kg_j+_bwxD5NYf_cr-1-gsWdFpui8WxY9Uw@mail.gmail.com \
--to=saurabh.globe@gmail.com \
--cc=dev@dpdk.org \
--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).