All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 80922] New: XCOM :Enemy Unknown will crash and kill the output after some time.
Date: Fri, 04 Jul 2014 17:46:41 +0000	[thread overview]
Message-ID: <bug-80922-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1753 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=80922

          Priority: medium
            Bug ID: 80922
          Assignee: dri-devel@lists.freedesktop.org
           Summary: XCOM :Enemy Unknown will crash and kill the output
                    after some time.
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: half-shot@molrams.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

Created attachment 102280
  --> https://bugs.freedesktop.org/attachment.cgi?id=102280&action=edit
glxinfo

Wish I could describe it better but there is no better words. The game will
lock up the card and the monitor output will go blank, although once I got
lucky and it crashed to the terminal spewing errors about radeon. Due to the
fact that the system crashes the only. This crash usually happens during a
gameplay sequence and has not happened in a menu as of yet. The crash also will
usually recover the first time after loosing visual output for 10 seconds but
then will cut out a second (or rarely a third) and not return to the game.

Due to it crashing randomly (no specific scene causing it) and always requiring
about a hour of play, would it make sense to be a memory issue?

It did not occur to me that I would need Dmesg output, if its needed then
remind me and I will reproduce another crash with the log file.

I also have a apitrace, but it totals 23GB and I do not know which bit would
need trimming.


System Specs:

AMD PhenomII X6 T55
AMD RadeonHD 7950
Mesa 10.3.0-devel (git-370184e)
LLVM 3.5.0 (svn)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3163 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

             reply	other threads:[~2014-07-04 17:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04 17:46 bugzilla-daemon [this message]
2015-08-02 10:38 ` [Bug 80922] XCOM :Enemy Unknown will crash and kill the output after some time bugzilla-daemon
2015-08-02 11:57 ` bugzilla-daemon
2015-08-02 12:38 ` 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-80922-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.