From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103246] PoE: GPU hang with mesa >= 17.2.0 + gallium-nine
Date: Wed, 11 Apr 2018 18:11:26 +0000 [thread overview]
Message-ID: <bug-103246-502-S1pLy8keQ1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103246-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1651 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103246
iive@yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |regression
--- Comment #1 from iive@yahoo.com ---
The symptoms are typical for shader infinite loop, followed by botched driver
restart. Definitely not Wine fault.
Does the bug still happen with current mesa3d+llvm?
While the game is free, it would still be good idea if you can create an
apitrace recording of a place where the game crashes. Ask in #d3d9 at
irc.freenode about the ftp access, or use google drive or similar file sharing.
(We might use the trace for regression testing in future).
It might be good idea if you also fill bugreport to the github Ixit/Mesa-3D
issue tracker.
I usually place the apitrace wrapper d3d9.dll inside the game directory (main
or where game.exe is). Then using `winecfg` add library override for "d3d9" to
be "native, built-in".
If everything goes well, the wrapper would create a new trace inside the game
directory every time the game is started. So don't forget to remove it when you
are done.
Naturally, use working mesa3d version for the trace. Then install new version
of mesa and check if the trace crashes.
If you can compile mesa3d on your own, you might be able to help narrow down
the problem further. I cannot do that, since my card is using the R600 driver,
so it is very unlikely to have the same shader miscompilation.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2948 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-11 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 18:20 [Bug 103246] PoE: GPU hang with mesa >= 17.2.0 + gallium-nine bugzilla-daemon
2018-04-11 18:11 ` bugzilla-daemon [this message]
2018-04-11 18:21 ` bugzilla-daemon
2018-05-13 17:50 ` bugzilla-daemon
2018-05-13 18:12 ` 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-103246-502-S1pLy8keQ1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox