From: "CHIDAMBARAM, GOVIND (GOVIND)" <govind@research.att.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] i40e_dev_sync_phy_type errors
Date: Wed, 31 Jul 2019 03:01:41 +0000 [thread overview]
Message-ID: <D9667CC9.3AC1A%govind@research.att.com> (raw)
Any idea what is wrong? I see errors with i40e
i40e_dev_sync_phy_type(): Failed to sync phy type: status=-53
# lspci -k -s 0000:81:00.0
81:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)
Subsystem: Hewlett-Packard Company Ethernet 10Gb 2-port 562SFP+ Adapter
Kernel driver in use: igb_uio
Kernel modules: i40e
# lspci -k -s 0000:c1:00.0
c1:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)
Subsystem: Hewlett-Packard Company Ethernet 10Gb 2-port 562SFP+ Adapter
Kernel driver in use: igb_uio
Kernel modules: i40e
/dpdk-18.08/x86_64-native-linuxapp-gcc/app/testpmd -w 0000:81:00.0 -w 0000:81:00.1 -w 0000:c1:00.0 -w 0000:c1:00.1 -- -i --rxq=4 --txq=4 --forward-mode=rxonly
EAL: Detected 176 lcore(s)
EAL: Detected 4 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: PCI device 0000:81:00.0 on NUMA socket 2
EAL: probe driver: 8086:1572 net_i40e
i40e_dev_sync_phy_type(): Failed to sync phy type: status=-53
EAL: PCI device 0000:81:00.1 on NUMA socket 2
EAL: probe driver: 8086:1572 net_i40e
i40e_dev_sync_phy_type(): Failed to sync phy type: status=-53
EAL: PCI device 0000:c1:00.0 on NUMA socket 3
EAL: probe driver: 8086:1572 net_i40e
i40e_dev_sync_phy_type(): Failed to sync phy type: status=-53
EAL: PCI device 0000:c1:00.1 on NUMA socket 3
EAL: probe driver: 8086:1572 net_i40e
i40e_dev_sync_phy_type(): Failed to sync phy type: status=-53
Interactive-mode selected
Set rxonly packet forwarding mode
testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=1547456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
testpmd: create a new mbuf pool <mbuf_pool_socket_1>: n=1547456, size=2176, socket=1
testpmd: preferred mempool ops selected: ring_mp_mc
testpmd: create a new mbuf pool <mbuf_pool_socket_2>: n=1547456, size=2176, socket=2
testpmd: preferred mempool ops selected: ring_mp_mc
testpmd: create a new mbuf pool <mbuf_pool_socket_3>: n=1547456, size=2176, socket=3
testpmd: preferred mempool ops selected: ring_mp_mc
Configuring Port 0 (socket 2)
i40e_dev_sync_phy_type(): Failed to sync phy type: status=-53
Port 0: 48:DF:37:68:AF:B0
Configuring Port 1 (socket 2)
i40e_dev_sync_phy_type(): Failed to sync phy type: status=-53
Port 1: 48:DF:37:68:AF:B8
Configuring Port 2 (socket 3)
i40e_dev_sync_phy_type(): Failed to sync phy type: status=-53
Port 2: 48:DF:37:65:82:A0
Configuring Port 3 (socket 3)
i40e_dev_sync_phy_type(): Failed to sync phy type: status=-53
Port 3: 48:DF:37:65:82:A8
Checking link statuses...
Done
Cheers
CG
reply other threads:[~2019-07-31 3:02 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=D9667CC9.3AC1A%govind@research.att.com \
--to=govind@research.att.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).