From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: dpdk-2.0.0: crash in ixgbe_recv_scattered_pkts_vec->_recv_raw_pkts_vec->desc_to_olflags_v Date: Wed, 1 Jul 2015 12:11:49 +0100 Message-ID: <20150701111149.GB2480@bricha3-MOBL3> References: <5700614.EXxNvnLqa2@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org To: Gopakumar Choorakkot Edakkunni Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 556BC6A80 for ; Wed, 1 Jul 2015 13:12:15 +0200 (CEST) Content-Disposition: inline In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Tue, Jun 30, 2015 at 05:50:14PM -0700, Gopakumar Choorakkot Edakkunni wrote: > So update on this. Summary is that its purely my fault, apologies for > prematurely suspecting the wrong areas. Details below > > 1. So my AWS box had an eth0 interface without DPDK, I enabled dpdk > AND created a KNI interface also AND named the KNI interface to be > eth0 > > 2. So Ubuntu started its dhcpclient on that interface, but my app > doesnt really do anything do read the dhcp (renews) from the KNI and > send it out the physical port and vice versa .. The kni was just > sitting there not doing much of Rx/Tx > > 3. Now my l2fwd-equivalent code started working fine, after a few > minutes, the dhcp client on ubuntu gave up attempting dhcp renew (eth0 > already had an IP) and attempted to take off the IP from eth0 > > 4. At this point the standard KNI examples in dpdk which has callbacks > registered, ended up being invoked - and the examples have a > port_stop() and a port_start() in them - and exactly at this point my > app crashed > > So my bad! I just no-oped the callbacks for now and changed AWS eht0 > from dhcp to static IP and this are fine now ! My system has been up > for long with no issues. > > Thanks again Thomas and Bruce for the quick response and suggestions > No problem. Thanks for letting us know that this was resolved. Regards, /Bruce