From: Paul Dufresne <dufresnep@zoho.com>
To: "nouveau" <nouveau@lists.freedesktop.org>
Subject: Re: [Nouveau] GPU MMU faults (was Meaning of the engines in paramaters of nouveau module)
Date: Tue, 05 Dec 2023 09:27:55 -0500 [thread overview]
Message-ID: <18c3a60dcc9.b6b5c07328625.5575400648759809450@zoho.com> (raw)
In-Reply-To: <CAPM=9tz6xA=iY617nCTpjW9haJzV=nhgbQfVVzkdG8GYphM+Ww@mail.gmail.com>
---- Le lun., 04 déc. 2023 22:27:49 -0500 Dave Airlie a écrit ----
> On Mon, 4 Dec 2023 at 05:04, Paul Dufresne dufresnep@zoho.com> wrote:
> >
> > In https://nouveau.freedesktop.org/KernelModuleParameters.html, there is:
> > Here is a list of engines:
> > DEVICE
> > DMAOBJ
...
> > PVP
> > SW
> > Also, in debug:
> > CLIENT
> >
...
> > Also, my interest is linked to the state of GPU graph given after a context switch timeout that looks like:
> > [ 1696.780305] nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
> > [ 1696.780361] nouveau 0000:01:00.0: fifo:000000:00[ gr]: 8006e005: busy 1 faulted 0 chsw 1 save 1 load 1 chid 5*-> chid 6
> > [ 1696.780422] nouveau 0000:01:00.0: fifo:000000:07[ ce2]: 00050005: busy 0 faulted 0 chsw 0 save 0 load 0 chid 5 -> chid 5
> > [ 1696.780476] nouveau 0000:01:00.0: fifo:000004:04[ ce0]: 00000000: busy 0 faulted 0 chsw 0 save 0 load 0 chid 0 -> chid 0
> > [ 1696.780529] nouveau 0000:01:00.0: fifo:000001:01[ mspdec]: 00000000: busy 0 faulted 0 chsw 0 save 0 load 0 chid 0 -> chid 0
> > [ 1696.780581] nouveau 0000:01:00.0: fifo:000002:02[ msppp]: 00000000: busy 0 faulted 0 chsw 0 save 0 load 0 chid 0 -> chid 0
> > [ 1696.780633] nouveau 0000:01:00.0: fifo:000003:03[ msvld]: 00000000: busy 0 faulted 0 chsw 0 save 0 load 0 chid 0 -> chid 0
> > [ 1696.780689] nouveau 0000:01:00.0: fifo:000000:00[ gr]: 8006e005: busy 1 faulted 0 chsw 1 save 1 load 1 chid 5*-> chid 6
> > [ 1696.780744] nouveau 0000:01:00.0: fifo:000000:00[ gr]: 8006e005: busy 1 faulted 0 chsw 1 save 1 load 1 chid 5*-> chid 6
> > [ 1696.780795] nouveau 0000:01:00.0: fifo:000000:00[ gr]: triggering mmu fault on 0x00
> > [ 1696.780835] nouveau 0000:01:00.0: fifo:000000:07[ ce2]: 00050005: busy 0 faulted 0 chsw 0 save 0 load 0 chid 5 -> chid 5
> > [ 1696.780942] nouveau 0000:01:00.0: fifo:000000:00[ gr]: 00000100: mmu fault triggered
> > [ 1696.780987] nouveau 0000:01:00.0: fifo:000000:00[ gr]: c006e005: busy 1 faulted 1 chsw 1 save 1 load 1 chid 5*-> chid 6
> > [ 1696.781040] nouveau 0000:01:00.0: fifo:000000:0005:[Renderer[13701]] rc scheduled
> >
> > where I suspect ce2, is linked to PCE2.
> >
> > Is there a documentation that describes those "engines"?
>
> CE is copy engine.
> But this looks like an mmu fault on the GPU side, so some shader is
> doing something wrong most likely.
>
> Dave.
>
Sometimes the GPU mmu fault is on a gr engine, sometimes on ce2 engine.
But the driver is stable when using nouveau.noaccel=1 (not seen other kind of errors too, like deadlock detections when using noaccel=1).
Looking at the code, I begin to think that noaccel=0 allows for user-side channel creation, and so create the need for context switching... not sure.
prev parent reply other threads:[~2023-12-05 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 19:04 [Nouveau] Meaning of the engines in paramaters of nouveau module Paul Dufresne
2023-12-05 3:27 ` Dave Airlie
2023-12-05 14:27 ` Paul Dufresne [this message]
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=18c3a60dcc9.b6b5c07328625.5575400648759809450@zoho.com \
--to=dufresnep@zoho.com \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).