From: mikhail <mikhail.v.gavrilov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Marek Olšák" <maraeo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: All games maded with Unity engine in steam catalog crashes on AMD GPU, but worked on Intel GPU on same machine.
Date: Thu, 01 Feb 2018 21:27:34 +0500 [thread overview]
Message-ID: <1517502454.21706.3.camel@gmail.com> (raw)
In-Reply-To: <CAAxE2A4vOw-uK1rNFPWCpE933B7mJwYt3V-vq4hpxeuGwzQV2w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, 2018-01-30 at 22:38 +0100, Marek Olšák wrote:
> On Tue, Jan 30, 2018 at 10:36 PM, Marek Olšák <maraeo@gmail.com>
> wrote:
> > On Tue, Jan 30, 2018 at 10:04 PM, mikhail <mikhail.v.gavrilov@gmail
> > .com> wrote:
> > > On Tue, 2018-01-30 at 20:12 +0100, Marek Olšák wrote:
> > > > Can you record an apitrace on a driver that is not radeonsi?
> > >
> > > All traces from five listed games was recorded on Intel GPU (not
> > > radeonsi).
> > > I also understood why for some games traces was not recorded
> > > yesterday.
> > > It happens because such games are 32 bit and for correct working
> > > apitrace was needed apitrace-libs-7.1-7.fc27.i686 package, but
> > > only
> > > apitrace-libs-7.1-7.fc27.x86_64 was installed.
> > >
> > > > If yes, can you correctly replay the apitrace on a driver that
> > > > is not
> > > > radeonsi?
> > >
> > > All traces was correctly replayed on Intel GPU (not radeonsi).
> > >
> > > > If yes, can you reproduce the crash if you replay the apitrace
> > > > on
> > > > radeonsi?
> > >
> > > All traces also was correctly replayed on AMD Vega 56 GPU
> > > (radeonsi)
> > > without crashes.
> > >
> > > What does this give us?
> > >
> > > Anyway launching listed games under AMD Vega 56 GPU lead to new
> > > crases.
> >
> > Thanks. It's possible that Unity contains its own version of LLVM
> > or
> > its own version of some standard libraries that LLVM uses, and
> > radeonsi doesn't like when games replace its dependencies.
>
> It's also possible that some symbols exported by Unity clash with
> those exported by LLVM.
>
> Marek
>
I am created thread in Unity forum with describeb issue and link to
this thread:
https://forum.unity.com/threads/all-games-maded-with-unity-engine-crash
es-on-amd-gpu-but-worked-on-intel-gpu-on-same-machine.515193/#post-3376
548
And got answer from Tak:
This looks like a driver crash in free/delete after
mesa_glsl_link_shader.
I don't believe that Unity is duplicating these symbols (as concluded
in the freedesktop thread) - as far as I can tell, this is all in the
radeonsi driver.
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2018-02-01 16:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 16:15 All games maded with Unity engine in steam catalog crashes on AMD GPU, but worked on Intel GPU on same machine mikhail
[not found] ` <1517156104.15379.10.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-29 15:40 ` Marek Olšák
[not found] ` <CAAxE2A53JUCvPQsKDQ-NYzDp1ixkZrHqHb=3nUKOQWT6t+5wKw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-29 17:19 ` mikhail
[not found] ` <1517246354.5736.2.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-29 17:34 ` Marek Olšák
[not found] ` <CAAxE2A792+0WB0LSn6wYcHGcZQVuOsrYzXdYbPgOJkYM+vJnFQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-29 17:51 ` mikhail
[not found] ` <1517248296.11388.3.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-29 18:18 ` Marek Olšák
[not found] ` <CAAxE2A6+Vnr0zs7T0cLSUcvxUin=tbCO_Mjb2+qCSx5aJ9bbYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-30 18:08 ` mikhail
[not found] ` <1517335699.9211.8.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-30 19:12 ` Marek Olšák
2018-01-30 21:04 ` mikhail
[not found] ` <1517346270.6516.7.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-30 21:36 ` Marek Olšák
[not found] ` <CAAxE2A6aeHYAdVZo1ND14BP3JN=kP1Y4m83k0QVXDpBWCGJvQQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-30 21:38 ` Marek Olšák
[not found] ` <CAAxE2A4vOw-uK1rNFPWCpE933B7mJwYt3V-vq4hpxeuGwzQV2w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-01 16:27 ` mikhail [this message]
[not found] ` <1517502454.21706.3.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-01 17:34 ` Marek Olšák
[not found] ` <CAAxE2A771dnvh249kbgvmb-1-mnP_1fGpWkPvhQQ7gCUppsf2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-01 18:39 ` mikhail
[not found] ` <1517510384.18433.3.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-01 20:31 ` Marek Olšák
[not found] ` <CAAxE2A42A-bjU=qhZqRH-6aaJXbKDjxjj=Obyrk2-CC1BAbtig-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-02 16:13 ` mikhail
[not found] ` <1517587985.12783.5.camel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-02 16:25 ` Michel Dänzer
2018-02-02 16:46 ` Marek Olšák
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=1517502454.21706.3.camel@gmail.com \
--to=mikhail.v.gavrilov-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=maraeo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.