From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 177] binding i40e with uio_pci_generic fails for DPDK 19.02.0-rc1
Date: Fri, 04 Jan 2019 03:22:15 +0000 [thread overview]
Message-ID: <bug-177-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=177
Bug ID: 177
Summary: binding i40e with uio_pci_generic fails for DPDK
19.02.0-rc1
Product: DPDK
Version: 18.11
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
DPDK: 19.02.0-rc1
uname -ar: Linux saesrv02-S2600CWR.intel.com 4.15.0-43-generic #46-Ubuntu SMP
Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
lsb_release -a:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
lsmod | grep uio:
igb_uio 16384 0
uio_pci_generic 16384 0
uio 20480 2 igb_uio,uio_pci_generic
Error:
$ ../../usertools/dpdk-devbind.py -b uio_pci_generic 0000:08:00.1
Error: bind failed for 0000:08:00.1 - Cannot bind to driver uio_pci_generic
Error: unbind failed for 0000:08:00.1 - Cannot open
/sys/bus/pci/drivers//unbind
Success with igb_uio:
../../usertools/dpdk-devbind.py -b igb_uio 0000:08:00.1
ethtool details for NIC:
driver: i40e
version: 2.1.14-k
firmware-version: 6.01 0x80003484 1.1747.0
expansion-rom-version:
bus-info: 0000:08:00.3
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
Has something changed for i40 PF to prevent probe or init in PMD level?
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-01-04 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 3:22 bugzilla [this message]
2019-01-10 2:41 ` [Bug 177] binding i40e with uio_pci_generic fails for DPDK 19.02.0-rc1 bugzilla
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=bug-177-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.