[vpp-dev] Not getting DHCP ip on second DPDK interface
Hi, I created two DPDK interface on ubuntu VM and setting them to DHCP client. But only one interface gets DHCP IP. 1. BGvpp# show int Name Idx State MTU (L3/IP4/IP6/MPLS) Counter Count GigabitEthernet2/1/0 1 down 9000/0/0/0 GigabitEthernet2/2/0 2 down 9000/0/0/0 local0 0 down 0/0/0/0 DBGvpp# 2. session set DBGvpp# set interface state GigabitEthernet2/1/0 up DBGvpp# set dh dhcp dhcpv6 DBGvpp# set dhcp client intfc GigabitEthernet2/1/0 DBGvpp# show int address GigabitEthernet2/1/0 (up): L3 192.168.128.98/17 GigabitEthernet2/2/0 (dn): local0 (dn): DBGvpp# set interface state GigabitEthernet2/2/0 up DBGvpp# et dhcp client intfc GigabitEthernet2/2/0 unknown input `et dhcp client intfc GigabitEt...' DBGvpp# set dhcp client intfc GigabitEthernet2/2/0 DBGvpp# show int address GigabitEthernet2/1/0 (up): L3 192.168.128.98/17 GigabitEthernet2/2/0 (up): local0 (dn): DBGvpp# show int Name Idx State MTU (L3/IP4/IP6/MPLS) Counter Count GigabitEthernet2/1/0 1 up 9000/0/0/0 rx packets 827 rx bytes 113977 tx packets 5 tx bytes 1330 drops 827 ip4 460 ip6 326 GigabitEthernet2/2/0 2 up 9000/0/0/0 rx packets 512 rx bytes 63609 tx packets 4 tx bytes 1288 drops 512 ip4 294 ip6 202 local0 0 down 0/0/0/0 DBGvpp# show dhc dhcp dhcp6 dhcpv6 DBGvpp# show dhcp client [0] GigabitEthernet2/1/0 state DHCP_BOUND installed 1 addr 192.168.128.98/17 gw 192.168.128.1 server 192.168.128.1 dns 192.168.128.1 [1] GigabitEthernet2/2/0 state DHCP_BOUND installed 1 addr 192.168.128.97/17 gw 192.168.128.1 server 192.168.128.1 dns 192.168.128.1 DBGvpp# HOWEVER ABOVE OUTPUT SHOWS THAT BOTH INTERFACE HAS AN IP address ASSIGNED . BUT 'show int address' does not show ip on second interface: DBGvpp# show int address GigabitEthernet2/1/0 (up): L3 192.168.128.98/17 GigabitEthernet2/2/0 (up): local0 (dn): Also noticed that ping to Internet works only until first interface gets IP address. The moment the second interface is set to DHCP Client, ping stops working. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17096): https://lists.fd.io/g/vpp-dev/message/17096 Mute This Topic: https://lists.fd.io/mt/75840242/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] Notifier events on ip assignment/change
Hi, Is there a way to register to some notification in VPP so that I can get events when an interface gets an Ip address either statically or via DHCP? Scenario is that I would need to open some sockets on an interface and if ip address changes in case of DHCP lease expire, I want to open socket on new ip address. For this I need a notification. Currently if I open socket on udp://0.0.0.0/port , but later interface ip updates, I stop receiving packets. Regards, Aishwarya -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16927): https://lists.fd.io/g/vpp-dev/message/16927 Mute This Topic: https://lists.fd.io/mt/75412759/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] vpp-20.01/src/vlib/threads.c:1408 (vlib_worker_thread_barrier_sync_int) assertion `vlib_get_thread_index () == 0'
Hi,
I am using vpp20.01 on multicore env running on a VM and getting a crash:
*(vlib_worker_thread_barrier_sync_int) assertion `vlib_get_thread_index () ==
0' fails
* Startup.conf snippet:
cpu {
main-core 0
corelist-workers 1
}
In code I am trying something like this:
clib_error_t *
clients_connect (vlib_main_t * vm, u32 n_clients, char *uri)
{
vnet_connect_args_t _a, *a = &_a;
int i, rv;
clib_memset (a, 0, sizeof (*a));
for (i = 0; i < n_clients; i++)
{
a->uri = (char *) uri;
a->api_context = i;
a->app_index = my_app_index;
*vlib_worker_thread_barrier_sync (vm);*
if ((rv = *vnet_connect_uri* (a)))
{
vlib_worker_thread_barrier_release (vm);
return clib_error_return (0, "connect returned: %d", rv);
}
*vlib_worker_thread_barrier_release (vm);*
}
return 0;
}
Can someone let me know why the assert is failing?
Regards,
Aishwarya
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16917): https://lists.fd.io/g/vpp-dev/message/16917
Mute This Topic: https://lists.fd.io/mt/75392381/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] VPP20.01: vpp-20.01/src/vnet/session/application.c:960 (vnet_listen) assertion `vlib_thread_is_main_w_barrier ()' fails
Hi Florin, Thanks a lot for the input. Tried your suggestion and it looks good. One query: Is this applicable to "vnet_connect_uri" api as well? I.e it shall be called from main thread? Regards, Aishwarya -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16893): https://lists.fd.io/g/vpp-dev/message/16893 Mute This Topic: https://lists.fd.io/mt/75330170/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] VPP20.01: vpp-20.01/src/vnet/session/application.c:960 (vnet_listen) assertion `vlib_thread_is_main_w_barrier ()' fails
[Edited Message Follows]
HI,
I am trying to run a VPP application on multicore env and get a crash when I
call 'vnet_bind_uri'. If I run in just without workers in startup.conf, I dont
get any crash. Please if someone can help me understand why is this crash
coming?
I am using VPP 20.01 on a Ubuntu VM:
startup.conf:
unix {
nodaemon
interactive \
cli-listen /run/vpp/cli.sock
log /tmp/vpp.log
full-coredump
poll-sleep-usec 100
}
api-trace {
on
}
socksvr {
default
}
cpu {
*main-core 0*
*workers 1*
}
dpdk {
dev :02:04.0
}
socksvr { socket-name /tmp/vpp-api.sock}
GDB:
Thread 1 "vpp_main" received signal SIGABRT, Aborted.
0x7f5dd1f86428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x7f5dd1f86428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#1 0x7f5dd1f8802a in __GI_abort () at abort.c:89
#2 0x00407510 in os_panic () at
/home/aishwarya/BN/vpp-20.01/src/vpp/vnet/main.c:355
#3 0x7f5dd234dfb2 in debugger () at
/home/aishwarya/BN/vpp-20.01/src/vppinfra/error.c:84
#4 0x7f5dd234e4a1 in _clib_error (how_to_die=2, function_name=0x0,
line_number=0, fmt=0x7f5dd3a20bc0 "%s:%d (%s) assertion `%s' fails")
at /home/aishwarya/BN/vpp-20.01/src/vppinfra/error.c:158
*#5 0x7f5dd36ec397 in vnet_listen (a=0x7f5d93010b50) at
/home/aishwarya/BN/vpp-20.01/src/vnet/session/application.c:960*
*#6 0x7f5dd36fdb1d in vnet_bind_uri (a=0x7f5d93010b50) at
/home/aishwarya/BN/vpp-20.01/src/vnet/session/application_interface.c:138*
#7 0x7f5d8734 in zt_app_listen (vm=0x7f5dd2b4e480 ,
port=9993)
at /home/aishwarya/BN/vpp-20.01/src/plugins/zt_pkt_handler.c:1249
#8 0x7f5d87349987 in zt_node_create (vm=0x7f5dd2b4e480 )
at /home/aishwarya/BN/vpp-20.01/src/plugins/zt_pkt_handler.c:924
#9 0x7f5d8734d661 in zt_app_command_fn (vm=0x7f5dd2b4e480
, input=0x7f5d93010f00, cmd=0x7f5d92abecc8)
at /home/aishwarya/BN/vpp-20.01/src/plugins/zt_pkt_handler.c:1835
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16886): https://lists.fd.io/g/vpp-dev/message/16886
Mute This Topic: https://lists.fd.io/mt/75330170/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] VPP20.01: vpp-20.01/src/vnet/session/application.c:960 (vnet_listen) assertion `vlib_thread_is_main_w_barrier ()' fails
HI,
I am trying to run a VPP application on multicore env and get a crash when I
call 'vnet_bind_uri'. If I run in just without workers in startup.conf, I dont
get any crash. Please if someone can help me understand why is this crash
coming?
I am using VPP 20.01 on a Ubuntu VM:
startup.conf:
unix {
nodaemon
interactive \
cli-listen /run/vpp/cli.sock
log /tmp/vpp.log
full-coredump
poll-sleep-usec 100
}
api-trace {
on
}
socksvr {
default
}
cpu {
*main-core 0*
*workers 1*
}
dpdk {
dev :02:04.0
}
socksvr { socket-name /tmp/vpp-api.sock}
GDB:
Thread 1 "vpp_main" received signal SIGABRT, Aborted.
0x7f5dd1f86428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x7f5dd1f86428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#1 0x7f5dd1f8802a in __GI_abort () at abort.c:89
#2 0x00407510 in os_panic () at
/home/aishwarya/BN/vpp-20.01/src/vpp/vnet/main.c:355
#3 0x7f5dd234dfb2 in debugger () at
/home/aishwarya/BN/vpp-20.01/src/vppinfra/error.c:84
#4 0x7f5dd234e4a1 in _clib_error (how_to_die=2, function_name=0x0,
line_number=0, fmt=0x7f5dd3a20bc0 "%s:%d (%s) assertion `%s' fails")
at /home/aishwarya/BN/vpp-20.01/src/vppinfra/error.c:158
*#5 0x7f5dd36ec397 in vnet_listen (a=0x7f5d93010b50) at
/home/aishwarya/BN/vpp-20.01/src/vnet/session/application.c:960*
*#6 0x7f5dd36fdb1d in vnet_bind_uri (a=0x7f5d93010b50) at
/home/aishwarya/BN/vpp-20.01/src/vnet/session/application_interface.c:138*
#7 0x7f5d8734 in zt_app_listen (vm=0x7f5dd2b4e480 ,
port=9993)
at /home/aishwarya/BN/vpp-20.01/src/plugins/zerotier/zt_pkt_handler.c:1249
#8 0x7f5d87349987 in zt_node_create (vm=0x7f5dd2b4e480 )
at /home/aishwarya/BN/vpp-20.01/src/plugins/zerotier/zt_pkt_handler.c:924
#9 0x7f5d8734d661 in zt_app_command_fn (vm=0x7f5dd2b4e480
, input=0x7f5d93010f00, cmd=0x7f5d92abecc8)
at /home/aishwarya/BN/vpp-20.01/src/plugins/zerotier/zt_pkt_handler.c:1835
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16886): https://lists.fd.io/g/vpp-dev/message/16886
Mute This Topic: https://lists.fd.io/mt/75330170/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] Crash on setting interface as DHCP client #vpp #vpp-20.01
Hi Ben,
This patch seems to be already applied in VPP20.01.
int
dhcp_client_for_us (u32 bi, vlib_buffer_t * b,
ip4_header_t * ip,
udp_header_t * udp, dhcp_header_t * dhcp)
{
dhcp_client_main_t *dcm = _client_main;
*vlib_main_t *vm = dcm->vlib_main;*
dhcp_client_t *c;
uword *p;
*f64 now = vlib_time_now (dcm->vlib_main);*
u8 dhcp_message_type = 0;
dhcp_option_t *o;
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16726): https://lists.fd.io/g/vpp-dev/message/16726
Mute This Topic: https://lists.fd.io/mt/74890182/21656
Mute #vpp: https://lists.fd.io/g/fdio+vpp-dev/mutehashtag/vpp
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] Crash on setting interface as DHCP client #vpp #vpp-20.01
[Edited Message Follows]
Hi Team,
I am facing an issue when I try to set the interface to DHCP Client on
VPP-20.01 with worker thread enabled in the startup.conf.
Environment Used:
1. Vpp 20.01 running on a Ubuntu 16.01 VM.
2. Two CPU cores allocated
cat /proc/cpuinfo | grep processor
processor : 0
processor : 1
Startup.conf
unix {
nodaemon
interactive \
cli-listen /run/vpp/cli.sock
log /tmp/vpp.log
full-coredump
}
api-trace {
on
}
socksvr {
default
}
cpu {
*main-core 0*
*corelist-workers 1*
}
dpdk {
dev :02:01.0
}
socksvr { socket-name /tmp/vpp-api.sock}
Running VPP Debug CLI:
___ _ _ _ ___
__/ __/ _ \ (_)__ | | / / _ \/ _ \
_/ _// // / / / _ \ | |/ / ___/ ___/
/_/ /(_)_/\___/ |___/_/ /_/
DBGvpp# show th
ID Name Type LWP Sched Policy (Priority) lcore
Core Socket State
0 vpp_main 50887 other (0) 0
0 0
1 vpp_wk_0 workers 50889 other (0) 1
0 2
DBGvpp# show int
Name Idx State MTU (L3/IP4/IP6/MPLS) Counter
Count
GigabitEthernet2/1/0 1 down 9000/0/0/0
local0 0 down 0/0/0/0
DBGvpp# set interface state GigabitEthernet2/1/0 up
DBGvpp# show int
Name Idx State MTU (L3/IP4/IP6/MPLS) Counter
Count
GigabitEthernet2/1/0 1 up 9000/0/0/0
local0 0 down 0/0/0/0
*DBGvpp# set dhcp client intfc GigabitEthernet2/1/0*
*DBGvpp# 1: /home/aishwarya/BN/vpp-20.01/src/vlib/main.h:287 (vlib_time_now)
assertion `vm->thread_index == __os_thread_index' fails*
*Aborted (core dumped)*
Makefile:547: recipe for target 'run' failed
make: *** [run] Error 134
Backtrace in GDB:
Thread 3 "vpp_wk_0" received signal SIGABRT, Aborted.
0x7f467392a428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
54 in ../sysdeps/unix/sysv/linux/raise.c
(gdb) bt
#0 0x7f467392a428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#1 0x7f467392c02a in __GI_abort () at abort.c:89
#2 0x00407555 in os_exit (code=1) at
/home/aishwarya/BN/vpp-20.01/src/vpp/vnet/main.c:379
#3 0x7f46742bb919 in unix_signal_handler (signum=6, si=0x7f4634b7d2b0,
uc=0x7f4634b7d180) at /home/aishwarya/BN/vpp-20.01/src/vlib/unix/main.c:187
#4
#5 0x7f467392a428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#6 0x7f467392c02a in __GI_abort () at abort.c:89
#7 0x00407510 in os_panic () at
/home/aishwarya/BN/vpp-20.01/src/vpp/vnet/main.c:355
#8 0x7f4673cf1fb2 in debugger () at
/home/aishwarya/BN/vpp-20.01/src/vppinfra/error.c:84
*#9 0x7f4673cf24a1 in _clib_error (how_to_die=2, function_name=0x0,
line_number=0, fmt=0x7f46307fa9f8 "%s:%d (%s) assertion `%s' fails")*
*at /home/aishwarya/BN/vpp-20.01/src/vppinfra/error.c:158*
*#10 0x7f463078c575 in vlib_time_now (vm=0x7f46744f2480 )
at /home/aishwarya/BN/vpp-20.01/src/vlib/main.h:287*
*#11 0x7f463078f473 in dhcp_client_for_us (bi=635348, b=0x10026c7500,
ip=0x10026c760e, udp=0x10026c7622, dhcp=0x10026c762a)*
*at /home/aishwarya/BN/vpp-20.01/src/plugins/dhcp/client.c:282*
*#12 0x7f46307b2030 in dhcp_proxy_to_client_input (vm=0x7f46348f5fc0,
node=0x7f4634bfa2c0, from_frame=0x7f4634bda980)*
*at /home/aishwarya/BN/vpp-20.01/src/plugins/dhcp/dhcp4_proxy_node.c:566*
#13 0x7f467425371d in dispatch_node (vm=0x7f46348f5fc0,
node=0x7f4634bfa2c0, type=VLIB_NODE_TYPE_INTERNAL,
dispatch_state=VLIB_NODE_STATE_POLLING, frame=0x7f4634bda980,
last_time_stamp=50239219631664) at
/home/aishwarya/BN/vpp-20.01/src/vlib/main.c:1208
#14 0x7f4674253ede in dispatch_pending_node (vm=0x7f46348f5fc0,
pending_frame_index=4, last_time_stamp=50239219631664) at
/home/aishwarya/BN/vpp-20.01/src/vlib/main.c:1376
#15 0x7f4674255b3c in vlib_main_or_worker_loop (vm=0x7f46348f5fc0,
is_main=0) at /home/aishwarya/BN/vpp-20.01/src/vlib/main.c:1833
#16 0x7f46742563aa in vlib_worker_loop (vm=0x7f46348f5fc0) at
/home/aishwarya/BN/vpp-20.01/src/vlib/main.c:1940
#17 0x7f467429459a in vlib_worker_thread_fn (arg=0x7f463595b380) at
/home/aishwarya/BN/vpp-20.01/src/vlib/threads.c:1751
#18 0x7f4673d12394 in clib_calljmp () at
/home/aishwarya/BN/vpp-20.01/src/vppinfra/longjmp.S:123
#19 0x7f361b3fed30 in ?? ()
#20 0x7f467428ec94 in vlib_worker_thread_bootstrap_fn (arg=0x7f463595b380)
at /home/aishwarya/BN/vpp-20.01/src/vlib/threads.c:573
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Can someone please help me understand and fix this issue?
Regards,
Aishwarya
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online
[vpp-dev] Crash on setting interface as DHCP client #vpp #vpp-20.01
Hi Team,
I am facing an issue when I try to set the interface to DHCP Client on
VPP-20.01 with worker thread enabled in the startup.conf.
Environment Used:
1. Vpp 20.01 running on a Ubuntu 16.01 VM.
2. Two CPU cores allocated
cat /proc/cpuinfo | grep processor
processor : 0
processor : 1
Startup.conf
unix {
nodaemon
interactive \
cli-listen /run/vpp/cli.sock
log /tmp/vpp.log
full-coredump
}
api-trace {
on
}
socksvr {
default
}
cpu {
*main-core 0*
*corelist-workers 1*
}
dpdk {
dev :02:01.0
}
socksvr { socket-name /tmp/vpp-api.sock}
Running VPP Debug CLI:
___ _ _ _ ___
__/ __/ _ \ (_)__ | | / / _ \/ _ \
_/ _// // / / / _ \ | |/ / ___/ ___/
/_/ /(_)_/\___/ |___/_/ /_/
DBGvpp# show int
Name Idx State MTU (L3/IP4/IP6/MPLS) Counter
Count
GigabitEthernet2/1/0 1 down 9000/0/0/0
local0 0 down 0/0/0/0
DBGvpp# set interface state GigabitEthernet2/1/0 up
DBGvpp# show int
Name Idx State MTU (L3/IP4/IP6/MPLS) Counter
Count
GigabitEthernet2/1/0 1 up 9000/0/0/0
local0 0 down 0/0/0/0
*DBGvpp# set dhcp client intfc GigabitEthernet2/1/0*
*DBGvpp# 1: /home/aishwarya/BN/vpp-20.01/src/vlib/main.h:287 (vlib_time_now)
assertion `vm->thread_index == __os_thread_index' fails*
*Aborted (core dumped)*
Makefile:547: recipe for target 'run' failed
make: *** [run] Error 134
Backtrace in GDB:
Thread 3 "vpp_wk_0" received signal SIGABRT, Aborted.
0x7f467392a428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
54 in ../sysdeps/unix/sysv/linux/raise.c
(gdb) bt
#0 0x7f467392a428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#1 0x7f467392c02a in __GI_abort () at abort.c:89
#2 0x00407555 in os_exit (code=1) at
/home/aishwarya/BN/vpp-20.01/src/vpp/vnet/main.c:379
#3 0x7f46742bb919 in unix_signal_handler (signum=6, si=0x7f4634b7d2b0,
uc=0x7f4634b7d180) at /home/aishwarya/BN/vpp-20.01/src/vlib/unix/main.c:187
#4
#5 0x7f467392a428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#6 0x7f467392c02a in __GI_abort () at abort.c:89
#7 0x00407510 in os_panic () at
/home/aishwarya/BN/vpp-20.01/src/vpp/vnet/main.c:355
#8 0x7f4673cf1fb2 in debugger () at
/home/aishwarya/BN/vpp-20.01/src/vppinfra/error.c:84
*#9 0x7f4673cf24a1 in _clib_error (how_to_die=2, function_name=0x0,
line_number=0, fmt=0x7f46307fa9f8 "%s:%d (%s) assertion `%s' fails")*
*at /home/aishwarya/BN/vpp-20.01/src/vppinfra/error.c:158*
*#10 0x7f463078c575 in vlib_time_now (vm=0x7f46744f2480 )
at /home/aishwarya/BN/vpp-20.01/src/vlib/main.h:287*
*#11 0x7f463078f473 in dhcp_client_for_us (bi=635348, b=0x10026c7500,
ip=0x10026c760e, udp=0x10026c7622, dhcp=0x10026c762a)*
*at /home/aishwarya/BN/vpp-20.01/src/plugins/dhcp/client.c:282*
*#12 0x7f46307b2030 in dhcp_proxy_to_client_input (vm=0x7f46348f5fc0,
node=0x7f4634bfa2c0, from_frame=0x7f4634bda980)*
*at /home/aishwarya/BN/vpp-20.01/src/plugins/dhcp/dhcp4_proxy_node.c:566*
#13 0x7f467425371d in dispatch_node (vm=0x7f46348f5fc0,
node=0x7f4634bfa2c0, type=VLIB_NODE_TYPE_INTERNAL,
dispatch_state=VLIB_NODE_STATE_POLLING, frame=0x7f4634bda980,
last_time_stamp=50239219631664) at
/home/aishwarya/BN/vpp-20.01/src/vlib/main.c:1208
#14 0x7f4674253ede in dispatch_pending_node (vm=0x7f46348f5fc0,
pending_frame_index=4, last_time_stamp=50239219631664) at
/home/aishwarya/BN/vpp-20.01/src/vlib/main.c:1376
#15 0x7f4674255b3c in vlib_main_or_worker_loop (vm=0x7f46348f5fc0,
is_main=0) at /home/aishwarya/BN/vpp-20.01/src/vlib/main.c:1833
#16 0x7f46742563aa in vlib_worker_loop (vm=0x7f46348f5fc0) at
/home/aishwarya/BN/vpp-20.01/src/vlib/main.c:1940
#17 0x7f467429459a in vlib_worker_thread_fn (arg=0x7f463595b380) at
/home/aishwarya/BN/vpp-20.01/src/vlib/threads.c:1751
#18 0x7f4673d12394 in clib_calljmp () at
/home/aishwarya/BN/vpp-20.01/src/vppinfra/longjmp.S:123
#19 0x7f361b3fed30 in ?? ()
#20 0x7f467428ec94 in vlib_worker_thread_bootstrap_fn (arg=0x7f463595b380)
at /home/aishwarya/BN/vpp-20.01/src/vlib/threads.c:573
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Can someone please help me understand and fix this issue?
Regards,
Aishwarya
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16724): https://lists.fd.io/g/vpp-dev/message/16724
Mute This Topic: https://lists.fd.io/mt/74890182/21656
Mute #vpp: https://lists.fd.io/g/fdio+vpp-dev/mutehashtag/vpp
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
