If possible, repeat the exercise with a debug image. The code involved is well 
tested, and does not crash without “help.” I wouldn’t be surprised to run into 
an ASSERT elsewhere which explains the problem.

For the specific packet in question: see if 
vnet_buffer(b)->sw_if_index[VLIB_TX] is set to a nonexistent FIB index. That’s 
one possible reason why the root mtrie ply might not play nicely with the other 
children.

HTH... Dave

From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of abbas ali chezgi 
via Lists.Fd.Io
Sent: Tuesday, August 28, 2018 5:16 AM
To: Vpp-dev <vpp-dev@lists.fd.io>
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] crash in vpp 18.07

more info after full core dump:


#0  0x00007f57b1b6e428 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f57b1b7002a in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00005565b7348dee in os_exit (code=code@entry=1)
    at 
/w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vpp/vnet/main.c:355
#3  0x00007f57b3210035 in unix_signal_handler (signum=<optimized out>, 
si=<optimized out>,
    uc=<optimized out>) at 
/w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vlib/unix/main.c:157
#4  <signal handler called>
#5  0x00007f57b29b7321 in ip4_fib_mtrie_lookup_step_one 
(dst_address=0x7f576af32a1a, m=<optimized out>)
    at 
/w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vnet/ip/ip4_mtrie.h:229
#6  ip4_local_check_src (error0=<synthetic pointer>, last_check=<synthetic 
pointer>,
    ip0=0x7f576af32a0e, b=0x7f576af32900)
    at 
/w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vnet/ip/ip4_forward.c:1280
#7  ip4_local_inline (head_of_feature_arc=1, frame=<optimized out>, 
node=<optimized out>,
    vm=0x7f57b342cf80 <vlib_global_main>)
    at 
/w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vnet/ip/ip4_forward.c:1514
#8  ip4_local (frame=<optimized out>, node=<optimized out>, vm=0x7f57b342cf80 
<vlib_global_main>)
    at 
/w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vnet/ip/ip4_forward.c:1534
#9  ip4_local_avx2 (vm=0x7f57b342cf80 <vlib_global_main>, node=0x7f577155c3c0, 
frame=0x7f57721c4400)
    at 
/w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vnet/ip/ip4_forward.c:1555
#10 0x00007f57b31d63a4 in dispatch_node (last_time_stamp=85226775203136, 
frame=0x7f57721c4400,
    dispatch_state=VLIB_NODE_STATE_POLLING, type=VLIB_NODE_TYPE_INTERNAL, 
node=0x7f577155c3c0,
    vm=0x7f57b342cf80 <vlib_global_main>)
    at /w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vlib/main.c:988
#11 dispatch_pending_node (vm=vm@entry=0x7f57b342cf80 <vlib_global_main>,
    pending_frame_index=pending_frame_index@entry=5,
    last_time_stamp=last_time_stamp@entry=85226775203136)
    at /w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vlib/main.c:1138
#12 0x00007f57b31d7dee in vlib_main_or_worker_loop (is_main=1, 
vm=0x7f57b342cf80 <vlib_global_main>)
    at /w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vlib/main.c:1616
#13 vlib_main_loop (vm=0x7f57b342cf80 <vlib_global_main>)
    at /w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vlib/main.c:1635
#14 vlib_main (vm=vm@entry=0x7f57b342cf80 <vlib_global_main>, 
input=input@entry=0x7f57717e4fa0)
    at /w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vlib/main.c:1826
#15 0x00007f57b320f4d3 in thread0 (arg=140014646382464)
    at 
/w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vlib/unix/main.c:607
#16 0x00007f57b234e778 in clib_calljmp ()
    at 
/w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vppinfra/longjmp.S:110
#17 0x00007ffce83886c0 in ?? ()
#18 0x00007f57b3210576 in vlib_unix_main (argc=<optimized out>, argv=<optimized 
out>)
    at 
/w/workspace/vpp-merge-1807-ubuntu1604/build-data/../src/vlib/unix/main.c:674
#19 0x3670637400000038 in ?? ()
#20 0x502074657365722d in ?? ()
#21 0x64207374656b6361 in ?? ()
#22 0x6620646570706f72 in ?? ()
#23 0x206b63616c20726f in ?? ()
#24 0x696620787220666f in ?? ()
#25 0x6563617073206f66 in ?? ()
#26 0x000000006425203a in ?? ()
#27 0x0000000000000000 in ?? ()


On Tuesday, August 28, 2018, 1:30:26 PM GMT+4:30, abbas ali chezgi via 
Lists.Fd.Io <chezgi=yahoo....@lists.fd.io<mailto:chezgi=yahoo....@lists.fd.io>> 
wrote:



this crash accoured in vpp 18.07:

vpp[71]: received signal SIGSEGV, PC 0x7f125c775321, faulting address 
0x7f16ae006978
vpp[71]: #0  0x00007f125cfcdf7f 0x7f125cfcdf7f
vpp[71]: #1  0x00007f125bed6390 0x7f125bed6390
vpp[71]: #2  0x00007f125c775321 ip4_local_avx2 + 0x905
vpp[71]: #3  0x00007f125cf943a4 0x7f125cf943a4
vpp[71]: #4  0x00007f125cf95dee vlib_main + 0x71e
vpp[71]: #5  0x00007f125cfcd4d3 0x7f125cfcd4d3
vpp[71]: #6  0x00007f125c10c778 0x7f125c10c778



running options:

unix {
    log /outDir/vpp.log
    cli-listen /run/vpp/cli.sock
}


api-segment {
    prefix vpp1
}


plugins {
    plugin default { enable }
    plugin dpdk_plugin.so { disable }
}






thanks.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10311): https://lists.fd.io/g/vpp-dev/message/10311
Mute This Topic: https://lists.fd.io/mt/25038079/1239119
Group Owner: vpp-dev+ow...@lists.fd.io<mailto:ow...@lists.fd.io>
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub 
<https://lists.fd.io/g/vpp-dev/unsub%20> 
[che...@yahoo.com<mailto:che...@yahoo.com>]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10316): https://lists.fd.io/g/vpp-dev/message/10316
Mute This Topic: https://lists.fd.io/mt/25038079/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to