mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Christoph Hellwig <hch@lst.de>, Meelis Roos <mroos@linux.ee>
Cc: iommu@lists.linux-foundation.org,
	Linux Kernel list <linux-kernel@vger.kernel.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 14:26:30 +0100	[thread overview]
Message-ID: <e3f0e78a-3e3d-aae7-2588-599184dee534@arm.com> (raw)
In-Reply-To: <20180910132304.GA20244@lst.de>

On 10/09/18 14:23, Christoph Hellwig wrote:
> 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.

Given the __alloc_pages_slowpath() warning, this looks like it's 
probably stemming from the oversized PASID table issue which a few other 
folks have hit too. I think this patch is the most up-to-date fix:

https://www.mail-archive.com/iommu@lists.linux-foundation.org/msg25639.html

Robin.

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10  8:16 Meelis Roos
2018-09-10 13:23 ` Christoph Hellwig
2018-09-10 13:26   ` Robin Murphy [this message]
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=e3f0e78a-3e3d-aae7-2588-599184dee534@arm.com \
    --to=robin.murphy@arm.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®