From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id AEB225A8C for ; Mon, 23 Feb 2015 12:12:21 +0100 (CET) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga101.fm.intel.com with ESMTP; 23 Feb 2015 03:12:20 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.09,630,1418112000"; d="scan'208";a="531376851" Received: from omishael-mobl.ger.corp.intel.com ([10.252.18.211]) by orsmga003.jf.intel.com with SMTP; 23 Feb 2015 03:03:19 -0800 Received: by (sSMTP sendmail emulation); Mon, 23 Feb 2015 11:12:17 +0025 Date: Mon, 23 Feb 2015 11:12:17 +0000 From: Bruce Richardson To: Tetsuya Mukawa Message-ID: <20150223111216.GA8504@bricha3-MOBL3> References: <54E9695A.5010509@igel.co.jp> <20150222204645.GA7672@bricha3-MOBL3> <54EA9189.6050203@igel.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54EA9189.6050203@igel.co.jp> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Testpmd returns error. 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: Mon, 23 Feb 2015 11:12:22 -0000 On Mon, Feb 23, 2015 at 11:33:45AM +0900, Tetsuya Mukawa wrote: > On 2015/02/23 5:46, Bruce Richardson wrote: > > On Sun, Feb 22, 2015 at 02:30:02PM +0900, Tetsuya Mukawa wrote: > >> Hi, > >> > >> In my environment, testpmd in latest master branch returns error like below. > >> > >> $ sudo ./tools/dpdk_nic_bind.py -b igb_uio 0000:02:00.0 > >> $ sudo ./x86_64-native-linuxapp-gcc/app/testpmd -c f -n 1 -- -i > >> EAL: Detected lcore 0 as core 0 on socket 0 > >> EAL: Detected lcore 1 as core 1 on socket 0 > >> EAL: Detected lcore 2 as core 2 on socket 0 > >> EAL: Detected lcore 3 as core 3 on socket 0 > >> EAL: Detected lcore 4 as core 4 on socket 0 > >> EAL: Detected lcore 5 as core 5 on socket 0 > >> EAL: Detected lcore 6 as core 6 on socket 0 > >> EAL: Detected lcore 7 as core 7 on socket 0 > >> EAL: Support maximum 128 logical core(s) by configuration. > >> EAL: Detected 8 lcore(s) > >> EAL: VFIO modules not all loaded, skip VFIO support... > >> EAL: Setting up memory... > >> EAL: Ask a virtual area of 0x280000000 bytes > >> EAL: Virtual area found at 0x7ffd40000000 (size = 0x280000000) > >> EAL: Requesting 10 pages of size 1024MB from socket 0 > >> EAL: TSC frequency is ~3991450 KHz > >> EAL: Master core 0 is ready (tid=f7fd6840) > >> PMD: ENICPMD trace: rte_enic_pmd_init > >> EAL: Core 3 is ready (tid=f58e0700) > >> EAL: Core 2 is ready (tid=f60e1700) > >> EAL: Core 1 is ready (tid=f68e2700) > >> EAL: PCI device 0000:02:00.0 on NUMA socket -1 > >> EAL: probe driver: 8086:10b9 rte_em_pmd > >> EAL: PCI memory mapped at 0x7fffc0000000 > >> EAL: pci_map_resource(): cannot mmap(23, 0x7fffc0020000, 0x20000, > >> 0x1000): Invalid argument (0xffffffffffffffff) > >> EAL: Error - exiting with code: 1 > >> Cause: Requested device 0000:02:00.0 cannot be used > >> > >> > >> I've run git-bisect, and it seems following commit cause this error. > >> > >> commit 4a499c64959074ba6fa6a5a2b3a2a6aa10627fa1 > >> Author: Danny Zhou > >> Date: Fri Feb 20 16:59:15 2015 +0000 > >> > >> eal/linux: enable uio_pci_generic support > >> > >> Someone, could you please check it? > >> > >> Thanks, > >> Tetsuya > >> > > Hi Tetsuya, > > > > trying to reproduce the problem here, with no success so far with a mix of 1G > > and 10G ports. Is there anything special about your environment that might > > especially trigger this issue? Is it a VM or running on the host machine etc.? > > Hi Bruce, > > I appreciate for your testing. > > I've tried it on an another system, and I couldn't reproduce it. > Could you please see below? > > - The system I can reproduce the issue > OS: Ubuntu14.04 > Kernel: Linux eris 3.13.0-30-generic > CPU: AMD FX(tm)-8350 Eight-Core Processor > NIC: Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet > Controller (Copper) (rev 06) > > - The system I cannot reproduce the issue > OS: ubuntu14.04 > Kernel: Linux ubuntu-igel 3.13.0-30-generic > Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz > NIC: Ethernet controller: Intel Corporation I350 Gigabit Network > Connection (rev 01) > > I will check it more in next testing phase. > Until then, I will use the system I cannot reproduce the issue. > > Regards, > Tetsuya > > > Regards, > > /Bruce > > > Thanks Tetsuya, Declan has managed to find a board here that can reproduce the issue so we are now investigating possible solutions. /Bruce