From: Lyude Paul <lyude@redhat.com>
To: dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Cc: "Timur Tabi" <ttabi@nvidia.com>,
"Dave Airlie" <airlied@redhat.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Ben Skeggs" <bskeggs@nvidia.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Ben Skeggs" <bskeggs@redhat.com>,
"David Airlie" <airlied@gmail.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Maxime Ripard" <mripard@kernel.org>,
"Danilo Krummrich" <dakr@kernel.org>,
"Lyude Paul" <lyude@redhat.com>
Subject: [PATCH 0/2] drm/nouveau: Fix cursor-related display hang
Date: Fri, 19 Dec 2025 16:52:01 -0500 [thread overview]
Message-ID: <20251219215344.170852-1-lyude@redhat.com> (raw)
This is a fix for one of the many issues I've been finding on my brand
new desktop. This one in particular is easy to hit if you have a cursor
with a continously updating surface between two displays, what fun!
Reminds me of a another bug from long ago…
Lyude Paul (2):
drm/nouveau/disp/nv50-: Set lock_core in curs507a_prepare
drm/nouveau/kms/nv50-: Assert we hold nv50_disp->lock in
nv50_head_flush_*
drivers/gpu/drm/nouveau/dispnv50/curs507a.c | 1 +
drivers/gpu/drm/nouveau/dispnv50/head.c | 5 +++++
2 files changed, 6 insertions(+)
base-commit: 8e7460eac786c72f48c4e04ce9be692b939428ce
--
2.52.0
next reply other threads:[~2025-12-19 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 21:52 Lyude Paul [this message]
2025-12-19 21:52 ` [PATCH 1/2] drm/nouveau/disp/nv50-: Set lock_core in curs507a_prepare Lyude Paul
2025-12-19 21:52 ` [PATCH 2/2] drm/nouveau/kms/nv50-: Assert we hold nv50_disp->lock in nv50_head_flush_* Lyude Paul
2026-01-13 22:26 ` [PATCH 0/2] drm/nouveau: Fix cursor-related display hang Dave Airlie
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=20251219215344.170852-1-lyude@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=bskeggs@nvidia.com \
--cc=bskeggs@redhat.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=simona@ffwll.ch \
--cc=ttabi@nvidia.com \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®