From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 88] DPDK service core getting crashed with eventdev scheduler
Date: Fri, 31 Aug 2018 03:55:07 +0000 [thread overview]
Message-ID: <bug-88-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=88
Bug ID: 88
Summary: DPDK service core getting crashed with eventdev
scheduler
Product: DPDK
Version: 18.05
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: critical
Priority: Normal
Component: eventdev
Assignee: dev@dpdk.org
Reporter: tirutaniguru.14391@gmail.com
Target Milestone: ---
While testing performance with eventdev, I am seeing a crash in dpdk service
core. Test scenario is given below
1) DPDK 1805
2) Eventdev 2 ordered Queues(Q0 and Q1) & 2 Ports
2) 2 Workers threads + 1 Service core for running scheduling.
3) 1st worker is getting packet from NIC and enqueueing to Q0(packet processing
is done by both the workers)
4) Packet rate of 5.6Mpps (Pkt size 64 bytes)
Thread 7 "lcore-slave-6" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fdde35fd700 (LWP 9067)]
0x00007fffb3ce1101 in iq_alloc_chunk (sw=0x7ff9e80c3500)
at dpdk/dpdk-18.05/drivers/event/sw/iq_chunk.h:35
35 sw->chunk_list_head = chunk->next;
(gdb) bt
#0 0x00007fffb3ce1101 in iq_alloc_chunk (sw=0x7ff9e80c3500)
at dpdk/dpdk-18.05/drivers/event/sw/iq_chunk.h:35
#1 iq_enqueue (ev=0x7ff9e80d3800, iq=0x7ff9e85119a0, sw=0x7ff9e80c3500)
at dpdk/dpdk-18.05/drivers/event/sw/iq_chunk.h:79
#2 __pull_port_lb (allow_reorder=1, port_id=0, sw=0x7ff9e80c3500)
at dpdk/dpdk-18.05/drivers/event/sw/sw_evdev_scheduler.c:435
#3 sw_schedule_pull_port_lb (sw=0x7ff9e80c3500, port_id=0)
at dpdk/dpdk-18.05/drivers/event/sw/sw_evdev_scheduler.c:452
#4 0x00007fffb3ce2824 in sw_event_schedule (dev=0x7fffb490b6c0
<rte_event_devices>)
at dpdk/dpdk-18.05/drivers/event/sw/sw_evdev_scheduler.c:524
#5 0x00007fffb3cdbb1a in sw_sched_service_func (args=0x7fffb490b6c0
<rte_event_devices>)
at dpdk/dpdk-18.05/drivers/event/sw/sw_evdev.c:795
#6 0x00007fffb35e6326 in rte_service_runner_do_callback (s=0x7ff9e93fe000,
cs=0x7ff9e93dad40, service_idx=0)
at dpdk/dpdk-18.05/lib/librte_eal/common/rte_service.c:345
#7 0x00007fffb35e643f in service_run (i=0, cs=0x7ff9e93dad40, service_mask=1)
at dpdk/dpdk-18.05/lib/librte_eal/common/rte_service.c:372
#8 0x00007fffb35e6599 in rte_service_runner_func (arg=0x0)
at dpdk/dpdk-18.05/lib/librte_eal/common/rte_service.c:422
#9 0x00007fffb35b872a in eal_thread_loop (arg=0x0)
at dpdk/dpdk-18.05/lib/librte_eal/linuxapp/eal/eal_thread.c:153
#10 0x00007ffff614b6ba in start_thread (arg=0x7fdde35fd700) at
pthread_create.c:333
#11 0x00007ffff5c7d41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
Is this a known issue at high load or am I doing something wrong?
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-08-31 3:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-88-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).