public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1897] iavf_execute_vf_cmd(): Return failure -22 for cmd 11
Date: Thu, 26 Feb 2026 04:35:54 +0000	[thread overview]
Message-ID: <bug-1897-3@http.bugs.dpdk.org/> (raw)

http://bugs.dpdk.org/show_bug.cgi?id=1897

            Bug ID: 1897
           Summary: iavf_execute_vf_cmd(): Return failure -22 for cmd 11
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: albe19021990@gmail.com
  Target Milestone: ---

Good day. Every time I am trying to set rte_eth_dev_default_mac_addr_set on my
VF I get next error message in logs:

iavf_execute_vf_cmd(): Return failure -22 for cmd 11
iavf_add_del_eth_addr(): fail to execute command OP_DEL_ETH_ADDR
iavf_dev_set_default_mac_addr(): Fail to delete old MAC:{}

On dpdk initialization step if there are no MAC on interface - new MAC
generated and assigned

https://github.com/DPDK/dpdk/blob/main/drivers/net/intel/iavf/iavf_ethdev.c#L2851

But real asignment is made in iavf_dev_start by sending
VIRTCHNL_ETHER_ADDR_PRIMARY request to linux kernel.

https://github.com/DPDK/dpdk/blob/main/drivers/net/intel/iavf/iavf_ethdev.c#L1069
https://github.com/DPDK/dpdk/blob/main/drivers/net/intel/iavf/iavf_vchnl.c#L1426

But if we change MAC with iavf_dev_set_default_mac_addr it removes old MAC, and
assing new MAC. As iavf_dev_start was not called yet we try to remove non
asigned VIRTCHNL_ETHER_ADDR_PRIMARY MAC. linux kernel checks this and return
-EINVAL.

If we call rte_eth_dev_default_mac_addr_set second time with other MAC - there
will be no stderr, as there are MAC in linux kernel and delete primary MAC
operation will now be executed without -EINVAL.

This is not a critical issue, but this stderr confusing. As
rte_eth_dev_default_mac_addr_set return success, but logs say about error.

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

             reply	other threads:[~2026-02-26  4:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26  4:35 bugzilla [this message]
2026-03-04 18:05 ` [DPDK/other Bug 1897] iavf_execute_vf_cmd(): Return failure -22 for cmd 11 bugzilla

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-1897-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