All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107595] amd-staging-drm-next: BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 - R4 Mullins
Date: Thu, 16 Aug 2018 19:32:25 +0000	[thread overview]
Message-ID: <bug-107595-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1236 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107595

            Bug ID: 107595
           Summary: amd-staging-drm-next: BUG: unable to handle kernel
                    NULL pointer dereference at 0000000000000018 - R4
                    Mullins
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: soprwa@gmail.com

Created attachment 141148
  --> https://bugs.freedesktop.org/attachment.cgi?id=141148&action=edit
oops kernel message

Booting latest amd-staging-drm-next is causing kernel OOPS.

Hardware is Lenovo netbook G50-45 A6 6310 APU with R4 Mullins. Kernel booted
with "amdgpu.dc=1" and "amdgpu.dpm=1". 

Blank eDP screen can be caused by another bug:
https://bugs.freedesktop.org/show_bug.cgi?id=106940, but three is no picture on
connected HDMI monitor also (opposite to the situation in mentioned bug
report).

Panic message, that I've got from pstore, attached.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2874 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

             reply	other threads:[~2018-08-16 19:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 19:32 bugzilla-daemon [this message]
2018-08-16 19:52 ` [Bug 107595] amd-staging-drm-next: BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 - R4 Mullins bugzilla-daemon
2018-08-16 20:57 ` bugzilla-daemon
2018-08-16 23:49 ` bugzilla-daemon
2018-08-17  5:21 ` bugzilla-daemon
2018-08-17  6:53 ` bugzilla-daemon
2018-08-23 10:45 ` bugzilla-daemon
2018-08-23 12:02 ` bugzilla-daemon
2018-08-23 12:09 ` bugzilla-daemon
2018-08-23 13:19 ` bugzilla-daemon
2018-08-23 14:04 ` bugzilla-daemon
2018-09-10 11:00 ` bugzilla-daemon
2018-09-16  9:01 ` bugzilla-daemon
2018-09-17  9:36 ` bugzilla-daemon
2018-09-17 14:43 ` 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-107595-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.