From: Jani Nikula <jani.nikula@linux.intel.com>
To: Christoph Hellwig <hch@lst.de>, Peter Zijlstra <peterz@infradead.org>
Cc: intel-gfx@lists.freedesktop.org, x86@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
hch@lst.de
Subject: Re: [Intel-gfx] 5.13 i915/PAT regression on Brasswell, adding nopat to the kernel commandline worksaround this
Date: Tue, 18 May 2021 12:28:36 +0300 [thread overview]
Message-ID: <87eee4fl17.fsf@intel.com> (raw)
In-Reply-To: <20210512115736.GA10444@lst.de>
On Wed, 12 May 2021, Christoph Hellwig <hch@lst.de> wrote:
> On Wed, May 12, 2021 at 01:15:03PM +0200, Peter Zijlstra wrote:
>> IIRC it's because of 74ffa5a3e685 ("mm: add remap_pfn_range_notrack"),
>> which added a sanity check to make sure expectations were met. It turns
>> out they were not.
>>
>> The bug is not new, the warning is. AFAIK the i915 team is aware, but
>> other than that I've not followed.
>
>
> The actual culprit is b12d691ea5e0 ("i915: fix remap_io_sg to verify the
> pgprot"), but otherwise agreed. Someone the i915 maintainers all seem
> to be on vacation as the previous report did not manage to trigger any
> kind of reply.
We are aware. I've been rattling the cages to get more attention.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2021-05-18 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 9:57 5.13 i915/PAT regression on Brasswell, adding nopat to the kernel commandline worksaround this Hans de Goede
2021-05-12 11:15 ` Peter Zijlstra
2021-05-12 11:57 ` Christoph Hellwig
2021-05-12 12:36 ` Hans de Goede
2021-05-18 9:28 ` Jani Nikula [this message]
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=87eee4fl17.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=hch@lst.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@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