From: Diego Calleja <diegocg@gmail.com>
To: intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: -stable regression in Intel graphics, introduced in Linux 5.10.9
Date: Sun, 28 Feb 2021 15:29:07 +0100 [thread overview]
Message-ID: <3423617.kz1aARBMGD@archlinux> (raw)
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
This regression consists in graphics artifacts that will *only* start appearing after resuming
from suspend. They don't happen immediately after resuming from suspend either, but
after some minutes.
My system has integrated intel graphics
00:02.0 VGA compatible controller: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller])
CPU: Intel(R) Core(TM) i3-4170T CPU @ 3.20GHz
For reference, this is the list of i915 commits that went into 5.10.9.
commit ecca0c675bdecebdeb2f2eb76fb33520c441dacf
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Mon Jan 11 22:52:19 2021 +0000
drm/i915/gt: Restore clear-residual mitigations for Ivybridge, Baytrail
commit 09aa9e45863e9e25dfbf350bae89fc3c2964482c upstream.
commit de3f572607c29f7fdd1bfd754646d08e32db0249
Author: Imre Deak <imre.deak@intel.com>
Date: Wed Dec 9 17:39:52 2020 +0200
drm/i915/icl: Fix initing the DSI DSC power refcount during HW readout
commit 2af5268180410b874fc06be91a1b2fbb22b1be0c upstream.
commit 54c9246a47fa8559c3ec6da2048e976a4b8750f6
Author: Hans de Goede <hdegoede@redhat.com>
Date: Wed Nov 18 13:40:58 2020 +0100
drm/i915/dsi: Use unconditional msleep for the panel_on_delay when there is no reset-deassert MIPI-sequence
commit 00cb645fd7e29bdd20967cd20fa8f77bcdf422f9 upstream.
commit 0a34addcdbd9e03e3f3d09bcd5a1719d90b2d637
Author: Jani Nikula <jani.nikula@intel.com>
Date: Fri Jan 8 17:28:41 2021 +0200
drm/i915/backlight: fix CPU mode backlight takeover on LPT
commit bb83d5fb550bb7db75b29e6342417fda2bbb691c upstream.
commit 48b8c6689efa7cd65a72f620940a4f234b944b73
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Mon Jan 11 22:52:18 2021 +0000
drm/i915/gt: Limit VFE threads based on GT
commit ffaf97899c4a58b9fefb11534f730785443611a8 upstream.
commit 481e27f050732b8c680f26287dd44967fddf9a79
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Mon Jan 11 22:52:20 2021 +0000
drm/i915: Allow the sysadmin to override security mitigations
commit 984cadea032b103c5824a5f29d0a36b3e9df6333 upstream.
Regards
next reply other threads:[~2021-02-28 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 14:29 Diego Calleja [this message]
2021-02-28 15:14 ` -stable regression in Intel graphics, introduced in Linux 5.10.9 Greg KH
2021-02-28 16:28 ` [Intel-gfx] " Hans de Goede
2021-02-28 16:57 ` Greg KH
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=3423617.kz1aARBMGD@archlinux \
--to=diegocg@gmail.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