DPDK patches and discussions
 help / color / mirror / Atom feed
From: liaobiting <liaobiting@huawei.com>
To: "dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>
Cc: "liucheng (J)" <liucheng11@huawei.com>,
	Zhengjingzhou <zhengjingzhou@huawei.com>,
	"Huangjian (J)" <huangjian.huangjian@huawei.com>,
	 "Raofei (Milo,
	Hybrid Cloud Infrastructure Service Program)"
	<milo.raofei@huawei.com>, wangyunjian <wangyunjian@huawei.com>
Subject: [dpdk-dev] Please help to see this DPDK problem//Reply: DPDK 20.11 - i40evf: No response for 14
Date: Tue, 26 Oct 2021 06:37:58 +0000	[thread overview]
Message-ID: <0aa6df50062147f68c2325c4237c5e24@huawei.com> (raw)

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

BUG: DPDK-20.11- i40evf: No response for 14

Hi:
I am using Intel SR-IOV XL710 VF with DPDK v20.11 to create a dpdkbond but failed.
         [cid:image001.png@01D7CA75.76DF9EB0]
         As the picture shows, when dpdk bond start and slave link up, it triggers lsc callback function which registers in the eal thread, and then in the activate_slave process,
i40evf send msg 14 to pf to config promisc, but there is no response received. Because function "i40evf_handle_aq_msg" in which vf receives response from pf
is in the same thread of eal with function "_i40evf_execute_vf_cmd" in which vf sends msg to pf. Thus, when eal thread goes in function _i40evf_execute_vf_cmd,
it can't handle msg from pf at the same time, then it will report "No response for 14" in dpdk log.

And there are the error logs in dpdk:
2021-10-11T11:03:32.812516+08:00|info|ovs-vswitchd[1721043]|EAL: [eth_dev_ops] Slave 1: set mtu: 9058 .
2021-10-11T11:03:32.822434+08:00|info|ovs-vswitchd[1721043]|EAL: [eth_dev_ops] Slave 1: dev configure succeed.
2021-10-11T11:03:33.022426+08:00|info|ovs-vswitchd[1721043]|EAL: LSC CALLBACK: slave 0000:87:02.0 links up
2021-10-11T11:03:33.022455+08:00|info|ovs-vswitchd[1721043]|PMD: Slave 1: lacp_rate has been set to slow.
2021-10-11T11:03:35.034445+08:00|warning|ovs-vswitchd[1721043]|_i40evf_execute_vf_cmd(): No response for 14
2021-10-11T11:03:35.034628+08:00|err|ovs-vswitchd[1721043]|i40evf_config_promisc(): fail to execute command CONFIG_PROMISCUOUS_MODE
2021-10-11T11:03:35.034657+08:00|info|ovs-vswitchd[1721043]|EAL: [eth_dev_ops] Slave 1: enable allmulticast.
2021-10-11T11:03:35.034680+08:00|err|ovs-vswitchd[1721043]|bond_mode_8023ad_register_lacp_mac(1250) - failed to enable allmulti mode for port 1: Resource temporarily unavailable
2021-10-11T11:03:35.034702+08:00|debug|ovs-vswitchd[1721043]|bond_mode_8023ad_register_lacp_mac(1266) - forced promiscuous for port 1
2021-10-11T11:03:35.034725+08:00|info|ovs-vswitchd[1721043]|EAL: [eth_dev_ops] Slave 1 (net_bonding_trunk1): Configuring and applying resources successed.
2021-10-11T11:03:35.034746+08:00|info|ovs-vswitchd[1721043]|EAL: [eth_dev_ops] slave 1 (net_bonding_trunk1) activate.
2021-10-11T11:03:35.034771+08:00|debug|ovs-vswitchd[1721043]|     0 [Port 1: rx_machine] -> INITIALIZE
2021-10-11T11:03:35.034794+08:00|debug|ovs-vswitchd[1721043]|     0 [Port 1: mux_machine] -> DETACHED
2021-10-11T11:03:35.084534+08:00|err|ovs-vswitchd[1721043]|i40evf_handle_aq_msg(): command mismatch,expect 8, get 14
2021-10-11T11:03:35.134545+08:00|debug|ovs-vswitchd[1721043]|   100 [Port 1: mux_machine] DETACHED -> WAITING
2021-10-11T11:03:35.544648+08:00|info|ovs-vswitchd[1721043]|EAL: [eth_dev_ops] Slave 1: start dev.

How can I solve this problem ?
Thakns for help.
Regards,
Liao

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 23756 bytes --]

                 reply	other threads:[~2021-10-26  9:57 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=0aa6df50062147f68c2325c4237c5e24@huawei.com \
    --to=liaobiting@huawei.com \
    --cc=dev@dpdk.org \
    --cc=huangjian.huangjian@huawei.com \
    --cc=liucheng11@huawei.com \
    --cc=milo.raofei@huawei.com \
    --cc=users@dpdk.org \
    --cc=wangyunjian@huawei.com \
    --cc=zhengjingzhou@huawei.com \
    /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).