[Intel-wired-lan] [PATCH iwl-next] libie: log more info when virtchnl fails
Paul Menzel
pmenzel at molgen.mpg.de
Mon Apr 27 10:40:17 UTC 2026
Dear Li,
Thank you for your patch.
Am 24.04.26 um 05:15 schrieb Li Li via Intel-wired-lan:
> Virtchnl failures can be hard to debug without logs. Logging the details
> of virtchnl transactions can be useful for debugging virtchnl-related
> issues.
Why is the first added one added as error, and the second as info?
Do you have a reproducer to get each of the new log messages?
> Tested: Built and booted on a test machine.
Please paste the new messages.
> Signed-off-by: Li Li <boolli at google.com>
> ---
> drivers/net/ethernet/intel/libie/controlq.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/net/ethernet/intel/libie/controlq.c b/drivers/net/ethernet/intel/libie/controlq.c
> index ebc05355e39d..7eaa77413621 100644
> --- a/drivers/net/ethernet/intel/libie/controlq.c
> +++ b/drivers/net/ethernet/intel/libie/controlq.c
> @@ -762,6 +762,16 @@ libie_ctlq_xn_process_recv(struct libie_ctlq_xn_recv_params *params,
> status = ctlq_msg->chnl_retval ? -EFAULT : 0;
>
> xn = &xnm->ring[xn_index];
> +
> + if (ctlq_msg->chnl_retval) {
> + dev_err_ratelimited(
> + params->ctlq->dev,
> + "Non-zero virtchnl ret val (msg op: %u, ret val: %u, msg_cookie: %u, data_len: %u); xn op: %u, id: %u, cookie: %u\n",
> + ctlq_msg->chnl_opcode, ctlq_msg->chnl_retval,
> + msg_cookie, ctlq_msg->data_len, xn->virtchnl_opcode,
> + xn->index, xn->cookie);
> + }
> +
> if (ctlq_msg->chnl_opcode != xn->virtchnl_opcode ||
> msg_cookie != xn->cookie)
> return false;
> @@ -1011,6 +1021,11 @@ int libie_ctlq_xn_send(struct libie_ctlq_xn_send_params *params)
> params->recv_mem = xn->recv_mem;
> break;
> default:
> + dev_notice_ratelimited(
> + params->ctlq->dev,
> + "Transaction failed (op %u, xn state: %d, id: %u, cookie: %u, size: %zu)\n",
> + params->chnl_opcode, xn->state, xn->index, xn->cookie,
> + xn->recv_mem.iov_len);
> ret = -EBADMSG;
> break;
> }
Kind regards,
Paul
More information about the Intel-wired-lan
mailing list