Hi,

Sorry for my late response.
I  build VPP with 1707 release and everything is OK.

Thanks.

On Sun, Jul 16, 2017 at 6:05 PM, Neale Ranns (nranns) <nra...@cisco.com>
wrote:

>
>
> Hi Andrew,
>
>
>
> A couple of things would be useful to help track this down, if you
> wouldn’t mind.
>
>
>
> 1.       Please run a debug image, then many of those ‘<optimised out>’
> will be recovered in the core dump. Then you can (or maybe you can with the
> image you have) go to frame:
>
> #18 0x00007ffff732987f in cdp_input_format_trace (s=<optimized out>,
> args=<optimized out>) at /root/vpp-1707/build-data/../
> src/vnet/cdp/cdp_input.c:492
>
> and do ‘print *tlv’
>
> 2.       Get a pcap file of the input traffc or a tcp_dump. I’d like to
> see the CDP TLVs in the packet on the wire.
>
>
>
> Thanks,
>
> neale
>
>
>
> *From: *<vpp-dev-boun...@lists.fd.io> on behalf of Andrew Taylor <
> andrew2016tay...@gmail.com>
> *Date: *Sunday, 16 July 2017 at 13:22
> *To: *"Luke, Chris" <chris_l...@comcast.com>, "vpp-dev@lists.fd.io" <
> vpp-dev@lists.fd.io>
>
> *Subject: *Re: [vpp-dev] show trace bug in vpp stable 1707
>
>
>
> I checked with different heap-size, I think there is a bug in new memory
> management design.
>
> I used the default configuration of vpp: (vpp unix interactive)
>
>
>
>
>
> when the trace is added. vpp can't show trace and core dump accrued.
>
>
>
>
>
> On Sat, Jul 15, 2017 at 5:48 PM, Luke, Chris <chris_l...@comcast.com>
> wrote:
>
> Hi Andrew,
>
>
>
> The trace raises more questions! :)
>
>
>
> What is in your startup.conf and parameters on the VPP command line?
>
>
>
> It says “out of memory” trying to format a string; I am wondering if you
> have an exceptionally small heap configured.
>
>
>
> How long did it take before it crashed?
>
>
>
> If you reduce the number of packets to capture the traces of, to something
> like 5, does it still crash? Or just take longer to crash?
>
>
>
> Thanks,
>
> Chris.
>
>
>
> *From:* Andrew Taylor [mailto:andrew2016tay...@gmail.com]
> *Sent:* Saturday, July 15, 2017 2:38
> *To:* Luke, Chris <chris_l...@cable.comcast.com>
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] show trace bug in vpp stable 1707
>
>
>
>
>
> *This is a vpp config :*
>
> set int ip address GigabitEthernet0/4/0 192.168.30.135/24
> set int state GigabitEthernet0/4/0 up
> set int ip address GigabitEthernet0/5/0 192.168.40.135/24
> set int state GigabitEthernet0/5/0 up
>
>
>
> trace add dpdk-input 100
>
> show trace
>
>
>
> *this is a bt output:*
>
>
> #0  0x00007ffff6395c37 in __GI_raise (sig=sig@entry=6) at
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #1  0x00007ffff6399028 in __GI_abort () at abort.c:89
> #2  0x0000000000406fd3 in os_panic () at /root/vpp-1707/build-data/../
> src/vpp/vnet/main.c:263
> #3  0x00007ffff6bae5bf in clib_mem_alloc_aligned_at_offset
> (os_out_of_memory_on_failure=1, align_offset=<optimized out>, align=4,
> size=699583872) at /root/vpp-1707/build-data/../src/vppinfra/mem.h:102
> #4  vec_resize_allocate_memory (v=<optimized out>, length_increment=length_
> increment@entry=2, data_bytes=<optimized out>, header_bytes=<optimized
> out>, header_bytes@entry=0, data_align=data_align@entry=4) at
> /root/vpp-1707/build-data/../src/vppinfra/vec.c:84
> #5  0x00007ffff6b6724c in _vec_resize (data_align=0, header_bytes=0,
> data_bytes=<optimized out>, length_increment=2, v=<optimized out>) at
> /root/vpp-1707/build-data/../src/vppinfra/vec.h:142
> #6  format_integer (s=<optimized out>, s@entry=0x7fffca8d1b4c '-'
> <repeats 19 times>, " Start of thread 0 vpp_main ", '-' <repeats 19 times>,
> "\nPacket 1\n\n00:00:37:241764: dpdk-input\n  GigabitEthernet0/4/0 rx queue
> 0\n  buffer 0x1ca7: current data 0, length 474, free-list 0, clo"...,
> number=<optimized out>, options=options@entry=0x7fffb65ce310) at
> /root/vpp-1707/build-data/../src/vppinfra/format.c:535
> #7  0x00007ffff6b67d26 in do_percent (va=0x7fffb65ce398, fmt=<optimized
> out>, _s=<synthetic pointer>) at /root/vpp-1707/build-data/../
> src/vppinfra/format.c:314
> #8  va_format (s=0x7fffca8d1b4c '-' <repeats 19 times>, " Start of thread
> 0 vpp_main ", '-' <repeats 19 times>, "\nPacket 1\n\n00:00:37:241764:
> dpdk-input\n  GigabitEthernet0/4/0 rx queue 0\n  buffer 0x1ca7: current
> data 0, length 474, free-list 0, clo"..., fmt=<optimized out>, 
> va=va@entry=0x7fffb65ce398)
> at /root/vpp-1707/build-data/../src/vppinfra/format.c:404
> #9  0x00007ffff6b67417 in format (s=<optimized out>, fmt=fmt@entry=0x49c67a
> "%02x") at /root/vpp-1707/build-data/../src/vppinfra/format.c:423
> #10 0x000000000043ce7f in format_hex_bytes (s=<optimized out>,
> va=<optimized out>) at /root/vpp-1707/build-data/../
> src/vpp/api/api_format.c:4266
> #11 0x00007ffff6b67b63 in do_percent (va=0x7fffb65ce588, fmt=<optimized
> out>, _s=<synthetic pointer>) at /root/vpp-1707/build-data/../
> src/vppinfra/format.c:373
> #12 va_format (s=0x7fffb664aeb4 '0' <repeats 200 times>..., fmt=<optimized
> out>, va=va@entry=0x7fffb65ce588) at /root/vpp-1707/build-data/../
> src/vppinfra/format.c:404
> #13 0x00007ffff6b67417 in format (s=<optimized out>, 
> fmt=fmt@entry=0x7ffff766983e
> "%s(%d): %U\n") at /root/vpp-1707/build-data/../src/vppinfra/format.c:423
> #14 0x00007ffff7326c44 in format_generic_tlv (s=<optimized out>,
> va=<optimized out>) at /root/vpp-1707/build-data/../
> src/vnet/cdp/cdp_input.c:74
> #15 0x00007ffff6b67b63 in do_percent (va=0x7fffb65ce768, fmt=<optimized
> out>, _s=<synthetic pointer>) at /root/vpp-1707/build-data/../
> src/vppinfra/format.c:373
> #16 va_format (s=0x7fffb664aeb4 '0' <repeats 200 times>..., fmt=<optimized
> out>, va=va@entry=0x7fffb65ce768) at /root/vpp-1707/build-data/../
> src/vppinfra/format.c:404
> #17 0x00007ffff6b67417 in format (s=<optimized out>, 
> fmt=fmt@entry=0x7ffff769e08f
> "  %U") at /root/vpp-1707/build-data/../src/vppinfra/format.c:423
> #18 0x00007ffff732987f in cdp_input_format_trace (s=<optimized out>,
> args=<optimized out>) at /root/vpp-1707/build-data/../
> src/vnet/cdp/cdp_input.c:492
> #19 0x00007ffff6b67b63 in do_percent (va=0x7fffb65ce948, fmt=<optimized
> out>, _s=<synthetic pointer>) at /root/vpp-1707/build-data/../
> src/vppinfra/format.c:373
> #20 va_format (s=0x7fffb665b9d8 '-' <repeats 19 times>, " Start of thread
> 0 vpp_main ", '-' <repeats 19 times>, "\nPacket 1\n\n00:00:37:241764:
> dpdk-input\n  GigabitEthernet0/4/0 rx queue 0\n  buffer 0x1ca7: current
> data 0, length 474, free-list 0, clo"..., fmt=<optimized out>, 
> va=va@entry=0x7fffb65ce948)
> at /root/vpp-1707/build-data/../src/vppinfra/format.c:404
> #21 0x00007ffff6b67417 in format (s=<optimized out>, 
> fmt=fmt@entry=0x7ffff79a41c7
> "\n  %U") at /root/vpp-1707/build-data/../src/vppinfra/format.c:423
> #22 0x00007ffff79895fb in format_vlib_trace (s=<optimized out>,
> va=<optimized out>) at /root/vpp-1707/build-data/../src/vlib/trace.c:162
> #23 0x00007ffff6b67b63 in do_percent (va=0x7fffb65ceb38, fmt=<optimized
> out>, _s=<synthetic pointer>) at /root/vpp-1707/build-data/../
> src/vppinfra/format.c:373
> #24 va_format (s=0x7fffb665d110 '-' <repeats 19 times>, " Start of thread
> 0 vpp_main ", '-' <repeats 19 times>, "\nPacket 1\n\n00:00:37:",
> fmt=<optimized out>, va=va@entry=0x7fffb65ceb38) at
> /root/vpp-1707/build-data/../src/vppinfra/format.c:404
> #25 0x00007ffff6b67417 in format (s=s@entry=0x7fffb665d110 '-' <repeats
> 19 times>, " Start of thread 0 vpp_main ", '-' <repeats 19 times>,
> "\nPacket 1\n\n00:00:37:", fmt=fmt@entry=0x7ffff79a420e "Packet
> %d\n%U\n\n") at /root/vpp-1707/build-data/../src/vppinfra/format.c:423
> #26 0x00007ffff798a813 in cli_show_trace_buffer (vm=0x7ffff7bb02e0
> <vlib_global_main>, input=<optimized out>, cmd=<optimized out>) at
> /root/vpp-1707/build-data/../src/vlib/trace.c:299
> #27 0x00007ffff794f021 in vlib_cli_dispatch_sub_commands 
> (vm=vm@entry=0x7ffff7bb02e0
> <vlib_global_main>, cm=cm@entry=0x7ffff7bb0550 <vlib_global_main+624>,
> input=input@entry=0x7fffb65ceed0, parent_command_index=<optimized out>)
> at /root/vpp-1707/build-data/../src/vlib/cli.c:588
> #28 0x00007ffff794f3d7 in vlib_cli_dispatch_sub_commands 
> (vm=vm@entry=0x7ffff7bb02e0
> <vlib_global_main>, cm=cm@entry=0x7ffff7bb0550 <vlib_global_main+624>,
> input=input@entry=0x7fffb65ceed0, parent_command_index=parent_
> command_index@entry=0) at /root/vpp-1707/build-data/../src/vlib/cli.c:566
> #29 0x00007ffff794f600 in vlib_cli_input (vm=0x7ffff7bb02e0
> <vlib_global_main>, input=input@entry=0x7fffb65ceed0,
> function=function@entry=0x7ffff7992150 <unix_vlib_cli_output>,
> function_arg=function_arg@entry=0) at /root/vpp-1707/build-data/../
> src/vlib/cli.c:662
> #30 0x00007ffff79930f0 in unix_cli_process_input (cli_file_index=0,
> cm=0x7ffff7bb01a0 <unix_cli_main>) at /root/vpp-1707/build-data/../
> src/vlib/unix/cli.c:2189
> #31 0x00007ffff79968d5 in unix_cli_process (vm=0x7ffff7bb02e0
> <vlib_global_main>, rt=0x7fffb65be000, f=<optimized out>) at
> /root/vpp-1707/build-data/../src/vlib/unix/cli.c:2286
> #32 0x00007ffff795a006 in vlib_process_bootstrap (_a=<optimized out>) at
> /root/vpp-1707/build-data/../src/vlib/main.c:1259
> #33 0x00007ffff6b708c8 in clib_calljmp () at /root/vpp-1707/build-data/../
> src/vppinfra/longjmp.S:110
> #34 0x00007fffb6075830 in ?? ()
> #35 0x00007ffff795b3b1 in vlib_process_startup (f=0x0, p=0x7fffb65be000,
> vm=0x7ffff7bb02e0 <vlib_global_main>) at /root/vpp-1707/build-data/../
> src/vlib/main.c:1281
> #36 dispatch_process (vm=0x7ffff7bb02e0 <vlib_global_main>,
> p=0x7fffb65be000, last_time_stamp=0, f=0x0) at /root/vpp-1707/build-data/../
> src/vlib/main.c:1324
> #37 0x0000000000000000 in ?? ()
>
>
>
> On Thu, Jul 13, 2017 at 3:16 PM, Luke, Chris <chris_l...@comcast.com>
> wrote:
>
> Andrew,
>
>
>
> Are you able to recreate it with a debug build running in the debugger, so
> we can get a backtrace?
>
>
>
> Can you share details on how VPP is setup at the time of the crash?
>
>
>
> Chris
>
>
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
> Behalf Of *Andrew Taylor
> *Sent:* Thursday, July 13, 2017 5:19
> *To:* vpp-dev@lists.fd.io
> *Subject:* [vpp-dev] show trace bug in vpp stable 1707
>
>
>
>
>
> Hi,
>
> by following commands in VPP Stable 1707, core dump accrued when packets
> received.
>
> trace add dpdk-input 100
> sh trace
>
> Does it a bug or something changed in this version ?
>
>
>
> Thanks.
>
>
>
>
>
>
>
>
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Reply via email to