From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 728765A34 for ; Tue, 10 Nov 2015 11:54:22 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 10 Nov 2015 02:54:19 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,270,1444719600"; d="scan'208";a="847442280" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.208.62]) by fmsmga002.fm.intel.com with SMTP; 10 Nov 2015 02:54:18 -0800 Received: by (sSMTP sendmail emulation); Tue, 10 Nov 2015 10:54:17 +0025 Date: Tue, 10 Nov 2015 10:54:17 +0000 From: Bruce Richardson To: Ariel Rodriguez Message-ID: <20151110105417.GD29836@bricha3-MOBL3> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] URGENT please help. Issue on ixgbe_tx_free_bufs version 2.0.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2015 10:54:22 -0000 On Tue, Nov 10, 2015 at 01:35:21AM -0300, Ariel Rodriguez wrote: > Dear dpdk experts. > > Im having a recurrent segmentation fault under the > function ixgbe_tx_free_bufs (ixgbe_rxtx.c:150) (i enable -g3 -O0). > > Surfing the core dump i find out this: > > txep = &(txq->sw_ring[txq->tx_next_dd - (txq->tx_rs_thresh - 1)]); > > txq->tx_next_dd = 31 > txq->txq->tx_rs_thresh=32 > > Obviosly txep points out to the first element but > > *(txep).mbuf == INVALID MBUF ADDRESS > > The same applies to > > *(txep+1).mbuf ; *(txep +2).mbuf;*(txep+3).mbuf > > from *(txep+4) .mbuf to *(txep+31).mbuf seems to be valid because im able > to derefence the mbuf's > > > Note: > > I disable CONFIG_RTE_IXGBE_INC_VECTOR because i gets similiar behavior , I > thought the problem would disappear disabling that feature. > > > the program always runs well up to 4 or 5 hours and then crash ... always > in the same line. > > this is the backtrace of the program: > > #0 0x0000000000677a64 in rte_atomic16_read (v=0x47dc14c18b14) at > /opt/dpdk-2.0.0/x86_64-native-linuxapp-gcc/include/generic/rte_atomic.h:151 > #1 0x0000000000677c1d in rte_mbuf_refcnt_read (m=0x47dc14c18b00) at > /opt/dpdk-2.0.0/x86_64-native-linuxapp-gcc/include/rte_mbuf.h:411 > #2 0x000000000067a13c in __rte_pktmbuf_prefree_seg (m=0x47dc14c18b00) at > /opt/dpdk-2.0.0/x86_64-native-linuxapp-gcc/include/rte_mbuf.h:778 > #3 rte_pktmbuf_free_seg (m=0x47dc14c18b00) at > /opt/dpdk-2.0.0/x86_64-native-linuxapp-gcc/include/rte_mbuf.h:810 > #4 ixgbe_tx_free_bufs (txq=0x7ffb40ae52c0) at > /opt/dpdk-2.0.0/lib/librte_pmd_ixgbe/ixgbe_rxtx.c:150 > #5 tx_xmit_pkts (tx_queue=0x7ffb40ae52c0, tx_pkts=0x64534770 , > nb_pkts=32) at /opt/dpdk-2.0.0/lib/librte_pmd_ixgbe/ixgbe_rxtx.c:256 > #6 0x000000000067c6f3 in ixgbe_xmit_pkts_simple (tx_queue=0x7ffb40ae52c0, > tx_pkts=0x64534570 , nb_pkts=80) at > /opt/dpdk-2.0.0/lib/librte_pmd_ixgbe/ixgbe_rxtx.c:343 > #7 0x00000000004ec93d in rte_eth_tx_burst (port_id=1 '\001', queue_id=0, > tx_pkts=0x64534570 , nb_pkts=144) at > /opt/dpdk-2.0.0/x86_64-native-linuxapp-gcc/include/rte_ethdev.h:2572 > Hi, I'd like a bit more information to help debug your problem: * what application are you running when you see this crash? If it's an app of your own making, can you reproduce the crash using one of the standard DPDK apps, or example apps, e.g. testpmd, l2fwd, etc. * Can you also try to verify if the crash occurs with the latest DPDK code available in git from dpdk.org? Regards, /Bruce