Comment # 5
on bug 106194
from Jon
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.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
