All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206781] GM104 (GeForce 840m) with many errors "fifo: SCHED_ERROR 20"
Date: Sat, 07 Mar 2020 22:25:49 +0000	[thread overview]
Message-ID: <bug-206781-2300-rUpVziiaUe@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206781-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=206781

Ilia Mirkin (imirkin@alum.mit.edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |imirkin@alum.mit.edu

--- Comment #1 from Ilia Mirkin (imirkin@alum.mit.edu) ---
As mentioned on IRC, the MMIO faults at the start aren't anything to worry
about.

These two I've never seen before:

nouveau 0000:07:00.0: fifo: fault 01 [WRITE] at 0000000000150000 engine 05
[BAR2] client 08 [HUB/HOST_CPU_NB] reason 02 [PTE] on channel -1 [007fd38000
unknown]
nouveau 0000:07:00.0: fifo: fault 01 [WRITE] at 0000000000000000 engine 05
[BAR2] client 08 [HUB/HOST_CPU_NB] reason 0a [UNSUPPORTED_APERTURE] on channel
-1 [007fd38000 unknown]

And the SCHED thing is most frequently due to the ctxsw firmware timing out or
other error. But given the faults above, could easily be follow-on from that.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-03-07 22:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-07 21:41 [Bug 206781] New: GM104 (GeForce 840m) with many errors "fifo: SCHED_ERROR 20" bugzilla-daemon
2020-03-07 22:25 ` bugzilla-daemon [this message]
2020-03-08 11:16 ` [Bug 206781] " bugzilla-daemon

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=bug-206781-2300-rUpVziiaUe@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@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.