From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 865] [dpdk-21.11]launch testpmd with "--vfio-intr=legacy" appears core dumped
Date: Fri, 29 Oct 2021 06:50:27 +0000 [thread overview]
Message-ID: <bug-865-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=865
Bug ID: 865
Summary: [dpdk-21.11]launch testpmd with "--vfio-intr=legacy"
appears core dumped
Product: DPDK
Version: 21.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: yanx.xia@intel.com
Target Milestone: ---
Environment:
OS: Ubuntu21.10 kernel driver: 5.13.0-19-generic
Compiler: gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0
Hardware platform: Intel(R) Xeon(R) Platinum 8280M CPU @ 2.70GHz
NIC hardware: fortpark_BASE-T
Steps to reproduce
# 1. bind nic to vfio-pci
usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:3d:00.0 0000:3d:00.1
# 2. bbuild app and check it
meson configure -Dexamples=link_status_interrupt x86_64-native-linuxapp-clang
ninja -C x86_64-native-linuxapp-clang
ls x86_64-native-linuxapp-clang/examples/dpdk-link_status_interrupt
# 3. launch testpmd
x86_64-native-linuxapp-clang/examples/dpdk-link_status_interrupt -l 1,2,3,4
-n 4 --file-prefix=dpdk_29738_20211027174729 --vfio-intr=legacy -- -p 0x3
Show the output from the previous commands:
x86_64-native-linuxapp-clang/examples/dpdk-link_status_interrupt -l 1,2,3,4
-n 4 --file-prefix=dpdk_29738_20211027174729 --vfio-intr=legacy -- -p 0x3
EAL: Detected CPU lcores: 112
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/dpdk_29738_20211027174729/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: 1024 hugepages of size 2097152 reserved, but no mounted hugetlbfs found
for that size
EAL: VFIO support initialized
EAL: Using IOMMU type 1 (Type 1)
EAL: Error setting up interrupts!
EAL: 0000:3d:00.0 setup device failed
EAL: Requested device 0000:3d:00.0 cannot be used
EAL: 0000:3d:00.1 failed to select IOMMU type
EAL: Requested device 0000:3d:00.1 cannot be used
PANIC in main():
No Ethernet port - bye
6:
[x86_64-native-linuxapp-clang/examples/dpdk-link_status_interrupt(_start+0x25)
[0x1107fd5]]
5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x7d) [0x7f469af4a07d]]
4: [/lib/x86_64-linux-gnu/libc.so.6(+0x2dfd0) [0x7f469af49fd0]]
3:
[x86_64-native-linuxapp-clang/examples/dpdk-link_status_interrupt(main+0x9d8)
[0x1108a78]]
2:
[x86_64-native-linuxapp-clang/examples/dpdk-link_status_interrupt(__rte_panic+0xbb)
[0x1293d7b]]
1:
[x86_64-native-linuxapp-clang/examples/dpdk-link_status_interrupt(rte_dump_stack+0x20)
[0x12ba500]]
Aborted (core dumped)
Expected Result:
x86_64-native-linuxapp-clang/examples/dpdk-link_status_interrupt -l 1,2,3,4
-n 4 --file-prefix=dpdk_29738_20211027174729 --vfio-intr=legacy -- -p 0x3
EAL: Detected CPU lcores: 112
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/dpdk_29738_20211027174729/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: 1024 hugepages of size 2097152 reserved, but no mounted hugetlbfs found
for that size
EAL: VFIO support initialized
EAL: Using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: net_i40e (8086:37d2) device: 0000:3d:00.0 (socket 0)
EAL: Error enabling INTx interrupts for fd 31
EAL: Probe PCI driver: net_i40e (8086:37d2) device: 0000:3d:00.1 (socket 0)
EAL: Error enabling INTx interrupts for fd 35
Lcore 1: RX port 0
Lcore 2: RX port 1
Initializing port 0... EAL: Error masking INTx interrupts for fd 31
done:
Port 0, MAC address: A4:BF:01:6A:68:E1Initializing port 1... EAL: Error masking
INTx interrupts for fd 35
done:
Port 1, MAC address: A4:BF:01:6A:68:E2
Checking link status...................................................In
registered callback...
Event type: LSC interrupt
Port 0 Link up at 10 Gbps FDX Autoneg....In registered callback...
Event type: LSC interrupt
Port 1 Link up at 10 Gbps FDX Autonegdone
LSI: entering main loop on lcore 2
LSI: -- lcoreid=2 portid=1
LSI: lcore 4 has nothing to do
LSI: lcore 3 has nothing to do
LSI: entering main loop on lcore 1
LSI: -- lcoreid=1 portid=0
Port 0 Link up at 10 Gbps FDX AutonegPort 1 Link up at 10 Gbps FDX AutonegPort
statistics ====================================
Statistics for port 0 ------------------------------
Link status: Link up
Link speed: 10 Gbps
Link duplex: full-duplex
Packets sent: 0
Packets received: 0
Packets dropped: 0
Statistics for port 1 ------------------------------
Link status: Link up
Link speed: 10 Gbps
Link duplex: full-duplex
Packets sent: 0
Packets received: 0
Packets dropped: 0
Aggregate statistics ===============================
Total packets sent: 0
Total packets received: 0
Total packets dropped: 0
====================================================
Version the regression was introduced:
commit 8cb5d08db940a6b26f5c5ac03b49bac25e9a7022
Author: Harman Kalra <hkalra@marvell.com>
Date: Sat Oct 23 02:19:32 2021 +0530
interrupts: extend event list
Dynamically allocating the efds and elist array of intr_handle
structure, based on size provided by user. Eg size can be
MSIX interrupts supported by a PCI device.
Signed-off-by: Harman Kalra <hkalra@marvell.com>
Signed-off-by: David Marchand <david.marchand@redhat.com>
Acked-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Tested-by: Raslan Darawsheh <rasland@nvidia.com>
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-10-29 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 6:50 bugzilla [this message]
2021-11-02 1:59 ` 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-865-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).