All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99851] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)
Date: Mon, 20 Feb 2017 22:19:32 +0000	[thread overview]
Message-ID: <bug-99851-502-tRgYznSqlR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99851-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1074 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99851

--- Comment #15 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Christian Zigotzky from comment #12)
> Hi All,
> 
> I have the same problem. 
> 
> System:
> 
> A-EON AmigaOne X1000 PowerPC
> Nemo board with a P.A. Semi PA6T-1682M CPU
> 8GB RAM
> ASUS Radeon HD7790 1GB VRAM
> ubuntu MATE 17.04 PowerPC (PPC32) with the kernels 4.10-rc8 (DRM 2.49.0) and
> 4.9.10 (DRM 2.48.0)
> Mesa 17.0.0

(In reply to Sinan Gürkan from comment #13)
> (In reply to Christian Zigotzky from comment #12)
> 
> 
> Hello everyone..
> 
> I also have the same problem..
> 
> A-EON Amiga X5000 PowerPC
> Varisys Cyrus Board with P5020
> 8GB RAM
> ASUS Radeon R7 265
> Ubuntu Mate 17.04 - Mesa 17.0.0
> Kernel 4.10-rc8

Please try to provide more details.  It sounds like there may be several issues
at play here.  What do you mean by the same problem?  ring test errors in the
kernel driver?  Some sort of Xorg "crash"?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2212 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-02-20 22:19 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-99851-502@http.bugs.freedesktop.org/>
2017-02-20  4:00 ` [Bug 99851] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) bugzilla-daemon
2017-02-20 22:13 ` bugzilla-daemon
2017-02-20 22:17 ` bugzilla-daemon
2017-02-20 22:19 ` bugzilla-daemon [this message]
2017-02-20 22:47 ` bugzilla-daemon
2017-02-21 22:01 ` bugzilla-daemon
2017-02-21 23:09 ` bugzilla-daemon
2017-02-22 21:44 ` bugzilla-daemon
2017-02-22 22:25 ` bugzilla-daemon
2017-02-22 22:41 ` bugzilla-daemon
2017-02-27 15:20 ` bugzilla-daemon
2017-02-27 17:32 ` bugzilla-daemon
2017-02-27 18:32 ` bugzilla-daemon
2017-03-02  8:03 ` bugzilla-daemon
2017-03-24 10:18 ` bugzilla-daemon
2017-03-24 16:48 ` bugzilla-daemon
2017-03-24 17:03 ` bugzilla-daemon
2017-03-24 17:54 ` bugzilla-daemon
2017-05-18 13:48 ` bugzilla-daemon
2017-05-18 21:00 ` bugzilla-daemon
2017-05-18 21:01 ` bugzilla-daemon
2017-05-18 21:09 ` bugzilla-daemon
2017-05-19  1:35 ` bugzilla-daemon
2017-05-19  1:36 ` bugzilla-daemon
2017-05-19 18:14 ` bugzilla-daemon
2017-05-19 18:15 ` bugzilla-daemon
2017-05-24 10:59 ` bugzilla-daemon
2017-05-25 18:42 ` bugzilla-daemon
2017-05-27  8:22 ` bugzilla-daemon
2017-05-27  8:24 ` bugzilla-daemon
2017-05-27  8:24 ` bugzilla-daemon
2017-05-29  7:18 ` bugzilla-daemon
2017-05-29  9:42 ` bugzilla-daemon
2017-06-02 22:49 ` bugzilla-daemon
2017-06-02 22:52 ` bugzilla-daemon
2017-06-02 22:53 ` bugzilla-daemon
2017-06-02 22:53 ` bugzilla-daemon
2017-06-05  2:31 ` bugzilla-daemon
2017-06-13 13:25 ` bugzilla-daemon
2017-07-17 13:20 ` bugzilla-daemon
2017-08-10 22:37 ` bugzilla-daemon
2017-09-15 19:36 ` bugzilla-daemon
2017-09-15 20:33 ` bugzilla-daemon
2017-09-15 21:44 ` bugzilla-daemon
2017-10-07 15:06 ` bugzilla-daemon
2017-10-11  7:45 ` bugzilla-daemon
2017-12-06 22:00 ` bugzilla-daemon
2017-12-08  7:00 ` bugzilla-daemon
2018-06-21 22:25 ` bugzilla-daemon
2018-08-25 22:59 ` bugzilla-daemon
2019-11-19  9:24 ` 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-99851-502-tRgYznSqlR@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.