From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 103953] [DC] Polaris10: Missing modes when enabling DC Date: Wed, 28 Feb 2018 01:42:11 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0714096322==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 3D4A76E868 for ; Wed, 28 Feb 2018 01:42:11 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0714096322== Content-Type: multipart/alternative; boundary="15197821310.71F7Ca6.19362" Content-Transfer-Encoding: 7bit --15197821310.71F7Ca6.19362 Date: Wed, 28 Feb 2018 01:42:11 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D103953 --- Comment #7 from Luke McKee --- As suggested to the users here, I've tried your latest staging branch with dc=3D1 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 sc= reen 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 er= ror: Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: (EE) EnterVT fa= iled 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=3D20269, last emitted seq=3D20270 Feb 28 08:02:28 hojuruku kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring uvd_enc0 timeout, last signaled seq=3D2306, last emitted seq=3D2308 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 is= n't compiled as a kernel module even if you don't have the hardware. Shall I op= en another ticket about that? --=20 You are receiving this mail because: You are the assignee for the bug.= --15197821310.71F7Ca6.19362 Date: Wed, 28 Feb 2018 01:42:11 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 7 on bug 10395= 3 from Luke McKee 
As suggested to the users here,

I've tried your latest staging branch with dc=3D1
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 sc=
reen
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 er=
ror:
Feb 28 00:48:26 hojuruku /usr/libexec/gdm-x-session[20032]: (EE) EnterVT fa=
iled
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 inform=
ation.
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=3D20269, last emitted seq=3D20270
Feb 28 08:02:28 hojuruku kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR*
ring uvd_enc0 timeout, last signaled seq=3D2306, last emitted seq=3D2308
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 is=
n't
compiled as a kernel module even if you don't have the hardware. Shall I op=
en
another ticket about that?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15197821310.71F7Ca6.19362-- --===============0714096322== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0714096322==--