From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100398] [agd5f] New errors when tonga card powers up
Date: Sun, 26 Mar 2017 01:09:01 +0000 [thread overview]
Message-ID: <bug-100398-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2230 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100398
Bug ID: 100398
Summary: [agd5f] New errors when tonga card powers up
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: mike@fireburn.co.uk
I'm seeing the below messages on agd5f's drm-next-4.12-wip branch when the
Tonga discret card powers up - this doesn't seem to prevent rendering but I'm
not sure what each of the rings are
Possibly related to the recent KIQ changes
[17689.424825] [drm] PCIE GART of 4096M enabled (table at 0x0000000000040000).
[17689.473369] [drm] ring test on 0 succeeded in 11 usecs
[17689.473531] [drm] ring test on 9 succeeded in 20 usecs
[17689.473646] [drm] ring test on 1 succeeded in 19 usecs
[17689.676500] [drm:gfx_v8_0_ring_test_ring] *ERROR* amdgpu: ring 2 test failed
(scratch(0xC040)=0xCAFEDEAD)
[17689.825919] [drm:gfx_v8_0_ring_test_ring] *ERROR* amdgpu: ring 3 test failed
(scratch(0xC040)=0xCAFEDEAD)
[17689.974629] [drm:gfx_v8_0_ring_test_ring] *ERROR* amdgpu: ring 4 test failed
(scratch(0xC040)=0xCAFEDEAD)
[17690.127396] [drm:gfx_v8_0_ring_test_ring] *ERROR* amdgpu: ring 5 test failed
(scratch(0xC040)=0xCAFEDEAD)
[17690.289456] [drm:gfx_v8_0_ring_test_ring] *ERROR* amdgpu: ring 6 test failed
(scratch(0xC040)=0xCAFEDEAD)
[17690.439040] [drm:gfx_v8_0_ring_test_ring] *ERROR* amdgpu: ring 7 test failed
(scratch(0xC040)=0xCAFEDEAD)
[17690.587548] [drm:gfx_v8_0_ring_test_ring] *ERROR* amdgpu: ring 8 test failed
(scratch(0xC040)=0xCAFEDEAD)
[17690.587553] [drm:amdgpu_resume] *ERROR* resume of IP block <gfx_v8_0> failed
-22
[17690.587556] [drm:amdgpu_device_resume] *ERROR* amdgpu_resume failed (-22).
[17690.595905] [drm:amdgpu_fill_buffer] *ERROR* Trying to clear memory with
ring turned off.
[17690.595935] [drm:amdgpu_fill_buffer] *ERROR* Trying to clear memory with
ring turned off.
[17696.119220] amdgpu 0000:01:00.0: GPU pci config reset
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3528 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-03-26 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 1:09 bugzilla-daemon [this message]
2017-03-27 22:05 ` [Bug 100398] [agd5f] New errors when tonga card powers up bugzilla-daemon
2017-03-27 23:21 ` bugzilla-daemon
2017-03-29 22:14 ` bugzilla-daemon
2017-03-29 23:31 ` bugzilla-daemon
2017-03-31 18:51 ` bugzilla-daemon
2017-03-31 20:55 ` bugzilla-daemon
2017-03-31 20:57 ` 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-100398-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).