From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98915] NULL pointer dereference on boot - amdgpu_debugfs_add_files
Date: Wed, 30 Nov 2016 15:33:48 +0000 [thread overview]
Message-ID: <bug-98915-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 885 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98915
Bug ID: 98915
Summary: NULL pointer dereference on boot -
amdgpu_debugfs_add_files
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: major
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: rafael.ristovski@gmail.com
Created attachment 128289
--> https://bugs.freedesktop.org/attachment.cgi?id=128289&action=edit
Kernel log
When booting linux-next version 20161129+ (iirc 20161128 worked fine) the
kernel spits out a null pointer deref. which can be traced to
amdgpu_debugfs_add_files.
Kernel log attached.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2283 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-11-30 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 15:33 bugzilla-daemon [this message]
2016-11-30 15:35 ` [Bug 98915] NULL pointer dereference on boot - amdgpu_debugfs_add_files bugzilla-daemon
2016-11-30 15:50 ` bugzilla-daemon
2016-12-03 10:11 ` bugzilla-daemon
2016-12-03 10:14 ` bugzilla-daemon
2016-12-03 23:37 ` bugzilla-daemon
2016-12-05 11:43 ` bugzilla-daemon
2016-12-10 11:28 ` 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-98915-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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.