All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 10 Feb 2021 11:37:19 +0100	[thread overview]
Message-ID: <02fd493c-957f-890d-d0ad-ebd4119f55f2@redhat.com> (raw)
In-Reply-To: <161291205642.6673.10994709665368036431@build.alporthouse.com>

Hi,

On 2/10/21 12:07 AM, Chris Wilson wrote:
> Quoting Hans de Goede (2021-02-09 11:46:46)
>> 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.
>>
>> Note the original / first reporter of:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1925346
>>
>> Is using hsw-gt2, so it seems that the problem is not just the enabling of
>> the mitigations on ivy-bridge / bay-trail but that there actually is
>> a regression on devices where the WA worked fine before...
> 
> There have been 3 crashes uploaded related to v5.10.9, and in all 3
> cases the ACTHD has been in the first page. This strongly suggests that
> the w/a is scribbling over address 0. And there's then a very good
> chance that
> 
> commit 29d35b73ead4e41aa0d1a954c9bfbdce659ec5d6
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Mon Jan 25 12:50:33 2021 +0000
> 
>     drm/i915/gt: Always try to reserve GGTT address 0x0
>     
>     commit 489140b5ba2e7cc4b853c29e0591895ddb462a82 upstream.
> 
> in v5.10.14 is sufficient to hide the issue.

That one actually is already in v5.10.13 and the various reportes of these
issues have already tested 5.10.13. They did mention that it took longer
to reproduce with 5.10.13 then with 5.10.10, but that could also be due to:

"drm/i915/gt: Clear CACHE_MODE prior to clearing residuals"
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.10.y&id=520d05a77b2866eb4cb9e548e1d8c8abcfe60ec5

Regards,

Hans


WARNING: multiple messages have this Message-ID (diff)
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: Wed, 10 Feb 2021 11:37:19 +0100	[thread overview]
Message-ID: <02fd493c-957f-890d-d0ad-ebd4119f55f2@redhat.com> (raw)
In-Reply-To: <161291205642.6673.10994709665368036431@build.alporthouse.com>

Hi,

On 2/10/21 12:07 AM, Chris Wilson wrote:
> Quoting Hans de Goede (2021-02-09 11:46:46)
>> 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.
>>
>> Note the original / first reporter of:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1925346
>>
>> Is using hsw-gt2, so it seems that the problem is not just the enabling of
>> the mitigations on ivy-bridge / bay-trail but that there actually is
>> a regression on devices where the WA worked fine before...
> 
> There have been 3 crashes uploaded related to v5.10.9, and in all 3
> cases the ACTHD has been in the first page. This strongly suggests that
> the w/a is scribbling over address 0. And there's then a very good
> chance that
> 
> commit 29d35b73ead4e41aa0d1a954c9bfbdce659ec5d6
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Mon Jan 25 12:50:33 2021 +0000
> 
>     drm/i915/gt: Always try to reserve GGTT address 0x0
>     
>     commit 489140b5ba2e7cc4b853c29e0591895ddb462a82 upstream.
> 
> in v5.10.14 is sufficient to hide the issue.

That one actually is already in v5.10.13 and the various reportes of these
issues have already tested 5.10.13. They did mention that it took longer
to reproduce with 5.10.13 then with 5.10.10, but that could also be due to:

"drm/i915/gt: Clear CACHE_MODE prior to clearing residuals"
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.10.y&id=520d05a77b2866eb4cb9e548e1d8c8abcfe60ec5

Regards,

Hans

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2021-02-10 10:41 UTC|newest]

Thread overview: 34+ 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 20:38 ` [Intel-gfx] " Hans de Goede
2021-02-08 23:27 ` Chris Wilson
2021-02-08 23:27   ` Chris Wilson
2021-02-09 11:46   ` Hans de Goede
2021-02-09 11:46     ` Hans de Goede
2021-02-09 11:55     ` Chris Wilson
2021-02-09 11:55       ` Chris Wilson
2021-02-09 23:07     ` Chris Wilson
2021-02-09 23:07       ` Chris Wilson
2021-02-10 10:37       ` Hans de Goede [this message]
2021-02-10 10:37         ` Hans de Goede
2021-02-10 12:48         ` Chris Wilson
2021-02-10 12:48           ` Chris Wilson
2021-02-11 10:36           ` Hans de Goede
2021-02-11 10:36             ` Hans de Goede
2021-02-11 10:49             ` Chris Wilson
2021-02-11 10:49               ` Chris Wilson
2021-02-11 12:26               ` Hans de Goede
2021-02-11 12:26                 ` Hans de Goede
2021-02-14 16:00                 ` Hans de Goede
2021-02-14 16:00                   ` Hans de Goede
2021-02-15 14:26                   ` Greg Kroah-Hartman
2021-02-15 14:26                     ` Greg Kroah-Hartman
2021-03-01 14:10                     ` Greg Kroah-Hartman
2021-03-01 14:10                       ` Greg Kroah-Hartman
2021-02-18 14:04                   ` Hans de Goede
2021-02-18 14:04                     ` Hans de Goede
2021-02-25 11:52               ` Hans de Goede
2021-02-25 11:52                 ` Hans de Goede
2021-02-11  0:00         ` Chris Wilson
2021-02-11  0:00           ` Chris Wilson
2021-02-09 16:43   ` Hans de Goede
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=02fd493c-957f-890d-d0ad-ebd4119f55f2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.