DPDK usage discussions
 help / color / mirror / Atom feed
From: Hui Wei <huiweics@hotmail.com>
To: Venumadhav Josyula <vjosyula@gmail.com>
Cc: dev <dev@dpdk.org>, users <users@dpdk.org>,
	Venumadhav Josyula <vjosyula@parallelwireless.com>
Subject: Re: [dpdk-users] [dpdk-dev] seeing a problem dpdk startup
Date: Thu, 28 Nov 2019 08:01:13 +0000	[thread overview]
Message-ID: <HK0PR06MB2740BD93025024FC86B65708D0470@HK0PR06MB2740.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <CA+i0PGW7Y=qjObomC-AsvOtT7Mrm-i867g+SRferGRmX5ze8zw@mail.gmail.com>

I think  BIOS turn off vt-d, use igb_uio can work around.

>Hi Hui,
>
>I understand that and we are exploring that.
>
>But is there no work around there where in it defaults to igb_uio driver
>something like that..... Basic idea is we should not be situation of no
>port detected at all under this situation ?
>
>Thanks,
>Regards,
>Venu
>
>On Thu, 28 Nov 2019 at 13:15, Hui Wei <huiweics@hotmail.com> wrote:
>
>>
>> >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.
>>
>> Intel Vt-d document addresses RMRR, but not that clearly. Check BIOS
>> setup,
>> no link share, for example, a nic detect by linux kernel, it was shared by
>> BIOS for
>> IPMI. If change BIOS setup don't solve your problem, contact platform
>> vendor update
>> nic firmware, a server made by HP, check HP's website for firmware.
>>
>> >
>> >======
>> >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 ?
>> >
>> >Thanks,
>> >Regards,
>> >Venu

  reply	other threads:[~2019-11-28  8:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28  7:01 [dpdk-users] " Venumadhav Josyula
2019-11-28  7:39 ` [dpdk-users] [dpdk-dev] " Gavin Hu (Arm Technology China)
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 [this message]
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 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=HK0PR06MB2740BD93025024FC86B65708D0470@HK0PR06MB2740.apcprd06.prod.outlook.com \
    --to=huiweics@hotmail.com \
    --cc=dev@dpdk.org \
    --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
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).