From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 433E3A0487 for ; Mon, 1 Jul 2019 09:54:07 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 693582C38; Mon, 1 Jul 2019 09:54:06 +0200 (CEST) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id 350342C23 for ; Mon, 1 Jul 2019 09:54:05 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 10AF5A0613; Mon, 1 Jul 2019 09:54:05 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Mon, 01 Jul 2019 07:54:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: ethdev X-Bugzilla-Version: 19.05 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: ullas-d.bhat@hpe.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 attachments.created 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 301] DPDK driver is crashing for Mellanox-5 NIC card 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://bugs.dpdk.org/show_bug.cgi?id=3D301 Bug ID: 301 Summary: DPDK driver is crashing for Mellanox-5 NIC card Product: DPDK Version: 19.05 Hardware: x86 OS: Linux Status: CONFIRMED Severity: critical Priority: Normal Component: ethdev Assignee: dev@dpdk.org Reporter: ullas-d.bhat@hpe.com Target Milestone: --- Created attachment 44 --> https://bugs.dpdk.org/attachment.cgi?id=3D44&action=3Dedit Back trace for core dump file Hardware Details: Server : ProLiant DL380 Gen10 (Processor - Intel(R) Xeon(R) Gold 6126 CPU @ 2.60GHz) OS Version : Red Hat Enterprise Linux Server release 7.6 (Maipo) Kernel version : 3.10.0-957.el7.x86_64 # lspci |grep -i ether 12:00.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX= -4 Lx] 12:00.1 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX= -4 Lx] # lspci | grep Mellanox | awk '{print $1}' | xargs -i -r mstvpd {} ID: HPE Eth 10/25Gb 2p 640SFP28 Adptr PN: 817751-001 EC: G-5903 SN: ACA91800ML V0: PCIe GEN3 x8 10/25Gb 15W V2: 5918 V4: B883038282D0 V5: 0G VA: HP:V2=3DMFG:V3=3DFW_VER:V4=3DMAC:V5=3DPCAR VB: HPE ConnectX-4 Lx SFP28 # ethtool -i ens1f1 driver: mlx5_core version: 4.6-1.0.1 firmware-version: 14.23.8036 (HP_2420110034) expansion-rom-version: bus-info: 0000:12:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes Problem Description: _________________________ We are running our DPDK app with latest Mellanox NIC card which has 10GBPS = of VLAN capacity, while app running in PMD mode for receiving and transmitting= RTP packets.After sometime our app crashes and generates core dump file. We have attached a file with back trace for core dump. We also see same cra= sh with dpdk-18.11 version. This issue is not seen when run with Intel I350 NIC Card Crash back trace snippet=20 Program terminated with signal 11, Segmentation fault. #0 rte_atomic16_read (v=3D0x6666666666666678) at /home/dpdk-stable-18.08.1/x86_64-native-linuxapp-gcc/include/generic/rte_at= omic.h:258 258 return v->cnt; Missing separate debuginfos, use: debuginfo-install glibc-2.17-260.el7.x86_= 64 libgcc-4.8.5-36.el7.x86_64 libibverbs-46mlnx1-1.46101.x86_64 libmnl-1.0.3-7.el7.x86_64 libnl3-3.2.28-4.el7.x86_64 libpcap-1.5.3-11.el7.x86_64 libstdc++-4.8.5-36.el7.x86_64 numactl-libs-2.0.9-7.el7.x86_64 (gdb) bt #0 rte_atomic16_read (v=3D0x6666666666666678) at /home/dpdk-stable-18.08.1/x86_64-native-linuxapp-gcc/include/generic/rte_at= omic.h:258 #1 rte_mbuf_refcnt_read (m=3D0x6666666666666666) at /home/dpdk-stable-18.08.1/x86_64-native-linuxapp-gcc/include/rte_mbuf.h:820 #2 rte_pktmbuf_prefree_seg (m=3D0x6666666666666666) at /home/dpdk-stable-18.08.1/x86_64-native-linuxapp-gcc/include/rte_mbuf.h:1638 #3 mlx5_tx_complete (txq=3D) at /home/dpdk-stable-18.08.1/drivers/net/mlx5/mlx5_rxtx.h:577 #4 mlx5_tx_burst (dpdk_txq=3D, pkts=3D0x7ffd96e5cce0, pkts_= n=3D1) at /home/dpdk-stable-18.08.1/drivers/net/mlx5/mlx5_rxtx.c:505 #5 0x000000000047d04a in rte_eth_tx_burst (queue_id=3D0, nb_pkts=3D, tx_pkts=3D0x7ffd96e5cce0, port_id=3D) at /usr/local/include/dpdk/rte_ethdev.h:4101 #6 RteSendPacket (m=3D0x7f31ec5eab40, port=3D) at /home/dpdk-stable-18.08.1/examples/ocmp-dpdk/rte-iflib.c:105 #7 PMD () at /home/dpdk-stable-18.08.1/examples/ocmp-dpdk/rte-iflib.c:612 #8 0x00000000004d4e73 in rte_eal_mp_remote_launch (f=3Df@entry=3D0x47a3a0 , arg=3Darg@entry=3D0x0, call_master=3Dcall_master@entry=3DCALL= _MASTER) at /home/dpdk-stable-18.08.1/lib/librte_eal/common/eal_common_launch.c:= 62 #9 0x000000000047e3a4 in RteMainLoop () at /home/dpdk-stable-18.08.1/examples/ocmp-dpdk/rte-iflib.c:630 #10 0x000000000046f95e in main (argc=3D, argv=3D) at /home/dpdk-stable-18.08.1/examples/ocmp-dpdk/dpdk-app.cc:377 Occurrence frequency: ________________ Always --=20 You are receiving this mail because: You are the assignee for the bug.=