RX timeout on channel when failed to get min WQE

Infrastructure & Networking Software And Drivers Network Management Products
1

Hello,

I’ve encountered issue when using Connect-X5.

OS is Ubuntu 18.04, kernel 5.4

Driver version 23.10-1.1.9 and FW - 16.35.3006 (MT_0000000425) and also happened on kernel one as well - 5.7-1.0.2 with FW - 16.34.1002 (MT_0000000425)

[Thu Dec  4 12:43:21 2025] mlx5_core 0000:af:00.0: RX timeout on channel: 26, ICOSQ: 0x3a8, RQ: 0x3ab, CQ: 0x487
[Thu Dec  4 12:43:21 2025] mlx5_core 0000:af:00.0: EQ 0x21: Cons = 0x393d736c, irqn = 0x24f
[Thu Dec  4 12:43:21 2025] mlx5_core 0000:af:00.0: Failed to get min RX wqes on Channel[30] RQN[0x3c3] wq cur_sz(0) min_rx_wqes(2)
[Thu Dec  4 12:43:21 2025] mlx5_core 0000:af:00.0: RX timeout on channel: 30, ICOSQ: 0x3c0, RQ: 0x3c3, CQ: 0x49b
[Thu Dec  4 12:43:21 2025] mlx5_core 0000:af:00.0: Failed to get min RX wqes on Channel[32] RQN[0x3cf] wq cur_sz(0) min_rx_wqes(2)
[Thu Dec  4 12:43:21 2025] mlx5_core 0000:af:00.0: RX timeout on channel: 32, ICOSQ: 0x3cc, RQ: 0x3cf, CQ: 0x4a5
[Thu Dec  4 12:43:22 2025] mlx5_core 0000:af:00.0: Failed to get min RX wqes on Channel[33] RQN[0x3d5] wq cur_sz(0) min_rx_wqes(2)
[Thu Dec  4 12:43:22 2025] mlx5_core 0000:af:00.0: RX timeout on channel: 33, ICOSQ: 0x3d2, RQ: 0x3d5, CQ: 0x4aa
[Thu Dec  4 12:43:22 2025] mlx5_core 0000:af:00.0: Failed to get min RX wqes on Channel[34] RQN[0x3db] wq cur_sz(0) min_rx_wqes(2)
[Thu Dec  4 12:43:22 2025] mlx5_core 0000:af:00.0: ICOSQ: 0x3d8, RQ: 0x3db, CQ: 0x4af
[Thu Dec  4 12:43:22 2025] mlx5_core 0000:af:00.0: Link down

This is the logs being seen in dmesg. During it server is experiencing troubles with network connectivity and availability. There is no full no connection at all, rather response time climbs too high, causing issues. It happens not very frequently and it seems not clear - how to reproduce this at the moment. Reboot helps in that case. Have you encountered something like this?

It seems, that functionality regarding such logs has been added here Making sure you're not a bot!

Thank you in advance

2

Hello,

This might be related to version misalignment - I suggest trying to install the latest available FW for CX5 (please note that CX5 is EOL, so no new version will be released) along with the corresponding Driver version.

See:

If the issue still persists with the latest available FW and driver combination, please open a case with Enterprise Support and it will be handled based on entitlement.

Thanks,

Jonathan.