From: Hans de Goede <hdegoede@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: [Intel-gfx] [5.10.y regression] i915 clear-residuals mitigation is causing gfx issues
Date: Mon, 8 Feb 2021 21:38:58 +0100 [thread overview]
Message-ID: <fe6040b5-72a0-9882-439e-ea7fc0b3935d@redhat.com> (raw)
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:
https://bugzilla.redhat.com/show_bug.cgi?id=1925346
Which should be fully visible without a bugzilla account.
I noticed that 5.10.13 had one more related i915 patch, so I've asked the reporters
to retest with 5.10.13, 5.10.13 is better, but things are not fixed there, it just
takes longer for the problems to show up.
Greg, I can prepare a Fedora test-kernel build for the reporters to test with
the following 3 commits reverted:
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)
Reverting these 3 is not ideal, but it is probably the fastest way to get
this resolved for the 5.10.y series.
Greg, do you want me to have the reporters test a 5.10.y series kernel
with these 3 reverts ?
Regards,
Hans
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-02-08 20:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 20:38 Hans de Goede [this message]
2021-02-08 23:27 ` [Intel-gfx] [5.10.y regression] i915 clear-residuals mitigation is causing gfx issues 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
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=fe6040b5-72a0-9882-439e-ea7fc0b3935d@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).