From: Nini Gu <ngu@redhat.com>
To: dev@dpdk.org
Subject: Re: Failures of testpmd on XXV710 card
Date: Wed, 6 Dec 2023 19:32:23 +0800 [thread overview]
Message-ID: <CALK=oAeEJrx0qT-dmxJDXfwy0vX0kxPRfjz06QUX2wkvp2ygoA@mail.gmail.com> (raw)
In-Reply-To: <CALK=oAffF4yz8A2cn8-iKirzotAyfWG=GRWyK2cL0g5q+zN26g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2695 bytes --]
Sorry, forgot the subject, add it.
On Wed, Dec 6, 2023 at 7:30 PM Nini Gu <ngu@redhat.com> wrote:
> Hello,
>
> 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. Does anyone familiar with these? Are these related to
> the XXV710 card or something else?
>
>
> *# 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: 2EAL: Detected NUMA nodes: 1EAL: Auto-detected
> process type: PRIMARYEAL: Detected shared linkage of DPDKEAL: Multi-process
> socket /var/run/dpdk/rx/mp_socketEAL: Selected IOVA mode 'PA'EAL: VFIO
> support initializedEAL: 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 offloadiavf_dev_configure():
> configure VLAN failed: -95iavf_set_rx_function(): request RXDID[1] in
> Queue[0] is legacy, set rx_pkt_burst as legacy for all queues*
> *......*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *testpmd> quitTelling 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
> 9iavf_disable_queues(): Failed to execute command of
> OP_DISABLE_QUEUESiavf_stop_queues(): Fail to stop queuesiavf_stop_queues():
> Fail to stop queuesiavf_execute_vf_cmd(): No response for cmd
> 11iavf_add_del_all_mac_addr(): fail to execute command
> OP_DEL_ETHER_ADDRESSDoneShutting down port 0...Closing ports...Port 0 is
> closedDone*
>
> Bye...
>
> Thanks in advance!
> --
> Regards,
> Nini Gu
>
--
Regards,
Nini Gu
[-- Attachment #2: Type: text/html, Size: 3488 bytes --]
parent reply other threads:[~2023-12-06 11:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CALK=oAffF4yz8A2cn8-iKirzotAyfWG=GRWyK2cL0g5q+zN26g@mail.gmail.com>]
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='CALK=oAeEJrx0qT-dmxJDXfwy0vX0kxPRfjz06QUX2wkvp2ygoA@mail.gmail.com' \
--to=ngu@redhat.com \
--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).