From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 9EE7F46A23; Thu, 3 Jul 2025 18:49:10 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6175740267; Thu, 3 Jul 2025 18:49:10 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 5B75140264 for ; Thu, 3 Jul 2025 18:49:08 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 4FF0E46AE7; Thu, 3 Jul 2025 18:49:08 +0200 (CEST) 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 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: core X-Bugzilla-Version: 25.03 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: yonig@radcom.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17515613480.035a.1300103 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --17515613480.035a.1300103 Date: Thu, 3 Jul 2025 18:49:08 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1738 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 virt= io interfaces bound to the kernel driver: Starting a secondary DPDK process (w= ith 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 a= lso use virtio and the same kernel version. Steps to Reproduce: ./dpdk-testpmd -l 4,5 -n 4 -a 0000:00:04.0 --proc-type=3Dprimary -- -i ./dpdk-testpmd -l 6,7 -n 4 -a 0000:00:04.0 --proc-type=3Dsecondary -- -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 pro= cess 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 --=20 You are receiving this mail because: You are the assignee for the bug.= --17515613480.035a.1300103 Date: Thu, 3 Jul 2025 18:49:08 +0200 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID 1738
Summary bus/pci: Secondary process initialization kills non-DPDK netw= ork 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 interf=
ace bound to vfio-pci and additional virtio
interfaces bound to the kernel driver: Starting a secondary DPDK process (w=
ith
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 a=
lso
use virtio and the same kernel version.

Steps to Reproduce:
./dpdk-testpmd -l 4,5 -n 4 -a 0000:00:04.0 --proc-type=3Dprimary -- -i
./dpdk-testpmd -l 6,7 -n 4 -a 0000:00:04.0 --proc-type=3Dsecondary -- -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 pro=
cess
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.
=20=20=20=20=20=20=20=20=20=20
= --17515613480.035a.1300103--