From: Dave Airlie <airlied@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: nouveau@lists.freedesktop.org, dakr@kernel.org
Subject: [PATCH] [RFC] nouveau: hack fix for regression from 6.2
Date: Tue, 7 Jan 2025 16:46:00 +1000 [thread overview]
Message-ID: <20250107064600.536897-1-airlied@gmail.com> (raw)
From: Dave Airlie <airlied@redhat.com>
I recently got a regression report for RHEL 8.10 with a multi-card
GP106 setup. This led me down a rabbit hole of a few problems,
I've sent the cross-fence device fix but this is also needed to
make things work properly.
Hopefully I can at least work out how to restrict this to pre-Ampere
maybe? or find something else
This reverts 6762510bc8447dc4eb4c3d99541de6b31843e649
Author: Ben Skeggs <bskeggs@redhat.com>
Date: Wed Jun 1 20:48:08 2022 +1000
drm/nouveau/gr/gf100-: call FECS WFI_GOLDEN_SAVE method
The symptoms are on a dual GPU (turing and pascal) gnome-shell
gets a lot of
nouveau 0000:01:00.0: gr: DATA_ERROR 0000009c [] ch 2 [017fd2f000 gnome-shell[1554]] subc 0 class c597 mthd 0d78 data 00000004
and nothing renders on the second GPU (the data errors are on the primary GPU).
---
drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgf100.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgf100.c b/drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgf100.c
index cb390e0134a23..fa4c2174ea089 100644
--- a/drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgf100.c
+++ b/drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgf100.c
@@ -1514,7 +1514,7 @@ gf100_grctx_generate(struct gf100_gr *gr, struct gf100_gr_chan *chan, struct nvk
grctx->main(chan);
- if (!gr->firmware) {
+ if (1) {// {!gr->firmware) {
/* Trigger a context unload by unsetting the "next channel valid" bit
* and faking a context switch interrupt.
*/
--
2.43.0
reply other threads:[~2025-01-07 6:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250107064600.536897-1-airlied@gmail.com \
--to=airlied@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.