From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-la0-f50.google.com (mail-la0-f50.google.com [209.85.215.50]) by dpdk.org (Postfix) with ESMTP id 1B3029ADC for ; Tue, 24 Mar 2015 11:54:15 +0100 (CET) Received: by laae1 with SMTP id e1so24015533laa.2 for ; Tue, 24 Mar 2015 03:54:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VzTUo7D422qqUHqSW2u78uJd/ltGUdPOdDvnYRtQxW4=; b=WzlxOC75RwbYFWvkfE2l2ETvemtQYHj/amWNeYG9b68Qftrt1zyHZJT7wGvTfPRtUH DRE+TBO/bBUpdjxH+hz1ni9RpMDhSgyl4IMJ2+A0ZA55yKlOuK5SRfswIdHvoOCVLuAr PjhAgKabej/SeSvF1NVIDenxWBvRV+8Q4rTZJxH8Um7h/gsB8PsZ94VbYd9TiFeBU6+n crU0f3ZsEuLZ432yLnS/lhaUwMW1pN9CJYNy6q61o87bWIkxTmN//ArsaB9gqcQ1SJq8 3PGRv9DH14e+TpO1Zwae8YW70gOE0InUVQpwcq2nViaV0zeADwYh2xlu9aL/9PwqV1k8 x9oA== MIME-Version: 1.0 X-Received: by 10.112.17.68 with SMTP id m4mr3266323lbd.50.1427194454820; Tue, 24 Mar 2015 03:54:14 -0700 (PDT) Received: by 10.25.41.194 with HTTP; Tue, 24 Mar 2015 03:54:14 -0700 (PDT) In-Reply-To: References: <20150323145958.GA12720@bricha3-MOBL3> <20150323212459.GA5502@mhcomputing.net> Date: Tue, 24 Mar 2015 12:54:14 +0200 Message-ID: From: Dor Green To: Matthew Hall Content-Type: text/plain; charset=UTF-8 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 10:54:15 -0000 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. > > > 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.