From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1738] bus/pci: Secondary process initialization kills non-DPDK network interfaces
Date: Thu, 03 Jul 2025 16:49:08 +0000 [thread overview]
Message-ID: <bug-1738-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2041 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1738
Bug ID: 1738
Summary: bus/pci: Secondary process initialization kills
non-DPDK network interfaces
Product: DPDK
Version: 25.03
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: yonig@radcom.com
Target Milestone: ---
On a system with one virtio interface bound to vfio-pci and additional virtio
interfaces bound to the kernel driver: Starting a secondary DPDK process (with
a -a flag specifying the pci address bound to vfio) causes all the kernel
network interfaces to stop working, requiring a reboot.
This behavior is reproduced on a specific environment consisting of several
VMs, but we have been unable to reproduce it on other environments, which also
use virtio and the same kernel version.
Steps to Reproduce:
./dpdk-testpmd -l 4,5 -n 4 -a 0000:00:04.0 --proc-type=primary -- -i
./dpdk-testpmd -l 6,7 -n 4 -a 0000:00:04.0 --proc-type=secondary -- -i
This happens on all dpdk versions starting at 24.3.
I have narrowed the cause down to the following two commits:
4b741542ecde - bus/pci: avoid depending on private kernel value
647a0a6ecb04 - bus/pci: fix VFIO region info in secondary process
Without these commits there is no issue. With only 4b741542ecde, there is an
error in the secondary process initialization (virtio_pci_init(): failed to
remap pci device). With both commits, the network dies during secondary process
initialization.
The kernel log contains lines such as:
kernel: NETDEV WATCHDOG: ens3 (virtio_net): transmit queue 0 timed out
...
kernel: virtio_net virtio0 ens3: TX timeout on queue: 0, sq: output.0, vq: 0x1,
name: output.0, 5286000 usecs ago
Kernel version: kernel 5.14.0-362.8.1.el9_3.x86_64
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3923 bytes --]
reply other threads:[~2025-07-03 16:49 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-1738-3@https.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.