From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 5E38C4A6E for ; Wed, 12 Nov 2014 15:02:33 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga102.fm.intel.com with ESMTP; 12 Nov 2014 06:12:15 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,862,1389772800"; d="scan'208";a="415406842" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.220.93]) by FMSMGA003.fm.intel.com with SMTP; 12 Nov 2014 06:03:16 -0800 Received: by (sSMTP sendmail emulation); Wed, 12 Nov 2014 14:12:12 +0025 Date: Wed, 12 Nov 2014 14:12:12 +0000 From: Bruce Richardson To: Manoj Viswanath Message-ID: <20141112141211.GA6688@bricha3-MOBL3> References: <20141105101246.GA9856@bricha3-MOBL3> <20141107153053.GA10376@bricha3-MOBL3> <20141110105802.GA7036@bricha3-MOBL3> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] Ports not detected by IGB_UIO in DPDK 1.7.1 in QEMU_KVM environment 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: Wed, 12 Nov 2014 14:02:34 -0000 On Tue, Nov 11, 2014 at 07:18:32PM +0530, Manoj Viswanath wrote: > Bruce, > > Thanks for the input. > Sure, will figure out the offending file behind this error and update this > thread. > > Meanwhile, wanted to share one more observation regarding this issue: > The "file descriptor error" is NOT SEEN with DPDK 1.7.0 (dpdk-1.7.0.tar.gz > ) when explicitly > binding NICs to IGB_UIO using the .py script. > > The issue is only seen when using DPDK 1.7.1 ( dpdk-1.7.1.tar.gz > ). I hope the > version i am using is the last official tag in the 1.7.x tree. > Given that it's narrowed down to a change between 1.7.0 and 1.7.1 would it also be possible for you to use git bisect to track down the commit that introduces the error? /Bruce