The backtrace appears to indicate that ipv6 link-level traffic is involved.
It’s likely that the interface corresponding to sw_if_index 2 isn’t
ipv6-enabled.
Begs the question why the code wipe out – copying Neale but he is on leave at
the moment – please enable ipv6 on the interface.
It would be useful to run a debug image, since it would almost certainly ASSERT
here rather than dereferencing a NULL pointer which causes signal 11 (SIGSEGV):
u32
ip6_ll_fib_get (u32 sw_if_index)
{
ASSERT (vec_len (ip6_ll_table.ilt_fibs) > sw_if_index);
return (ip6_ll_table.ilt_fibs[sw_if_index]);
}
In future, please try to format backtraces so we can read them without undue
head-scratching.
HTH... Dave
From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Amit Mehra
Sent: Monday, July 6, 2020 5:58 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Observing a crash in vpp-20.05
Hi,
I am running some light ipv4 traffic around 5K pps and observing a core with
the following bt
Program terminated with signal 6, Aborted. #0 0x00002b838f53f387 in raise ()
from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install
OPWVs11-8.1-el7.x86_64 (gdb) bt #0 0x00002b838f53f387 in raise () from
/lib64/libc.so.6 #1 0x00002b838f540a78 in abort () from /lib64/libc.so.6 #2
0x000055deea85617e in os_exit (code=code@entry=1) at
/bfs-build/build-area.42/builds/LinuxNBngp_8.X_RH7/2020-07-02-1702/third-party/vpp_2005/vpp_2005/src/vpp/vnet/main.c:390
#3 0x00002b838de26716 in unix_signal_handler (signum=11, si=<optimized out>,
uc=<optimized out>) at
/bfs-build/build-area.42/builds/LinuxNBngp_8.X_RH7/2020-07-02-1702/third-party/vpp_2005/vpp_2005/src/vlib/unix/main.c:187
#4 <signal handler called> #5 0x00002b838d434479 in ip6_ll_fib_get
(sw_if_index=2) at
/bfs-build/build-area.42/builds/LinuxNBngp_8.X_RH7/2020-07-02-1702/third-party/vpp_2005/vpp_2005/src/vnet/ip/ip6_ll_table.c:32
#6 0x00002b838d7c4904 in ip6_ll_dpo_inline (frame=0x2b8397edf880,
node=0x2b83988669c0, vm=0x2b8397ca9040) at
/bfs-build/build-area.42/builds/LinuxNBngp_8.X_RH7/2020-07-02-1702/third-party/vpp_2005/vpp_2005/src/vnet/dpo/ip6_ll_dpo.c:132
#7 ip6_ll_dpo_switch (vm=0x2b8397ca9040, node=0x2b83988669c0,
frame=0x2b8397edf880) at
/bfs-build/build-area.42/builds/LinuxNBngp_8.X_RH7/2020-07-02-1702/third-party/vpp_2005/vpp_2005/src/vnet/dpo/ip6_ll_dpo.c:170
#8 0x00002b838dddeec7 in dispatch_node (last_time_stamp=<optimized out>,
frame=0x2b8397edf880, dispatch_state=VLIB_NODE_STATE_POLLING,
type=VLIB_NODE_TYPE_INTERNAL, node=0x2b83988669c0, vm=0x2b8397ca9040) at
/bfs-build/build-area.42/builds/LinuxNBngp_8.X_RH7/2020-07-02-1702/third-party/vpp_2005/vpp_2005/src/vlib/main.c:1235
#9 dispatch_pending_node (vm=vm@entry=0x2b8397ca9040,
pending_frame_index=pending_frame_index@entry=4, last_time_stamp=<optimized
out>) at
/bfs-build/build-area.42/builds/LinuxNBngp_8.X_RH7/2020-07-02-1702/third-party/vpp_2005/vpp_2005/src/vlib/main.c:1403
#10 0x00002b838dde00bf in vlib_main_or_worker_loop (is_main=0,
vm=0x2b8397ca9040) at
/bfs-build/build-area.42/builds/LinuxNBngp_8.X_RH7/2020-07-02-1702/third-party/vpp_2005/vpp_2005/src/vlib/main.c:1862
#11 vlib_worker_loop (vm=0x2b8397ca9040) at
/bfs-build/build-area.42/builds/LinuxNBngp_8.X_RH7/2020-07-02-1702/third-party/vpp_2005/vpp_2005/src/vlib/main.c:1996
#12 0x00002b838e8c5cac in clib_calljmp () from
/opt/opwv/S11/8.1/tools/vpp/lib/libvppinfra.so.20.05 #13 0x00002b85ca3b3c40 in
?? () #14 0x00002b8411e3107a in eal_thread_loop (arg=<optimized out>) at
/bfs-build/build-area.42/builds/LinuxNBngp_8.X_RH7/2020-07-02-1702/third-party/vpp_2005/vpp_2005/build-root/build-vpp-native/external/dpdk-20.02/lib/librte_eal/linux/eal/eal_thread.c:153
#15 0x0000000000010d0c in ?? ()
Is this a known issue in vpp-20.05?
Regards
Amit
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16887): https://lists.fd.io/g/vpp-dev/message/16887
Mute This Topic: https://lists.fd.io/mt/75329694/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
