Re: Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6)

From: Hans de Goede <hdegoede@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	"Regzbot (on behalf of Thorsten Leemhuis)" 
	<regressions@leemhuis.info>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Matthew Auld <matthew.auld@intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6)
Date: Thu, 19 May 2022 18:09:55 +0200	[thread overview]
Message-ID: <063d7fdb-2d4c-5798-773b-d82b4f0e918a@redhat.com> (raw)
In-Reply-To: <04f2e08c-4c39-16d3-d785-f36494c6256c@redhat.com>

Hi,

On 5/17/22 17:50, Hans de Goede wrote:
> Hi,
> 
> On 5/9/22 21:04, Hans de Goede wrote:
>> Hi,
>>
>> On 5/9/22 19:20, Linus Torvalds wrote:
>>> On Mon, May 9, 2022 at 3:47 AM Regzbot (on behalf of Thorsten
>>> Leemhuis) <regressions@leemhuis.info> wrote:
>>>>
>>>> Hi Linus! Here's a quick compilation of open reports about regressions in
>>>> 5.18-rc that I'm currently aware of; most of the reports are quite
>>>> recent and there afaics is nothing that looks particularly worrisome.
>>>
>>> Well, the Intel GPU issue seems likely to cause problems for lots of people:
>>>
>>>> [ *NEW* ] drm/i915: BYT rendering broken due to "Remove short-term pins from execbuf, v6"
>>>> -----------------------------------------------------------------------------------------
>>>> https://linux-regtracking.leemhuis.info/regzbot/regression/1366349e-f96a-3f2c-3094-f5cd1a6fa31f@redhat.com/
>>>> https://lore.kernel.org/dri-devel/1366349e-f96a-3f2c-3094-f5cd1a6fa31f@redhat.com/
>>>>
>>>> By Hans de Goede; 0 days ago; 2 activities, latest 0 days ago.
>>>> Introduced in b5cfe6f7a6e1 (v5.18-rc1)
>>>>
>>>> Recent activities from: Tvrtko Ursulin (1), Hans de Goede (1)
>>>
>>> Although it looks possible that it mainly affects old chipsets (ie the
>>> two reports are for a Bay Trail chip and a Core 2 Duo chip - I have no
>>> idea how they compare).
>>>
>>> That probably means there are a lot of machines out there, but likely
>>> not the kind that most kernel developers will be testing, so not a ton
>>> of reports until it hits distro kernels etc.
>>>
>>> It looks like Maarten is already involved.
>>
>> This is being tracked here:
>> https://gitlab.freedesktop.org/drm/intel/-/issues/5806
>>
>> I've just tested a patch from Maarten which fixes things for me,
>> so hopefully we can get this resolved soon.
> 
> Maarten, it would be nice if we can get this fixed before 5.18
> is released. What is the status of getting your:
> 
> https://patchwork.freedesktop.org/patch/485889/

A quick status update, this is fixed by:

https://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-fixes&id=7b1d6924f27ba24b9e47abb9bd53d0bbc430a835

Which was just pushed to:

https://cgit.freedesktop.org/drm-intel/log/?h=drm-intel-fixes

Note this is not part of any pending drm-fixes* pull-reqs yet though.

Regards,

Hans