From: Chris Wilson <chris@chris-wilson.co.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hans de Goede <hdegoede@redhat.com>,
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: Mon, 08 Feb 2021 23:27:38 +0000 [thread overview]
Message-ID: <161282685855.9448.10484374241892252440@build.alporthouse.com> (raw)
In-Reply-To: <fe6040b5-72a0-9882-439e-ea7fc0b3935d@redhat.com>
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.
-Chris
next prev parent reply other threads:[~2021-02-08 23:28 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 ` Chris Wilson [this message]
2021-02-09 11:46 ` [Intel-gfx] " 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=161282685855.9448.10484374241892252440@build.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--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).