From: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Problem in DPDK1.4 controlling 82599 ixgbe NICS with Fedora 19
Date: Thu, 10 Oct 2013 10:53:56 +0530 [thread overview]
Message-ID: <C7CE7EEF248E2B48BBA63D0ABEEE700C43EA663693@GUREXMB01.ASIAN.AD.ARICENT.COM> (raw)
Hi,
I am using DPDK1.4 with Fedora 19 [I am aware that DPDK1.4 release notes do not claim Fedora 19 as supported, but I tried nevertheless and reporting this issue]
When I bootup, I see the following in lscpi output [I have two dual port 82599 10 Gb NIC's]
01:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (rev 01)
01:00.1 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (rev 01)
03:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (rev 01)
03:00.1 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (rev 01)
I also have 4 interfaces in ifconfig output shown by Fedora 19 - p1p1, p1p2, p2p1, p2p2 corresponding to the 4 ports above.
These work fine.
Now I try to unbind these ports so that they can be controlled by DPDK. (I load the igb_uio ofcourse as usual)
Now I first unbind the port represented by p1p1, this works and DPDK takes over this port.
However, now when I try to unbind the p1p2, it gives the following error
[root@localhost DPDK]# ./tools/pci_unbind.py --bind=igb_uio p1p2
Error: bind failed for 0000:01:00.1 - Cannot bind to driver igb_uio
Error: unbind failed for 0000:01:00.1 - Cannot open /sys/bus/pci/drivers//unbind
I cannot unbind any other ports either.
The one port which is unbound works fine with DPDK application without issues.
So the question is, why are the other ports giving issues ?
The same machine works with Fedora18 properly and is able to unbind all the 4 ports.
Regards
-Prashant
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
next reply other threads:[~2013-10-10 5:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 5:23 Prashant Upadhyaya [this message]
2013-10-10 12:59 ` Cyril Cressent
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=C7CE7EEF248E2B48BBA63D0ABEEE700C43EA663693@GUREXMB01.ASIAN.AD.ARICENT.COM \
--to=prashant.upadhyaya@aricent.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).