All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106194] AMDGPU RIP: dm_update_crtcs_state on kernel 4.17rc2
Date: Sat, 28 Apr 2018 20:14:52 +0000	[thread overview]
Message-ID: <bug-106194-502-58uKMymjiQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106194-502@http.bugs.freedesktop.org/>


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

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

--- Comment #5 from Jon <jonemilj@gmail.com> ---
I might be having the same issue, however my stack looks a bit different,
perhaps due to different kernel commits and the way it is triggered. Can you
guys trigger this hang by locking the window manager session/screen and waiting
for the display(s) to go to sleep? That's how I can reliably trigger my similar
hang.

april 28 20:16:49 beist.localdomain kernel: kernel BUG at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:4708!               
april 28 20:16:49 beist.localdomain kernel: invalid opcode: 0000 [#1] SMP NOPTI 
april 28 20:16:49 beist.localdomain kernel: RIP:
0010:dm_update_crtcs_state+0x397/0x410 [amdgpu] 
...
april 28 20:16:49 beist.localdomain kernel: Call Trace:                         
april 28 20:16:49 beist.localdomain kernel:  amdgpu_dm_atomic_check+0x182/0x3b0
[amdgpu]                                                                        
april 28 20:16:49 beist.localdomain kernel:  drm_atomic_check_only+0x33a/0x4f0
[drm]                                                                           
april 28 20:16:49 beist.localdomain kernel:  drm_atomic_commit+0x13/0x50 [drm]  
april 28 20:16:49 beist.localdomain kernel: 
drm_atomic_connector_commit_dpms+0xe5/0xf0 [drm]                                
april 28 20:16:49 beist.localdomain kernel: 
drm_mode_obj_set_property_ioctl+0x174/0x290 [drm]                               
april 28 20:16:49 beist.localdomain kernel:  ?
drm_mode_connector_set_obj_prop+0x70/0x70 [drm]                                 
april 28 20:16:49 beist.localdomain kernel: 
drm_mode_connector_property_set_ioctl+0x3e/0x60 [drm]                           
april 28 20:16:49 beist.localdomain kernel:  drm_ioctl_kernel+0x5b/0xb0 [drm]   
april 28 20:16:49 beist.localdomain kernel:  drm_ioctl+0x2c3/0x360 [drm]        
april 28 20:16:49 beist.localdomain kernel:  ?
drm_mode_connector_set_obj_prop+0x70/0x70 [drm]                                 
april 28 20:16:49 beist.localdomain kernel:  amdgpu_drm_ioctl+0x49/0x80
[amdgpu]                                                                        
april 28 20:16:49 beist.localdomain kernel:  do_vfs_ioctl+0xa4/0x620            
april 28 20:16:49 beist.localdomain kernel:  ksys_ioctl+0x70/0x80               
april 28 20:16:49 beist.localdomain kernel:  __x64_sys_ioctl+0x16/0x20          
april 28 20:16:49 beist.localdomain kernel:  do_syscall_64+0x5b/0x160           
april 28 20:16:49 beist.localdomain kernel: 
entry_SYSCALL_64_after_hwframe+0x44/0xa9                                        
april 28 20:16:49 beist.localdomain kernel: RIP: 0033:0x7f7d092cc0f7

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

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

  parent reply	other threads:[~2018-04-28 20:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 17:18 [Bug 106194] AMD Fury X system freeze on kernel 4.17rc2 bugzilla-daemon
2018-04-23 17:21 ` [Bug 106194] AMDGPU RIP: dm_update_crtcs_state " bugzilla-daemon
2018-04-25  6:34 ` bugzilla-daemon
2018-04-28 15:13 ` bugzilla-daemon
2018-04-28 15:15 ` bugzilla-daemon
2018-04-28 15:19 ` bugzilla-daemon
2018-04-28 17:24 ` bugzilla-daemon
2018-04-28 20:14 ` bugzilla-daemon [this message]
2018-04-28 21:12 ` bugzilla-daemon
2018-04-29  5:05 ` bugzilla-daemon
2018-05-02 16:49 ` bugzilla-daemon
2018-05-07  0:41 ` bugzilla-daemon
2018-05-08  5:26 ` bugzilla-daemon
2018-05-09 15:41 ` bugzilla-daemon
2018-05-16 20:42 ` 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-106194-502-58uKMymjiQ@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.