From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95015] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)
Date: Fri, 15 Sep 2017 21:25:01 +0000 [thread overview]
Message-ID: <bug-95015-502-H46E7u5gjv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95015-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 771 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95015
--- Comment #13 from Joshua Cogliati <jjcogliati-r1@yahoo.com> ---
Just for reference, this error comes from the line:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/radeon/r600.c#n2848
Basically, the r600 driver writes 0xCAFEDEAD into a scratch register, then uses
a ring write to try and write 0xDEADBEEF into the scratch register, and then
waits and then reads the scratch register again to see what is in it. If it is
not 0xDEADBEEF, then the test fails and hardware acceleration is turned off.
The important question is why is the ring write failing, and I don't have an
answer.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1772 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
next prev parent reply other threads:[~2017-09-15 21:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 10:25 [Bug 95015] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) bugzilla-daemon
2016-04-23 10:40 ` bugzilla-daemon
2016-04-23 10:50 ` bugzilla-daemon
2016-04-24 12:06 ` bugzilla-daemon
2016-05-03 20:53 ` bugzilla-daemon
2016-05-03 21:05 ` bugzilla-daemon
2016-05-08 10:24 ` bugzilla-daemon
2016-05-09 2:04 ` bugzilla-daemon
2016-06-22 0:05 ` bugzilla-daemon
2016-06-22 11:06 ` bugzilla-daemon
2017-05-08 19:22 ` bugzilla-daemon
2017-05-08 19:24 ` bugzilla-daemon
2017-05-08 19:25 ` bugzilla-daemon
2017-09-15 21:25 ` bugzilla-daemon [this message]
2019-11-19 9:15 ` 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-95015-502-H46E7u5gjv@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