All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 103467] [NVC0/GF108] fifo: read fault at cd90f4d000 engine 07 [PFIFO] client 07 [BAR_READ] reason 00 [PT_NOT_PRESENT] on channel 1 [003fe11000 DRM]
Date: Thu, 26 Oct 2017 14:48:49 +0000	[thread overview]
Message-ID: <bug-103467-8800-aAZJ3AtRgp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103467-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 636 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=103467

--- Comment #2 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
Can you grab dmesg from the beginning, and boot with nouveau.debug=trace? Try
increasing the kernel log buffer, or send it over netconsole or something.

Note that no one has gotten this to work in the past (although few have tried
with any level of persistence).

I believe at last report, the issue was something to do with the color LUT
being set up wrong, although that's clearly not your present issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1572 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2017-10-26 14:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 14:36 [Bug 103467] New: [NVC0/GF108] fifo: read fault at cd90f4d000 engine 07 [PFIFO] client 07 [BAR_READ] reason 00 [PT_NOT_PRESENT] on channel 1 [003fe11000 DRM] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-103467-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-10-26 14:38   ` [Bug 103467] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-26 14:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-10-26 15:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-26 15:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-26 15:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-26 15:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-26 15:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-26 16:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-26 16:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-26 17:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-26 17:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-26 17:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-06 21:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-06 21:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-06 21:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-103467-8800-aAZJ3AtRgp@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.