From: <mariappan.rajendran@infinite.com>
To: <users@dpdk.org>
Subject: [dpdk-users] 82575EB binding is failed
Date: Wed, 6 Apr 2016 15:21:22 +0530 [thread overview]
Message-ID: <2B014DC1628745DDAE41CBCC6D4613E9@infics.com> (raw)
Hi Team,
I am running DPDK 2.2.0 on top of Ubuntu 14.04 and my server have 2 NIC cards. With this, when I am trying to bind my non active 82575EB NIC to DPDK, but after giving the PCI ID, the server hanged. Below are the logs from setup.sh.
Option: 23
Network devices using DPDK-compatible driver
============================================
<none>
Network devices using kernel driver
===================================
0000:03:00.0 '82575EB Gigabit Network Connection' if=eth0 drv=igb unused=igb_uio *Active*
0000:03:00.1 '82575EB Gigabit Network Connection' if=eth1 drv=igb unused=igb_uio
Other network devices
=====================
<none>
Enter PCI address of device to bind to IGB UIO driver: 0000:03:00.1
OK
Press enter to continue ... (after binding system resides in this same screen)
I also ensured that this NIC is supported or not by DPDK by browsing the rte_pci_dev_ids.h file, it is there, but still the binding is failed. Below are the logs.
tellabs@tellabs:~/dpdk-1.7.1$ lspci -nn | grep -i eth
03:00.0 Ethernet controller [0200]: Intel Corporation 82575EB Gigabit Network Connection [8086:10a7] (rev 02)
03:00.1 Ethernet controller [0200]: Intel Corporation 82575EB Gigabit Network Connection [8086:10a7] (rev 02)
tellabs@tellabs:~/dpdk$ grep -i "10a7" lib/librte_eal/common/include/rte_pci_dev_ids.h
#define E1000_DEV_ID_82575EB_COPPER 0x10A7
Please let me know what could be the problem, and how to resolve it. Your help is much appreciated.
Thanks,
Mari.
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s).
If you are not the intended recipient, please notify so to the sender by e-mail and delete the original message.
In such cases, please notify us immediately at info@infinite.com . Further, you are not to copy,
disclose, or distribute this e-mail or its contents to any unauthorized person(s) .Any such actions are
considered unlawful. This e-mail may contain viruses. Infinite has taken every reasonable precaution to minimize
this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should
carry out your own virus checks before opening the e-mail or attachments. Infinite reserves the right to monitor
and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail
address may be stored on the Infinite e-mail system.
***INFINITE******** End of Disclaimer********INFINITE********
reply other threads:[~2016-04-06 9:50 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=2B014DC1628745DDAE41CBCC6D4613E9@infics.com \
--to=mariappan.rajendran@infinite.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).