DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1334] Failures of testpmd on XXV710 card in VMs under Openshift Container Platform
Date: Fri, 08 Dec 2023 06:56:11 +0000	[thread overview]
Message-ID: <bug-1334-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 2884 bytes --]

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

            Bug ID: 1334
           Summary: Failures of testpmd on XXV710 card in VMs under
                    Openshift Container Platform
           Product: DPDK
           Version: 22.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: testpmd
          Assignee: dev@dpdk.org
          Reporter: niny.gu.2022@gmail.com
  Target Milestone: ---

I met the following issue when running dpdk-testpmd under the OpenShift
Virtualization environment recently. We did the test on 2 VFs, each passed
through to a VM, and they come from the same PF(XXV710) on the host. However,
it's found there are the following errors when I quit the test on the receiver
side.

# dpdk-testpmd --socket-mem 256 --lcores 0,1 -n 1 -a 00:05:00.0 --proc-type
auto --file-prefix rx -- --forward-mode=rxonly --port-topology=chained
--disable-rss -i --rxq=1 --txq=1 --rxd=256 --txd=256 --nb-cores=1 --auto-start
EAL: Detected CPU lcores: 2
EAL: Detected NUMA nodes: 1
EAL: Auto-detected process type: PRIMARY
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rx/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: VFIO support initialized
EAL: Using IOMMU type 8 (No-IOMMU)
EAL: Probe PCI driver: net_iavf (8086:154c) device: 0000:05:00.0 (socket -1)
......
iavf_dev_init_vlan(): Failed to update vlan offload
iavf_dev_configure(): configure VLAN failed: -95
iavf_set_rx_function(): request RXDID[1] in Queue[0] is legacy, set
rx_pkt_burst as legacy for all queues
......
testpmd> quit
Telling cores to stop...
Waiting for lcores to finish...

  ---------------------- Forward statistics for port 0  ----------------------
  RX-packets: 158837911      RX-dropped: 0             RX-total: 158837911
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ----------------------------------------------------------------------------

  +++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
  RX-packets: 158837911      RX-dropped: 0             RX-total: 158837911
  TX-packets: 0              TX-dropped: 0             TX-total: 0
  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Done.

Stopping port 0...
Stopping ports...
iavf_execute_vf_cmd(): Return failure -37 for cmd 9
iavf_disable_queues(): Failed to execute command of OP_DISABLE_QUEUES
iavf_stop_queues(): Fail to stop queues
iavf_stop_queues(): Fail to stop queues
iavf_execute_vf_cmd(): No response for cmd 11
iavf_add_del_all_mac_addr(): fail to execute command OP_DEL_ETHER_ADDRESS
Done

Shutting down port 0...
Closing ports...
Port 0 is closed
Done

Bye...

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

[-- Attachment #2: Type: text/html, Size: 4770 bytes --]

                 reply	other threads:[~2023-12-08  6:56 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-1334-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).