RDMA/mlx5: print wc status on CQE error and dump needed
Subsystems (2)
PATCH 1/1 RDMA/mlx5: print wc status on CQE error and dump needed
mlx5_handle_error_cqe() only dump the content of the CQE which is raw hex data, and not straighforward for debug. Print WC status message when we got CQE error and dump is need.
Here is an example of how the dmesg log looks like with this:
[166755.330649] infiniband mlx5_0: mlx5_handle_error_cqe:333:(pid 0): WC error: 10, message: remote access error [166755.332323] infiniband mlx5_0: dump_cqe:272:(pid 0): dump error cqe [166755.332944] 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [166755.333574] 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [166755.334202] 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [166755.334837] 00000030: 00 00 00 00 00 00 88 13 08 03 61 b3 1e a1 42 d3
--- drivers/infiniband/hw/mlx5/cq.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/infiniband/hw/mlx5/cq.c +4 -1
@@ -328,8 +328,11 @@ static void mlx5_handle_error_cqe(struct mlx5_ib_dev *dev, } wc->vendor_err = cqe->vendor_err_synd; -if (dump) +if (dump) { +mlx5_ib_warn (dev,"WC error: %d, Message: %s\n" , + wc->status,ib_wc_status_msg (wc->status));dump_cqe (dev, cqe); + } } static void handle_atomics(struct mlx5_ib_qp *qp, struct mlx5_cqe64 *cqe64,
Signature · 1 line
2.19.1.3.ge56e4f7
Quoted 13 lines · Dust Li
mlx5_handle_error_cqe()only dump the content of the CQE which is raw hex data, and not straighforward for debug. Print WC status message when we got CQE error and dump is need.Here is an example of how the dmesg log looks like with this:
[166755.330649] infiniband mlx5_0: mlx5_handle_error_cqe:333:(pid 0): WC error: 10, message: remote access error [166755.332323] infiniband mlx5_0: dump_cqe:272:(pid 0): dump error cqe [166755.332944] 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [166755.333574] 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [166755.334202] 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [166755.334837] 00000030: 00 00 00 00 00 00 88 13 08 03 61 b3 1e a1 42 d3
Quoted 5 lines
Signed-off-by Dust Li <[email protected]>--- drivers/infiniband/hw/mlx5/cq.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
Thanks,
Quoted 13 lines · Dust Li
mlx5_handle_error_cqe()only dump the content of the CQE which is raw hex data, and not straighforward for debug. Print WC status message when we got CQE error and dump is need.Here is an example of how the dmesg log looks like with this:
[166755.330649] infiniband mlx5_0: mlx5_handle_error_cqe:333:(pid 0): WC error: 10, message: remote access error [166755.332323] infiniband mlx5_0: dump_cqe:272:(pid 0): dump error cqe [166755.332944] 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [166755.333574] 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [166755.334202] 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [166755.334837] 00000030: 00 00 00 00 00 00 88 13 08 03 61 b3 1e a1 42 d3
Quoted 5 lines
Signed-off-by Dust Li <[email protected]>Acked-by Leon Romanovsky <[email protected]>--- drivers/infiniband/hw/mlx5/cq.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
Applied to for-next, thanks
Jason