From: 朱 <zhuhy163@163.com>
To: users@dpdk.org
Subject: DPDK segment fault in vmxnet3
Date: Mon, 30 May 2022 16:39:38 +0800 (CST) [thread overview]
Message-ID: <38de8332.52d3.181141ee5c5.Coremail.zhuhy163@163.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2027 bytes --]
ESXi 6.5
Guest OS: Ubuntu 20.04
Network Driver: VMXNET3
DPDK: 21.11.1
There are three network adapters, one for ssh, two for DPDK.
## set kernel parameters
echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
echo 1 > /sys/module/vfio/parameters/enable_unsafe_noiommu_mode
## bind dev
root@dpdk01:~/dpdk-stable-21.11.1/usertools# ./dpdk-devbind.py --status-dev net
Network devices using DPDK-compatible driver
============================================
0000:0b:00.0 'VMXNET3 Ethernet Controller 07b0' drv=vfio-pci unused=vmxnet3
0000:13:00.0 'VMXNET3 Ethernet Controller 07b0' drv=vfio-pci unused=vmxnet3
Network devices using kernel driver
===================================
0000:03:00.0 'VMXNET3 Ethernet Controller 07b0' if=eth0 drv=vmxnet3 unused=vfio-pci *Active*
# testpmd segment fault
root@dpdk01:~/dpdk-stable-21.11.1/build/app# ./dpdk-testpmd -l 0-3 -n 4
EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available 1048576 kB hugepages reported
EAL: VFIO support initialized
EAL: Using IOMMU type 8 (No-IOMMU)
EAL: Ignore mapping IO port bar(3)
EAL: Probe PCI driver: net_vmxnet3 (15ad:7b0) device: 0000:0b:00.0 (socket 0)
EAL: Ignore mapping IO port bar(3)
EAL: Probe PCI driver: net_vmxnet3 (15ad:7b0) device: 0000:13:00.0 (socket 0)
testpmd: create a new mbuf pool <mb_pool_0>: n=171456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
Configuring Port 0 (socket 0)
Port 0: 00:0C:29:AE:03:68
Configuring Port 1 (socket 0)
Segmentation fault (core dumped)
# gdb info
Thread 1 "dpdk-testpmd" received signal SIGSEGV, Segmentation fault.
0x0000555555930c0f in vmxnet3_write_mac.isra ()
(gdb) where
#0 0x0000555555930c0f in vmxnet3_write_mac.isra ()
#1 0x0000555555931e5c in vmxnet3_dev_start ()
#2 0x000055555624c6cc in rte_eth_dev_start ()
#3 0x00005555560e13d0 in start_port ()
#4 0x000055555597d98b in main ()
[-- Attachment #1.2: Type: text/html, Size: 3074 bytes --]
[-- Attachment #2: 图片.png --]
[-- Type: image/png, Size: 47164 bytes --]
reply other threads:[~2022-05-31 14:50 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=38de8332.52d3.181141ee5c5.Coremail.zhuhy163@163.com \
--to=zhuhy163@163.com \
--cc=users@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).