From: Hans de Goede <firstname.lastname@example.org>
To: Maarten Lankhorst <email@example.com>,
Jani Nikula <firstname.lastname@example.org>,
Joonas Lahtinen <email@example.com>,
Rodrigo Vivi <firstname.lastname@example.org>,
Tvrtko Ursulin <email@example.com>
Cc: intel-gfx <firstname.lastname@example.org>,
Subject: [5.18 regression] drm/i915 BYT rendering broken due to "Remove short-term pins from execbuf, v6"
Date: Sun, 8 May 2022 16:38:32 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
When running a 5.18-rc4 (and -rc5) kernel on a Chuwi Hi 8, which is
a Bay Trail based tablet with 2G RAM and a 1200x1920 DSI panel.
I noticed that gnome-shell was misrendering. Many UI elements were
missing (they were all black) and at the gdm login screen (which is
a special gnome-shell session) the screen often was entirely black
until I move the cursor around and then various things got
highlighted after which they sometimes stuck around and sometimes
they disappeared again after the highlight.
Since this problem does not happen with various 5.17.y kernels I
believe that this is a kernel regression in 5.18. I've bisected this
and the bisect points to:
commit b5cfe6f7a6e1 ("drm/i915: Remove short-term pins from execbuf, v6.")
from Maarten. This commit cleanly reverts on top of 5.18-rc5 and
I can confirm that 5.18-rc5 with b5cfe6f7a6e1 reverted fixes things.
I would be more then happy to test any possible fixes for this.
next reply other threads:[~2022-05-08 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 14:38 Hans de Goede [this message]
2022-05-09 7:01 ` [5.18 regression] drm/i915 BYT rendering broken due to "Remove short-term pins from execbuf, v6" Thorsten Leemhuis
2022-05-13 8:18 ` [5.18 regression] drm/i915 BYT rendering broken due to "Remove short-term pins from execbuf, v6" #forregzbot Thorsten Leemhuis
2022-05-09 9:15 ` [5.18 regression] drm/i915 BYT rendering broken due to "Remove short-term pins from execbuf, v6" Tvrtko Ursulin
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).