From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 50655] New: ATI RV670 [Radeon HD 3870] Ioquake games causes GPU lockup (waiting for 0x00003039 last fence id 0x00003030)
Date: Sun, 03 Jun 2012 21:23:01 +0000 [thread overview]
Message-ID: <bug-50655-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=50655
Bug #: 50655
Summary: ATI RV670 [Radeon HD 3870] Ioquake games causes GPU
lockup (waiting for 0x00003039 last fence id
0x00003030)
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: BryanQuigley@Ubuntu.com
Created attachment 62474
--> https://bugs.freedesktop.org/attachment.cgi?id=62474
kern.log
Tested and reproducible with Urban Terror, Warsow, and World of Padman. Used
phoronix test suite, and at some point during the run of each game, it would
either freeze or eventually display weird output to the screen (attached).
Occasionally a VT switch would let the game "appear" again. Other times you
can hear the sound of the game continue.
I am using the 3.4 kernel and drivers/X, etc from Xorg Edgers PPA, which for
the ati driver would be 6.14.99+git20120525.b1e9c308 and mesa is
8.1~git20120530.ff3eef1a.
You should be able to reproduce this by:
Installing phoronix test suite
(http://www.phoronix-test-suite.com/?k=downloads)
and then running: phoronix-test-suite benchmark urbanterror
(or warsow or padman)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-06-03 21:23 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 21:23 bugzilla-daemon [this message]
2012-06-03 21:23 ` [Bug 50655] ATI RV670 [Radeon HD 3870] Ioquake games causes GPU lockup (waiting for 0x00003039 last fence id 0x00003030) bugzilla-daemon
2012-06-03 21:23 ` bugzilla-daemon
2012-06-03 22:41 ` bugzilla-daemon
2012-06-04 5:22 ` bugzilla-daemon
2012-06-04 12:33 ` bugzilla-daemon
2012-06-04 14:37 ` bugzilla-daemon
2012-06-04 18:50 ` bugzilla-daemon
2012-06-05 16:02 ` bugzilla-daemon
2012-06-07 4:39 ` bugzilla-daemon
2012-06-07 4:42 ` bugzilla-daemon
2012-06-07 7:40 ` bugzilla-daemon
2012-06-07 13:43 ` bugzilla-daemon
2012-06-07 14:16 ` bugzilla-daemon
2012-06-07 14:20 ` bugzilla-daemon
2012-06-07 16:19 ` bugzilla-daemon
2012-08-15 14:49 ` bugzilla-daemon
2012-08-24 1:14 ` bugzilla-daemon
2012-08-24 4:31 ` bugzilla-daemon
2012-08-24 4:32 ` bugzilla-daemon
2012-12-10 5:55 ` bugzilla-daemon
2012-12-10 5:56 ` bugzilla-daemon
2012-12-10 5:56 ` bugzilla-daemon
2012-12-10 5:56 ` bugzilla-daemon
2012-12-10 6:09 ` bugzilla-daemon
2012-12-10 15:49 ` bugzilla-daemon
2012-12-10 21:21 ` bugzilla-daemon
2012-12-11 2:01 ` bugzilla-daemon
2012-12-11 4:15 ` bugzilla-daemon
2012-12-11 6:59 ` bugzilla-daemon
2012-12-11 17:15 ` bugzilla-daemon
2012-12-11 18:05 ` bugzilla-daemon
2012-12-11 18:13 ` bugzilla-daemon
2012-12-11 21:38 ` bugzilla-daemon
2012-12-11 21:54 ` bugzilla-daemon
2012-12-13 16:17 ` bugzilla-daemon
2012-12-13 16:34 ` bugzilla-daemon
2012-12-13 17:08 ` bugzilla-daemon
2012-12-13 17:11 ` bugzilla-daemon
2012-12-13 22:54 ` bugzilla-daemon
2012-12-16 21:12 ` bugzilla-daemon
2013-02-19 1:53 ` bugzilla-daemon
2013-02-19 22:42 ` bugzilla-daemon
2013-02-19 23:21 ` bugzilla-daemon
2013-02-21 23:03 ` bugzilla-daemon
2013-02-21 23:36 ` bugzilla-daemon
2013-02-22 0:14 ` bugzilla-daemon
2013-02-22 0:15 ` bugzilla-daemon
2013-02-22 0:15 ` bugzilla-daemon
2013-02-22 0:16 ` bugzilla-daemon
2013-02-22 0:18 ` bugzilla-daemon
2013-02-22 1:03 ` bugzilla-daemon
2013-02-22 5:24 ` bugzilla-daemon
2013-02-22 13:34 ` bugzilla-daemon
2013-02-22 14:36 ` bugzilla-daemon
2013-02-22 14:36 ` bugzilla-daemon
2013-02-22 14:37 ` bugzilla-daemon
2013-02-22 14:37 ` bugzilla-daemon
2013-02-22 14:38 ` bugzilla-daemon
2013-02-22 15:36 ` bugzilla-daemon
2013-02-22 16:06 ` bugzilla-daemon
2013-02-22 16:53 ` bugzilla-daemon
2013-02-22 17:40 ` bugzilla-daemon
2013-02-22 18:19 ` bugzilla-daemon
2013-02-22 19:25 ` bugzilla-daemon
2013-02-22 19:43 ` bugzilla-daemon
2013-02-22 19:53 ` bugzilla-daemon
2013-02-22 19:59 ` bugzilla-daemon
2013-02-22 20:04 ` bugzilla-daemon
2013-02-22 20:56 ` bugzilla-daemon
2013-02-22 21:15 ` bugzilla-daemon
2013-02-22 21:25 ` bugzilla-daemon
2013-02-22 21:42 ` bugzilla-daemon
2013-02-22 22:56 ` bugzilla-daemon
2013-02-22 23:31 ` bugzilla-daemon
2013-02-22 23:33 ` bugzilla-daemon
2013-02-22 23:49 ` bugzilla-daemon
2013-02-23 12:09 ` bugzilla-daemon
2013-02-23 17:41 ` bugzilla-daemon
2013-02-23 20:01 ` bugzilla-daemon
2013-02-24 8:22 ` bugzilla-daemon
2013-04-24 18:46 ` [Bug 50655] [r600g][RV670 HD3870] " bugzilla-daemon
2014-07-30 14:04 ` bugzilla-daemon
2014-07-30 15:02 ` bugzilla-daemon
2014-07-30 19:14 ` bugzilla-daemon
2017-09-01 20:27 ` 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-50655-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.