From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by dpdk.org (Postfix, from userid 33) id 302862C55; Fri, 31 Aug 2018 05:55:07 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Fri, 31 Aug 2018 03:55:07 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: eventdev X-Bugzilla-Version: 18.05 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: tirutaniguru.14391@gmail.com X-Bugzilla-Status: CONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 88] DPDK service core getting crashed with eventdev scheduler X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Aug 2018 03:55:07 -0000 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 ) at dpdk/dpdk-18.05/drivers/event/sw/sw_evdev_scheduler.c:524 #5 0x00007fffb3cdbb1a in sw_sched_service_func (args=3D0x7fffb490b6c0 ) 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.=