All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107300] [REGRESSION] NULL pointer dereference when waking up monitor
Date: Thu, 19 Jul 2018 21:41:19 +0000	[thread overview]
Message-ID: <bug-107300-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 107300
           Summary: [REGRESSION] NULL pointer dereference when waking up
                    monitor
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: mr.nuke.me@gmail.com

Created attachment 140719
  --> https://bugs.freedesktop.org/attachment.cgi?id=140719&action=edit
dmesg

I'm noticing this with linux-17.6 on an RX 480, but did not experience this
problem with linux-4.16 and earlier.

I let the machine  without any input for a while, and it automatically puts the
monitor to sleep. To wake up the screen, I move the mouse or hit the keyboard.

About a third of the time, the login screen comes up, and there's no response.
SSH then dmesg points to an amazingly well crafted NULL pointer dereference in
[amdgpu].

Surprisingly, this isn't some 4billionk triple-gazillion monitor setup, which
I've always had driver issues with. This issue happens with a single display.

For fast access, this is the backtrace: 
[59233.951991] Call Trace:
[59233.952068]  dm_update_crtcs_state+0x26c/0x4d0 [amdgpu]
[59233.952140]  amdgpu_dm_atomic_check+0x1b1/0x3b0 [amdgpu]
[59233.952172]  drm_atomic_check_only+0x360/0x4f0 [drm]
[59233.952192]  drm_atomic_commit+0x13/0x50 [drm]
[59233.952211]  drm_atomic_connector_commit_dpms+0xdb/0x100 [drm]
[59233.952230]  drm_mode_obj_set_property_ioctl+0x178/0x280 [drm]
[59233.952249]  ? drm_mode_connector_set_obj_prop+0x80/0x80 [drm]
[59233.952266]  drm_mode_connector_property_set_ioctl+0x39/0x60 [drm]
[59233.952283]  drm_ioctl_kernel+0x5b/0xb0 [drm]
[59233.952300]  drm_ioctl+0x1b3/0x370 [drm]
[59233.952318]  ? drm_mode_connector_set_obj_prop+0x80/0x80 [drm]
[59233.952375]  amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
[59233.952382]  do_vfs_ioctl+0xa4/0x610
[59233.952386]  ksys_ioctl+0x60/0x90
[59233.952389]  __x64_sys_ioctl+0x16/0x20
[59233.952394]  do_syscall_64+0x5b/0x160
[59233.952399]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

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

[-- Attachment #1.2: Type: text/html, Size: 3700 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-07-19 21:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19 21:41 bugzilla-daemon [this message]
2018-07-20  7:42 ` [Bug 107300] [REGRESSION] NULL pointer dereference when waking up monitor bugzilla-daemon
2018-08-05 17:11 ` bugzilla-daemon
2019-11-19  8:44 ` 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-107300-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.