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: Mon, 30 Oct 2017 06:12:37 +0000 [thread overview]
Message-ID: <bug-197103-2300-Ra5c2VHPOx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197103-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=197103
Igor Gnatenko (i.gnatenko.brain@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |CODE_FIX
--- Comment #6 from Igor Gnatenko (i.gnatenko.brain@gmail.com) ---
(In reply to Thorsten Leemhuis from comment #5)
> Is this still happening? There was a patch recently to fix oops without
> fbdev emulation:
> https://git.kernel.org/torvalds/c/4813766325374af6ed0b66879ba6a0bbb05c83b6
Doesn't seem to be happening anymore with Linux version
4.14.0-0.rc6.git3.2.fc28.x86_64 (mockbuild@buildvm-02.phx2.fedoraproject.org)
(gcc version 7.2.1 20170829 (Red Hat 7.2.1-1) (GCC)) #1 SMP Thu Oct 26 21:53:34
UTC 2017
--
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
prev parent reply other threads:[~2017-10-30 6:12 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
2017-10-17 16:14 ` bugzilla-daemon
2017-10-29 12:29 ` bugzilla-daemon
2017-10-30 6:12 ` bugzilla-daemon [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=bug-197103-2300-Ra5c2VHPOx@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.