linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@freenet.de>
To: Joerg Roedel <joro@8bytes.org>,
	Andreas Hartmann <andihartmann@freenet.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	linux-pci <linux-pci@vger.kernel.org>,
	iommu <iommu@lists.linux-foundation.org>,
	Tejun Heo <tj@kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Since Linux 4.1: A lot of AMD-Vi IO_PAGE_FAULTs
Date: Wed, 29 Jul 2015 18:31:07 +0200	[thread overview]
Message-ID: <55B8FFCB.30602@maya.org> (raw)
In-Reply-To: <20150729152208.GS10969@8bytes.org>

Hi Jörg,

On 07/29/2015 at 05:22 PM, Joerg Roedel wrote:
> Hi Andreas,
> 
> On Fri, Jul 24, 2015 at 07:59:07PM +0200, Andreas Hartmann wrote:
>> New information: During testing, I now realized that Linux 4.0.9 shows
>> the same problem ... . I'm now testing 3.19.4.
> 
> Have you seen the issue on 3.19 too or hasn't it happened there at all
> yet? The question is where to look for a commit that breaks it on  your
> machine.

3.19 works perfectly. It's an issue with new dm crypt:
http://www.spinics.net/lists/dm-devel/msg24019.html


Thanks for asking!
Regards,
Andreas

  reply	other threads:[~2015-07-29 16:34 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
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 [this message]
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=55B8FFCB.30602@maya.org \
    --to=andihartmann@freenet.de \
    --cc=alex.williamson@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=tj@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).