All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raimonds Cicans <ray@apollo.lv>
To: linux-kernel@vger.kernel.org
Subject: Question about: AMD-Vi: Event logged [IO_PAGE_FAULT ...
Date: Mon, 05 Jan 2015 17:25:25 +0200	[thread overview]
Message-ID: <54AAACE5.2020909@apollo.lv> (raw)

Hello.

After kernel upgrade (3.13 => 3.17) I started to receive following 
string in my logs:
AMD-Vi: Event logged [IO_PAGE_FAULT device=08:00.0 domain=0x001c 
address=0x0000000001355000 flags=0x0000]

I would like to deeper understand this problem, so it
would be nice if some body can fix my assumptions and
answer my questions.


Assumptions:

1) This message is generated by AMD IOMMU subsystem
      because PCIe device 08:00.0 tried to access memory
      region which was not mapped to any real memory
      (lspci show that this device is DVB-S2 receiver card
       TBS 6981)

2) Because flags are 0 and because in general receivers
     write to memory not read from memory it is memory
     write operation

3) Possible causes:
     a) memory region was never mapped
     b) device accessed memory region before it was mapped
     c) device accessed memory region after it was unmapped

3) Suspects:
      a) kernel's DMA subsystem: very unlikely
      b) kernel's IOMMU subsystem: very unlikely
      c) AMD IOMMU driver: unlikely? - i had problems with AMD IOMMU
          itself in kernels 3.14 - 3.17 (AMD-Vi: Completion-Wait loop 
timed out)
          So maybe this problem not fully fixed?
      d) Receiver's driver: likely


Questions:
1) What 'domain=0x001c' mean?
2) Where I can find definition of possible flags?
3) What kind of address is written in message?
      - physical?
      - virtual?
      - address from devices point of view?


Thank you.


Raimonds Cicans

             reply	other threads:[~2015-01-05 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 15:25 Raimonds Cicans [this message]
2015-01-05 16:49 ` Question about: AMD-Vi: Event logged [IO_PAGE_FAULT Joerg Roedel

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=54AAACE5.2020909@apollo.lv \
    --to=ray@apollo.lv \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.