From: Lilijun <jerry.lilijun@huawei.com>
To: "Zhang, Jerry" <jerry.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Problems when testing l2fwd with ixgbevf pmd dirver
Date: Thu, 23 Oct 2014 15:03:38 +0800 [thread overview]
Message-ID: <5448A84A.50508@huawei.com> (raw)
In-Reply-To: <4255D795-B31C-42C0-975D-36FA23D70F2A@intel.com>
On 2014/10/23 13:56, Zhang, Jerry wrote:
> Hi lijun,
>
> It seems that one of the PCI BAR mapping failed. Need to identify the accurate code line of the mapping error.
>
> Is this a common issue for all 82599 VFs in your environment or just one rare case? If it's just one case, maybe it is caused by configure problem and please try to reconfigure your PF/VF.
The PF nic has not been up yet, so VF pmd dirver initialize failed.
That's ok now.
Thanks.
>
> Thank you!
>
> 发自我的 iPhone
>
>> 在 2014年10月23日，11:37，Lilijun <jerry.lilijun@huawei.com> 写道：
>>
>> Hi all,
>>
>> I am testing the example l2fwd of dpdk-1.7.0 using intel 82599 VF NICs.
>> But the VF can't be used when doing probe pmd driver with following error:
>>
>> EAL: PCI device 0000:02:10.0 on NUMA socket -1
>> EAL: probe driver: 8086:10ed rte_ixgbevf_pmd
>> EAL: PCI memory mapped at 0x7f78b181f000
>> EAL: PCI memory mapped at 0x7f78b181b000
>> EAL: Error - exiting with code: 1
>> Cause: Requested device 0000:02:10.0 cannot be used
>>
>> Any suggestions?
>>
>> Thanks,
>> Jerry
>>
prev parent reply other threads:[~2014-10-23 6:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 3:36 Lilijun
2014-10-23 3:44 ` Zhang, Helin
2014-10-23 4:31 ` Lilijun
2014-10-23 4:56 ` Zhang, Helin
2014-10-23 5:51 ` Lilijun
2014-10-23 5:52 ` Dong, Binghua
2014-10-23 7:02 ` Lilijun
2014-10-23 5:37 ` Dong, Binghua
2014-10-23 5:54 ` Lilijun
2014-10-23 5:56 ` Zhang, Jerry
2014-10-23 7:03 ` Lilijun [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=5448A84A.50508@huawei.com \
--to=jerry.lilijun@huawei.com \
--cc=dev@dpdk.org \
--cc=jerry.zhang@intel.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).