DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] [Bug 578] i40evf_check_api_version(): PF/VF API version mismatch:(0.0)-(1.1) with multiple DPDK instances using different VFs with the same PF
@ 2020-11-18  9:45 bugzilla
  2020-12-09  0:54 ` bugzilla
  0 siblings, 1 reply; 2+ messages in thread
From: bugzilla @ 2020-11-18  9:45 UTC (permalink / raw)
  To: dev

https://bugs.dpdk.org/show_bug.cgi?id=578

            Bug ID: 578
           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: 20.08
          Hardware: All
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: juraj.linkes@pantheon.tech
  Target Milestone: ---

ISSUE DESCRIPTION:
VPP uses DPDK during startup with these init args:
EAL init args: -c 200000000 -n 4 --in-memory --log-level debug --file-prefix
vpp -w 0000:91:03.0 -w 0000:91:03.1 --master-lcore 33

When there's only one VPP starting up, the initialization is successful. When
we add multiple VPPs the initialization sometimes fails:
2020/11/16 08:58:49:660 notice     dpdk           EAL: Detected 64 lcore(s)
2020/11/16 08:58:49:660 notice     dpdk           EAL: Detected 2 NUMA nodes
2020/11/16 08:58:49:660 notice     dpdk           EAL: Selected IOVA mode 'VA'
2020/11/16 08:58:49:660 notice     dpdk           EAL: Probing VFIO support...
2020/11/16 08:58:49:660 notice     dpdk           EAL: VFIO support initialized
2020/11/16 08:58:49:660 notice     dpdk           EAL:   using IOMMU type 1
(Type 1)
2020/11/16 08:58:49:660 notice     dpdk           EAL: Probe PCI driver:
net_i40e_vf (8086:154c) device: 0000:91:03.0 (socket 1)
2020/11/16 08:58:49:660 notice     dpdk           i40evf_check_api_version():
PF/VF API version mismatch:(0.0)-(1.1)
2020/11/16 08:58:49:660 notice     dpdk           i40evf_init_vf(): check_api
version failed
2020/11/16 08:58:49:660 notice     dpdk           i40evf_dev_init(): Init vf
failed
2020/11/16 08:58:49:660 notice     dpdk           EAL: Releasing pci mapped
resource for 0000:91:03.0
2020/11/16 08:58:49:660 notice     dpdk           EAL: Calling
pci_unmap_resource for 0000:91:03.0 at 0x2101000000
2020/11/16 08:58:49:660 notice     dpdk           EAL: Calling
pci_unmap_resource for 0000:91:03.0 at 0x2101010000
2020/11/16 08:58:49:660 notice     dpdk           EAL: Requested device
0000:91:03.0 cannot be used
2020/11/16 08:58:49:660 notice     dpdk           EAL:   using IOMMU type 1
(Type 1)


EXPANDED SETUP/FAILURE EXPLANATION:
There is one testsuite running tests serially in one Jenkins job. Each test
starts VPP anew, so the DPDK initialization happens multiple times during a
testsuite run. When there is only one Jenkins job running, no failure is
observed. With multiple Jenkins jobs (and multiple testsuites running in
parallel), there is a small likelihood that a small number (usually just 1) of
initialization failures will occur, suggesting that when multiple DPDK
instances are retrieving PF/VF version there's a race condition resulting in PF
version 0.0 being retrieved.
Each Jenkins job uses two different VFs from the same PF.

An illustration of what likely happens:
VPP1 in job1 starts and DPDK initializes VF1 and VF2 from a PF.
VPP2 in job2 starts and DPDK initializes VF3 and VF4 from the same PF.
One or more of VF1, VF2, VF3 or VF4 don't get properly initialized because of:
i40evf_check_api_version(): PF/VF API version mismatch:(0.0)-(1.1)

NIC:
Intel Ethernet Converged Network Adapter XL710-Q2
cat /sys/class/net/enp5s0f0/device/device 
0x1583
cat /sys/class/net/enp5s0f0/device/vendor 
0x8086
cat /sys/class/net/enp5s0f0/device/subsystem_device 
0x0001
cat /sys/class/net/enp5s0f0/device/subsystem_vendor 
0x8086

DRIVER/FIRMWARE VERSION:
driver: i40e
version: 2.1.14-k
firmware-version: 6.01 0x800035da 1.1747.0
expansion-rom-version: 
bus-info: 0000:05:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [dpdk-dev] [Bug 578] i40evf_check_api_version(): PF/VF API version mismatch:(0.0)-(1.1) with multiple DPDK instances using different VFs with the same PF
  2020-11-18  9:45 [dpdk-dev] [Bug 578] i40evf_check_api_version(): PF/VF API version mismatch:(0.0)-(1.1) with multiple DPDK instances using different VFs with the same PF bugzilla
@ 2020-12-09  0:54 ` bugzilla
  0 siblings, 0 replies; 2+ messages in thread
From: bugzilla @ 2020-12-09  0:54 UTC (permalink / raw)
  To: dev

https://bugs.dpdk.org/show_bug.cgi?id=578

beilei.xing@intel.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |beilei.xing@intel.com
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #3 from beilei.xing@intel.com ---
As described in https://mails.dpdk.org/archives/dev/2020-December/194032.html,
suggest to report the issue to the kernel community.
Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-12-09  0:54 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-18  9:45 [dpdk-dev] [Bug 578] i40evf_check_api_version(): PF/VF API version mismatch:(0.0)-(1.1) with multiple DPDK instances using different VFs with the same PF bugzilla
2020-12-09  0:54 ` bugzilla

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git