From: Tomasz K <tomasz.kasowicz@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev <dev@dpdk.org>, B Gopikrishna <b.gopikrishna@tcs.com>
Subject: Re: [dpdk-dev] rte_eth_dev_configure fails on VM with e1000 drivers
Date: Fri, 18 Apr 2014 14:37:00 +0200 [thread overview]
Message-ID: <CAHJKsGzfy9bRAdxjVf6YJP9H7s3=64PFcPoVxAfmP7no0CkWBA@mail.gmail.com> (raw)
In-Reply-To: <8080666.eQLb0Bv3Fe@xps13>
Hi Gopi
I recently run into the same problem when using 82576 with igb_uio on VM.
The problem is not e1000 or igb. The problem is with the other network
device managed by virtio-pci driver
Notice that when application polls for ETH devices it prints out
EAL: probe driver: 1af4:1000 rte_virtio_pmd
EAL: 0000:00:03.0 not managed by UIO driver, skipping
So even though this NIC is not managed by igb_uio driver the app prints
that driver used for it is rte_virtio_pmd.
After setting up ETH devices app tries to set up tx/rx queues and it fails
on port 0 (which is virtio)
You can try and run the application with -p 0x6 instead of 0x3. This should
mask out port0 from configuration
Thanks
Tomasz
2014-04-18 14:31 GMT+02:00 Thomas Monjalon <thomas.monjalon@6wind.com>:
> Hi,
>
> 2014-04-18 17:39, B Gopikrishna:
> > when I run the l3fwd application with the below command line, I am
> observing
> > the error "Cannot configure device: err=-22, port=0". The complete log is
> > posted below.
>
> Could you try to reproduce it with the git HEAD version?
> It may be fixed by this commit:
> d73d8f3 timer: fix TSC frequency by not reading /proc/cpuinfo
>
> --
> Thomas
>
next prev parent reply other threads:[~2014-04-18 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 12:09 B Gopikrishna
2014-04-18 12:31 ` Thomas Monjalon
2014-04-18 12:37 ` Tomasz K [this message]
2014-04-29 9:28 ` B Gopikrishna
2014-04-29 9:39 ` Marc Sune
2014-04-29 9:30 ` [dpdk-dev] rte_eth_dev_configure fails on VM with e1000 drivers #PERSONAL# B Gopikrishna
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='CAHJKsGzfy9bRAdxjVf6YJP9H7s3=64PFcPoVxAfmP7no0CkWBA@mail.gmail.com' \
--to=tomasz.kasowicz@gmail.com \
--cc=b.gopikrishna@tcs.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).