From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1856] i40evf_check_api_version(): PF/VF API version mismatch:(0.0)-(1.1) with multiple DPDK instances using different VFs with the same PF
Date: Fri, 19 Dec 2025 11:31:37 +0000 [thread overview]
Message-ID: <bug-1856-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1856
Bug ID: 1856
Summary: i40evf_check_api_version(): PF/VF API version
mismatch:(0.0)-(1.1) with multiple DPDK instances
using different VFs with the same PF
Product: DPDK
Version: 24.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: srija.bhattacharyya@wipro.com
Target Milestone: ---
We encountered an issue with DPDK initialization, where a PF/VF API version
mismatch occurred for VFs from the same PF. This issue was previously reported
under Bug ID:578.
Below here is a list of firmware versions that we tested with DPDK 24.11:
Driver Driver version firmware version
i40e 2.22.18 6.00 0x800063b6 18.5.17
i40e 2.22.18 8.40 0x8000b1fb 20.5.16
i40e 2.22.18 8.40 0x8000b1fb 20.5.16
i40e 2.22.18 9.54 0x800063b6 24.0.5
i40e 2.22.18 7.10 0x80009d2d 19.5.15
We would like to confirm if this issue has been fixed in any of the newer
firmware or driver versions. If it has been resolved, kindly specify which
driver and firmware version contains the fix.
We would appreciate any guidance on whether the issue persists or is addressed
in any of those versions.
Thanks,
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2025-12-19 11:31 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-1856-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).