From: lyude@redhat.com
To: Marek Czernohous <mczernohous@gmail.com>,
nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, Danilo Krummrich <dakr@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Ben Skeggs <bskeggs@nvidia.com>
Subject: Re: [PATCH v3 3/4] drm/nouveau/fifo/nv04: filter benign CACHE_ERROR from Mesa NV50 bind probe
Date: Thu, 20 Aug 2026 15:21:15 -0400 [thread overview]
Message-ID: <c07891a66d5373c12b2baf8ef97540b34169955f.camel@redhat.com> (raw)
In-Reply-To: <20260812231330.705425-4-mczernohous@gmail.com>
On Thu, 2026-08-13 at 01:13 +0200, Marek Czernohous wrote:
> + * chip that reaches this handler, not just on
> Tesla.
> + * Demote to debug to keep dmesg clean while still
> catching
> + * real CACHE_ERROR events.
> + */
> + if ((mthd & 0x1ffc) == 0x0060 &&
> + (data & 0xffffff00) == 0xbeef0200) {
> + nvkm_debug(subdev, "CACHE_ERROR - ch %d subc
> %d mthd %04x data %08x (benign, skipped)\n",
> + chid, (mthd >> 13) & 7, mthd &
> 0x1ffc, data);
> + } else {
> + chan = nvkm_chan_get_chid(&fifo->engine,
> chid, &flags);
> + nvkm_error(subdev, "CACHE_ERROR - ch %d [%s]
> subc %d mthd %04x data %08x\n",
> + chid, chan ? chan->name :
> "unknown",
> + (mthd >> 13) & 7, mthd & 0x1ffc,
> data);
> + nvkm_chan_put(&chan, flags);
> + }
I assume this won't break anything, but hindsight is always 20/20 - so,
I think we should probably keep the print of the channel name even when
demoting this to debug in case we have to investigate this someday. We
should also move the nvkm_chan_get_chid(…) call and nvkm_chan_put(…)
call out of the conditional, and probably move all of the printf
arguments into their own local variables in this function so there's
less to maintain for future changes.
> }
next prev parent reply other threads:[~2026-08-20 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 23:13 [PATCH v3 0/4] drm/nouveau: channel-kill event ordering fixes, and lower the gate to NV50 Marek Czernohous
2026-08-12 23:13 ` [PATCH v3 1/4] drm/nouveau: unsubscribe the channel-kill event before the fence context Marek Czernohous
2026-08-20 19:10 ` lyude
2026-08-12 23:13 ` [PATCH v3 2/4] drm/nouveau: subscribe to the channel-kill event after " Marek Czernohous
2026-08-20 20:01 ` lyude
2026-08-12 23:13 ` [PATCH v3 3/4] drm/nouveau/fifo/nv04: filter benign CACHE_ERROR from Mesa NV50 bind probe Marek Czernohous
2026-08-20 19:21 ` lyude [this message]
2026-08-12 23:13 ` [PATCH v3 4/4] drm/nouveau: subscribe to channel-kill events on NV50 and newer Marek Czernohous
2026-08-20 21:56 ` lyude
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=c07891a66d5373c12b2baf8ef97540b34169955f.camel@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@gmail.com \
--cc=bskeggs@nvidia.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mczernohous@gmail.com \
--cc=nouveau@lists.freedesktop.org \
--cc=simona@ffwll.ch \
/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®