From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92270] Radeon R7 M260/M265 - *ERROR* amdgpu: ring 0 test failed (scratch(0xC040)=0xCAFEDEAD)
Date: Tue, 06 Oct 2015 15:27:16 +0000 [thread overview]
Message-ID: <bug-92270-502-CWVJBm4rnb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92270-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 699 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92270
--- Comment #6 from Christian König <deathsimple@vodafone.de> ---
(In reply to Alex Deucher from comment #5)
> Created attachment 118719 [details] [review]
> Mark iceland as experimental
>
> (In reply to Christian König from comment #2)
> >
> > @Alex: How well did we already tested Topaz? If not we might want to disable
> > the PCI-ID for now.
>
> We haven't really tested them much. How about the attached patch?
Yeah, probably a good idea until we have time to fix those.
Patch is Reviewed-by: Christian König <christian.koenig@amd.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2066 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:[~2015-10-06 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 20:06 [Bug 92270] Radeon R7 M260/M265 - *ERROR* amdgpu: ring 0 test failed (scratch(0xC040)=0xCAFEDEAD) bugzilla-daemon
2015-10-03 20:07 ` bugzilla-daemon
2015-10-05 13:17 ` bugzilla-daemon
2015-10-05 22:52 ` bugzilla-daemon
2015-10-06 14:57 ` bugzilla-daemon
2015-10-06 14:59 ` bugzilla-daemon
2015-10-06 15:27 ` bugzilla-daemon [this message]
2015-12-11 15:14 ` bugzilla-daemon
2016-01-16 20:47 ` bugzilla-daemon
2016-01-18 6:19 ` bugzilla-daemon
2016-05-31 1:34 ` bugzilla-daemon
2016-05-31 2:39 ` 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-92270-502-CWVJBm4rnb@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).