From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 62959] r600g (HD 6950 Cayman) fails piglit tests and hangs system
Date: Mon, 08 Apr 2013 16:08:48 +0000 [thread overview]
Message-ID: <bug-62959-502-wOVhgMMYIS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-62959-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 337 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=62959
--- Comment #14 from Jerome Glisse <glisse@freedesktop.org> ---
Created attachment 77607
--> https://bugs.freedesktop.org/attachment.cgi?id=77607&action=edit
Full flush on vm flush
Can you try this patch ?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1352 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-04-08 16:08 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-31 4:00 [Bug 62959] New: r600g (HD 6950 Cayman) fails piglit tests and hangs system bugzilla-daemon
2013-03-31 4:03 ` [Bug 62959] " bugzilla-daemon
2013-03-31 4:08 ` bugzilla-daemon
2013-03-31 4:23 ` bugzilla-daemon
2013-04-03 10:30 ` bugzilla-daemon
2013-04-03 12:43 ` bugzilla-daemon
2013-04-03 12:49 ` bugzilla-daemon
2013-04-03 13:36 ` bugzilla-daemon
2013-04-03 16:20 ` bugzilla-daemon
2013-04-03 17:16 ` bugzilla-daemon
2013-04-04 18:01 ` bugzilla-daemon
2013-04-04 18:17 ` bugzilla-daemon
2013-04-04 18:49 ` bugzilla-daemon
2013-04-04 19:07 ` bugzilla-daemon
2013-04-05 23:45 ` bugzilla-daemon
2013-04-08 16:08 ` bugzilla-daemon [this message]
2013-04-08 16:09 ` bugzilla-daemon
2013-04-08 16:32 ` bugzilla-daemon
2013-04-08 17:09 ` bugzilla-daemon
2013-04-09 0:21 ` bugzilla-daemon
2013-04-09 0:48 ` bugzilla-daemon
2013-04-09 1:16 ` bugzilla-daemon
2013-04-09 1:34 ` bugzilla-daemon
2013-04-09 4:16 ` bugzilla-daemon
2013-04-09 12:52 ` bugzilla-daemon
2013-04-09 23:56 ` bugzilla-daemon
2013-04-10 0:11 ` bugzilla-daemon
2013-04-10 0:18 ` bugzilla-daemon
2013-04-10 1:20 ` bugzilla-daemon
2013-04-10 2:05 ` bugzilla-daemon
2013-04-10 13:06 ` bugzilla-daemon
2013-04-10 13:21 ` bugzilla-daemon
2013-04-10 22:54 ` bugzilla-daemon
2013-04-11 1:04 ` bugzilla-daemon
2013-04-11 13:45 ` bugzilla-daemon
2013-04-14 14:28 ` bugzilla-daemon
2013-04-20 7:54 ` bugzilla-daemon
2013-04-20 14:44 ` bugzilla-daemon
2013-04-20 14:52 ` bugzilla-daemon
2013-04-20 15:58 ` bugzilla-daemon
2013-04-20 16:08 ` bugzilla-daemon
2013-04-20 16:10 ` bugzilla-daemon
2013-04-20 16:19 ` bugzilla-daemon
2013-04-20 16:35 ` bugzilla-daemon
2013-04-20 16:41 ` bugzilla-daemon
2013-04-20 17:00 ` bugzilla-daemon
2013-04-20 17:08 ` bugzilla-daemon
2013-04-21 6:24 ` bugzilla-daemon
2013-04-21 7:20 ` bugzilla-daemon
2013-04-21 13:45 ` bugzilla-daemon
2013-04-21 15:36 ` bugzilla-daemon
2013-04-21 16:44 ` bugzilla-daemon
2013-04-21 18:08 ` bugzilla-daemon
2013-04-22 15:08 ` bugzilla-daemon
2013-04-24 2:31 ` bugzilla-daemon
2013-04-24 13:11 ` bugzilla-daemon
2013-04-24 13:21 ` bugzilla-daemon
2013-04-24 13:30 ` bugzilla-daemon
2013-04-24 13:42 ` bugzilla-daemon
2013-04-24 14:51 ` bugzilla-daemon
2013-04-24 15:07 ` bugzilla-daemon
2013-04-25 14:04 ` bugzilla-daemon
2013-04-27 15:04 ` bugzilla-daemon
2013-04-27 15:09 ` bugzilla-daemon
2013-04-27 15:16 ` bugzilla-daemon
2013-05-09 9:28 ` bugzilla-daemon
2013-06-09 7:04 ` bugzilla-daemon
2013-07-14 1:10 ` bugzilla-daemon
2013-07-15 10:36 ` bugzilla-daemon
2013-07-15 10:44 ` bugzilla-daemon
2013-07-15 12:24 ` bugzilla-daemon
2013-07-15 12:30 ` bugzilla-daemon
2013-07-15 13:44 ` bugzilla-daemon
2013-07-15 13:50 ` bugzilla-daemon
2013-07-15 14:17 ` bugzilla-daemon
2013-07-15 19:43 ` 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-62959-502-wOVhgMMYIS@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;
as well as URLs for NNTP newsgroup(s).