From: Joerg Roedel <joro@8bytes.org>
To: Andreas Hartmann <andihartmann@freenet.de>
Cc: Alex Williamson <alex.williamson@redhat.com>,
linux-pci <linux-pci@vger.kernel.org>,
iommu <iommu@lists.linux-foundation.org>
Subject: Re: Since Linux 4.1: A lot of AMD-Vi IO_PAGE_FAULTs
Date: Tue, 21 Jul 2015 18:35:17 +0200 [thread overview]
Message-ID: <20150721163517.GG10969@8bytes.org> (raw)
In-Reply-To: <55AE7147.7070902@maya.org>
On Tue, Jul 21, 2015 at 06:20:23PM +0200, Andreas Hartmann wrote:
> [ 48.193901] <6>[fglrx] Firegl kernel thread PID: 1840
> [ 48.193985] <6>[fglrx] Firegl kernel thread PID: 1841
> [ 48.194063] <6>[fglrx] Firegl kernel thread PID: 1842
> [ 48.194172] <6>[fglrx] IRQ 28 Enabled
> [ 48.261580] <6>[fglrx] Reserved FB block: Shared offset:0, size:1000000
> [ 48.261586] <6>[fglrx] Reserved FB block: Unshared offset:f7b4000, size:4000
> [ 48.261587] <6>[fglrx] Reserved FB block: Unshared offset:f7b8000, size:548000
> [ 48.261588] <6>[fglrx] Reserved FB block: Unshared offset:3fff3000, size:d000
>From a first glance it doesn't look like an IOMMU driver issue, because
the addresses where the faults happen are not from the AMD IOMMU driver.
And you have proprietary closed-source drivers loaded, can you reproduce
the issue without fglrx?
Joerg
next prev parent reply other threads:[~2015-07-21 16:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55AE5F84.5020204@01019freenet.de>
2015-07-21 15:34 ` Since Linux 4.1: A lot of AMD-Vi IO_PAGE_FAULTs Alex Williamson
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 [this message]
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
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=20150721163517.GG10969@8bytes.org \
--to=joro@8bytes.org \
--cc=alex.williamson@redhat.com \
--cc=andihartmann@freenet.de \
--cc=iommu@lists.linux-foundation.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 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).