From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60802] Corruption with DMA ring on cayman
Date: Fri, 22 Feb 2013 04:29:47 +0000 [thread overview]
Message-ID: <bug-60802-502-ClxXV5O2uC@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-60802-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 579 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=60802
--- Comment #25 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
For the info, I use a now-unavailable demo used to test features for Amnesia
(RendererFeattest). It is no where to be found anymore I think. It is a quick
and progressive test (starting with almost nothing and adding or testing
different features on every change). I'd be happy to use piglit tests, but last
time I tried a couple of weeks ago, it was still locking my computer.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1336 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
next prev parent reply other threads:[~2013-02-22 4:29 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 16:44 [Bug 60802] New: Kernel 3.8-rc7 breaks rendering on Radeon (confirmed on Cayman) bugzilla-daemon
2013-02-14 6:39 ` [Bug 60802] " bugzilla-daemon
2013-02-14 6:42 ` bugzilla-daemon
2013-02-14 6:42 ` bugzilla-daemon
2013-02-18 1:43 ` bugzilla-daemon
2013-02-18 1:44 ` [Bug 60802] (bisect 8696e33f06b0c52195152cc6a0e3d52233f486c1) " bugzilla-daemon
2013-02-18 13:47 ` [Bug 60802] Corruption with DMA ring on cayman bugzilla-daemon
2013-02-18 14:34 ` bugzilla-daemon
2013-02-19 3:25 ` bugzilla-daemon
2013-02-19 6:33 ` bugzilla-daemon
2013-02-19 8:14 ` bugzilla-daemon
2013-02-19 22:49 ` bugzilla-daemon
2013-02-20 5:10 ` bugzilla-daemon
2013-02-20 6:35 ` bugzilla-daemon
2013-02-20 6:59 ` bugzilla-daemon
2013-02-20 13:31 ` bugzilla-daemon
2013-02-20 18:28 ` bugzilla-daemon
2013-02-20 18:32 ` bugzilla-daemon
2013-02-20 18:53 ` bugzilla-daemon
2013-02-20 19:53 ` bugzilla-daemon
2013-02-20 22:31 ` bugzilla-daemon
2013-02-21 3:14 ` bugzilla-daemon
2013-02-21 6:57 ` bugzilla-daemon
2013-02-21 8:18 ` bugzilla-daemon
2013-02-21 14:57 ` bugzilla-daemon
2013-02-21 16:36 ` bugzilla-daemon
2013-02-22 4:29 ` bugzilla-daemon [this message]
2013-02-25 12:16 ` bugzilla-daemon
2013-02-25 15:13 ` bugzilla-daemon
2013-02-25 16:35 ` bugzilla-daemon
2013-02-27 2:52 ` bugzilla-daemon
2013-02-27 6:59 ` bugzilla-daemon
2013-02-27 13:37 ` bugzilla-daemon
2013-02-27 21:13 ` bugzilla-daemon
2013-02-27 22:26 ` bugzilla-daemon
2013-02-28 2:17 ` bugzilla-daemon
2013-02-28 6:44 ` bugzilla-daemon
2013-03-01 3:32 ` bugzilla-daemon
2013-03-01 6:51 ` bugzilla-daemon
2013-03-01 9:56 ` bugzilla-daemon
2013-03-01 12:47 ` bugzilla-daemon
2013-03-01 14:35 ` bugzilla-daemon
2013-03-05 16:06 ` bugzilla-daemon
2013-03-05 19:27 ` bugzilla-daemon
2013-03-11 3:53 ` bugzilla-daemon
2013-03-13 22:46 ` bugzilla-daemon
2013-03-13 22:50 ` bugzilla-daemon
2013-03-14 2:03 ` bugzilla-daemon
2013-03-14 3:30 ` bugzilla-daemon
2013-03-14 3:37 ` bugzilla-daemon
2013-03-14 4:29 ` bugzilla-daemon
2013-03-14 23:33 ` bugzilla-daemon
2013-03-15 0:40 ` bugzilla-daemon
2013-03-15 1:21 ` bugzilla-daemon
2013-03-15 1:32 ` bugzilla-daemon
2013-03-15 3:47 ` bugzilla-daemon
2013-03-15 13:01 ` bugzilla-daemon
2013-03-15 13:57 ` bugzilla-daemon
2013-03-15 15:32 ` bugzilla-daemon
2013-03-15 16:47 ` bugzilla-daemon
2013-03-15 17:36 ` bugzilla-daemon
2013-03-15 19:21 ` bugzilla-daemon
2013-03-15 19:25 ` bugzilla-daemon
2013-03-15 19:35 ` bugzilla-daemon
2013-03-15 22:17 ` bugzilla-daemon
2013-03-16 4:21 ` bugzilla-daemon
2013-03-17 17:29 ` bugzilla-daemon
2013-03-17 17:43 ` bugzilla-daemon
2013-03-18 0:13 ` 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-60802-502-ClxXV5O2uC@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