From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@kernel.org, andrew+netdev@lunn.ch,
netdev@vger.kernel.org
Cc: Li Li <boolli@google.com>,
anthony.l.nguyen@intel.com, aleksander.lobakin@intel.com,
sridhar.samudrala@intel.com, emil.s.tantilov@intel.com,
decot@google.com, brianvv@google.com,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
Samuel Salin <Samuel.salin@intel.com>
Subject: [PATCH net-next 2/2] libie: log more info when virtchnl fails
Date: Tue, 29 Sep 2026 16:13:01 -0700 [thread overview]
Message-ID: <20260929231305.1515873-3-anthony.l.nguyen@intel.com> (raw)
In-Reply-To: <20260929231305.1515873-1-anthony.l.nguyen@intel.com>
From: Li Li <boolli@google.com>
Virtchnl failures can be hard to debug without logs. Logging the details
of virtchnl transactions can be useful for debugging virtchnl-related
issues.
Tested: Built & booted on a test machine and synthetically produced a
virtual failure to produce the following log:
idpf 0000:01:00.0: Non-zero virtchnl ret val 6 (msg op: 1, data_len: 8);
xn id: 0, cookie: 0
idpf 0000:01:00.0: Transaction failed (op 1, xn state:
3, id: 0, cookie: 0, size: 8)
Signed-off-by: Li Li <boolli@google.com>
Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Tested-by: Samuel Salin <Samuel.salin@intel.com>
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
---
drivers/net/ethernet/intel/libie/controlq.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/drivers/net/ethernet/intel/libie/controlq.c b/drivers/net/ethernet/intel/libie/controlq.c
index 6214fc036ce5..5fce6d9db1e2 100644
--- a/drivers/net/ethernet/intel/libie/controlq.c
+++ b/drivers/net/ethernet/intel/libie/controlq.c
@@ -835,6 +835,13 @@ libie_ctlq_xn_process_recv(struct libie_ctlq_xn_recv_params *params,
return false;
}
+ if (ctlq_msg->chnl_retval) {
+ dev_err_ratelimited(params->ctlq->dev,
+ "Non-zero virtchnl ret val %u (msg op: %u, data_len: %u); xn id: %u, cookie: %u\n",
+ ctlq_msg->chnl_retval, ctlq_msg->chnl_opcode,
+ ctlq_msg->data_len, xn->index, xn->cookie);
+ }
+
if (xn->state != LIBIE_CTLQ_XN_ASYNC &&
xn->state != LIBIE_CTLQ_XN_WAITING) {
spin_unlock(&xn->xn_lock);
@@ -1088,6 +1095,10 @@ int libie_ctlq_xn_send(struct libie_ctlq_xn_send_params *params)
params->recv_mem = xn->recv_mem;
break;
default:
+ dev_err_ratelimited(params->ctlq->dev,
+ "Transaction failed (op %u, xn state: %u, id: %u, cookie: %u, size: %zu)\n",
+ params->chnl_opcode, xn->state, xn->index,
+ xn->cookie, xn->recv_mem.iov_len);
ret = -EBADMSG;
break;
}
--
2.47.1
next prev parent reply other threads:[~2026-09-29 23:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 23:12 [PATCH net-next 0/2][pull request] Intel Wired LAN Driver Updates 2026-09-29 (idpf, libie) Tony Nguyen
2026-09-29 23:13 ` [PATCH net-next 1/2] idpf: add flow-based XDP fallback for FWs without Tx FIFO support Tony Nguyen
[not found] ` <20260930231331.1E2051F000FF@smtp.kernel.org>
2026-10-01 15:43 ` Alexander Lobakin
2026-10-06 0:47 ` Jakub Kicinski
2026-10-03 23:35 ` netdev-bot+sashiko
2026-10-07 15:10 ` Alexander Lobakin
2026-09-29 23:13 ` Tony Nguyen [this message]
2026-10-03 23:35 ` [PATCH net-next 2/2] libie: log more info when virtchnl fails netdev-bot+sashiko
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=20260929231305.1515873-3-anthony.l.nguyen@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=Samuel.salin@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=boolli@google.com \
--cc=brianvv@google.com \
--cc=davem@davemloft.net \
--cc=decot@google.com \
--cc=edumazet@kernel.org \
--cc=emil.s.tantilov@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sridhar.samudrala@intel.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