From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.31.42]) by dpdk.org (Postfix) with ESMTP id BA1205A15 for ; Tue, 20 Jan 2015 11:39:04 +0100 (CET) Received: from [80.153.53.149] (helo=nb-mweiser.local) by smtprelay04.ispgateway.de with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from ) id 1YDWD9-0003Vw-Tv for dev@dpdk.org; Tue, 20 Jan 2015 11:39:04 +0100 Message-ID: <54BE3047.9060909@allegro-packets.com> Date: Tue, 20 Jan 2015 11:39:03 +0100 From: Martin Weiser User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: dev@dpdk.org References: <54BCDBF1.8020909@allegro-packets.com> In-Reply-To: <54BCDBF1.8020909@allegro-packets.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Df-Sender: bWFydGluLndlaXNlckBhbGxlZ3JvLXBhY2tldHMuY29t Subject: Re: [dpdk-dev] Segmentation fault in ixgbe_rxtx_vec.c:444 with 1.8.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, 20 Jan 2015 10:39:04 -0000 Hi again, I did some further testing and it seems like this issue is linked to jumbo frames. I think a similar issue has already been reported by Prashant Upadhyaya with the subject 'Packet Rx issue with DPDK1.8'. In our application we use the following rxmode port configuration: =2Emq_mode =3D ETH_MQ_RX_RSS, =2Esplit_hdr_size =3D 0, =2Eheader_split =3D 0, =2Ehw_ip_checksum =3D 1, =2Ehw_vlan_filter =3D 0, =2Ejumbo_frame =3D 1, =2Ehw_strip_crc =3D 1, =2Emax_rx_pkt_len =3D 9000, and the mbuf size is calculated like the following: (2048 + sizeof(struct rte_mbuf) + RTE_PKTMBUF_HEADROOM) This works fine with DPDK 1.7 and jumbo frames are split into buffer chains and can be forwarded on another port without a problem. With DPDK 1.8 and the default configuration (CONFIG_RTE_IXGBE_INC_VECTOR enabled) the application sometimes crashes like described in my first mail and sometimes packet receiving stops with subsequently arriving packets counted as rx errors. When CONFIG_RTE_IXGBE_INC_VECTOR is disabled the packet processing also comes to a halt as soon as jumbo frames arrive with a the slightly different effect that now rte_eth_tx_burst refuses to send any previously received packets. Is there anything special to consider regarding jumbo frames when moving from DPDK 1.7 to 1.8 that we might have missed? Martin On 19.01.15 11:26, Martin Weiser wrote: > Hi everybody, > > we quite recently updated one of our applications to DPDK 1.8.0 and are= > now seeing a segmentation fault in ixgbe_rxtx_vec.c:444 after a few min= utes. > I just did some quick debugging and I only have a very limited > understanding of the code in question but it seems that the 'continue' > in line 445 without increasing 'buf_idx' might cause the problem. In on= e > debugging session when the crash occurred the value of 'buf_idx' was 2 > and the value of 'pkt_idx' was 8965. > Any help with this issue would be greatly appreciated. If you need any > further information just let me know. > > Martin > >