From: Ramaraj Pandian <nr.pandian at samsung.com>
To: spdk@lists.01.org
Subject: [SPDK] Spdk NvmeOverTcp with VPP crashes on perf tool exit
Date: Fri, 25 Jan 2019 21:37:41 +0000 [thread overview]
Message-ID: <7aec1668aec1494b97c449ce53b1b155@samsung.com> (raw)
In-Reply-To: CGME20190125213742uscas1p1284488346f5adfedfe9e316988bf1474@uscas1p1.samsung.com
[-- Attachment #1: Type: text/plain, Size: 2705 bytes --]
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
next reply other threads:[~2019-01-25 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 21:37 Ramaraj Pandian [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-26 1:06 [SPDK] Spdk NvmeOverTcp with VPP crashes on perf tool exit Luse, Paul E
2019-01-29 23:13 Ramaraj Pandian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7aec1668aec1494b97c449ce53b1b155@samsung.com \
--to=spdk@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox