From: "Posadas, Emerson" <emerson.posadas@intel.com>
To: Victor Detoni <victordetoni@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] port 0 is not present on the board
Date: Tue, 1 Mar 2016 16:43:19 +0000 [thread overview]
Message-ID: <DC37A2D0D1A435489038224DF610BC991BE1B1C5@FMSMSX106.amr.corp.intel.com> (raw)
In-Reply-To: <CANpwN=vTq6o3Hn_Gq+YuEY9BFh8mP-qKjmmrwqg+DQ24HtnsZw@mail.gmail.com>
Hi Victor
Yes, the devices are already binded to the DPDK driver:
I have just found that my devices are not supported by DPDK, this is probably the reason l3fwd is failing.
Thanks anyways
EP
From: Victor Detoni [mailto:victordetoni@gmail.com]
Sent: Tuesday, March 1, 2016 10:31 AM
To: Posadas, Emerson <emerson.posadas@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] port 0 is not present on the board
Did you try to bind nics through
/tools/dpdk_nic_bind.py script?
Em terça-feira, 1 de março de 2016, Posadas, Emerson <emerson.posadas@intel.com> escreveu:
I see that this issue was raised a couple of months ago on this thread (http://dpdk.org/ml/archives/dev/2014-December/010661.html)
But seems that the fix on that thread does not work on my DPDK setup using l3fwd application. The full output I'm getting looks as follows.
# ./examples/l3fwd/build/l3fwd -c 0x3 -n 2 -- -p 0x3 --config="(0,0,0),(1,0,1)"
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: Detected lcore 8 as core 8 on socket 0
EAL: Detected lcore 9 as core 9 on socket 0
EAL: Detected lcore 10 as core 10 on socket 0
EAL: Detected lcore 11 as core 11 on socket 0
EAL: Detected lcore 12 as core 12 on socket 0
EAL: Detected lcore 13 as core 13 on socket 0
EAL: Detected lcore 14 as core 14 on socket 0
EAL: Detected lcore 15 as core 15 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 16 lcore(s)
EAL: VFIO modules not all loaded, skip VFIO support...
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f2880400000 (size = 0x200000)
EAL: Ask a virtual area of 0xc400000 bytes
EAL: Virtual area found at 0x7f2873e00000 (size = 0xc400000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f2873000000 (size = 0xc00000)
EAL: Ask a virtual area of 0x3400000 bytes
EAL: Virtual area found at 0x7f286fa00000 (size = 0x3400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f286f400000 (size = 0x400000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f286f000000 (size = 0x200000)
EAL: Ask a virtual area of 0x1400000 bytes
EAL: Virtual area found at 0x7f286da00000 (size = 0x1400000)
EAL: Ask a virtual area of 0xa800000 bytes
EAL: Virtual area found at 0x7f2863000000 (size = 0xa800000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f2862c00000 (size = 0x200000)
EAL: Ask a virtual area of 0xd6800000 bytes
EAL: Ask a virtual area of 0xd6800000 bytes
EAL: Virtual area found at 0x7f278c200000 (size = 0xd6800000)
EAL: Ask a virtual area of 0x2000000 bytes
EAL: Virtual area found at 0x7f278a000000 (size = 0x2000000)
EAL: Ask a virtual area of 0x1800000 bytes
EAL: Virtual area found at 0x7f2788600000 (size = 0x1800000)
EAL: Ask a virtual area of 0x2800000 bytes
EAL: Virtual area found at 0x7f2785c00000 (size = 0x2800000)
EAL: Ask a virtual area of 0x1000000 bytes
EAL: Virtual area found at 0x7f2784a00000 (size = 0x1000000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f2783c00000 (size = 0xc00000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f2783600000 (size = 0x400000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f2782800000 (size = 0xc00000)
EAL: Ask a virtual area of 0x1800000 bytes
EAL: Virtual area found at 0x7f2780e00000 (size = 0x1800000)
EAL: Ask a virtual area of 0x1000000 bytes
EAL: Virtual area found at 0x7f277fc00000 (size = 0x1000000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f277f600000 (size = 0x400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f277f000000 (size = 0x400000)
EAL: Ask a virtual area of 0x800000 bytes
EAL: Virtual area found at 0x7f277e600000 (size = 0x800000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f277e000000 (size = 0x400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f277da00000 (size = 0x400000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f277d600000 (size = 0x200000)
EAL: Requesting 2048 pages of size 2MB from socket 0
EAL: TSC frequency is ~1700004 KHz
EAL: Master lcore 0 is ready (tid=81d1b8c0;cpuset=[0])
EAL: lcore 1 is ready (tid=7cde7700;cpuset=[1])
EAL: PCI device 0000:01:00.0 on NUMA socket -1
EAL: probe driver: 8086:1572 rte_i40e_pmd
EAL: Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:01:00.1 on NUMA socket -1
EAL: probe driver: 8086:1572 rte_i40e_pmd
EAL: Not managed by a supported kernel driver, skipped
port 0 is not present on the board
EAL: Error - exiting with code: 1
Cause: check_port_config failed
root@host:~
My DPDK version is 2.2.0. Any suggestion or idea to fix the issue would be accepted.
EP
next prev parent reply other threads:[~2016-03-01 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 16:11 Posadas, Emerson
2016-03-01 16:31 ` Victor Detoni
2016-03-01 16:43 ` Posadas, Emerson [this message]
2016-03-01 17:15 ` De Lara Guarch, Pablo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DC37A2D0D1A435489038224DF610BC991BE1B1C5@FMSMSX106.amr.corp.intel.com \
--to=emerson.posadas@intel.com \
--cc=dev@dpdk.org \
--cc=victordetoni@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).