All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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	[thread overview]
Message-ID: <bug-109048-502-bVjw3xTyar@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109048-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1055 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=109048

--- Comment #6 from Henri Valta <cg@jakorasia.info> ---
(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 crash
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 = GL_TEXTURE_1D, level = 0, internalformat =
3, width = 256, border = 0, format = GL_RGB, type = GL_UNSIGNED_BYTE, pixels =
blob(768)) // incomplete"

so does this mean the trace for the glTexImage1D is not executed with the trace
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.

[-- Attachment #1.2: Type: text/html, Size: 1970 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-02-13  9:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13  8:51 [Bug 109048] Penumbra Overture crash in radeonsi_dri.so bugzilla-daemon
2018-12-13  8:51 ` bugzilla-daemon
2018-12-13  8:53 ` bugzilla-daemon
2018-12-13  9:11 ` [Bug 109048] [amdgpu] [apitrace] " bugzilla-daemon
2018-12-13  9:12 ` [Bug 109048] [amdgpu] [apitrace] Penumbra Overture crash in radeonsi_dri.so on RX580 bugzilla-daemon
2019-02-12 11:57 ` bugzilla-daemon
2019-02-12 19:26 ` bugzilla-daemon
2019-02-12 23:15 ` bugzilla-daemon
2019-02-13  9:11 ` bugzilla-daemon [this message]
2019-02-13  9:55 ` bugzilla-daemon
2019-02-13 10:20 ` bugzilla-daemon
2019-02-13 10:21 ` bugzilla-daemon
2019-02-13 19:05 ` bugzilla-daemon
2019-02-13 20:37 ` bugzilla-daemon
2019-02-17 23:10 ` bugzilla-daemon
2019-02-17 23:11 ` bugzilla-daemon
2019-02-18  8:33 ` bugzilla-daemon
2019-02-18  8:43 ` bugzilla-daemon
2019-09-09  0:34 ` bugzilla-daemon
2019-09-25 18:44 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-109048-502-bVjw3xTyar@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.