[dpdk-dev] [Bug 605] HPE 100G 841QSFP28 fails on jumbo frames when not configured for it - Unexpected CQE error syndrome

[dpdk-dev] [Bug 605] HPE 100G 841QSFP28 fails on jumbo frames when not configured for it - Unexpected CQE error syndrome

[bugzilla]

https://bugs.dpdk.org/show_bug.cgi?id=605

            Bug ID: 605
           Summary: HPE 100G 841QSFP28 fails on jumbo frames when not
                    configured for it - Unexpected CQE error syndrome
           Product: DPDK
           Version: 19.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: pavel.krauz@anritsu.com
  Target Milestone: ---

Hello,
our customer has 
HPE InfiniBand EDR/Ethernet 100Gb 2-port 841QSFP28 Adapter (MLX5 adapter) and
has jumbo frames in their network. 

When we set our application using DPDK 19.11.4 to receive packets with maximum
length of 9038 and jumbo frames rx offload flags to DEV_RX_OFFLOAD_SCATTER |
DEV_RX_OFFLOAD_JUMBO_FRAME, then everything works fine.

However when we set maximum packet length to be:
port_conf.rxmode.max_rx_pkt_len = RTE_ETHER_MAX_LEN;
and do not set the rx offload flags then the DPDK card mlx5 driver reports
error files and reports packet loss. It seems that when jumbo are not
configured in DPDK but present in the network, the driver/card is failing.


I have 85MB of compressed debug files from mlx5 driver that I can share.

here is the first line in the debug files:

==> dpdk_mlx5_port_1_rxq_1_1099615000 <==
Unexpected CQE error syndrome 0x34 CQN = 3304 RQN = 12583234 wqe_counter =
47611 rq_ci = 38111 cq_ci = 1318495

==> dpdk_mlx5_port_1_rxq_1_1108098344 <==
Unexpected CQE error syndrome 0xe9 CQN = 3304 RQN = 12583234 wqe_counter = 0
rq_ci = 32768 cq_ci = 822834

==> dpdk_mlx5_port_1_rxq_1_1365813620 <==
Unexpected CQE error syndrome 0xb0 CQN = 3304 RQN = 12583234 wqe_counter =
55537 rq_ci = 38963 cq_ci = 709664

==> dpdk_mlx5_port_1_rxq_1_1370939994 <==
Unexpected CQE error syndrome 0xcf CQN = 3304 RQN = 12583234 wqe_counter =
20208 rq_ci = 55008 cq_ci = 762646

==> dpdk_mlx5_port_1_rxq_1_1383113394 <==
Unexpected CQE error syndrome 0xdb CQN = 3304 RQN = 12583234 wqe_counter =
26607 rq_ci = 32768 cq_ci = 978768

==> dpdk_mlx5_port_1_rxq_1_149947326 <==
Unexpected CQE error syndrome 0xe2 CQN = 3304 RQN = 12583234 wqe_counter = 6862
rq_ci = 32768 cq_ci = 1018398

==> dpdk_mlx5_port_1_rxq_1_1614261196 <==
Unexpected CQE error syndrome 0xe7 CQN = 3304 RQN = 12583234 wqe_counter =
39098 rq_ci = 32768 cq_ci = 555823

==> dpdk_mlx5_port_1_rxq_1_1632566952 <==
Unexpected CQE error syndrome 0x9a CQN = 3304 RQN = 12583234 wqe_counter =
12891 rq_ci = 38780 cq_ci = 1024427

==> dpdk_mlx5_port_1_rxq_1_1651330084 <==
Unexpected CQE error syndrome 0x74 CQN = 3304 RQN = 12583234 wqe_counter = 7765
rq_ci = 32768 cq_ci = 40533

-- 
You are receiving this mail because:
You are the assignee for the bug.