DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 503] can not detected device when use meson build dpdk
Date: Tue, 07 Jul 2020 06:28:19 +0000	[thread overview]
Message-ID: <bug-503-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=503

            Bug ID: 503
           Summary: can not detected device when use meson build dpdk
           Product: DPDK
           Version: 20.08
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: meson
          Assignee: dev@dpdk.org
          Reporter: lihongx.ma@intel.com
  Target Milestone: ---

os:
ubuntu18.04 4.15.0-101-generic x86_64 GNU/Linux

step:
$ cd dpdk
$ ./devtools/test-meson-builds.sh
$ ./build-x86-default/app/dpdk-testpmd -c 0xf -n 4 -- -i
EAL: Detected 112 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: No free hugepages reported in hugepages-2048kB
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL:   using IOMMU type 1 (Type 1)
EAL: Failed to map pci BAR3
EAL:   0000:18:00.0 mapping BAR3 failed: Success
EAL: Requested device 0000:18:00.0 cannot be used
EAL: Failed to map pci BAR3
EAL:   0000:18:00.1 mapping BAR3 failed: Success
EAL: Requested device 0000:18:00.1 cannot be used
EAL: No legacy callbacks, legacy socket not created
testpmd: No probed ethernet devices
Interactive-mode selected
testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=171456, size=2176,
socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
Done


first bad commit id:
commit 2fd3567e542595d38deea7c186ee52621a46dc99
Author: Tal Shnaiderman <talshn@mellanox.com>
Date:   Mon Jun 29 15:37:34 2020 +0300

    pci: use OS generic memory mapping functions

    Changing all of PCIs Unix memory mapping to the
    new memory allocation API wrapper.

    Change all of PCI mapping function usage in
    bus/pci to support the new API.

    Signed-off-by: Tal Shnaiderman <talshn@mellanox.com>

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2020-07-07  6:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07  6:28 bugzilla [this message]
2020-07-13  5:25 ` bugzilla

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=bug-503-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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).