From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89377] [radeonsi] "Hand of Fate" is stuck on SIGPWR/SIGXCPU after start
Date: Sun, 01 Mar 2015 16:48:37 +0000 [thread overview]
Message-ID: <bug-89377-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2418 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=89377
Bug ID: 89377
Summary: [radeonsi] "Hand of Fate" is stuck on SIGPWR/SIGXCPU
after start
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: kai@dev.carbon-project.org
QA Contact: dri-devel@lists.freedesktop.org
Blocks: 77449
The Unity3D-based (Mono) game "Hand of Fate" is stuck on a black screen after
the initial static screens (logos) and just the music is playing. If I attach
GDB to the game I see SIGPWR being received by the game, pressing c just get's
me another such signal, sometimes the endless SIGPWR stream is broken by a
SIGXCPU or two.
This sounds oddly reminiscent of bug #60929, but I'm not seeing this with any
other Mono-based game besides "Hand of Fate". And since I haven't managed to
start the game with R600_LLVM=0, I can't verify, whether this is the same bug
or a different one.
Please also note, that there seems to be a similar issue (ie. same effect) with
this game, that can be fixed by rebooting most of the time, if I go by the
forums. See e.g.
<http://steamcommunity.com/app/266510/discussions/0/617329150700428644/#c617329150701149465>,
where the developer recommends this procedure. Not sure, if those two are
related.
My current stack (Debian testing as a base) is:
GPU: Hawaii PRO [Radeon R9 290] (ChipID = 0x67b1)
Mesa: Git:master/050bf75c8b
libdrm: Git:master/1f73578df3
LLVM: SVN:trunk/r230209 (3.7 devel)
X.Org: Git:master/xorg-server-1.17.1
Linux: 3.19.0
Firmware: <http://people.freedesktop.org/~agd5f/radeon_ucode/>
> 9e05820da42549ce9c89d147cf1f8e19 hawaii_ce.bin
> c8bab593090fc54f239c8d7596c8d846 hawaii_mc.bin
> 3618dbb955d8a84970e262bb2e6d2a16 hawaii_me.bin
> c000b0fc9ff6582145f66504b0ec9597 hawaii_mec.bin
> 0643ad24b3beff2214cce533e094c1b7 hawaii_pfp.bin
> ba6054b7d78184a74602fd81607e1386 hawaii_rlc.bin
> 11288f635737331b69de9ee82fe04898 hawaii_sdma.bin
> 284429675a5560e0fad42aa982965fc2 hawaii_smc.bin
libclc: Git:master/5cd2688a9f
DDX: Git:master/b8ec9ed4fe
Let me know, if you need something else.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4237 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-03-01 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 16:48 bugzilla-daemon [this message]
2015-03-01 21:15 ` [Bug 89377] [radeonsi] "Hand of Fate" is stuck on SIGPWR/SIGXCPU after start bugzilla-daemon
2015-03-02 11:02 ` 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-89377-502@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;
as well as URLs for NNTP newsgroup(s).