From: AndyChen <andychenzy@gmail.com>
To: Jayakumar Satri <JS00123073@techmahindra.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK.L.1.4.1-4: error in binding of network ports to igb_uio driver
Date: Tue, 10 Sep 2013 13:55:30 +0800 [thread overview]
Message-ID: <CAHhF9PEey=wG-rEKrSGtoZfQTtgX7Yfmu8joXKP3DAQcDSMVzw@mail.gmail.com> (raw)
In-Reply-To: <AD44A5B3E441204283C1A3CDFE6D49CC0289ECFC@SINBNGEX001.TechMahindra.com>
down the port 0000:0b:00.1 from linux igb, then bind it to igb_uio
On Tue, Sep 10, 2013 at 12:34 PM, Jayakumar Satri <
JS00123073@techmahindra.com> wrote:
> Hi,
>
> In the DPDK getting started guide, the following is mentioned.
>
> "By default, Intel(r) DPDK applications automatically unbind all support
> network ports from the kernel driver in use and rebind those ports to
> the igb_uio driver."
>
>
>
> I am using DPDK.L.1.4.1-4. I run the l2fwd application from the
> examples. I get the following error. Request your guidance in overcoming
> this.
>
> EAL: PCI device 0000:0b:00.1 on NUMA socket 0
>
> EAL: probe driver: 8086:10fb rte_ixgbe_pmd
>
> EAL: 0000:0b:00.1 not managed by UIO driver, skipping
>
> EAL: Error - exiting with code: 1
>
>
>
> Also, when I used the pci_undind tool, I get the message - Routing table
> indicates that interface 0000:0b:00.1 is active. Not modifying
>
>
>
> Regards,
>
> Jaya Kumar.
>
>
>
> ============================================================================================================================
> Disclaimer: This message and the information contained herein is
> proprietary and confidential and subject to the
> Tech Mahindra policy statement, you may review the policy at <a href="
> http://www.techmahindra.com/Disclaimer.html">
> http://www.techmahindra.com/Disclaimer.html</a>
> externally and <a href="http://tim.techmahindra.com/tim/disclaimer.html">
> http://tim.techmahindra.com/tim/disclaimer.html</a> internally within
> Tech Mahindra.
>
> ============================================================================================================================
>
prev parent reply other threads:[~2013-09-10 5:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 4:34 Jayakumar Satri
2013-09-10 5:55 ` AndyChen [this message]
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='CAHhF9PEey=wG-rEKrSGtoZfQTtgX7Yfmu8joXKP3DAQcDSMVzw@mail.gmail.com' \
--to=andychenzy@gmail.com \
--cc=JS00123073@techmahindra.com \
--cc=dev@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).