> > On 7 Jun 2018, at 13:38, xyxue <xy...@fiberhome.com> wrote: > > > Hi guys, > > When I create two host interface in vat. two minutes later the SIGABRT appear > . The 'fill_free_list' was called about 56 times. > > VPP# /home/vpp/build-data/../src/vlib/buffer.c:615 (alloc_from_free_list) > assertion `len >= n_alloc_buffers' fails > > Program received signal SIGABRT, Aborted. > 0xb7ffd424 in __kernel_vsyscall () > (gdb) bt > #0 0xb7ffd424 in __kernel_vsyscall () > #1 0xb72a02d7 in __GI_raise (sig=sig@entry=6) at > ../nptl/sysdeps/unix/sysv/linux/raise.c:56 > #2 0xb72a1b13 in __GI_abort () at abort.c:90 > #3 0x0804cb1c in os_panic () at > /home/vpp/build-data/../src/vpp/vnet/main.c:353 > #4 0xb74b9a8c in debugger () at > /home/vpp/build-data/../src/vppinfra/error.c:84 > #5 0xb74b9db1 in _clib_error (how_to_die=2, function_name=0x0, > line_number=0, fmt=0xb7f7bd58 "%s:%d (%s) assertion `%s' fails") > at /home/vpp/build-data/../src/vppinfra/error.c:143 > #6 0xb7ef929d in alloc_from_free_list (vm=0xb7fa8920 <vlib_global_main>, > free_list=0x376e0400, alloc_buffers=0x3778b9a0, n_alloc_buffers=256) > at /home/vpp/build-data/../src/vlib/buffer.c:615 > #7 0xb7ef9449 in vlib_buffer_alloc_internal (vm=0xb7fa8920 > <vlib_global_main>, buffers=0x3778b9a0, n_buffers=256) at > /home/vpp/build-data/../src/vlib/buffer.c:638 > #8 0xb7bf2048 in vlib_buffer_alloc (vm=0xb7fa8920 <vlib_global_main>, > buffers=0x3778b9a0, n_buffers=256) at > /home/vpp/build-data/../src/vlib/buffer_funcs.h:263 > #9 0xb7bf3889 in af_packet_device_input_fn (vm=0xb7fa8920 > <vlib_global_main>, node=0x373b1b00, frame=0x0, apif=0x377815a8) > at /home/vpp/build-data/../src/vnet/devices/af_packet/node.c:207 > #10 0xb7bf40fa in af_packet_input_fn (vm=0xb7fa8920 <vlib_global_main>, > node=0x373b1b00, frame=0x0) at > /home/vpp/build-data/../src/vnet/devices/af_packet/node.c:352 > #11 0xb7f34c2e in dispatch_node (vm=0xb7fa8920 <vlib_global_main>, > node=0x373b1b00, type=VLIB_NODE_TYPE_INPUT, > dispatch_state=VLIB_NODE_STATE_INTERRUPT, frame=0x0, > last_time_stamp=127565946476942) at > /home/vpp/build-data/../src/vlib/main.c:1010 > #12 0xb7f36a16 in vlib_main_or_worker_loop (vm=0xb7fa8920 <vlib_global_main>, > is_main=1) at /home/vpp/build-data/../src/vlib/main.c:1556 > #13 0xb7f371a7 in vlib_main_loop (vm=0xb7fa8920 <vlib_global_main>) at > /home/vpp/build-data/../src/vlib/main.c:1649 > #14 0xb7f377c9 in vlib_main (vm=0xb7fa8920 <vlib_global_main>, > input=0x37359fd0) at /home/vpp/build-data/../src/vlib/main.c:1806 > #15 0xb7f728db in thread0 (arg=3086649632) at > /home/vpp/build-data/../src/vlib/unix/main.c:622 > #16 0xb74cae48 in clib_calljmp () at > /home/vpp/build-data/../src/vppinfra/longjmp.S:204 > #17 0xb7fa8920 in ?? () from > /home/vpp/build-root/install-vpp_debug-native/vpp/lib/libvlib.so.0 > #18 0x0804c6c2 in main (argc=3, argv=0xbffff584) at > /home/vpp/build-data/../src/vpp/vnet/main.c:273 > (gdb) > > Is this a problem in vpp? How can I solve the problem?
Hard to say out of this limited data you provided....
