Comment # 7
on bug 103953
from Luke McKee
As suggested to the users here, I've tried your latest staging branch with dc=1 On a Polaris RX560 latest everything (libva-git,vdpau-git,mesa-git,xf86-amdgpu-git,amd-drm-staging-next master 4.15-rc4). It seems the other users here are using DRI2. I'll try again with DRI3. What happens here is when gdm is used (with and without wayland compiled in enabled) I think it switches vt's when you sign in. After logging in the screen get's scrambled. This is all I could find useful in the logs. Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: (EE) AMDGPU(0): failed to set mode: Invalid argument Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: (WW) AMDGPU(0): Failed to set mode on CRTC 0 Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: (EE) AMDGPU(0): Failed to enable any CRTC Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: (EE) Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: Fatal server error: Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: (EE) EnterVT failed for screen 0 Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: (EE) Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: Please consult the The X.Org Foundation support Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: at http://wiki.x.org Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: for help. Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: (EE) Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: (II) AIGLX: Suspending AIGLX clients for VT switch Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: (EE) Server terminated with error (1). Closing log file. The h265 will crash the pc too if you try and encode with ffmpeg. updating libva to git and trying again. Feb 28 08:02:28 hojuruku kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring uvd timeout, last signaled seq=20269, last emitted seq=20270 Feb 28 08:02:28 hojuruku kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring uvd_enc0 timeout, last signaled seq=2306, last emitted seq=2308 Feb 28 08:02:28 hojuruku kernel: [drm] IP block:gmc_v8_0 is hung! Feb 28 08:02:28 hojuruku kernel: [drm] IP block:gfx_v8_0 is hung! Feb 28 08:02:28 hojuruku kernel: [drm] IP block:uvd_v6_0 is hung! Feb 28 08:02:28 hojuruku kernel: [drm] IP block:gmc_v8_0 is hung! Feb 28 08:02:28 hojuruku kernel: [drm] IP block:gfx_v8_0 is hung! Feb 28 08:02:28 hojuruku kernel: [drm] GPU recovery disabled. Feb 28 08:02:28 hojuruku kernel: [drm] IP block:uvd_v6_0 is hung! Feb 28 08:02:28 hojuruku kernel: [drm] GPU recovery disabled. Another issue I've noticed is that there are kernel panic's if amd-iommu isn't compiled as a kernel module even if you don't have the hardware. Shall I open another ticket about that?
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
