Re: [vpp-dev] network loop

2017-11-22 Thread yug...@telincn.com
Hi all,
If I set down one of its interface and set up it,  then everything is OK.
Any ideas?

Regards,
Ewan





yug...@telincn.com
 
From: yug...@telincn.com
Date: 2017-11-17 12:21
To: vpp-dev
Subject: network loop
Hi  all,
My version is 17.04, sometimes there will be  a large number of packets 
transmitted by vpp.
It looks like that vpp has network loop itself. Here is the stack when the loop 
happened. Any idea?


(gdb) c
Continuing.
^C
Thread 1 "vpp_main" received signal SIGINT, Interrupt.
eth_em_xmit_pkts (tx_queue=0x7a8227972d00, tx_pkts=, 
nb_pkts=)
at 
/home/wangzy/VBRASV100R001/vpp1704/dpdk/_build/dpdk-17.02/drivers/net/e1000/em_rxtx.c:625
625 return nb_tx;
(gdb) bt
#0  eth_em_xmit_pkts (tx_queue=0x7a8227972d00, tx_pkts=, 
nb_pkts=)
at 
/home/wangzy/VBRASV100R001/vpp1704/dpdk/_build/dpdk-17.02/drivers/net/e1000/em_rxtx.c:625
#1  0x7f81b02923cf in rte_eth_tx_burst (nb_pkts=, 
tx_pkts=, queue_id=0, port_id=)
at 
/home/wangzy/VBRASV100R001/vpp1704/dpdk/_install/include/dpdk/rte_ethdev.h:2858
#2  tx_burst_vector_internal (tx_vector=, xd=, 
vm=)
at 
/home/wangzy/VBRASV100R001/vpp1704/build-data/../src/plugins/dpdk/device/device.c:282
#3  dpdk_interface_tx (f=, node=, vm=)
at 
/home/wangzy/VBRASV100R001/vpp1704/build-data/../src/plugins/dpdk/device/device.c:559
#4  dpdk_interface_tx_avx2 (vm=, node=, 
frame=)
at 
/home/wangzy/VBRASV100R001/vpp1704/build-data/../src/plugins/dpdk/device/device.c:789
#5  0x7f81f47e0119 in dispatch_node (vm=0x7f81f4a332a0 , 
node=0x7f81b1eb8800, type=, 
dispatch_state=VLIB_NODE_STATE_POLLING, frame=, 
last_time_stamp=13589960530660)
at /home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vlib/main.c:998
#6  0x7f81f47e040d in dispatch_pending_node (vm=vm@entry=0x7f81f4a332a0 
, p=0x7f81b52c3398, 
last_time_stamp=) at 
/home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vlib/main.c:1144
#7  0x7f81f47e0e6d in vlib_main_or_worker_loop (is_main=1, 
vm=0x7f81f4a332a0 )
at /home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vlib/main.c:1591
#8  vlib_main_loop (vm=0x7f81f4a332a0 ) at 
/home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vlib/main.c:1611
#9  vlib_main (vm=vm@entry=0x7f81f4a332a0 , 
input=input@entry=0x7f81b1854fa0)
at /home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vlib/main.c:1739
#10 0x7f81f4819f13 in thread0 (arg=140196131844768) at 
/home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vlib/unix/main.c:507
#11 0x7f81f2a53cd0 in clib_calljmp () at 
/home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vppinfra/longjmp.S:110
#12 0x7ffcb4160b00 in ?? ()
#13 0x7f81f481a92d in vlib_unix_main (argc=, argv=)
at /home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vlib/unix/main.c:606


Regards,
Ewan


yug...@telincn.com
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] network loop

2017-11-16 Thread yug...@telincn.com
Hi  all,
My version is 17.04, sometimes there will be  a large number of packets 
transmitted by vpp.
It looks like that vpp has network loop itself. Here is the stack when the loop 
happened. Any idea?


(gdb) c
Continuing.
^C
Thread 1 "vpp_main" received signal SIGINT, Interrupt.
eth_em_xmit_pkts (tx_queue=0x7a8227972d00, tx_pkts=, 
nb_pkts=)
at 
/home/wangzy/VBRASV100R001/vpp1704/dpdk/_build/dpdk-17.02/drivers/net/e1000/em_rxtx.c:625
625 return nb_tx;
(gdb) bt
#0  eth_em_xmit_pkts (tx_queue=0x7a8227972d00, tx_pkts=, 
nb_pkts=)
at 
/home/wangzy/VBRASV100R001/vpp1704/dpdk/_build/dpdk-17.02/drivers/net/e1000/em_rxtx.c:625
#1  0x7f81b02923cf in rte_eth_tx_burst (nb_pkts=, 
tx_pkts=, queue_id=0, port_id=)
at 
/home/wangzy/VBRASV100R001/vpp1704/dpdk/_install/include/dpdk/rte_ethdev.h:2858
#2  tx_burst_vector_internal (tx_vector=, xd=, 
vm=)
at 
/home/wangzy/VBRASV100R001/vpp1704/build-data/../src/plugins/dpdk/device/device.c:282
#3  dpdk_interface_tx (f=, node=, vm=)
at 
/home/wangzy/VBRASV100R001/vpp1704/build-data/../src/plugins/dpdk/device/device.c:559
#4  dpdk_interface_tx_avx2 (vm=, node=, 
frame=)
at 
/home/wangzy/VBRASV100R001/vpp1704/build-data/../src/plugins/dpdk/device/device.c:789
#5  0x7f81f47e0119 in dispatch_node (vm=0x7f81f4a332a0 , 
node=0x7f81b1eb8800, type=, 
dispatch_state=VLIB_NODE_STATE_POLLING, frame=, 
last_time_stamp=13589960530660)
at /home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vlib/main.c:998
#6  0x7f81f47e040d in dispatch_pending_node (vm=vm@entry=0x7f81f4a332a0 
, p=0x7f81b52c3398, 
last_time_stamp=) at 
/home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vlib/main.c:1144
#7  0x7f81f47e0e6d in vlib_main_or_worker_loop (is_main=1, 
vm=0x7f81f4a332a0 )
at /home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vlib/main.c:1591
#8  vlib_main_loop (vm=0x7f81f4a332a0 ) at 
/home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vlib/main.c:1611
#9  vlib_main (vm=vm@entry=0x7f81f4a332a0 , 
input=input@entry=0x7f81b1854fa0)
at /home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vlib/main.c:1739
#10 0x7f81f4819f13 in thread0 (arg=140196131844768) at 
/home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vlib/unix/main.c:507
#11 0x7f81f2a53cd0 in clib_calljmp () at 
/home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vppinfra/longjmp.S:110
#12 0x7ffcb4160b00 in ?? ()
#13 0x7f81f481a92d in vlib_unix_main (argc=, argv=)
at /home/wangzy/VBRASV100R001/vpp1704/build-data/../src/vlib/unix/main.c:606


Regards,
Ewan


yug...@telincn.com
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev