From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109048] [amdgpu] [apitrace] Penumbra Overture crash in radeonsi_dri.so on RX580 Date: Wed, 13 Feb 2019 09:11:40 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0717198710==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id E38846E2B2 for ; Wed, 13 Feb 2019 09:11:39 +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 --===============0717198710== Content-Type: multipart/alternative; boundary="15500490990.Fa6BF6C.1256" Content-Transfer-Encoding: 7bit --15500490990.Fa6BF6C.1256 Date: Wed, 13 Feb 2019 09:11:39 +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=3D109048 --- Comment #6 from Henri Valta --- (In reply to Timothy Arceri from comment #5) > I just tried a build of 18.3.3 and it didn't crash for me either. Just to= be > clear, does the trace actually crash for you? Or does it only happen when > your running the game? I thought the trace also crashed, but now checking more closely I see the c= rash I saw in coredumpctl list was from the recording run, not the replay run. Is there any way to maybe make the trace more useful? I see the last line with verbose replay says "49801900 @0 glTexImage1D(target =3D GL_TEXTURE_1D, level =3D 0, internalfo= rmat =3D 3, width =3D 256, border =3D 0, format =3D GL_RGB, type =3D GL_UNSIGNED_BYT= E, pixels =3D blob(768)) // incomplete" so does this mean the trace for the glTexImage1D is not executed with the t= race as it's incomplete? I believe this is the command where the crash happens, according to the backtrace --=20 You are receiving this mail because: You are the assignee for the bug.= --15500490990.Fa6BF6C.1256 Date: Wed, 13 Feb 2019 09:11:39 +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 # 6 on bug 10904= 8 from = Henri Valta 
(In reply to Timothy Arceri from comment #5)
> I just tried a build of 18.3.3 and it didn't cra=
sh for me either. Just to be
> clear, does the trace actually crash for you? Or does it only happen w=
hen
> your running the game?

I thought the trace also crashed, but now checking more closely I see the c=
rash
I saw in coredumpctl list was from the recording run, not the replay run.

Is there any way to maybe make the trace more useful?

I see the last line with verbose replay says
"49801900 @0 glTexImage1D(target =3D GL_TEXTURE_1D, level =3D 0, i=
nternalformat =3D
3, width =3D 256, border =3D 0, format =3D GL_RGB, type =3D GL_UNSIGNED_BYT=
E, pixels =3D
blob(768)) // incomplete"

so does this mean the trace for the glTexImage1D is not executed with the t=
race
as it's incomplete? I believe this is the command where the crash happens,
according to the backtrace

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