From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/vhost/virtio Bug 1424] x710 ports Error attaching device to DPDK
Date: Sun, 28 Apr 2024 11:03:28 +0000 [thread overview]
Message-ID: <bug-1424-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1424
Bug ID: 1424
Summary: x710 ports Error attaching device to DPDK
Product: DPDK
Version: 21.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: vhost/virtio
Assignee: dev@dpdk.org
Reporter: 125163227@qq.com
Target Milestone: ---
dpdk tools:
Network devices using DPDK-compatible driver
============================================
0000:b1:00.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=vfio-pci
unused=i40e
ovs-vswitchd:
2024-04-28T10:56:02.508Z|00518|dpdk|ERR|EAL: Driver cannot attach the device
(0000:b1:00.0)
2024-04-28T10:56:02.508Z|00519|dpdk|ERR|EAL: Failed to attach device on primary
process
2024-04-28T10:56:02.508Z|00520|netdev_dpdk|WARN|Error attaching device
'0000:b1:00.0' to DPDK
2024-04-28T10:56:02.508Z|00521|netdev|WARN|eth4: could not set configuration
(Invalid argument)
2024-04-28T10:56:02.508Z|00522|dpdk|ERR|Invalid port_id=288
CPU INFO:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 52 bits physical, 57 bits virtual
Byte Order: Little Endian
CPU(s): 128
On-line CPU(s) list: 0-127
Vendor ID: AuthenticAMD
BIOS Vendor ID: Advanced Micro Devices, Inc.
Model name: AMD EPYC 9334 32-Core Processor
BIOS Model name: AMD EPYC 9334 32-Core Processor
HugePages_Total: 12
HugePages_Free: 11
HugePages_Rsvd: 0
HugePages_Surp: 0
other_config : {dpdk-init="true", dpdk-socket-mem="1024,1024",
pmd-cpu-mask="0x100", userspace-tso-enable="true", vlan-limit="0"}
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3816 bytes --]
reply other threads:[~2024-04-28 11:03 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-1424-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 read-only IMAP folder(s) and NNTP newsgroup(s).