From: vpp-dev@lists.fd.io on behalf of Vijay Kumar via
lists.fd.io
Date: Wednesday, 27 July 2022 at 11:27
To: vpp-dev
Subject: [vpp-dev] Crash in vlib_buffer_enqueue_next
Hi experts,
I am seeing this callstack where the enque next crashes due to sig abort. Pls
let me know possible reasons
Hi experts,
We are seeing the below counters being pegged. The scenario is the UEs are
trying to establish TCP with VPP.
It would be highly appreciated if anyone could tell us why we see the msg
queue full counter shown below?
1 tcp4-rcv-process Events not sent for
Hi Pim,
I've tried populating the IPv6 neighbor table on the Linux side, but it still
doesn't work.
>
>
>
> najib@DPDK:~$ ip nei show dev xe1.921
>
>
>
> 2401:1700:1:1::bd lladdr c4:ad:34:4d:d2:a8 PERMANENT
>
>
>
>
>
> najib@-DPDK:~$ ping 2401:1700:1:1::bd
>
>
>
> PING
Hi experts,
I am seeing this callstack where the enque next crashes due to sig abort.
Pls let me know possible reasons for this call stack. I highly appreciate
any response related to this bt.
Program terminated with signal SIGABRT, Aborted.
#0 __pthread_kill_implementation (threadid=,
Hoi,
I have found with both VPP and DANOS (another open source routing platform
with DPDK under the covers), that some IPv6 neighbors consistently do not
make their way into the Linux neighbors list (but they are fine in VPP, as
you showed).
If you pre-populate the IPv6 neighbor table in the
