From: Dave Boutcher <dboutcher@ocient.com>
To: "pxv3620@rit.edu" <pxv3620@rit.edu>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] port 0 not present on board error
Date: Fri, 8 Dec 2017 04:18:54 +0000 [thread overview]
Message-ID: <BF625ED8-F071-4214-B5BF-BC23DCE102C4@ocient.com> (raw)
In-Reply-To: <CANp7S23QbjVD3zpj6M+Waifw+p6xxjMur7Jxgyz3z99pLcsF4A@mail.gmail.com>
Are you running as root (sudo)?
Dave B
On Dec 7, 2017, at 10:01 PM, Pragash Vijayaragavan <pxv3620@rit.edu<mailto:pxv3620@rit.edu>> wrote:
Hi Guys,
I am trying to run the l3fwd dpdk app on my machine.
I am getting the following error, can someone help me, Thanks.
pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ ./l3fwd -l 0-4
--no-huge -- -p 0x1
EAL: Detected 20 lcore(s)
EAL: Probing VFIO support...
EAL: Started without hugepages support, physical addresses not available
EAL: PCI device 0000:02:00.0 on NUMA socket 0
EAL: probe driver: 8086:1583 net_i40e
EAL: Requested device 0000:02:00.0 cannot be used
EAL: PCI device 0000:02:00.1 on NUMA socket 0
EAL: probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL: probe driver: 8086:1583 net_i40e
EAL: Requested device 0000:04:00.0 cannot be used
EAL: PCI device 0000:04:00.1 on NUMA socket 0
EAL: probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:08:00.0 on NUMA socket 0
EAL: probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:08:00.1 on NUMA socket 0
EAL: probe driver: 8086:1521 net_e1000_igb
L3FWD: LPM or EM none selected, default LPM on
port 0 is not present on the board
EAL: Error - exiting with code: 1
Cause: check_port_config failed
Thanks,
Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3620@rit.edu<mailto:pxv3620@rit.edu>
ph : 585 764 4662
next prev parent reply other threads:[~2017-12-08 4:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 4:01 Pragash Vijayaragavan
2017-12-08 4:18 ` Dave Boutcher [this message]
2017-12-08 4:21 ` Pragash Vijayaragavan
2017-12-08 12:11 Hristo.Trifonov
2017-12-08 20:22 ` Pragash Vijayaragavan
2017-12-11 11:21 Hristo.Trifonov
2017-12-11 21:24 ` Pragash Vijayaragavan
2017-12-12 6:17 ` Pragash Vijayaragavan
2017-12-12 7:17 ` Stephen Hemminger
2017-12-12 10:54 Hristo.Trifonov
2017-12-12 12:21 ` Pragash Vijayaragavan
2017-12-12 12:47 Hristo.Trifonov
2017-12-12 13:33 ` Pragash Vijayaragavan
2017-12-12 14:02 Hristo.Trifonov
2017-12-12 14:13 ` Pragash Vijayaragavan
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=BF625ED8-F071-4214-B5BF-BC23DCE102C4@ocient.com \
--to=dboutcher@ocient.com \
--cc=pxv3620@rit.edu \
--cc=users@dpdk.org \
/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).