This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 with default plasma (5.16.5), or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the !18.0.1-1 works well! This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor somehow by suspend and re-enable it after login. Use fe.: Xrender before login / before the system restored from suspend. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:ffffb7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0000000000000202 RBX: 0000000000000202 RCX: 000000000000046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0000000000000001 RSI: 0000000000000202 RDI: 0000000000000002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: ffffb7b54274b870 R08: 0000000000000000 R09: ffff94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: ffffb7b54274b708 R11: ffffb7b54274b70c R12: ffff94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: ffff94d970f2c300 R14: ffff94da758d25d0 R15: ffff94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 00007f2a1b9bea80(0000) GS:ffff94da87c40000(0000) knlGS:0000000000000000 Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 00007fb083e9b4a5 CR3: 000000012c110000 CR4: 00000000003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309290] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309370] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309376] do_vfs_ioctl+0x407/0x670 Oct 21 10:57:26 pc kernel: [ 9475.309379] ? do_futex+0x10f/0x1e0 Oct 21 10:57:26 pc kernel: [ 9475.309382] ksys_ioctl+0x67/0x90 Oct 21 10:57:26 pc kernel: [ 9475.309384] __x64_sys_ioctl+0x1a/0x20 Oct 21 10:57:26 pc kernel: [ 9475.309388] do_syscall_64+0x57/0x190 Oct 21 10:57:26 pc kernel: [ 9475.309392] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 27 0d 00 f7 d8 64 89 01 48 Oct 21 10:57:26 pc kernel: [ 9475.309398] RSP: 002b:00007ffe0e27c518 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Oct 21 10:57:26 pc kernel: [ 9475.309400] RAX: ffffffffffffffda RBX: 00007ffe0e27c550 RCX: 00007f2a1bd0c67b Oct 21 10:57:26 pc kernel: [ 9475.309401] RDX: 00007ffe0e27c550 RSI: 00000000c06864a2 RDI: 000000000000000d Oct 21 10:57:26 pc kernel: [ 9475.309402] RBP: 00000000c06864a2 R08: 0000000000000000 R09: 0000562bcc215600 Oct 21 10:57:26 pc kernel: [ 9475.309403] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 Oct 21 10:57:26 pc kernel: [ 9475.309404] R13: 000000000000000d R14: 0000562bcb275db0 R15: 0000000000000000 Oct 21 10:57:26 pc kernel: [ 9475.309407] ---[ end trace cae28d1e69119104 ]--- Oct 21 10:57:26 pc kernel: [ 9475.309432] ------------[ cut here ]---------
>xserver-xorg-video-amdgpu: 19.* or the newest from git, the !18.0.1-1 works well! Maybe you can bisect and see exactly where it breaks. If an update of xserver causes an issue it implies it's an issue lower down the stack. Also your syslog implies that. If it freezes, then we should be able to get a backtrace of the frozen state. Switch to a real VT and run "sudo gdb --pid `pidof kwin_x11` " then "set logging on" "set pagination off" "thread apply all bt" which should leave a file called gdb.txt in your home dir.
This is not easy. How can I debug a process and use the sleep function on its GUI parallelly? This is what I have however it doesn't seem to be usable: Thread 1 "kwin_x11" received signal SIGINT, Interrupt. [34m0x00007f5de717bc2f[m in [33m__GI___poll[m ([36mfds[m=0x7ffd491ea8b8, [36mnfds[m=1, [36mtimeout[m=-1) at [32m../sysdeps/unix/sysv/linux/poll.c[m:29 29 in [32m../sysdeps/unix/sysv/linux/poll.c[m Quit Quit Error detected on fd 0 error detected on stdin [Inferior 1 (process 2121) detached] Exception ignored in: <gdb.GdbOutputFile object at 0x7f03ff1c7e50> Traceback (most recent call last): File "/usr/share/gdb/python/gdb/__init__.py", line 43, in flush def flush(self): KeyboardInterrupt
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!