All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	iommu@lists.linux-foundation.org
Subject: Re: 4.19-rc3: IOMMU PT warnings: WARNING: CPU: 0 PID: 1 at mm/page_alloc.c:4065 __alloc_pages_slowpath+0xb7b/0xcd0
Date: Mon, 10 Sep 2018 15:23:04 +0200	[thread overview]
Message-ID: <20180910132304.GA20244@lst.de> (raw)
In-Reply-To: <alpine.LRH.2.21.1809101111040.31938@math.ut.ee>

On Mon, Sep 10, 2018 at 11:16:12AM +0300, Meelis Roos wrote:
> In 4.19-rc1, I found that to keep Intel integrated graphics working when 
> VT-d is on, I need to have IOMMU passthough on or GPU init would fail 
> with DMAR error and the screen would display static gibberish. So I 
> turned IOMMU PT on by default in kernel config. It worked, also in rc2.
> 
> Now with rc3, it still works but I get some warning splats in dmesg 
> about IOMMU passthrough:

Any chance you could bisect this down to a specific commit?  For
a start it might be worth if it is reproducable with:

   git://git.infradead.org/users/hch/dma-mapping.git dma-mapping-4.19-2

which were the only dma-mapping changes post -rc2.

  reply	other threads:[~2018-09-10 13:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10  8:16 4.19-rc3: IOMMU PT warnings: WARNING: CPU: 0 PID: 1 at mm/page_alloc.c:4065 __alloc_pages_slowpath+0xb7b/0xcd0 Meelis Roos
2018-09-10  8:16 ` Meelis Roos
2018-09-10 13:23 ` Christoph Hellwig [this message]
     [not found]   ` <20180910132304.GA20244-jcswGhMUV9g@public.gmane.org>
2018-09-10 13:26     ` Robin Murphy
2018-09-10 13:26       ` Robin Murphy
     [not found]       ` <e3f0e78a-3e3d-aae7-2588-599184dee534-5wv7dgnIgG8@public.gmane.org>
2018-09-10 14:07         ` Meelis Roos
2018-09-10 14:07           ` Meelis Roos
2018-09-10 14:36           ` Robin Murphy

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=20180910132304.GA20244@lst.de \
    --to=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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.