From: Al Patel <alps.oss@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>, Al Patel <alps.oss@gmail.com>
Subject: [dpdk-dev] Issue with binding NIC of type 82545EM to dpdk
Date: Tue, 29 Mar 2016 10:11:34 -0400 [thread overview]
Message-ID: <CAF9p440ikVd4bsOemwow-dMrK_LGXaDODrPqS_3r60cyTbhGDA@mail.gmail.com> (raw)
Hi,
I am having an issue with binding a nic of type 82545EM to dpdk. I am using
a
fedoracore23 VM on MAC with VMFusion.
./dpdk_nic_bind.py -b uio_pci_generic 0000:02:02.0
Error: bind failed for 0000:02:02.0 - Cannot bind to driver uio_pci_generic
Error: unbind failed for 0000:02:02.0 - Cannot open
/sys/bus/pci/drivers//unbind
it is unbound from e1000, repeating the command:
./dpdk_nic_bind.py -b uio_pci_generic 0000:02:02.0
Error: bind failed for 0000:02:02.0 - Cannot bind to driver uio_pci_generic
I repeated the same test on a ubuntu vm running on Virtualbox with
NIC type 82450EM
In this case, the device is able to bind successfully to uio_pci_generic
driver.
There is a igb_uio module that present. The device cannot be bound to the
igb_uio
driver.
My question is that why is the device being able to be bound to
uio_pci_generic driver on ubuntu and not on fedoracore? (Albeit on fedora
device is 82545EM and on ubuntu it is 82540EM). Both these are reported as
tested by Intel:
• Emulated Intel® 82540EM Gigabit Ethernet Controller [8086:100e]
• Emulated Intel® 82545EM Gigabit Ethernet Controller [8086:100f]
http://www.intel.com/content/dam/www/public/us/en/documents/release-notes/dpdk-release-notes.pdf
Are there any debugs to collect that can shed some light?
Details:
# lspci -v -s 02:02.0
02:02.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet
Controller (Copper) (rev 01)
DeviceName: Ethernet1
Subsystem: VMware PRO/1000 MT Single Port Adapter
Physical Slot: 34
Flags: 66MHz, medium devsel
Memory at fd5a0000 (64-bit, non-prefetchable) [size=128K]
Memory at fdfe0000 (64-bit, non-prefetchable) [size=64K]
I/O ports at 2040 [size=64]
[virtual] Expansion ROM at fd510000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
Capabilities: [e4] PCI-X non-bridge device
Kernel modules: e1000
Thx
-a
next reply other threads:[~2016-03-29 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 14:11 Al Patel [this message]
2016-03-29 16:26 ` Ferruh Yigit
2016-03-29 17:14 ` Al Patel
2016-03-30 0:51 ` Lu, Wenzhuo
2016-03-30 12:59 ` Al Patel
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=CAF9p440ikVd4bsOemwow-dMrK_LGXaDODrPqS_3r60cyTbhGDA@mail.gmail.com \
--to=alps.oss@gmail.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).