linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@freenet.de>
To: Joerg Roedel <joro@8bytes.org>
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: Fri, 24 Jul 2015 06:22:59 +0200	[thread overview]
Message-ID: <55B1BDA3.3030507@maya.org> (raw)
In-Reply-To: <20150721163517.GG10969@8bytes.org>

[-- Attachment #1: Type: text/plain, Size: 2558 bytes --]

On Tue, Jul 21, 2015 at 06:35PM +0200, Joerg Roedel wrote:
> 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?

Yes. I attached this one.

Meanwhile I tested with 4.0.9, too. I wasn't able to reproduce the
problem with this kernel even after lots of reboots (the problem w/ 4.1
usually comes up during boot process (but not only - it can be seen
after boot process, too)).

The problem always is, that there are errors w/ one of the sata discs
and at the same time, IO_PAGE_FAULT errors are rising as described before:

[  152.533708] ata3.00: failed command: READ FPDMA QUEUED
[  152.538102] ata3.00: failed command: READ FPDMA QUEUED
[  152.539862] ata3.00: failed command: READ FPDMA QUEUED
[  152.541778] ata3.00: failed command: WRITE FPDMA QUEUED
[  152.543861] ata3.00: failed command: WRITE FPDMA QUEUED

[ 5818.068050] ata2.00: failed command: WRITE FPDMA QUEUED
[ 5818.068059] ata2.00: failed command: WRITE FPDMA QUEUED

I compared dmesg from 4.1 w/ 4.0 and I realized the following *missing*
entries in 4.1:

[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)


What does this mean? Is there missing some part of the acpi initialization?


Thanks for any hint as Linux 4.1 is completely unusable here with these
errors.


Regards,
Andreas

[-- Attachment #2: dmesg.out.radeon-4.1.3-vanilla.xz --]
[-- Type: application/x-xz, Size: 21464 bytes --]

  parent reply	other threads:[~2015-07-24  4:26 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
2015-07-21 17:47         ` Andreas Hartmann
2015-07-24  4:22         ` Andreas Hartmann [this message]
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=55B1BDA3.3030507@maya.org \
    --to=andihartmann@freenet.de \
    --cc=alex.williamson@redhat.com \
    --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 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).