Hi, We executed few more tests on this and we observed that after applying the above policy with 4 sids, we can see packet coming out of the interface. But as soon we add the 5th sid or more we don't see the packet coming out of the interface and VPP crashes after sometime. We got the below trace for VPP crash on gdb:-
(gdb) c Continuing. Thread 1 "vpp_main" received signal SIGSEGV, Segmentation fault. 0x00007fe67f1cf256 in virtio_update_packet_stats () from /usr/lib/vpp_plugins//dpdk_plugin.so (gdb) bt #0 0x00007fe67f1cf256 in virtio_update_packet_stats () from /usr/lib/vpp_plugins//dpdk_plugin.so #1 0x00007fe67f1d6646 in virtio_xmit_pkts () from /usr/lib/vpp_plugins//dpdk_plugin.so #2 0x00007fe67f42d60e in rte_eth_tx_burst (nb_pkts=<optimized out>, tx_pkts=0x7fe6862afc00, queue_id=<optimized out>, port_id=<optimized out>) at /opt/vpp/external/x86_64/include/rte_ethdev.h:5680 #3 tx_burst_vector_internal (n_left=1, mb=0x7fe6862afc00, xd=<optimized out>, vm=<optimized out>) at /usr/src/debug/vpp-22.02.0-35~ge3c583654.x86_64/src/plugins/dpdk/device/device.c:175 #4 dpdk_device_class_tx_fn_hsw (vm=<optimized out>, node=<optimized out>, f=<optimized out>) at /usr/src/debug/vpp-22.02.0-35~ge3c583654.x86_64/src/plugins/dpdk/device/device.c:435 #5 0x00007fe6c66bd802 in dispatch_node (last_time_stamp=<optimized out>, frame=<optimized out>, dispatch_state=VLIB_NODE_STATE_POLLING, type=VLIB_NODE_TYPE_INTERNAL, node=0x7fe685e93c00, vm=0x7fe68547a680) at /usr/src/debug/vpp-22.02.0-35~ge3c583654.x86_64/src/vlib/main.c:975 #6 dispatch_pending_node (vm=vm@entry=0x7fe68547a680, pending_frame_index=pending_frame_index@entry=10, last_time_stamp=<optimized out>) at /usr/src/debug/vpp-22.02.0-35~ge3c583654.x86_64/src/vlib/main.c:1134 #7 0x00007fe6c66c1ebf in vlib_main_or_worker_loop (is_main=1, vm=<optimized out>) at /usr/src/debug/vpp-22.02.0-35~ge3c583654.x86_64/src/vlib/main.c:1600 #8 vlib_main_loop (vm=<optimized out>) at /usr/src/debug/vpp-22.02.0-35~ge3c583654.x86_64/src/vlib/main.c:1728 #9 vlib_main (vm=<optimized out>, vm@entry=0x7fe68547a680, input=input@entry=0x7fe675df5fa0) at /usr/src/debug/vpp-22.02.0-35~ge3c583654.x86_64/src/vlib/main.c:2017 #10 0x00007fe6c670cc86 in thread0 (arg=140628055271040) at /usr/src/debug/vpp-22.02.0-35~ge3c583654.x86_64/src/vlib/unix/main.c:671 #11 0x00007fe6c5c29388 in clib_calljmp () at /usr/src/debug/vpp-22.02.0-35~ge3c583654.x86_64/src/vppinfra/longjmp.S:123 #12 0x00007ffcdf319c80 in ?? () #13 0x00007fe6c670e210 in vlib_unix_main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/vpp-22.02.0-35~ge3c583654.x86_64/src/vlib/unix/main.c:751 #14 0xffffffffffffffff in ?? () #15 0x0001a53c00005137 in ?? () Can this be related to some buffer setting/packet size for DPDK? Any pointers on how can we debug the cause of this issue? Thanks and Regards, Chinmaya Agarwal.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21648): https://lists.fd.io/g/vpp-dev/message/21648 Mute This Topic: https://lists.fd.io/mt/92185133/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
