All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90481] Radeonsi driver, X crash while playing "Spec ops: the line"
Date: Mon, 23 Jan 2017 10:52:58 +0000	[thread overview]
Message-ID: <bug-90481-502-tNRpdB7qze@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-90481-502@http.bugs.freedesktop.org/>


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

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

--- Comment #27 from Samuel Pitoiset <samuel.pitoiset@gmail.com> ---
(In reply to Ryan Williams from comment #26)
> Tested with recent mesa git, Ubuntu 16.04 Padoka PPA, kernel 4.8.11, no gpu
> lockup with ~2 hour play. Probably fixed by same commit that fixed Arkham
> Origins in Wine and XCOM:EU.

If you have a VI+ card and this commit e490b7812cae778c61004971d86dc8299b6cd240
in your build, that would make sense. But the original ticket is for SI. Should
probably be closed because mesa 10.5 is very old though.

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

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

  parent reply	other threads:[~2017-01-23 10:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-16 14:59 [Bug 90481] Radeon R9 270X gpu lockup in game spec ops: the line bugzilla-daemon
2015-05-16 19:54 ` bugzilla-daemon
2015-05-17 18:37 ` bugzilla-daemon
2015-05-17 18:38 ` bugzilla-daemon
2015-05-19  1:00 ` bugzilla-daemon
2015-05-22 22:06 ` bugzilla-daemon
2016-01-31 16:25 ` bugzilla-daemon
2016-02-07 22:34 ` [Bug 90481] Radeonsi driver, X crash while playing "Spec ops: the line" bugzilla-daemon
2016-02-12  3:16 ` bugzilla-daemon
2016-04-10 12:47 ` bugzilla-daemon
2016-06-12 15:03 ` bugzilla-daemon
2016-06-13 15:40 ` bugzilla-daemon
2016-06-14  5:55 ` bugzilla-daemon
2016-07-01 14:37 ` bugzilla-daemon
2016-07-10 11:36 ` bugzilla-daemon
2016-08-01 16:29 ` bugzilla-daemon
2016-08-03 23:45 ` bugzilla-daemon
2016-08-10 22:03 ` bugzilla-daemon
2016-08-11 23:22 ` bugzilla-daemon
2016-08-12  4:12 ` bugzilla-daemon
2016-08-12 18:06 ` bugzilla-daemon
2016-08-12 18:07 ` bugzilla-daemon
2016-08-12 19:18 ` bugzilla-daemon
2016-08-13 11:19 ` bugzilla-daemon
2016-08-13 17:28 ` bugzilla-daemon
2016-08-13 23:03 ` bugzilla-daemon
2017-01-22 23:13 ` bugzilla-daemon
2017-01-23 10:52 ` bugzilla-daemon [this message]
2018-07-04  6:00 ` 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-90481-502-tNRpdB7qze@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.