From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94984] XCom2 crashes with SIGSEGV on radeonsi
Date: Sun, 17 Apr 2016 20:00:17 +0000 [thread overview]
Message-ID: <bug-94984-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1282 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94984
Bug ID: 94984
Summary: XCom2 crashes with SIGSEGV on radeonsi
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: kuehner.moritz@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 123016
--> https://bugs.freedesktop.org/attachment.cgi?id=123016&action=edit
gdb backtrace
At the start of a mission XCom2 crashes the moment when the drop solders of cut
scene ends. It doesn't happen in all maps only in this one as far as I can
tell.
I'm running Ubuntu 16.04 on an skylake CPU with a R9 380X. The crash happens
with stock Ubuntu mesa (11.2) as well as with mesa git
(git160414232200.eeff133) from padoka PPA.
I tried to create a apitrace, but for some reason I can not get XCom2 to start
with "apitrace trace" in front of it. Are there any apitrace ninja secrets to
tracing steam games ;-)? (The game is 64bit so thats not the problem).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2701 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 reply other threads:[~2016-04-17 20:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 20:00 bugzilla-daemon [this message]
2016-04-17 20:01 ` [Bug 94984] XCom2 crashes with SIGSEGV on radeonsi bugzilla-daemon
2016-04-18 3:06 ` bugzilla-daemon
2016-04-18 19:05 ` bugzilla-daemon
2016-04-21 13:04 ` bugzilla-daemon
2016-04-21 21:18 ` bugzilla-daemon
2016-04-21 21:20 ` bugzilla-daemon
2016-04-22 7:40 ` bugzilla-daemon
2016-04-22 9:02 ` bugzilla-daemon
2016-04-22 23:51 ` bugzilla-daemon
2016-04-23 2:53 ` bugzilla-daemon
2016-04-23 3:38 ` bugzilla-daemon
2016-04-25 8:30 ` bugzilla-daemon
2016-09-22 11:23 ` bugzilla-daemon
2016-09-27 10:19 ` bugzilla-daemon
2016-09-27 18:30 ` 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-94984-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 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.