Re: [SPDK] Spdk NvmeOverTcp with VPP crashes on perf tool exit

* Re: [SPDK] Spdk NvmeOverTcp with VPP crashes on perf tool exit
@ 2019-01-26  1:06 Luse, Paul E
  0 siblings, 0 replies; 3+ messages in thread
From: Luse, Paul E @ 2019-01-26  1:06 UTC (permalink / raw)
  To: spdk

[-- Attachment #1: Type: text/plain, Size: 3366 bytes --]

Hi Ram,

Although there's a good chance this might be fixed on master, it would be great if you could file an issue at https://github.com/spdk/spdk/issues so that we can get all the information necessary to figure out next steps.

Thx
Paul

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Ramaraj Pandian
Sent: Friday, January 25, 2019 2:38 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] Spdk NvmeOverTcp with VPP crashes on perf tool exit

I am trying to run spdk-perf-tcp tool against spdk TCP target with VPP enabled. Test successfully ran but on exit, target crashes with the following:

(gdb) bt
#0  0x00007f91e414d1f7 in __GI_raise (sig=sig(a)entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007f91e414e8e8 in __GI_abort () at abort.c:90
#2  0x000000000060e435 in os_panic () at /home/vpp_18.01.1/build-data/../src/vppinfra/unix-misc.c:176
#3  0x000000000055b63c in debugger () at /home/vpp_18.01.1/build-data/../src/vppinfra/error.c:84
#4  0x000000000055ba43 in _clib_error (how_to_die=2, function_name=0x0, line_number=0, fmt=0x6a0400 "%s:%d (%s) assertion `%s' fails")
    at /home/vpp_18.01.1/build-data/../src/vppinfra/error.c:143
#5  0x00000000005984bd in mheap_maybe_unlock (v=0x7f91b8001000) at /home/vpp_18.01.1/build-data/../src/vppinfra/mheap.c:80
#6  0x000000000059a6ec in mheap_put (v=0x7f91b8001000, uoffset=0) at /home/vpp_18.01.1/build-data/../src/vppinfra/mheap.c:862
#7  0x00000000005eae35 in clib_mem_free (p=0x7f91b80145e8) at /home/vpp_18.01.1/build-data/../src/vppinfra/mem.h:186
#8  0x00000000005eb15a in vec_resize_allocate_memory (v=0x7f91b80145ec, length_increment=6, data_bytes=57, header_bytes=4, data_align=4)
    at /home/vpp_18.01.1/build-data/../src/vppinfra/vec.c:96
#9  0x000000000056b0d9 in _vec_resize (v=0x7f91b80145ec, length_increment=6, data_bytes=53, header_bytes=0, data_align=0)
    at /home/vpp_18.01.1/build-data/../src/vppinfra/vec.h:142
#10 0x000000000056c3dc in va_format (s=0x7f91b80145ec "vppcom_session_close:2175: [447] vpp handle 0x1", fmt=0x6acaf0 "[%d] vpp handle 0x%llx, sid %d: closing session...", va=0x7f91e29fd4d0)
    at /home/vpp_18.01.1/build-data/../src/vppinfra/format.c:403
#11 0x000000000055b8f2 in _clib_error (how_to_die=4, function_name=0x6ae7c0 <__FUNCTION__.38260> "vppcom_session_close", line_number=2175, fmt=0x6acaf0 "[%d] vpp handle 0x%llx, sid %d: closing session...")
    at /home/vpp_18.01.1/build-data/../src/vppinfra/error.c:127
#12 0x000000000063d3f0 in vppcom_session_close (session_index=6) at /home/vpp_18.01.1/build-data/../src/vcl/vppcom.c:2174
#13 0x0000000000469e9c in spdk_vpp_sock_close (_sock=0x15bb810) at vpp.c:361
#14 0x00000000004aed70 in spdk_sock_close (sock=0x15bb8b8) at sock.c:113
#15 0x000000000047ed83 in spdk_nvmf_tcp_qpair_destroy (tqpair=0x15bb850) at tcp.c:548
#16 0x0000000000484d8c in spdk_nvmf_tcp_close_qpair (qpair=0x15bb850) at tcp.c:2804
#17 0x000000000047d73a in spdk_nvmf_transport_qpair_fini (qpair=0x15bb850) at transport.c:233
#18 0x000000000047bb40 in _spdk_nvmf_qpair_destroy (ctx=0x7f91d403ead0, status=0) at nvmf.c:734

I would really appreciate your help.

Thanks
Ram

_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk

^ permalink raw reply	[flat|nested] 3+ messages in thread