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 <dorgreen1 at gmail.com> 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 <mhall at mhcomputing.net> > > 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.
