https://bugs.freedesktop.org/show_bug.cgi?id=80618
Priority: medium Bug ID: 80618 Assignee: dri-devel@lists.freedesktop.org Summary: [r600g] XCOM Ennemy Unknown crash (RV770) Severity: normal Classification: Unclassified OS: Linux (All) Reporter: bioproduits@yahoo.fr Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI
Created attachment 101904 --> https://bugs.freedesktop.org/attachment.cgi?id=101904&action=edit dmesg
When playing xcom native, the game will always crash and return to desktop.
I have this message multiple times :
EE ../../../../../../src/gallium/drivers/r600/r600_shader.c:2198 r600_shader_from_tgsi - GPR limit exceeded - shader requires 755 registers EE ../../../../../../src/gallium/drivers/r600/r600_shader.c:157 r600_pipe_shader_create - translation from TGSI failed ! EE ../../../../../../src/gallium/drivers/r600/r600_state_common.c:750 r600_shader_select - Failed to build shader variant (type=1) -12 EE ../../../../../../src/gallium/drivers/r600/r600_shader.c:2198 r600_shader_from_tgsi - GPR limit exceeded - shader requires 755 registers EE ../../../../../../src/gallium/drivers/r600/r600_shader.c:157 r600_pipe_shader_create - translation from TGSI failed !
I attach dmesg and logfil of the game.
https://bugs.freedesktop.org/show_bug.cgi?id=80618
--- Comment #1 from nicolas bioproduits@yahoo.fr --- Created attachment 101905 --> https://bugs.freedesktop.org/attachment.cgi?id=101905&action=edit game log file
https://bugs.freedesktop.org/show_bug.cgi?id=80618
--- Comment #2 from Jan Kümmel freedesktop@snorc.org --- Does XCOM still crash when you use the memory corruption workaround from https://github.com/knecht/xcom-hacks ? See also: http://steamcommunity.com/app/200510/discussions/0/522730700169435716/
https://bugs.freedesktop.org/show_bug.cgi?id=80618
--- Comment #3 from nicolas bioproduits@yahoo.fr --- (In reply to comment #2)
Does XCOM still crash when you use the memory corruption workaround from https://github.com/knecht/xcom-hacks ? See also: http://steamcommunity.com/app/200510/discussions/0/522730700169435716/
hie, since my bug repport the game had an update but this doesn' solved my bug.
I have try to use this library, but because i only own Xcom ennemy unknown this won't work.
If i try to run like the explanations for ennemy within i have the splash screen and it quits, that is normal cause i don't have this game. So i tried to adapt to the game folders of ennemy unknown. What i've done is :
export LD_LIBRARY_PATH="~/.steam/steam/SteamApps/common/XCom-Enemy-Unknown/binaries/linux/x86_64/" cd ~/.steam/steam/SteamApps/common/XCom-Enemy-Unknown LD_PRELOAD=~/Téléchargements/xcom-hacks-master/libxcomfix.so binaries/linux/game.x86_64 szCmd: /bin/sh -c '"/home/nicolas/.steam/steam.sh" "steam://run/200510"' & sh: symbol lookup error: /home/nicolas/Téléchargements/xcom-hacks-master/libxcomfix.so: undefined symbol: dlsym Dumped crashlog to /home/nicolas/.local/share/feral-interactive/XCOM/crashes//19054cf4-ca78-8195-5d709904-5aa26fac.dmp Abandon (core dumped)
I assume there need to adapt libxcomfix.so to ennemy unknown, but i have no idea how to do that.
https://bugs.freedesktop.org/show_bug.cgi?id=80618
--- Comment #4 from Jan Kümmel freedesktop@snorc.org --- you didn't forget the -ldl when compiling, did you?
https://bugs.freedesktop.org/show_bug.cgi?id=80618
mirh mirh@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |mirh@protonmail.ch
--- Comment #5 from mirh mirh@protonmail.ch --- Could this be checked again? GPR limit problems should have been improved especially after bug 105371 (for the moment only in mesa-git)
https://bugs.freedesktop.org/show_bug.cgi?id=80618
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEEDINFO |RESOLVED
--- Comment #6 from Martin Peres martin.peres@free.fr --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/508.
dri-devel@lists.freedesktop.org