All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199653] New: [AMDGPU][DC] BUG: unable to handle kernel NULL pointer dereference (trace decoded)
Date: Tue, 08 May 2018 09:09:59 +0000	[thread overview]
Message-ID: <bug-199653-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=199653

            Bug ID: 199653
           Summary: [AMDGPU][DC] BUG: unable to handle kernel NULL pointer
                    dereference (trace decoded)
           Product: Drivers
           Version: 2.5
    Kernel Version: drm-next-4.18-wip (agd5f, AMDGPU)
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: marcus.husar@gmail.com
        Regression: No

Created attachment 275827
  --> https://bugzilla.kernel.org/attachment.cgi?id=275827&action=edit
Call trace of crash decoded with decode_stacktrace.sh

kernel: BUG: unable to handle kernel NULL pointer dereference at
00000000000002e4

This happens multiple times a day on my machine. It leads to a complete system
freeze. Yesterday I was lucky and got a stack trace.

It mostly happens browsing the web with Firefox (WebRender enabled, XWayland,
Gnome-Shell) when the cursor moves or rotates. But it can happen anywhere and
anytime.

The used kernel is from branch drm-next-4.18-wip@92fb374 of Alex Deucher, AMD
(agd5f). See: git://people.freedesktop.org/~agd5f/linux.

My machine:
 * Hardware name: Acer Swift SF315-41/Becks_RR, BIOS V1.04 01/09/2018
 * Ryzen Mobile 2500U
 * Firmware: VCN: 1.73 (latest available version)
 * My kernel is tainted because the i2c designware driver emits a warning
during
   boot. This should be unrelated to AMDGPU
   (see attachment i2c_designware_trace.txt).

Please ask if anything else is needed.

-- 
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

             reply	other threads:[~2018-05-08  9:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08  9:09 bugzilla-daemon [this message]
2018-05-08  9:10 ` [Bug 199653] [AMDGPU][DC] BUG: unable to handle kernel NULL pointer dereference (trace decoded) bugzilla-daemon
2018-05-08  9:13 ` bugzilla-daemon
2018-05-08  9:13 ` bugzilla-daemon
2018-05-29 12:25 ` bugzilla-daemon
2018-06-16 16:30 ` bugzilla-daemon
2018-06-16 18:23 ` bugzilla-daemon
2018-06-20 19:57 ` bugzilla-daemon
2018-07-13 20:03 ` bugzilla-daemon
2018-08-06 10:33 ` bugzilla-daemon
2018-08-06 11:05 ` bugzilla-daemon
2018-08-17 11:37 ` 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-199653-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.