From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196189] [BISECTED][REGRESSION] Nouveau on NVA8 renders the system unusable
Date: Sun, 25 Jun 2017 14:44:15 +0000 [thread overview]
Message-ID: <bug-196189-2300-OkLHrup9O0@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196189-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196189
Ilia Mirkin (imirkin@alum.mit.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |imirkin@alum.mit.edu
--- Comment #1 from Ilia Mirkin (imirkin@alum.mit.edu) ---
The case of the OOB messages should already be fixed in mainline, and I suspect
they are unrelated to your issue. (I assume you see them on the commit prior to
the one you bisected to as well?)
To get more nouveau debugging messages, you can do nouveau.debug=debug or
nouveau.debug=trace.
Thank you for doing the bisect - that is very useful. Most graphics-related
bugs are actually not hosted on the kernel bugzilla. I wish there were some way
to indicate this. See
https://nouveau.freedesktop.org/wiki/Bugs/
for the proper procedure to file nouveau bugs (although I believe this holds
for all graphics drivers).
--
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
next prev parent reply other threads:[~2017-06-25 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 12:03 [Bug 196189] New: [BISECTED][REGRESSION] Nouveau on NVA8 renders the system unusable bugzilla-daemon
2017-06-25 14:44 ` bugzilla-daemon [this message]
2017-06-25 17:13 ` [Bug 196189] " 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-196189-2300-OkLHrup9O0@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.