DPDK usage discussions
 help / color / mirror / Atom feed
From: "Rosen, Rami" <rami.rosen@intel.com>
To: "Martin Drašar" <drasar@ics.muni.cz>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK 17.05 does not find X510 card
Date: Mon, 18 Jun 2018 13:09:32 +0000	[thread overview]
Message-ID: <9B0331B6EBBD0E4684FBFAEDA55776F9672C7B30@HASMSX110.ger.corp.intel.com> (raw)
In-Reply-To: <5dde9d52-3662-72ae-04a6-b5ad3e122562@ics.muni.cz>

Hi, Martin,
How do you bind the device ? is it with igb_uio/vfio  ? In case this is what you do - can you please try with uio_pci_generic and tell if you get the same error ? 
The uio_pci_generic should be included in your distro as one of the kernel modules, you need just to do modprobe uio_pci_generic before binding to DPDK.

Regards,
Rami Rosen


-----Original Message-----
From: Martin Drašar [mailto:drasar@ics.muni.cz] 
Sent: Monday, June 18, 2018 15:41
To: Rosen, Rami <rami.rosen@intel.com>; users@dpdk.org
Subject: Re: [dpdk-users] DPDK 17.05 does not find X510 card

Dne 18.6.2018 v 11:54 Rosen, Rami napsal(a):
> Hi Martin,
>> dpdk_init()
> 
> I assume you run your own application.
> Can you post the log you get when running testpmd with --log-level=8 and -w I40E0_PCI_BUS_ID ....?
> 
> Also can you post "lspci -n"?
> Regards,
> Rami Rosen

Hello,

thank you for getting back to me so quick. I did some debugging and it turned out that i40e drivers were not linked when building the dpdk. I fixed this, but I have encountered another problem...

Although the cards are discovered, I get this error:

> EAL: pci_map_resource(): cannot mmap(102, 0x7fffc0000000, 0x1000000, 
> 0x0): Operation not permitted (0xffffffffffffffff)

I've seen some information about his mmap-related behavior and some hints about setting iomem=relaxed in grub. As making changes to grub means completely reinstalling my machine, I would like to ask, if you think that this could be the way to go.

Thanks,
Martin

  reply	other threads:[~2018-06-18 13:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18  8:55 Martin Drašar
2018-06-18  8:56 ` [dpdk-users] DPDK 17.05 does not find X710 card Martin Drašar
2018-06-18  9:54 ` [dpdk-users] DPDK 17.05 does not find X510 card Rosen, Rami
2018-06-18 12:41   ` Martin Drašar
2018-06-18 13:09     ` Rosen, Rami [this message]
2018-06-18 13:23       ` Martin Drašar
2018-06-18 13:34         ` Rosen, Rami
2018-06-18 13:43           ` Martin Drašar
2018-06-18 21:35             ` Martin Drašar
2018-06-19  0:21               ` Rosen, Rami
2018-06-19  9:57                 ` Martin Drašar
2018-06-19 14:12                   ` Martin Drašar
2018-06-21  5:58                     ` Avi Cohen (A)
2018-06-21 11:02                       ` Martin Drašar
2018-06-21 15:07                         ` Stephen Hemminger
2018-06-23 13:00                           ` Rosen, Rami
2018-06-25  8:23                             ` Martin Drašar
2018-06-25  9:35                               ` Rosen, Rami
2018-07-11 13:47                                 ` Martin Drašar

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=9B0331B6EBBD0E4684FBFAEDA55776F9672C7B30@HASMSX110.ger.corp.intel.com \
    --to=rami.rosen@intel.com \
    --cc=drasar@ics.muni.cz \
    --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).