From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93475] Saints Row IV causes GPU lockup on Linux
Date: Tue, 16 Aug 2016 18:51:26 +0000 [thread overview]
Message-ID: <bug-93475-502-FRp7HVTu2B@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93475-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 686 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93475
--- Comment #4 from Michael Stenzel <mastergizmo@arcor.de> ---
Hello,
I have a HD 5870, with radeon module.
Today I upgraded to kernel 4.7 and mesa git from a few hours ago.
Can confirm this issue with SR3, still locks the GPU up:
[ 2598.025126] radeon 0000:01:00.0: ring 3 stalled for more than 10025msec
[ 2598.025135] radeon 0000:01:00.0: GPU lockup (current fence id
0x000000000005d84c last fence id 0x000000000005d84d on ring 3)
after `export R600_DEBUG=nosb` the game seems to work fine here (played first
level for a few minutes).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1453 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 prev parent reply other threads:[~2016-08-16 18:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 14:13 [Bug 93475] Saints Row IV causes GPU lockup on Linux bugzilla-daemon
2016-06-17 5:39 ` bugzilla-daemon
2016-06-17 6:02 ` bugzilla-daemon
2016-06-17 6:04 ` bugzilla-daemon
2016-07-13 9:37 ` bugzilla-daemon
2016-08-16 18:51 ` bugzilla-daemon [this message]
2016-08-21 14:15 ` bugzilla-daemon
2017-03-12 13:24 ` bugzilla-daemon
2017-06-04 12:00 ` bugzilla-daemon
2019-07-04 1: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-93475-502-FRp7HVTu2B@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