From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26887] fence errors with rs785 and kernel 2.6.33
Date: Mon, 8 Mar 2010 00:57:40 -0800 (PST) [thread overview]
Message-ID: <20100308085740.95F8E1300C0@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-26887-502@http.bugs.freedesktop.org/>
http://bugs.freedesktop.org/show_bug.cgi?id=26887
--- Comment #5 from Marc <marvin24@gmx.de> 2010-03-08 00:57:40 PST ---
I tried to bisect this and found that 2.6.32 also has this issue (I got this
system a few weeks ago only). 2.6.31 shows "ring test failed" and I guess
support for rs785 was not added earlier. So this chip seems to never have
worked with KMS.
--
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
--
next prev parent reply other threads:[~2010-03-08 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 15:52 [Bug 26887] New: fence errors with rs785 and kernel 2.6.33 bugzilla-daemon
2010-03-04 15:53 ` [Bug 26887] " bugzilla-daemon
2010-03-05 11:07 ` bugzilla-daemon
2010-03-05 11:41 ` bugzilla-daemon
2010-03-05 15:37 ` bugzilla-daemon
2010-03-08 8:57 ` bugzilla-daemon [this message]
2010-03-10 9:27 ` bugzilla-daemon
2010-03-12 20:11 ` bugzilla-daemon
2010-03-12 20:40 ` bugzilla-daemon
2010-03-13 16:52 ` bugzilla-daemon
2011-02-05 3:13 ` bugzilla-daemon
2017-04-28 9:02 ` 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=20100308085740.95F8E1300C0@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).