From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26933] r600: piglit test failures
Date: Sun, 7 Mar 2010 03:03:32 -0800 (PST) [thread overview]
Message-ID: <20100307110332.7A58A1300A6@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-26933-502@http.bugs.freedesktop.org/>
http://bugs.freedesktop.org/show_bug.cgi?id=26933
--- Comment #1 from Török Edwin <edwintorok@gmail.com> 2010-03-07 03:03:32 PST ---
Created an attachment (id=33826)
--> (http://bugs.freedesktop.org/attachment.cgi?id=33826)
log
Full output from dmesg, Xorg.0.log, and glxinfo.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2010-03-07 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 11:03 [Bug 26933] New: r600: piglit test failures bugzilla-daemon
2010-03-07 11:03 ` bugzilla-daemon [this message]
2010-03-07 11:04 ` [Bug 26933] " bugzilla-daemon
2010-03-07 11:15 ` [Bug 26933] r600 driver (rv730): " bugzilla-daemon
2010-03-07 22:03 ` bugzilla-daemon
2010-03-08 12:22 ` bugzilla-daemon
2010-03-23 13:11 ` bugzilla-daemon
2012-11-02 16:47 ` bugzilla-daemon
2014-07-07 16: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=20100307110332.7A58A1300A6@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/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).