dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67276] kernel-3.11 [drm:r600_uvd_ring_test] *ERROR* radeon: ring 5 test failed (0xCAFEDEAD)
Date: Fri, 26 Jul 2013 16:47:29 +0000	[thread overview]
Message-ID: <bug-67276-502-e0FUGHQrDb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67276-502@http.bugs.freedesktop.org/>


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

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

--- Comment #16 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #15)
> Do you have any idea, why this happens randomly on cold boots but not when
> restarting the pc? I think the whole initialization process should be the
> same everytime the system is booted, so that the ring initialization should
> fail every time.
> 
> On I side note: Earlier I had an interesting problem. When rebooting the pc
> after a drm-lockup I could see the last screen before the restart. This
> means that some memory buffers were not completely cleared during the
> reboots.

Memory is never explicitly cleared.

> 
> Maybe I have a similar problem here: The faulty register isn't rewritten on
> every reboot???

The only way to figure out what is going on is to bisect.  There are a lot of
things that could cause ring tests to fail.

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

[-- Attachment #1.2: Type: text/html, Size: 1930 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

  parent reply	other threads:[~2013-07-26 16:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 21:02 [Bug 67276] New: kernel-3.11 [drm:r600_uvd_ring_test] *ERROR* radeon: ring 5 test failed (0xCAFEDEAD) bugzilla-daemon
2013-07-24 21:42 ` [Bug 67276] " bugzilla-daemon
2013-07-24 22:05 ` bugzilla-daemon
2013-07-25 12:02 ` bugzilla-daemon
2013-07-25 12:52 ` bugzilla-daemon
2013-07-25 13:06 ` bugzilla-daemon
2013-07-25 13:10 ` bugzilla-daemon
2013-07-25 13:26 ` bugzilla-daemon
2013-07-25 13:54 ` bugzilla-daemon
2013-07-25 14:17 ` bugzilla-daemon
2013-07-25 14:22 ` bugzilla-daemon
2013-07-26 11:10 ` bugzilla-daemon
2013-07-26 14:06 ` bugzilla-daemon
2013-07-26 14:44 ` bugzilla-daemon
2013-07-26 15:00 ` bugzilla-daemon
2013-07-26 15:13 ` bugzilla-daemon
2013-07-26 16:47 ` bugzilla-daemon [this message]
2013-07-26 16:48 ` bugzilla-daemon
2013-07-28  6:40 ` bugzilla-daemon
2013-07-28  9:05 ` bugzilla-daemon
2013-07-28  9:07 ` bugzilla-daemon
2013-07-28 12:15 ` bugzilla-daemon
2013-07-28 12:28 ` bugzilla-daemon
2013-07-28 14:56 ` bugzilla-daemon
2013-07-28 15:27 ` bugzilla-daemon
2013-08-09 11:27 ` bugzilla-daemon
2013-08-09 14:01 ` bugzilla-daemon
2013-08-15 14:49 ` bugzilla-daemon
2013-08-15 14:49 ` bugzilla-daemon
2013-08-15 14:50 ` 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-67276-502-e0FUGHQrDb@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