From: Hans de Goede <hdegoede@redhat.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
stable@vger.kernel.org
Subject: Re: [Intel-gfx] [5.10.y regression] i915 clear-residuals mitigation is causing gfx issues
Date: Tue, 9 Feb 2021 17:43:58 +0100 [thread overview]
Message-ID: <20c3d11d-75f6-ad82-1100-3015ff463406@redhat.com> (raw)
In-Reply-To: <161282685855.9448.10484374241892252440@build.alporthouse.com>
Hi,
On 2/9/21 12:27 AM, Chris Wilson wrote:
> Quoting Hans de Goede (2021-02-08 20:38:58)
>> Hi All,
>>
>> We (Fedora) have been receiving reports from multiple users about gfx issues / glitches
>> stating with 5.10.9. All reporters are users of Ivy Bridge / Haswell iGPUs and all
>> reporters report that adding i915.mitigations=off to the cmdline fixes things, see:
>
> I tried to reproduce this on the w/e on hsw-gt1, to no avail; and piglit
> did not report any differences with and without mitigations. I have yet
> to test other platforms. So I don't yet have an alternative. Though note
> that v5.11 and v5.12 will behave similarly, so we need to urgently find
> a fix for Linus's tree anyway.
Note I've gone ahead and prepared a test kernel for the Fedora bug reports
with the following 3 commits reverted from 5.10.y :
520d05a77b2866eb ("drm/i915/gt: Clear CACHE_MODE prior to clearing residuals")
ecca0c675bdecebd ("drm/i915/gt: Restore clear-residual mitigations for Ivybridge, Baytrail")
48b8c6689efa7cd6 ("drm/i915/gt: Limit VFE threads based on GT")
(Note this are the 5.10.y hashes)
I know going this route is not ideal but it might be best for 5.10.y for now.
I will let you know if reverting these 3 actually helps once I hear back
from the reporters of the issue.
Regards,
Hans
prev parent reply other threads:[~2021-02-09 16:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 20:38 [5.10.y regression] i915 clear-residuals mitigation is causing gfx issues Hans de Goede
2021-02-08 23:27 ` [Intel-gfx] " Chris Wilson
2021-02-09 11:46 ` Hans de Goede
2021-02-09 11:55 ` Chris Wilson
2021-02-09 23:07 ` Chris Wilson
2021-02-10 10:37 ` Hans de Goede
2021-02-10 12:48 ` Chris Wilson
2021-02-11 10:36 ` Hans de Goede
2021-02-11 10:49 ` Chris Wilson
2021-02-11 12:26 ` Hans de Goede
2021-02-14 16:00 ` Hans de Goede
2021-02-15 14:26 ` Greg Kroah-Hartman
2021-03-01 14:10 ` Greg Kroah-Hartman
2021-02-18 14:04 ` Hans de Goede
2021-02-25 11:52 ` Hans de Goede
2021-02-11 0:00 ` Chris Wilson
2021-02-09 16:43 ` Hans de Goede [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=20c3d11d-75f6-ad82-1100-3015ff463406@redhat.com \
--to=hdegoede@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@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).