-
Notifications
You must be signed in to change notification settings - Fork 343
rootston: blackscreen and freeze after switching to and from X #1359
Comments
Can you provide debug logs? |
@emersion Can you say what you're looking for exactly? Do you just want stdout+stderr from rootston or something else? |
After looking for logs, I found this in dmesg: [70050.542745] WARNING: CPU: 0 PID: 27920 at /build/linux-CuEUJv/linux-4.15.0/drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:3786 prepare_flip_isr+0x6c/0x70 [amdgpu] so looking like it's a problem with amdgpu. |
Ah, interesting. Yeah, this is definitely an amdgpu bug. |
Sorry for the noise. |
Nah, no problem. You should report this to amdgpu, they have a bug tracker on freedesktop.org. |
Just a note to those that have the same issues: After a bit of experimenting, it seems the bug causes even kernel panics for newer versions of the kernel/amdgpu. However the issue is most probably related to atomic modesetting and disabling atomic in wlroots can be used as a workaround - by using the |
Extra note: if |
Thanks, updated my comment. |
@emersion That extra note could be added to https://github.com/swaywm/wlroots/blob/master/docs/env_vars.md |
Sure, can you send a pull request? |
FWIW, this was from kernel 4.15. I tested 4.18 and rootston worked but wayfire locked up the machine without setting WLR_DRM_NO_ATOMIC=1. With kernel 4.19, rootston and wayfire launch fine (without disabling atomic) and I am able to switch to and from X without lockup so far. |
After starting rootston drm and switching to X, switching back to rootston (more often than not) results in blackscreen and renders the keyboard useless. The only way I've found to recover is ssh in and kill rootston. This also happens in wayfire. This is a backtrace from gdb while rootston is in this state:
The text was updated successfully, but these errors were encountered: