From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dor Green Subject: Re: Packet data out of bounds after rte_eth_rx_burst Date: Tue, 24 Mar 2015 11:55:33 +0200 Message-ID: References: <20150323145958.GA12720@bricha3-MOBL3> <20150323212459.GA5502@mhcomputing.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: dev-VfR2kkLFssw@public.gmane.org To: Matthew Hall Return-path: In-Reply-To: <20150323212459.GA5502-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 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. 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.