From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 919] Error attaching device to DPDK
Date: Mon, 03 Jan 2022 18:19:11 +0000 [thread overview]
Message-ID: <bug-919-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=919
Bug ID: 919
Summary: Error attaching device to DPDK
Product: DPDK
Version: 19.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: jmover@me.com
Target Milestone: ---
Error attaching device to DPDK while adding interfaces to OVS bond on Ubuntu.
Ubuntu 20.04.3
DPDK 19.11.10
OVS 2.13.3
NICs Intel x710 (fw 7.10)
Command:
ovs-vsctl add-bond ovsbr0 bond0 ens2f0 ens2f1 ens3f0 ens3f1 \
-- set Interface ens2f0 type=dpdk "options:dpdk-devargs=0000:5e:00.0" \
-- set Interface ens2f1 type=dpdk "options:dpdk-devargs=0000:5e:00.1" \
-- set Interface ens3f0 type=dpdk "options:dpdk-devargs=0000:d8:00.0" \
-- set Interface ens3f1 type=dpdk "options:dpdk-devargs=0000:d8:00.1"
Output:
ovs-vsctl: Error detected while setting up 'ens2f0': Error attaching device
'0000:5e:00.0' to DPDK. See ovs-vswitchd log for details.
ovs-vsctl: Error detected while setting up 'ens2f1': Error attaching device
'0000:5e:00.1' to DPDK. See ovs-vswitchd log for details.
ovs-vsctl: Error detected while setting up 'ens3f0': Error attaching device
'0000:d8:00.0' to DPDK. See ovs-vswitchd log for details.
ovs-vsctl: Error detected while setting up 'ens3f1': Error attaching device
'0000:d8:00.1' to DPDK. See ovs-vswitchd log for details.
ovs-vsctl: The default log directory is "/var/log/openvswitch".
/var/log/openvswitch/ovs-vswitchd.log
2022-01-03T16:00:05.776Z|00083|dpdk|ERR|EAL: Driver cannot attach the device
(0000:d8:00.1)
2022-01-03T16:00:05.776Z|00084|dpdk|ERR|EAL: Failed to attach device on primary
process
2022-01-03T16:00:05.776Z|00085|netdev_dpdk|WARN|Error attaching device
'0000:d8:00.1' to DPDK
2022-01-03T16:00:05.776Z|00086|netdev|WARN|ens3f1: could not set configuration
(Invalid argument)
2022-01-03T16:00:05.776Z|00087|dpdk|ERR|Invalid port_id=32
VT-d support is enabled:
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic
root=UUID=2849776f-b167-447f-a5d1-ea4b5c831c35 ro iommu=pt intel_iommu=on
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-01-03 18:19 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=bug-919-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 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).