Hi,

This should have been fixed with https://gerrit.fd.io/r/c/vpp/+/27183
It is merged in master and VPP 20.05 (but not 20.01 which is no longer 
maintained).
The best should be to upgrade to 20.05.

ben

> -----Original Message-----
> From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of
> ais...@gmail.com
> Sent: lundi 15 juin 2020 10:03
> To: vpp-dev@lists.fd.io
> Subject: [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 0000: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.
> 0x00007f467392a428 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  0x00007f467392a428 in __GI_raise (sig=sig@entry=6) at
> ../sysdeps/unix/sysv/linux/raise.c:54
> #1  0x00007f467392c02a in __GI_abort () at abort.c:89
> #2  0x0000000000407555 in os_exit (code=1) at /home/aishwarya/BN/vpp-
> 20.01/src/vpp/vnet/main.c:379
> #3  0x00007f46742bb919 in unix_signal_handler (signum=6,
> si=0x7f4634b7d2b0, uc=0x7f4634b7d180) at /home/aishwarya/BN/vpp-
> 20.01/src/vlib/unix/main.c:187
> #4  <signal handler called>
> #5  0x00007f467392a428 in __GI_raise (sig=sig@entry=6) at
> ../sysdeps/unix/sysv/linux/raise.c:54
> #6  0x00007f467392c02a in __GI_abort () at abort.c:89
> #7  0x0000000000407510 in os_panic () at /home/aishwarya/BN/vpp-
> 20.01/src/vpp/vnet/main.c:355
> #8  0x00007f4673cf1fb2 in debugger () at /home/aishwarya/BN/vpp-
> 20.01/src/vppinfra/error.c:84
> #9  0x00007f4673cf24a1 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 0x00007f463078c575 in vlib_time_now (vm=0x7f46744f2480
> <vlib_global_main>) at /home/aishwarya/BN/vpp-20.01/src/vlib/main.h:287
> #11 0x00007f463078f473 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 0x00007f46307b2030 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 0x00007f467425371d 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 0x00007f4674253ede 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 0x00007f4674255b3c in vlib_main_or_worker_loop (vm=0x7f46348f5fc0,
> is_main=0) at /home/aishwarya/BN/vpp-20.01/src/vlib/main.c:1833
> #16 0x00007f46742563aa in vlib_worker_loop (vm=0x7f46348f5fc0) at
> /home/aishwarya/BN/vpp-20.01/src/vlib/main.c:1940
> #17 0x00007f467429459a in vlib_worker_thread_fn (arg=0x7f463595b380) at
> /home/aishwarya/BN/vpp-20.01/src/vlib/threads.c:1751
> #18 0x00007f4673d12394 in clib_calljmp () at /home/aishwarya/BN/vpp-
> 20.01/src/vppinfra/longjmp.S:123
> #19 0x00007f361b3fed30 in ?? ()
> #20 0x00007f467428ec94 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 (#16725): https://lists.fd.io/g/vpp-dev/message/16725
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]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to