From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100964] RX-480 [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 0 test failed (scratch(0xC040)=0xCAFEDEAD)
Date: Mon, 08 May 2017 01:38:51 +0000 [thread overview]
Message-ID: <bug-100964-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3037 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100964
Bug ID: 100964
Summary: RX-480 [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR*
amdgpu: ring 0 test failed
(scratch(0xC040)=0xCAFEDEAD)
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: suzaku.29a@gmail.com
Created attachment 131248
--> https://bugs.freedesktop.org/attachment.cgi?id=131248&action=edit
dmesg output on amdgpu load failure
Inconsistent amdgpu driver loading for an RX-480:
Most of the time, the driver will fail to load starting with the error:
[drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 0 test failed
(scratch(0xC040)=0xCAFEDEAD)
The screen goes into stand-by and I get no display output. The rest of
the system still loads normally and I can ssh and look around.
------------
But it will, very seldom, load the driver normally (KMS enabled, display
still active).
------------
I can use nomodeset to prevent amdgpu from being initialized and the
display continues to work, but without 3D accel and just one monitor
working (out of two).
To confirm that the GPU actually works (both in general and in linux
with amdgpu), I tested it on a friend's PC with the same distro I'm
using (Debian Testing/amd64). The driver loaded normally on the first
try and worked consistently for all the reboots we tried.
Since then I've read anything I could find on the issue and I couldn't
find any solution. There are similar reports on other AMD videocards,
but none of them give me a solution for the inconsistency.
Things tried so far:
Debian testing and unstable with most of the kernels released since
4.7.0-1 up to their latest kernel 4.9.25-1 (4.9.0-3 in their
versioning system).
Gentoo with the genkernel 4.9.16.
Gentoo custom kernel 4.9.16
Gentoo with kernel 4.11 from https://cgit.freedesktop.org/~agd5f/linux/
(drm-fixes-4.11).
Alternating ACPI and most, if not all, amdgpu parameters in all
tested kernels.
Using different outputs (DVI, HDMI and both. I cannot test
DisplayPort).
The Debian and Gentoo installs are fresh in different drives. I can
test things on either one.
I'd be ok with my MB or CPU somehow being too old or incompatible. But
the few successful boots tell me that it can and *does* work on my pc.
I'm attaching two dmesg logs, one for the working boot and one for the
failing one. They were run shortly after each other and nothing was
changed in between.
I'm attaching lspci output too.
Please let me know if you need any other info or clarification on the
error.
Regards.
HV
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4571 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 reply other threads:[~2017-05-08 1:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 1:38 bugzilla-daemon [this message]
2017-05-08 1:41 ` [Bug 100964] RX-480 [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 0 test failed (scratch(0xC040)=0xCAFEDEAD) bugzilla-daemon
2017-05-08 1:42 ` bugzilla-daemon
2017-05-08 15:01 ` bugzilla-daemon
2017-05-08 16:44 ` bugzilla-daemon
2017-05-13 21:41 ` bugzilla-daemon
2017-08-13 1:29 ` bugzilla-daemon
2017-08-13 4:31 ` bugzilla-daemon
2017-08-13 4:37 ` bugzilla-daemon
2017-08-13 4:38 ` bugzilla-daemon
2017-08-13 21:51 ` bugzilla-daemon
2017-08-13 21:55 ` bugzilla-daemon
2019-11-19 8:16 ` 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-100964-502@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.