From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70528] RadeonSI : Specviewperf10/proe-04 cause system hang
Date: Thu, 27 Feb 2014 03:33:49 +0000 [thread overview]
Message-ID: <bug-70528-502-H7WKMfTi9p@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-70528-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 882 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=70528
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|git |unspecified
--- Comment #5 from Michel Dänzer <michel@daenzer.net> ---
I finally figured out why PTS failed to install the specviewperf10 test for me
(the installation hangs with ccache).
The proe-04 test only draws the splash screen here, after that I get lines
like:
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
in dmesg, indicating the kernel fails to process the drawing command streams,
probably due to running out of VRAM or GTT memory.
Does that match what you're seeing?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2214 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 prev parent reply other threads:[~2014-02-27 3:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 12:30 [Bug 70528] New: RadeonSI : Specviewperf10/proe-04 cause system hang bugzilla-daemon
2013-10-16 12:30 ` [Bug 70528] " bugzilla-daemon
2013-10-16 12:31 ` bugzilla-daemon
2013-10-17 2:56 ` bugzilla-daemon
2013-10-17 7:25 ` bugzilla-daemon
2013-10-17 7:29 ` bugzilla-daemon
2013-10-21 5:59 ` bugzilla-daemon
2014-02-27 3:33 ` bugzilla-daemon [this message]
2016-02-26 3:38 ` 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-70528-502-H7WKMfTi9p@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).