On Tue, Jun 09, 2026 at 01:30:47PM +0100, Loftus, Ciara wrote:
> > Subject: [PATCH v2] net/iavf: fix misleading AQ failure logging
> >
> > iavf_handle_virtchnl_msg() drains the admin receive queue in a loop
> > until iavf_clean_arq_element() reports that no descriptors are
> > pending. When the queue becomes empty, the base driver returns
> > IAVF_ERR_ADMIN_QUEUE_NO_WORK (-57), which is the documented
> > terminator for the drain loop, and is not an error.
> >
> > The current loop treats every non-IAVF_SUCCESS return as a failure
> > and logs it as follows:
> >
> > "Failed to read msg from AdminQ, ret: -57"
> >
> > This message floods the logs on every interrupt cycle and misleads
> > the triage during VF reset by chasing a real virtchnl problem
> > seeing these spurious -57 AQ failure lines in logs and assumes
> > the admin queue is broken, when in fact it has just been drained.
> >
> > This patch fixes the aforesaid issue by treating
> > IAVF_ERR_ADMIN_QUEUE_NO_WORK in virtchnl message drain as a normal
> > loop exit empty-queue condition and avoid logging it as an misleading
> > AQ failure.
> >
> > Fixes: 02d212ca3125 ("net/iavf: rename remaining avf strings")
Actually, I think the proper offending commit is earlier:
Fixes: 22b123a36d07 ("net/avf: initialize PMD")
> > Cc: [email protected]
> >
> > Signed-off-by: Anurag Mandal <[email protected]>
>
> Thanks Anurag.
>
> Acked-by: Ciara Loftus <[email protected]>
>
Patch applied to dpdk-next-net-intel.
Thanks,
/Bruce
