From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 197103] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 / IP: nouveau_fbcon_set_suspend_work+0x45/0xf0 [nouveau]
Date: Sun, 08 Oct 2017 13:21:16 +0000 [thread overview]
Message-ID: <bug-197103-2300-lhTEx5bYo1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197103-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=197103
Pierre Moreau (pierre.morrow@free.fr) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pierre.morrow@free.fr
--- Comment #3 from Pierre Moreau (pierre.morrow@free.fr) ---
Nouveau bugs, regardless of whether they lie in the kernel, Mesa or the Nouveau
DDX, should be reported at bugs.freedesktop.org (see
https://nouveau.freedesktop.org/wiki/Bugs/). You might want to add yourself to
the freedesktop bug, as updates are more likely to happen in that bug report
than this one.
Updates to this bug report are sent to the dri-devel mailing list, but not
every Nouveau developer follows it.
I’ll give 4.14-rc3 a try on my laptop (Optimus + GK107 as well).
--
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-10-08 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 7:27 [Bug 197103] New: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 / IP: nouveau_fbcon_set_suspend_work+0x45/0xf0 [nouveau] bugzilla-daemon
2017-10-02 7:30 ` [Bug 197103] " bugzilla-daemon
2017-10-08 10:57 ` bugzilla-daemon
2017-10-08 13:21 ` bugzilla-daemon [this message]
2017-10-17 16:14 ` bugzilla-daemon
2017-10-29 12:29 ` bugzilla-daemon
2017-10-30 6:12 ` 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-197103-2300-lhTEx5bYo1@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.