From: James Bensley <jwbensley@gmail.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Hard Crash with X710 and Pktgen
Date: Wed, 15 Nov 2017 18:04:34 +0000 [thread overview]
Message-ID: <CAAWx_pVmUK9+L_Ns-Q75Fj8FyTE0tzuQCtemvT9t3zACS_UjBg@mail.gmail.com> (raw)
In-Reply-To: <CAAWx_pVZxtCnp9=yzmyTg_EohnZHGNQ0=Yr7T0XFE353JzK75g@mail.gmail.com>
Hi All,
I have Pktgen working on this box now.
So for the sake of this list archives:
In addition to the 2x10G Intel X710 NIC there is a 2x1G Intel I350 NIC
in this box. Trying with the igb_uio or vfio-pci driver for the 1G NIC
had the same results as with the 10G NIC; hard lock-up when using
igb_uio and DPDK is reporting no free ports available when using
vfio-pci.
However with vfio-pci the following syslog message was logged:
"Device is ineligible for IOMMU domain attach due to platform RMRR
requirement. Contact your platform vendor."
After some searching this seems to be an issue with Kernels newer than
3.16 on HPE boxes (e.g.
https://forums.lime-technology.com/topic/53049-solved-device-is-ineligible-for-iommu-domain-attach-due-to-platform-rmrr/).
Looks like a BIOS setting can solve this issue
(https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04781229&sp4ts.oid=5249566).
I have multiple Kernels compiled on this box. I was using 4.13 for
some other testing, so I booted into 3.10, recompiled DPDK+Pktgen and
both the 10G and 1G NICs are working using the igb_uio driver.
I'd like to be a 4.10 kernel as I was testing some features in there
separate to DPDK so I will try disabling that BIOS setting and see if
this works with the newer Kernel version. The box is remote so I can't
do that right away!
Many thanks all for your time and help it is greatly appreciated.
Cheers,
James.
next prev parent reply other threads:[~2017-11-15 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 19:35 James Bensley
2017-11-13 21:49 ` Wiles, Keith
2017-11-14 4:49 ` Muhammad Zain-ul-Abideen
2017-11-14 6:29 ` Rosen, Rami
2017-11-14 8:37 ` James Bensley
2017-11-14 10:59 ` Johnson, Brian
2017-11-14 20:20 ` Wiles, Keith
2017-11-15 17:24 ` James Bensley
2017-11-15 18:04 ` James Bensley [this message]
2017-11-15 17:22 ` James Bensley
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=CAAWx_pVmUK9+L_Ns-Q75Fj8FyTE0tzuQCtemvT9t3zACS_UjBg@mail.gmail.com \
--to=jwbensley@gmail.com \
--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).