From: Talluri Chaitanyababu <[email protected]> After admin queue reinitialisation, completions from uninitialised ARQ ring descriptor memory may arrive before any real PF response. These carry opcode 0 (`VIRTCHNL_OP_UNKNOWN`) and trigger a WARNING log on every poll iteration, flooding the log during reset recovery.
Treat opcode 0 as a distinct case and log it at DEBUG level, while retaining WARNING for genuine opcode mismatches. Signed-off-by: Talluri Chaitanyababu <[email protected]> --- drivers/net/intel/iavf/iavf_vchnl.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/drivers/net/intel/iavf/iavf_vchnl.c b/drivers/net/intel/iavf/iavf_vchnl.c index 94ccfb5d6e..cd90d35023 100644 --- a/drivers/net/intel/iavf/iavf_vchnl.c +++ b/drivers/net/intel/iavf/iavf_vchnl.c @@ -299,8 +299,15 @@ iavf_read_msg_from_pf(struct iavf_adapter *adapter, uint16_t buf_len, /* async reply msg on command issued by vf previously */ result = IAVF_MSG_CMD; if (opcode != vf->pend_cmd) { - PMD_DRV_LOG(WARNING, "command mismatch, expect %u, get %u", - vf->pend_cmd, opcode); + if (opcode == VIRTCHNL_OP_UNKNOWN) + PMD_DRV_LOG(DEBUG, + "Spurious msg with opcode 0, pending cmd %u", + vf->pend_cmd); + else + PMD_DRV_LOG(WARNING, + "command mismatch, expect %u, get %u", + vf->pend_cmd, opcode); + result = IAVF_MSG_ERR; } } -- 2.43.0
