From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97122] list of 12 dEQP-GLES2 tests causing systematic GPU lockups
Date: Thu, 28 Jul 2016 22:54:48 +0000 [thread overview]
Message-ID: <bug-97122-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1825 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97122
Bug ID: 97122
Summary: list of 12 dEQP-GLES2 tests causing systematic GPU
lockups
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: issor.oruam@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 125386
--> https://bugs.freedesktop.org/attachment.cgi?id=125386&action=edit
List of tests inducing systematic GPU lockups
Hi,
while performing Android Compatibility Test Suite run on marshamallow-x86 with
mesa 12.0.1 I encountered systematic GPU lockups preceeded by full screen
artifact, sometime "noise screen alike" and some others "vertical stripes".
The issue was observed on HD7750 and HD7950.
The pattern and list of the 12 dEQP-GLES2 tests causing systematic GPU lockups
is the following:
dEQP-GLES2.functional.shaders.loops.while_{constant,uniform,dynamic}.{conditional,double}_continue_{vertex,fragment}
You can find in the attachments the dEQP GLES2 tests logs and some dmesg logs
captured during these GPU lockups.
I am available to collect further logs, if you could provide me instructions,
or to test patches and report back to help resolve the issue.
NOTE: I've already tried to define R600_DEBUG=nosb
which in android-x86 has to be done in init.x86.rc before building the iso
image,
but then running a test plan with the aforementioned failed tests,
I get again systematic GPU lockups.
Mauro Rossi
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3389 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:[~2016-07-28 22:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 22:54 bugzilla-daemon [this message]
2016-07-28 22:57 ` [Bug 97122] list of 12 dEQP-GLES2 tests causing systematic GPU lockups bugzilla-daemon
2016-07-28 23:00 ` bugzilla-daemon
2016-07-28 23:01 ` bugzilla-daemon
2016-08-01 12:08 ` bugzilla-daemon
2016-08-02 7:24 ` bugzilla-daemon
2016-08-02 7:35 ` bugzilla-daemon
2016-08-02 12:30 ` bugzilla-daemon
2016-08-02 17:41 ` bugzilla-daemon
2016-08-02 21:51 ` 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-97122-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.