DPDK patches and discussions
 help / color / Atom feed
From: "Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>
To: Venumadhav Josyula <vjosyula@gmail.com>,
	"dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>
Cc: Venumadhav Josyula <vjosyula@parallelwireless.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] seeing a problem dpdk startup
Date: Thu, 28 Nov 2019 07:39:29 +0000
Message-ID: <VI1PR08MB53760D20825E57805F2EE8118F470@VI1PR08MB5376.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CA+i0PGXydtZ87H-YtDqLeciyUV00Ak_WAQv5cs31AXW7yoNt7A@mail.gmail.com>

Hi Venumadhav,

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Venumadhav Josyula
> Sent: Thursday, November 28, 2019 3:01 PM
> To: dev@dpdk.org; users@dpdk.org
> Cc: Venumadhav Josyula <vjosyula@parallelwireless.com>
> Subject: [dpdk-dev] seeing a problem dpdk startup
> 
> We are seeing following error, no device is detected....
> ==========
> EAL: Detected 8 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: No free hugepages reported in hugepages-1048576kB
> EAL: Probing VFIO support...
> EAL: VFIO support initialized
> EAL: PCI device 0000:04:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1528 net_ixgbe
> EAL:   0000:04:00.0 failed to select IOMMU type
> EAL: Requested device 0000:04:00.0 cannot be used
> EAL: PCI device 0000:04:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1528 net_ixgbe
> EAL:   0000:04:00.1 failed to select IOMMU type
> EAL: Requested device 0000:04:00.1 cannot be used
> 
> ==================
> dmesg
> 
> [55455.259493] vfio-pci 0000:04:00.0: Device is ineligible for IOMMU domain
> attach due to platform RMRR requirement.  Contact your platform vendor.
> [55455.260947] vfio-pci 0000:04:00.1: Device is ineligible for IOMMU domain
> attach due to platform RMRR requirement.  Contact your platform vendor.
> 
> ======
> BOOT_IMAGE=/boot/vmlinuz-3.10.0-957.el7.pw.1.x86_64 root=/dev/sda3
> intel_iommu=on
> 
> 
> Can anybody suggest how to work around the issue ?
Did you check if the device is bound to DPDK? 
Here is an example on my host:
gavin@net-arm-thunderx2-01:~/dpdk$ ./usertools/dpdk-devbind.py -s

Network devices using DPDK-compatible driver
============================================
0000:0f:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=vfio-pci unused=i40e
0000:8a:00.0 'Ethernet Controller XXV710 for 25GbE SFP28 158b' drv=vfio-pci unused=i40e
0000:8a:00.1 'Ethernet Controller XXV710 for 25GbE SFP28 158b' drv=vfio-pci unused=i40e
> 
> Thanks,
> Regards,
> Venu

  reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28  7:01 Venumadhav Josyula
2019-11-28  7:39 ` Gavin Hu (Arm Technology China) [this message]
2019-11-28  7:43   ` Venumadhav Josyula
2019-11-28  7:45 ` Hui Wei
2019-11-28  7:48   ` Venumadhav Josyula
2019-11-28  8:01     ` Hui Wei
2019-11-28 14:15       ` Roberts, Lee A.
2019-11-28 14:20         ` Venumadhav Josyula
2019-11-28 16:11           ` Stephen Hemminger

Reply instructions:

You may reply publically 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=VI1PR08MB53760D20825E57805F2EE8118F470@VI1PR08MB5376.eurprd08.prod.outlook.com \
    --to=gavin.hu@arm.com \
    --cc=dev@dpdk.org \
    --cc=nd@arm.com \
    --cc=users@dpdk.org \
    --cc=vjosyula@gmail.com \
    --cc=vjosyula@parallelwireless.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

DPDK patches and discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/ public-inbox