From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83996] [drm:r100_ring_test] *ERROR* radeon: ring test failed - since linux-3.17_rc1 on RS690/RS740 [Radeon 2100]
Date: Wed, 17 Sep 2014 14:20:26 +0000 [thread overview]
Message-ID: <bug-83996-502-E7kMzM13Z2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-83996-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 635 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=83996
--- Comment #1 from Christian König <deathsimple@vodafone.de> ---
Created attachment 106432
--> https://bugs.freedesktop.org/attachment.cgi?id=106432&action=edit
Test for reverting the patch in question.
It's unlikely that the patch you mentioned causes such problems, but the patch
directly before this one could.
The attached patch (on top of Alex drm-fixes-3.17 branch) reverts this patch
and adds a few extra debug log lines.
So please test and report back with a new dmesg log.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1807 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:[~2014-09-17 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 13:42 [Bug 83996] New: [drm:r100_ring_test] *ERROR* radeon: ring test failed - since linux-3.17_rc1 on RS690/RS740 [Radeon 2100] bugzilla-daemon
2014-09-17 14:20 ` bugzilla-daemon [this message]
2014-09-17 23:42 ` [Bug 83996] " bugzilla-daemon
2014-09-18 1:18 ` bugzilla-daemon
2014-09-18 20:20 ` bugzilla-daemon
2014-09-19 1:34 ` bugzilla-daemon
2014-09-21 22:17 ` bugzilla-daemon
2014-09-22 2:34 ` 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-83996-502-E7kMzM13Z2@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).