From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 845] vf testpmd core dumped after executing "device_del dev1" in qemu
Date: Thu, 28 Oct 2021 05:48:13 +0000 [thread overview]
Message-ID: <bug-845-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=845
Bug ID: 845
Summary: vf testpmd core dumped after executing "device_del
dev1" in qemu
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: ---
DPDK commit: b66412f24f17fcba5a248888bf4b3c1f5d6880de
OS: Ubuntu20.04.3
Compiler: gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Hardware platform: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz.
Repoduced steps:
# 1. bind nic to vfio-pci
./usertools/dpdk-devbind.py -b vfio-pci 0000:81:00.0
# 2. launch qemu
taskset -c 0-7 qemu-system-x86_64 -enable-kvm -pidfile
/tmp/.vm0.pid -m 10240 -cpu host -smp 8 -name vm0
-monitor unix:/tmp/vm0_monitor.sock,server,nowait -chardev
socket,path=/tmp/vm0_qga0.sock,server,nowait,id=vm0_qga0 -device
virtio-serial -device
virtserialport,chardev=vm0_qga0,name=org.qemu.guest_agent.0
-device e1000,netdev=nttsip1 -netdev
user,id=nttsip1,hostfwd=tcp:10.240.183.247:6000-:22 -monitor
stdio -drive file=/home/image/test_vfio.img -vnc
:5 -device vfio-pci,host=0000:81:00.0,id=dev1
# 3. ssh vm and execute command in vm
ssh 10.240.183.247 -p 6000
echo 0 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
echo 1024 >
/sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages
modprobe vfio
modprobe vfio-pci
echo 1 > /sys/module/vfio/parameters/enable_unsafe_noiommu_mode
usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:00:05.0
# 4. vf launch testpmd
x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 0,1,2,3,4,5,6,7 -n 1 -a
0000:00:05.0 --file-prefix=dpdk_10860_20211027111447 -- -i --hot-plug
# 5. execute "device_del dev1" in the qemu window
device_del dev1
# 6. check output in tespmd window
Output:
# EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
EAL: uevent socket connection is broken.
The testpmd window hangs
Expected Result:
# Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
Invalid port_id=0
EAL: Cannot find device (0000:00:05.0) on bus (pci)
The tespmd window can be used normally.
Version the regression was introduced:
commit c2bd9367e18f5b00c1a3c5eb281a512ef52c5dfd
Author: Harman Kalra <hkalra@marvell.com>
Date: Sat Oct 23 02:19:32 2021 +0530
lib: remove direct access to interrupt handle
Removing direct access to interrupt handle structure fields,
rather use respective get set APIs for the same.
Making changes to all the libraries access the interrupt handle fields.
Signed-off-by: Harman Kalra <hkalra@marvell.com>
Signed-off-by: David Marchand <david.marchand@redhat.com>
Tested-by: Raslan Darawsheh <rasland@nvidia.com>
lib/bbdev/rte_bbdev.c | 4 ++--
lib/eal/linux/eal_dev.c | 57 +++++++++++++++++++++++++++++--------------------
lib/ethdev/rte_ethdev.c | 14 ++++++------
3 files changed, 43 insertions, 32 deletions
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-10-28 5:48 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-845-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).