From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 0C93F9AC2 for ; Tue, 24 Mar 2015 14:18:41 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP; 24 Mar 2015 06:17:19 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,458,1422950400"; d="scan'208";a="696929199" Received: from bricha3-mobl3.ger.corp.intel.com ([10.243.20.28]) by fmsmga002.fm.intel.com with SMTP; 24 Mar 2015 06:17:16 -0700 Received: by (sSMTP sendmail emulation); Tue, 24 Mar 2015 13:17:16 +0025 Date: Tue, 24 Mar 2015 13:17:16 +0000 From: Bruce Richardson To: Dor Green Message-ID: <20150324131715.GA11384@bricha3-MOBL3> References: <20150323145958.GA12720@bricha3-MOBL3> <20150323212459.GA5502@mhcomputing.net> 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] Packet data out of bounds after rte_eth_rx_burst 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, 24 Mar 2015 13:18:42 -0000 On Tue, Mar 24, 2015 at 12:54:14PM +0200, Dor Green wrote: > I've managed to fix it so 1.8 works, and the segmentation fault still occurs. > > On Tue, Mar 24, 2015 at 11:55 AM, Dor Green wrote: > > I tried 1.8, but that fails to initialize my device and fails at the pci probe: > > "Cause: Requested device 0000:04:00.1 cannot be used" > > Can't even compile 2.0rc2 atm, getting: > > "/usr/lib/gcc/x86_64-linux-gnu/4.6/include/emmintrin.h:701:1: note: > > expected '__m128i' but argument is of type 'int'" > > For reasons I don't understand. > > > > As for the example apps (in 1.7), I can run them properly but I don't > > think any of them do the same processing as I do. Note that mine does > > work with most packets. > > > > Couple of further questions: 1. What config options are being used to configure the port and what is the output printed at port initialization time? This is needed to let us track down what specific RX path is being used inside the ixgbe driver 2. What type of packets specifically cause problems? Is it reproducible with one particular packet, or packet type? Are you sending in jumbo-frames? Regards, /Bruce > > On Mon, Mar 23, 2015 at 11:24 PM, Matthew Hall wrote: > >> On Mon, Mar 23, 2015 at 05:19:00PM +0200, Dor Green wrote: > >>> I changed it to free and it still happens. Note that the segmentation fault > >>> happens before that anyway. > >>> > >>> I am using 1.7.1 at the moment. I can try using a newer version. > >> > >> I'm using 1.7.X in my open-source DPDK-based app and it works, but I have an > >> IGB 1-gigabit NIC though, and how RX / TX work are quite driver specific of > >> course. > >> > >> I suspect there's some issue with how things are working in your IXGBE NIC > >> driver / setup. Do the same failures occur inside of the DPDK's own sample > >> apps? > >> > >> Matthew.