All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93809] playing Just Cause causes system crash
Date: Thu, 21 Jan 2016 14:37:03 +0000	[thread overview]
Message-ID: <bug-93809-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 93809
           Summary: playing Just Cause causes system crash
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: aaalmosss@gmail.com

It happens randomly, usually when lots of things are happening, like during
settlement takeovers. The screen freezes, sound stops, and only the magic sysrq
keys are working.

GPU is Radeon R9 270x, Linux 4.3.3, libdrm 2.4.66, Mesa 11.1.1, wine 1.7.55. I
also tried gallium nine, and that made it more unstable, it crashes even when
just riding around. BTW nine doesn't help with the horrible performance (5-15
fps), but it introduces several graphical glitches.

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

[-- Attachment #1.2: Type: text/html, Size: 2200 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:[~2016-01-21 14:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21 14:37 bugzilla-daemon [this message]
2016-12-29 13:42 ` [Bug 93809] playing Just Cause causes system crash bugzilla-daemon
2019-11-19  9:11 ` 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-93809-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.