From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla@dpdk.org
Subject: [Bug 88] DPDK service core getting crashed with eventdev
	scheduler
Date: Fri, 31 Aug 2018 03:55:07 +0000
Message-ID: <bug-88-3@http.bugs.dpdk.org/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
To: dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

https://bugs.dpdk.org/show_bug.cgi?id=3D88

            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 proces=
sing
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=3D0x7ff9e80c3500)

at dpdk/dpdk-18.05/drivers/event/sw/iq_chunk.h:35

35 sw->chunk_list_head =3D chunk->next;

(gdb) bt

#0 0x00007fffb3ce1101 in iq_alloc_chunk (sw=3D0x7ff9e80c3500)

at dpdk/dpdk-18.05/drivers/event/sw/iq_chunk.h:35

#1 iq_enqueue (ev=3D0x7ff9e80d3800, iq=3D0x7ff9e85119a0, sw=3D0x7ff9e80c350=
0)

at dpdk/dpdk-18.05/drivers/event/sw/iq_chunk.h:79

#2 __pull_port_lb (allow_reorder=3D1, port_id=3D0, sw=3D0x7ff9e80c3500)

at dpdk/dpdk-18.05/drivers/event/sw/sw_evdev_scheduler.c:435

#3 sw_schedule_pull_port_lb (sw=3D0x7ff9e80c3500, port_id=3D0)

at dpdk/dpdk-18.05/drivers/event/sw/sw_evdev_scheduler.c:452

#4 0x00007fffb3ce2824 in sw_event_schedule (dev=3D0x7fffb490b6c0
<rte_event_devices>)

at dpdk/dpdk-18.05/drivers/event/sw/sw_evdev_scheduler.c:524

#5 0x00007fffb3cdbb1a in sw_sched_service_func (args=3D0x7fffb490b6c0
<rte_event_devices>)

at dpdk/dpdk-18.05/drivers/event/sw/sw_evdev.c:795

#6 0x00007fffb35e6326 in rte_service_runner_do_callback (s=3D0x7ff9e93fe000,
cs=3D0x7ff9e93dad40, service_idx=3D0)

at dpdk/dpdk-18.05/lib/librte_eal/common/rte_service.c:345

#7 0x00007fffb35e643f in service_run (i=3D0, cs=3D0x7ff9e93dad40, service_m=
ask=3D1)

at dpdk/dpdk-18.05/lib/librte_eal/common/rte_service.c:372

#8 0x00007fffb35e6599 in rte_service_runner_func (arg=3D0x0)

at dpdk/dpdk-18.05/lib/librte_eal/common/rte_service.c:422

#9 0x00007fffb35b872a in eal_thread_loop (arg=3D0x0)

at dpdk/dpdk-18.05/lib/librte_eal/linuxapp/eal/eal_thread.c:153

#10 0x00007ffff614b6ba in start_thread (arg=3D0x7fdde35fd700) 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?

--=20
You are receiving this mail because:
You are the assignee for the bug.=