From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 107300] [REGRESSION] NULL pointer dereference when waking up monitor Date: Thu, 19 Jul 2018 21:41:19 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1663469322==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id D05246E04E for ; Thu, 19 Jul 2018 21:41:19 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1663469322== Content-Type: multipart/alternative; boundary="15320364790.edEc.14843" Content-Transfer-Encoding: 7bit --15320364790.edEc.14843 Date: Thu, 19 Jul 2018 21:41:19 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D107300 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=3D140719&action=3Dedit 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 keyboa= rd. About a third of the time, the login screen comes up, and there's no respon= se. SSH then dmesg points to an amazingly well crafted NULL pointer dereference= in [amdgpu]. Surprisingly, this isn't some 4billionk triple-gazillion monitor setup, whi= ch I've always had driver issues with. This issue happens with a single displa= y. For fast access, this is the backtrace:=20 [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 --=20 You are receiving this mail because: You are the assignee for the bug.= --15320364790.edEc.14843 Date: Thu, 19 Jul 2018 21:41:19 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
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 [details]<=
/span>
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 keyboa=
rd.

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

Surprisingly, this isn't some 4billionk triple-gazillion monitor setup, whi=
ch
I've always had driver issues with. This issue happens with a single displa=
y.

For fast access, this is the backtrace:=20
[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.
= --15320364790.edEc.14843-- --===============1663469322== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1663469322==--