Re: [dpdk-dev] Testpmd returns error.

[Bruce Richardson <bruce.richardson@intel.com>]

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 <danny.zhou@intel.com>
> 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.?

Regards,
/Bruce