public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Diego Calleja <diegocg@gmail.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	intel-gfx@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [Intel-gfx] -stable regression in Intel graphics, introduced in Linux 5.10.9
Date: Sun, 28 Feb 2021 17:57:30 +0100	[thread overview]
Message-ID: <YDvLeslGElXdjf2t@kroah.com> (raw)
In-Reply-To: <e662d6bf-53e3-9774-37db-9e7ea88a4ec9@redhat.com>

On Sun, Feb 28, 2021 at 05:28:06PM +0100, Hans de Goede wrote:
> Hi,
> 
> On 2/28/21 4:14 PM, Greg KH wrote:
> > On Sun, Feb 28, 2021 at 03:29:07PM +0100, Diego Calleja wrote:
> >> Hi,
> >>
> >> There is a regression in Linux 5.10.9 that does not happen in 5.10.8. It is still there as
> >> of 5.11.1
> > 
> > Is this the same issue reported here:
> > 	https://lore.kernel.org/r/f1070486-891a-8ec0-0390-b9aeb03178ce@redhat.com
> > ?
> > 
> > If so, is this a problem in 5.11 as well?
> 
> I see in the original email:
> https://lore.kernel.org/stable/3423617.kz1aARBMGD@archlinux/
> 
> That Diego is using the iGPU part of a Haswell CPU, so yes this is almost
> certainly the same issue.
> 
> Diego as I already mentioned to another arch user, it would be good if the
> arch kernel-maintainers can pick-up these 3 commits from the drm-intel tree
> as downstream patches for now:
> 
> e627d5923cae ("drm/i915/gt: One more flush for Baytrail clear residuals")
> d30bbd62b1bf ("drm/i915/gt: Flush before changing register state")
> 1914911f4aa0 ("drm/i915/gt: Correct surface base address for renderclear")
> 
> We (Fedora) have added these as downstream patches for now and we have
> multiple reports that these resolve the problem.
> 
> Chris, can you please send the 2nd and 3th commit of the above list on
> their way to Linus ASAP, so that Greg can add them to the stable series?
> 
> ATM only the 1st commit is in Linus tree (unless the others have landed
> with different hashes?)

I have queued the first one up now, thanks.

greg k-h

  reply	other threads:[~2021-02-28 16:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-28 14:29 -stable regression in Intel graphics, introduced in Linux 5.10.9 Diego Calleja
2021-02-28 15:14 ` Greg KH
2021-02-28 16:28   ` [Intel-gfx] " Hans de Goede
2021-02-28 16:57     ` Greg KH [this message]
2021-02-28 20:05   ` Diego Calleja
2021-03-01  9:09     ` Greg KH
2021-03-01 10:11       ` Diego Calleja
2021-03-01 10:24         ` Greg KH

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=YDvLeslGElXdjf2t@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=diegocg@gmail.com \
    --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