From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 110258] Lenovo V110-15AST AMD A9-9410 AMD R5 Stoney hangs after waking after suspend. 5.0-5.1rc2 Date: Thu, 18 Jul 2019 10:50:25 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1513094595==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 689D66E395 for ; Thu, 18 Jul 2019 10:50:25 +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 --===============1513094595== Content-Type: multipart/alternative; boundary="15634470252.f922b.30623" Content-Transfer-Encoding: 7bit --15634470252.f922b.30623 Date: Thu, 18 Jul 2019 10:50:25 +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=3D110258 --- Comment #8 from Paul Gover --- Git bisect: 106c7d6148e5aadd394e6701f7e498df49b869d1 is the first bad commit commit 106c7d6148e5aadd394e6701f7e498df49b869d1 Author: Likun Gao Date: Thu Nov 8 20:19:54 2018 +0800 drm/amdgpu: abstract the function of enter/exit safe mode for RLC Abstract the function of amdgpu_gfx_rlc_enter/exit_safe_mode and some p= art of rlc_init to improve the reusability of RLC. Signed-off-by: Likun Gao Acked-by: Christian K=C3=B6nig Reviewed-by: Alex Deucher Signed-off-by: Alex Deucher :040000 040000 8f3b365496f3bbd380a62032f20642ace51c8fef e14ec968011019e3f601df3f15682bb9ae0bafc6 M drivers This run on my HP 15-bw0xx cpu:AMD A9-9420 RADEON R5, 5 COMPUTE CORES 2C+3G with integrated graphics: Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98E4] I get the same symptoms as above; a more involved scenario that may shed light is to switch to a tty and stop= xdm (and hence sddm) so I have no graphics sessions running. pm-suspend followed by resume works and brings me back to the tty, but when= I then start xdm, I get a broken screen, usually garbage or grey, and syslog shows something like the following: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq= =3D49, emitted seq=3D51 [drm] IP block:gfx_v8_0 is hung! [drm] GPU recovery disabled. If I enable amdgpu.gpu_recovery=3D1 kernel: [ 279.726475] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=3D57, emitted seq=3D59 kernel: [ 279.726536] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process X pid 2860 thread X:cs0 pid 2861 kernel: [ 279.726542] [drm] IP block:gfx_v8_0 is hung! kernel: [ 279.726609] amdgpu 0000:00:01.0: GPU reset begin! kernel: [ 279.726992] amdgpu 0000:00:01.0: GRBM_SOFT_RESET=3D0x000F0001 kernel: [ 279.727047] amdgpu 0000:00:01.0: SRBM_SOFT_RESET=3D0x00000100 kernel: [ 279.863162] [drm] recover vram bo from shadow start kernel: [ 279.863164] [drm] recover vram bo from shadow done kernel: [ 279.863166] [drm] Skip scheduling IBs! kernel: [ 279.863191] amdgpu 0000:00:01.0: GPU reset(2) succeeded! kernel: [ 280.015794] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! I can probably run diagnostics or collect a trace if someone tells me what = and how. The problem persists - I still get it running kernel 5.2.1 --=20 You are receiving this mail because: You are the assignee for the bug.= --15634470252.f922b.30623 Date: Thu, 18 Jul 2019 10:50:25 +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 # 8 on bug 11025= 8 from Paul Gover
Git bisect:

106c7d6148e5aadd394e6701f7e498df49b869d1 is the first bad commit
commit 106c7d6148e5aadd394e6701f7e498df49b869d1
Author: Likun Gao <Likun.Gao=
4;amd.com>
Date:   Thu Nov 8 20:19:54 2018 +0800

    drm/amdgpu: abstract the function of enter/exit safe mode for RLC

    Abstract the function of amdgpu_gfx_rlc_enter/exit_safe_mode and some p=
art
of
    rlc_init to improve the reusability of RLC.

    Signed-off-by: Likun Gao <L=
ikun.Gao@amd.com>
    Acked-by: Christian K=C3=B6nig <christian.koenig@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

:040000 040000 8f3b365496f3bbd380a62032f20642ace51c8fef
e14ec968011019e3f601df3f15682bb9ae0bafc6 M      drivers

This run on my HP 15-bw0xx
cpu:AMD A9-9420 RADEON R5, 5 COMPUTE CORES 2C+3G
with integrated graphics:
Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98E4]

I get the same symptoms as above;
a more involved scenario that may shed light is to switch to a tty and stop=
 xdm
(and hence sddm) so I have no graphics sessions running.
pm-suspend followed by resume works and brings me back to the tty, but when=
 I
then start xdm, I get a broken screen, usually garbage or grey, and syslog
shows something like the following:
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=
=3D49,
emitted seq=3D51
[drm] IP block:gfx_v8_0 is hung!
[drm] GPU recovery disabled.

If I enable amdgpu.gpu_recovery=3D1
kernel: [  279.726475] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, signaled seq=3D57, emitted seq=3D59
kernel: [  279.726536] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process
information: process X pid 2860 thread X:cs0 pid 2861
kernel: [  279.726542] [drm] IP block:gfx_v8_0 is hung!
kernel: [  279.726609] amdgpu 0000:00:01.0: GPU reset begin!
kernel: [  279.726992] amdgpu 0000:00:01.0: GRBM_SOFT_RESET=3D0x000F0001
kernel: [  279.727047] amdgpu 0000:00:01.0: SRBM_SOFT_RESET=3D0x00000100
kernel: [  279.863162] [drm] recover vram bo from shadow start
kernel: [  279.863164] [drm] recover vram bo from shadow done
kernel: [  279.863166] [drm] Skip scheduling IBs!
kernel: [  279.863191] amdgpu 0000:00:01.0: GPU reset(2) succeeded!
kernel: [  280.015794] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to
initialize parser -125!

I can probably run diagnostics or collect a trace if someone tells me what =
and
how.

The problem persists - I still get it running kernel 5.2.1


You are receiving this mail because:
  • You are the assignee for the bug.
= --15634470252.f922b.30623-- --===============1513094595== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1513094595==--