From: Paul Barrette <paul.barrette@windriver.com>
To: jinho hwang <hwang.jinho@gmail.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] DMAR fault
Date: Mon, 12 Aug 2013 16:28:26 -0400 [thread overview]
Message-ID: <5209456A.9020200@windriver.com> (raw)
In-Reply-To: <CAPQGAnGVzACKZDS5k894+-7kEZ2Sg6iSwkcj9+XOMYcuyGaeaQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2140 bytes --]
On 08/12/2013 04:19 PM, jinho hwang wrote:
> Hi All,
>
> I am using iommu to receive packets both from hypervisor and from VM.
> KVM is used for the virtualization. However, after I deliver the
> kernel options (iommu and pci realloc), I can not receive packets in
> hypervisor, but VF works fine in VM. When I tried to receive packets
> in hypervisor, dmesg shows the following:
>
> ixgbe 0000:03:00.1: complete
> ixgbe 0000:03:00.1: PCI INT A disabled
> igb_uio 0000:03:00.1: PCI INT A -> GSI 38 (level, low) -> IRQ 38
> igb_uio 0000:03:00.1: setting latency timer to 64
> igb_uio 0000:03:00.1: irq 87 for MSI/MSI-X
> uio device registered with irq 57
> DRHD: handling fault status reg 2
> DMAR:[DMA Read] Request device [03:00.1] fault addr *b9d0f000*
> DMAR:[fault reason 02] Present bit in context entry is clear
>
> 03:00.1 Ethernet controller: Intel Corporation 82599EB 10 Gigabit Dual
> Port Backplane Connection (rev 01)
> Subsystem: Intel Corporation Ethernet X520 10GbE Dual Port
> KX4-KR Mezz
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort+ >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 38
> Region 0: Memory at *d9400000* (64-bit, prefetchable) [size=4M]
> Region 2: I/O ports at ece0 [size=32]
> Region 4: Memory at d9bfc000 (64-bit, prefetchable) [size=16K]
> Expansion ROM at <ignored> [disabled]
> Capabilities: <access denied>
> Kernel driver in use: igb_uio
> Kernel modules: ixgbe
>
> We can see those addresses are not matched. So the kernel got fault. I
> am wondering why this happens?
I have seen this happen when VT-d is enabled in the bios. If you are
using dpdk 1.4, add "iommu=pt" to your boot line. Without it, no
packets are received.
Pb
>
> One suspicion for this is BIOS. I am currently using BIOS version 3.0,
> but the latest is 6.3.0. Does this affect the matter?
>
> Any help appreciated!
>
> Jinho
>
[-- Attachment #2: Type: text/html, Size: 5815 bytes --]
next prev parent reply other threads:[~2013-08-12 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 20:19 jinho hwang
2013-08-12 20:28 ` Paul Barrette [this message]
2013-08-12 22:07 ` jinho hwang
2013-08-12 22:22 ` Paul Barrette
2013-08-12 22:25 ` jinho hwang
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=5209456A.9020200@windriver.com \
--to=paul.barrette@windriver.com \
--cc=dev@dpdk.org \
--cc=hwang.jinho@gmail.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).