From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 101325] UE4Editor crash after pressing "play" with radeon southern island card (7850 HD) Date: Tue, 13 Jun 2017 16:30:38 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1897344684==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2BB496E34C for ; Tue, 13 Jun 2017 16:30:38 +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 --===============1897344684== Content-Type: multipart/alternative; boundary="14973714381.eD9ccF.11215"; charset="UTF-8" --14973714381.eD9ccF.11215 Date: Tue, 13 Jun 2017 16:30:38 +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=3D101325 --- Comment #10 from Julien Isorce --- Hi Luke, I can reproduce the ring stalled issue using your apitrace 100% of the time. In apitrace output I could notice: warning: extension `GL_EXT_gpu_shader4' unsupported in fragment shader message: api issue 4: FBO incomplete: no attachments and default width or height is 0 [-1] message: api performance issue 5: using glBufferSubData(buffer 1599, offset= 0, size 288) to update a GL_STATIC_DRAW buffer message: shader compiler issue 2: LLVM diagnostic (remark): :0:0: = 895 instructions in function message: shader compiler issue 3: too many identical messages; ignoring Using GALLIUM_DDEBUG and check_vm I could get some msg like: [1;32mPS - Constant buffer slot 4 (GPU list):ESC[0m ESC[1;33mSQ_BUF_RSRC_WORD0ESC[0m <- 0x000de0e0 ESC[1;33mSQ_BUF_RSRC_WORD1ESC[0m <- BASE_ADDRESS_HI =3D 0 STRIDE =3D 7200 (0x1c20) CACHE_SWIZZLE =3D 0 SWIZZLE_ENABLE =3D 0 ESC[1;33mSQ_BUF_RSRC_WORD2ESC[0m <- 0x4000c007 ESC[1;33mSQ_BUF_RSRC_WORD3ESC[0m <- DST_SEL_X =3D SQ_SEL_X DST_SEL_Y =3D SQ_SEL_0 DST_SEL_Z =3D SQ_SEL_0 DST_SEL_W =3D SQ_SEL_1 NUM_FORMAT =3D BUF_NUM_FORMAT_UNORM DATA_FORMAT =3D BUF_DATA_FORMAT_INVALID ELEMENT_SIZE =3D 2 INDEX_STRIDE =3D 2 ADD_TID_ENABLE =3D 1 ATC =3D 0 HASH_ENABLE =3D 0 HEAP =3D 0 MTYPE =3D 2 TYPE =3D SQ_RSRC_BUF_RSVD_2 USER_VM_ENABLE =3D 0 USER_VM_MODE =3D 1 NV =3D 0 !!!!! This slot was corrupted in GPU memory !!!!! I am using lastest git mesa, xserver, ddx, llvm and amd-staging-4.9 kernel. Similar result with amdgpu though it does not detect the gpu hang, all I can see is with radeontop, the graphic pipe is stuck at 100% for ever, but no e= rror in dmesg. And indeed R600_DEBUG=3Dnowc does not help in that case. I have the feeling that this is a llvm issue due to exotic shaders but only maintainers will be able to help you at this point.=20 Providing this is 100% reproductible on SI chip class (at least) on both ra= deon and amdgpu drivers, it would be intersting to know if it happens on a more recent graphic card too. --=20 You are receiving this mail because: You are the assignee for the bug.= --14973714381.eD9ccF.11215 Date: Tue, 13 Jun 2017 16:30:38 +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

Comme= nt # 10 on bug 10132= 5 from Julien Isorce 
Hi Luke,

I can reproduce the ring stalled issue using your apitrace 100% of the time.

In apitrace output I could notice:
warning: extension `GL_EXT_gpu_shader4' unsupported in fragment shader
message: api issue 4: FBO incomplete: no attachments and default width or
height is 0 [-1]
message: api performance issue 5: using glBufferSubData(buffer 1599, offset=
 0,
size 288) to update a GL_STATIC_DRAW buffer
message: shader compiler issue 2: LLVM diagnostic (remark): <unknown>=
:0:0: 895
instructions in function
message: shader compiler issue 3: too many identical messages; ignoring

Using GALLIUM_DDEBUG and check_vm I could get some msg like:


[1;32mPS - Constant buffer slot 4 (GPU list):ESC[0m
        ESC[1;33mSQ_BUF_RSRC_WORD0ESC[0m <- 0x000de0e0
        ESC[1;33mSQ_BUF_RSRC_WORD1ESC[0m <- BASE_ADDRESS_HI =3D 0
                             STRIDE =3D 7200 (0x1c20)
                             CACHE_SWIZZLE =3D 0
                             SWIZZLE_ENABLE =3D 0
        ESC[1;33mSQ_BUF_RSRC_WORD2ESC[0m <- 0x4000c007
        ESC[1;33mSQ_BUF_RSRC_WORD3ESC[0m <- DST_SEL_X =3D SQ_SEL_X
                             DST_SEL_Y =3D SQ_SEL_0
                             DST_SEL_Z =3D SQ_SEL_0
                             DST_SEL_W =3D SQ_SEL_1
                             NUM_FORMAT =3D BUF_NUM_FORMAT_UNORM
                             DATA_FORMAT =3D BUF_DATA_FORMAT_INVALID
                             ELEMENT_SIZE =3D 2
                             INDEX_STRIDE =3D 2
                             ADD_TID_ENABLE =3D 1
                             ATC =3D 0
                             HASH_ENABLE =3D 0
                             HEAP =3D 0
                             MTYPE =3D 2
                             TYPE =3D SQ_RSRC_BUF_RSVD_2
                             USER_VM_ENABLE =3D 0
                             USER_VM_MODE =3D 1
                             NV =3D 0
!!!!! This slot was corrupted in GPU memory !!!!!

I am using lastest git mesa, xserver, ddx, llvm and amd-staging-4.9 kernel.

Similar result with amdgpu though it does not detect the gpu hang, all I can
see is with radeontop, the graphic pipe is stuck at 100% for ever, but no e=
rror
in dmesg.

And indeed R600_DEBUG=3Dnowc does not help in that case.

I have the feeling that this is a llvm issue due to exotic shaders but only
maintainers will be able to help you at this point.=20

Providing this is 100% reproductible on SI chip class (at least) on both ra=
deon
and amdgpu drivers, it would be intersting to know if it happens on a more
recent graphic card too.

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