linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 9 May 2022 21:04:07 +0200	[thread overview]
Message-ID: <54664f6a-b046-1330-e794-cb533e942a94@redhat.com> (raw)
In-Reply-To: <CAHk-=wj0gHsG6iw3D8ufptm9a_dvTSqrrOFY9WopObbYbyuwnA@mail.gmail.com>

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.

Regards,

Hans


  reply	other threads:[~2022-05-09 19:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08 21:09 Linux 5.18-rc6 Linus Torvalds
2022-05-09  8:40 ` Build regressions/improvements in v5.18-rc6 Geert Uytterhoeven
2022-05-09  9:13   ` Build regressions/improvements in v5.18-rc6B Geert Uytterhoeven
2022-05-09 10:47 ` Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6) Regzbot (on behalf of Thorsten Leemhuis)
2022-05-09 17:20   ` Linus Torvalds
2022-05-09 19:04     ` Hans de Goede [this message]
2022-05-10 14:41       ` Maarten Lankhorst
2022-05-17 15:50       ` Hans de Goede
2022-05-19 16:09         ` Hans de Goede
2022-05-21  5:01           ` Linus Torvalds
2022-05-21 11:30             ` Thorsten Leemhuis
2022-05-09 23:06 ` Linux 5.18-rc6 Guenter Roeck

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=54664f6a-b046-1330-e794-cb533e942a94@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matthew.auld@intel.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=torvalds@linux-foundation.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).