All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Cc: linux-pci <linux-pci@vger.kernel.org>,
	iommu <iommu@lists.linux-foundation.org>,
	Joerg Roedel <joro@8bytes.org>
Subject: Re: Since Linux 4.1: A lot of AMD-Vi IO_PAGE_FAULTs
Date: Tue, 21 Jul 2015 09:34:46 -0600	[thread overview]
Message-ID: <1437492886.1391.847.camel@redhat.com> (raw)
In-Reply-To: <55AE5F84.5020204@01019freenet.de>

[cc +iommu, +joerg]

On Tue, 2015-07-21 at 17:04 +0200, Andreas Hartmann wrote:
> Hello!
> 
> Since Linux 4.1, I'm getting a lot of IO_PAGE_FAULT like this one
> 
> [   17.048609] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:11.0
> domain=0x0008 address=0x40ebaaab00618000 flags=0x0010]
> 
> with different addresses:
> 
> 0x40ebaaab00618000
> 0x40ebaaab00618040
> 0x0000000000000000
> 0x0000000000000180
> 0x00000000000000c0
> 0x0000000000000080
> 0x0000000000000100
> 0x0000000000000040
> 0x0000000000000140
> 0x00000000000001c0
> 0x0000000000000200
> 0x0000000000000240
> 0x0000000000000280
> 
> ...
> 
> device=00:11.0 is:
> 
> # lspci -vvs 00:11.0
> 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI]
> SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40) (prog-if 01 [AHCI
> 1.0])
>         Subsystem: Gigabyte Technology Co., Ltd Device b002
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
>         Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
>         Latency: 32, Cache Line Size: 64 bytes
>         Interrupt: pin A routed to IRQ 19
>         Region 0: I/O ports at ff00 [size=8]
>         Region 1: I/O ports at fe00 [size=4]
>         Region 2: I/O ports at fd00 [size=8]
>         Region 3: I/O ports at fc00 [size=4]
>         Region 4: I/O ports at fb00 [size=16]
>         Region 5: Memory at fdfff000 (32-bit, non-prefetchable) [size=1K]
>         Capabilities: [70] SATA HBA v1.0 InCfgSpace
>         Capabilities: [a4] PCI Advanced Features
>                 AFCap: TP+ FLR+
>                 AFCtrl: FLR-
>                 AFStatus: TP-
>         Kernel driver in use: ahci
> 
> 
> Any idea what could be wrong?
> 
> 
> Thanks,
> kind regards,
> Andreas Hartmann
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-07-21 15:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 15:04 Since Linux 4.1: A lot of AMD-Vi IO_PAGE_FAULTs Andreas Hartmann
2015-07-21 15:34 ` Alex Williamson [this message]
2015-07-21 15:56   ` Joerg Roedel
2015-07-21 16:20     ` Andreas Hartmann
2015-07-21 16:30       ` Joerg Roedel
2015-07-21 16:35       ` Joerg Roedel
2015-07-21 17:47         ` Andreas Hartmann
2015-07-24  4:22         ` Andreas Hartmann
2015-07-24 16:15           ` Bjorn Helgaas
2015-07-24 17:59             ` Andreas Hartmann
2015-07-29 15:22               ` Joerg Roedel
2015-07-29 16:31                 ` Andreas Hartmann
2015-07-25 18:22             ` Andreas Hartmann
2015-07-26 16:28               ` Andreas Hartmann
2015-07-21 18:21 ` Borislav Petkov

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=1437492886.1391.847.camel@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=andihartmann@01019freenet.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-pci@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.