From: Bruce Richardson <bruce.richardson@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: <dev@dpdk.org>, Talluri Chaitanyababu <chaitanyababux.talluri@intel.com>
Subject: Re: [PATCH 1/3] net/iavf: downgrade opcode 0 ARQ log to debug
Date: Tue, 9 Jun 2026 15:28:34 +0100 [thread overview]
Message-ID: <aigjEm-RskU5s45v@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260608145518.1705524-2-ciara.loftus@intel.com>
On Mon, Jun 08, 2026 at 02:55:16PM +0000, Ciara Loftus wrote:
> From: Talluri Chaitanyababu <chaitanyababux.talluri@intel.com>
>
> 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 <chaitanyababux.talluri@intel.com>
> ---
> drivers/net/intel/iavf/iavf_vchnl.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
Should this be backported as a bugfix?
next prev parent reply other threads:[~2026-06-09 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 14:55 [PATCH 0/3] net/iavf: vf reset fixes Ciara Loftus
2026-06-08 14:55 ` [PATCH 1/3] net/iavf: downgrade opcode 0 ARQ log to debug Ciara Loftus
2026-06-09 14:28 ` Bruce Richardson [this message]
2026-06-08 14:55 ` [PATCH 2/3] net/iavf: wait for PF reset start before reinitializing Ciara Loftus
2026-06-08 14:55 ` [PATCH 3/3] net/iavf: fix event handler refcount leak on HW reset Ciara Loftus
2026-06-09 14:53 ` [PATCH 0/3] net/iavf: vf reset fixes Bruce Richardson
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=aigjEm-RskU5s45v@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=chaitanyababux.talluri@intel.com \
--cc=ciara.loftus@intel.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