DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
To: "Rapelly, Varun" <vrapelly@sonusnet.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] iommu Error on DL380 G8 with RHEL 7.1
Date: Fri, 24 Jul 2015 10:17:00 +0100	[thread overview]
Message-ID: <55B2028C.5090601@intel.com> (raw)
In-Reply-To: <BLUPR03MB2649AEBBB4D66C08A9C44D0B7810@BLUPR03MB264.namprd03.prod.outlook.com>

On 24/07/2015 09:54, Rapelly, Varun wrote:
> Hi All,
>
> I'm not able to send packets through OVS bridge [with dpdk] when iommu is enabled on HP DL380 G8 [RHEL 7.1]. Getting following errors in dmesg.
>
> [    0.657681] IOMMU: Setting identity map for device 0000:01:00.2 [0xbdff6000 - 0xbdffcfff]
> [    0.657686] IOMMU: Prepare 0-16MiB unity mapping for LPC
> [ 4458.091522] dmar: DMAR:[DMA Read] Request device [0a:00.0] fault addr 1a633d000
> DMAR:[fault reason 06] PTE Read access is not set
> [ 4458.164541] dmar: DMAR:[DMA Read] Request device [0a:00.0] fault addr 1a633d000
> DMAR:[fault reason 06] PTE Read access is not set
> [ 4458.337565] dmar: DMAR:[DMA Read] Request device [0a:00.1] fault addr 1a63cd000
> DMAR:[fault reason 06] PTE Read access is not set
> [ 4458.637356] dmar: DMAR:[DMA Read] Request device [0a:00.0] fault addr 1a637d000
> DMAR:[fault reason 06] PTE Read access is not set
>
> Where as in another machine ProLiant DL380 G7 [RHEL 7.1] everything works fine. Is it something do with the hardware on Gen8 machine?
>
> The following link shows the similar problem.
>
> http://comments.gmane.org/gmane.comp.networking.dpdk.devel/2281
>
> In the below HP link, they quoted the same problem. I upgraded ROM to the latest version, but no luck. :(
>
> http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c03323800
>
>
>
> We need this flag to be enabled [SR-IOV] on that machine.
>
>
>
> Please let me know, is there any way to resolve this issue?
>
> Regards,
> Varun
>
Hi Varun,

As I replied in you previous post, the issue is most likely related to HP.
You need to contact HP for a solution to your issues as suggested in the 
following thread by Lee A. Roberts from HP:
http://dpdk.org/ml/archives/dev/2015-March/015504.html

Sergio

  reply	other threads:[~2015-07-24  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24  8:54 Rapelly, Varun
2015-07-24  9:17 ` Gonzalez Monroy, Sergio [this message]
2015-07-24  9:24   ` Rapelly, Varun
2015-07-24  9:45   ` Rapelly, Varun

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=55B2028C.5090601@intel.com \
    --to=sergio.gonzalez.monroy@intel.com \
    --cc=dev@dpdk.org \
    --cc=vrapelly@sonusnet.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).