From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199133] New: nouveau_mem_host+0x47/0x1b0 [nouveau]: NULL pointer dereference at 0000000000000040
Date: Sat, 17 Mar 2018 10:27:21 +0000 [thread overview]
Message-ID: <bug-199133-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=199133
Bug ID: 199133
Summary: nouveau_mem_host+0x47/0x1b0 [nouveau]: NULL pointer
dereference at 0000000000000040
Product: Drivers
Version: 2.5
Kernel Version: 4.15.8-300.fc27.x86_64
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: hectorcavalcantisaavedra@gmail.com
Regression: No
Created attachment 274787
--> https://bugzilla.kernel.org/attachment.cgi?id=274787&action=edit
Details on the kernel oops.
The nouveau driver causes kernel oops after the new DRM changes. I can
reproduce by using my system for a few minutes, mainly when using Chromium or
opening a PDF file (on Evince or on Chromium).
--
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 reply other threads:[~2018-03-17 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 10:27 bugzilla-daemon [this message]
2018-03-17 10:27 ` [Bug 199133] nouveau_mem_host+0x47/0x1b0 [nouveau]: NULL pointer dereference at 0000000000000040 bugzilla-daemon
2018-03-17 10:28 ` bugzilla-daemon
2018-03-17 14:36 ` bugzilla-daemon
2018-03-18 10:50 ` 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-199133-2300@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.