From: "Montorsi, Francesco" <fmontorsi@empirix.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] status of bnx2x driver?
Date: Fri, 4 May 2018 08:09:59 +0000 [thread overview]
Message-ID: <bb529b679c414f36813c64bcf5e71b92@bilemail1.empirix.com> (raw)
Hi all,
I'm trying to use DPDK 17.11.2 and DPDK 18.02.1 with a
Broadcom Limited NetXtreme II BCM57810 10 Gigabit Ethernet [14e4:168e]
NIC.
I did set
CONFIG_RTE_LIBRTE_BNX2X_PMD=y
And then tried the "testpmd" application.
Here's what I get:
EAL: Detected 32 lcore(s)
EAL: Probing VFIO support...
EAL: PCI device 0000:03:00.0 on NUMA socket 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:03:00.1 on NUMA socket 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:03:00.2 on NUMA socket 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:03:00.3 on NUMA socket 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:0a:00.0 on NUMA socket 0
EAL: probe driver: 14e4:168e net_bnx2x
EAL: PCI device 0000:0a:00.1 on NUMA socket 0
EAL: probe driver: 14e4:168e net_bnx2x
Interactive-mode selected
USER1: create a new mbuf pool <mbuf_pool_socket_0>: n=163456, size=2176, socket=0
USER1: create a new mbuf pool <mbuf_pool_socket_1>: n=163456, size=2176, socket=1
Configuring Port 0 (socket 0)
Fail to start port 0
Configuring Port 1 (socket 0)
Fail to start port 1
In dmesg I see:
...
[ 11.006979] bnx2x 0000:0a:00.0 ens3f0: Parity errors detected in blocks:
[ 11.007010] bnx2x: [bnx2x_open:12538(ens3f0)]Recovery flow hasn't been properly completed yet. Try again later.
[ 11.014147] bnx2x 0000:0a:00.1 ens3f1: Parity errors detected in blocks:
[ 11.014167] bnx2x: [bnx2x_open:12538(ens3f1)]Recovery flow hasn't been properly completed yet. Try again later.
[ 267.647210] bnx2x: [bnx2x_fw_command:3043(ens3f0)]FW failed to respond!
[ 267.647295] bnx2x 0000:0a:00.0 ens3f0: bc 7.15.3
[ 267.647343] bnx2x: [bnx2x_fw_dump_lvl:782(ens3f0)]3MCP PC at 0xffffffff
[ 273.551294] bnx2x: [bnx2x_fw_command:3043(ens3f1)]FW failed to respond!
[ 273.551382] bnx2x 0000:0a:00.1 ens3f1: bc 7.15.3
[ 273.551433] bnx2x: [bnx2x_fw_dump_lvl:782(ens3f1)]3MCP PC at 0xffffffff
[ 273.551506] bnx2x: [bnx2x_fw_dump_lvl:794(ens3f1)]Unable to dump trace buffer (mark ffffffff)
...
So my question is: what's the status of the bnx2x driver?
(apparently somebody already asked that in 2015: http://dpdk.org/ml/archives/dev/2015-November/027214.html ... I'm asking if there were any improvements)
Thanks,
Francesco Montorsi
reply other threads:[~2018-05-04 8:10 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=bb529b679c414f36813c64bcf5e71b92@bilemail1.empirix.com \
--to=fmontorsi@empirix.com \
--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).