From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91305] When running JTR OpenCL tests: radeon 0000:01:00.0: ring 0 stalled for more than ...msec
Date: Sat, 11 Jul 2015 08:34:06 +0000 [thread overview]
Message-ID: <bug-91305-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2047 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91305
Bug ID: 91305
Summary: When running JTR OpenCL tests: radeon 0000:01:00.0:
ring 0 stalled for more than ...msec
Product: Mesa
Version: 10.6
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: devurandom@gmx.net
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 117050
--> https://bugs.freedesktop.org/attachment.cgi?id=117050&action=edit
screenshot
I ran `john --test=0 --verbosity=5` from
JohnTheRipper@d8cb9ce98acd26bd917dff4cbb54bdc14b7133f9, which made X crash.
I was dropped to VT1, where the messages "radeon 0000:01:00.0: ring 0 stalled
for more than ...msec" and "radeon 0000:00:01.0: ring 3 stalled for more than
...msec" where flashing by. Afterwards messages of failed tests were logged
(typewrote from attached screenshot):
```
AMD-Vi: Event logged [IO_PAGE_FAULT device=00:01.0 domain=0x0000
address=0x000000041145c040 flags=0x0050]
[drm:cik_ring_test [radeon]] *ERROR* radeon: ring 1 test failed
(scratch(0x3010C)=0xCAFEDEAD)
[drm:cik_ring_test [radeon]] *ERROR* radeon: ring 2 test failed
(scratch(0x3010C)=0xCAFEDEAD)
[drm:cik_sdma_ring_test [radeon]] *ERROR* radeon: ring 4 test failed
(0xCAFEDEAD)
[drm:cik_resume [radeon]] *ERROR* cik startup failed on resume
radeon 0000:00:01.0: ring 0 stalled for more than 10281msec
[drm:cik_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35).
[drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX
ring (-35).
```
Since dmesg did not log these errors and journald is not accessible via
journalctl ATM ("Error was encountered while opening journal files: Invalid
argument"), I sadly cannot give you more accurate logs than the typewrote
screenshot.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3514 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
next reply other threads:[~2015-07-11 8:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 8:34 bugzilla-daemon [this message]
2015-07-11 8:35 ` [Bug 91305] When running JTR OpenCL tests: radeon 0000:01:00.0: ring 0 stalled for more than ...msec bugzilla-daemon
2015-07-11 8:35 ` bugzilla-daemon
2015-07-11 8:35 ` bugzilla-daemon
2015-07-11 8:36 ` bugzilla-daemon
2015-07-11 8:37 ` bugzilla-daemon
2015-07-11 8:38 ` bugzilla-daemon
2015-07-11 8:39 ` bugzilla-daemon
2015-07-11 8:39 ` bugzilla-daemon
2015-07-11 8:44 ` bugzilla-daemon
2015-07-12 6:59 ` [Bug 91305] When running JohnTheRipper " bugzilla-daemon
2015-07-12 9:28 ` bugzilla-daemon
2015-07-12 9:28 ` bugzilla-daemon
2015-07-13 13:31 ` bugzilla-daemon
2017-03-15 14:16 ` bugzilla-daemon
2018-05-30 7:13 ` [Bug 91305] [clover/kaveri] " bugzilla-daemon
2018-09-09 22:47 ` 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-91305-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.