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: Sun, 13 Aug 2017 01:29:38 +0000 [thread overview]
Message-ID: <bug-100964-502-gceADPxZwt@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100964-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2446 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100964
--- Comment #6 from Maxim Cournoyer <maxim.cournoyer@gmail.com> ---
Hi! I have the exact same issue ``[drm:gfx_v8_0_ring_test_ring [amdgpu]]
*ERROR* amdgpu: ring 0 test failed (scratch(0xC040)=0xCAFEDEAD)`` with a R9 285
GPU. I've had this problems for ages and had been using nomodeset to get by.
I'm trying this on Debian 9 (stretch), with kernel ``Linux debian 4.9.0-3-amd64
#1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26) x86_64 GNU/Linux``. I've attached
the full dmesg.
The interesting thing is that this seems to be related to the motherboard; when
using the very same card (R9 285) in another system, *with the same software*
(Debian 9), it works! It is not a hardware problem: the power supply is brand
new (Seasonic G550W), the RAM tests fine, the SSD is brand new, the CMOS
battery too, etc.
The problem occurs on Asus M2N SLI Deluxe motherboard based system; and it
disappears when using it with an equally old Asus P5W DH Deluxe based system.
I notice there is a message saying that the clock source is unstable right
before the error occurs; could it be related?
Here is an excerpt of the dmesg:
[ 11.552754]
failed to send pre message 5b ret is 0
[ 11.748489]
failed to send message 5b ret is 0
[ 11.748536] clocksource: timekeeping watchdog on CPU0: Marking clocksource
'tsc' as unstable because the skew is too large:
[ 11.748538] clocksource: 'acpi_pm' wd_now: f69088
wd_last: ba62a0 mask: ffffff
[ 11.748539] clocksource: 'tsc' cs_now: 167976623b
cs_last: 12698f30d7 mask: ffffffffffffffff
[ 11.957731] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 0
test failed (scratch(0xC040)=0xCAFEDEAD)
[ 11.957840] [drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block
<gfx_v8_0> failed -22
[ 11.957879] amdgpu 0000:03:00.0: amdgpu_init failed
[ 12.171671]
failed to send pre message 133 ret is 0
[ 12.385424]
failed to send message 133 ret is 0
[ 12.385433] DPM is not running right now, no need to disable DPM!
[ 12.386774] clocksource: Switched to clocksource acpi_pm
[ 12.772038]
I can provide dmesg from the working system (using the same software with the
same card) if judged useful.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3364 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-08-13 1:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 1:38 [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:41 ` 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 [this message]
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-gceADPxZwt@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.