All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 62959] New: r600g (HD 6950 Cayman) fails piglit tests and hangs system
Date: Sun, 31 Mar 2013 04:00:32 +0000	[thread overview]
Message-ID: <bug-62959-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2343 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=62959

          Priority: medium
            Bug ID: 62959
          Assignee: dri-devel@lists.freedesktop.org
           Summary: r600g (HD 6950 Cayman) fails piglit tests and hangs
                    system
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: alexandre.f.demers@gmail.com
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

Using mesa 0967c362bf378b7415c30ca6d9523d3b2a3a7f5d (and for a long time),
piglit tests fail and hangs the system (ssh session won't respond). Using an HD
6950 (Cayman).

Running "python2 piglit-run.py --no-concurrency tests/r600.tests
results/r600.results/", it fails everytime. According to the "main" file, the
last log info is:
       
"spec/glsl-1.30/execution/built-in-functions/fs-greaterThan-uvec4-uvec4": {
                "info": "Returncode: 0\n\nErrors:\n\n\nOutput:\n", 
                "returncode": 0, 
                "command":
"/home/dema1701/projects/display/piglit/framework/../bin/shader_runner
tests/../generated_tests/spec/glsl-1.30/execution/built-in-functions/fs-greaterThan-uvec4-uvec4.shader_test
-auto", 
                "result": "pass", 
                "time": 0.10875105857849121
            },
       
"spec/glsl-1.10/execution/variable-indexing/fs-temp-array-mat4-col-row-wr": {
                "info": "Returncode: 0\n\nErrors:\n\n\nOutput:\n", 
                "returncode": 0, 



Mesa's build options:
baseExec="./autogen.sh --prefix=/usr \
        --enable-debug \
        --enable-shared \
        --enable-osmesa \
        --enable-gbm \
        --enable-xvmc \
        --enable-vdpau \
        --enable-gles1 \
        --enable-gles2 \
        --enable-openvg \
        --enable-xorg \
        --enable-xa \
        --enable-egl \
        --enable-gallium-egl \
        --enable-glx-tls \
        --enable-texture-float \
        --enable-wgl \
        --with-gallium-drivers=r600,swrast,svga \
        --with-egl-platforms=x11,drm"
"$baseExec  --enable-64-bit --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --libdir=/usr/lib/x86_64-linux-gnu
--includedir=/usr/include/x86_64-linux-gnu"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3807 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

             reply	other threads:[~2013-03-31  4:00 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-31  4:00 bugzilla-daemon [this message]
2013-03-31  4:03 ` [Bug 62959] r600g (HD 6950 Cayman) fails piglit tests and hangs system bugzilla-daemon
2013-03-31  4:08 ` bugzilla-daemon
2013-03-31  4:23 ` bugzilla-daemon
2013-04-03 10:30 ` bugzilla-daemon
2013-04-03 12:43 ` bugzilla-daemon
2013-04-03 12:49 ` bugzilla-daemon
2013-04-03 13:36 ` bugzilla-daemon
2013-04-03 16:20 ` bugzilla-daemon
2013-04-03 17:16 ` bugzilla-daemon
2013-04-04 18:01 ` bugzilla-daemon
2013-04-04 18:17 ` bugzilla-daemon
2013-04-04 18:49 ` bugzilla-daemon
2013-04-04 19:07 ` bugzilla-daemon
2013-04-05 23:45 ` bugzilla-daemon
2013-04-08 16:08 ` bugzilla-daemon
2013-04-08 16:09 ` bugzilla-daemon
2013-04-08 16:32 ` bugzilla-daemon
2013-04-08 17:09 ` bugzilla-daemon
2013-04-09  0:21 ` bugzilla-daemon
2013-04-09  0:48 ` bugzilla-daemon
2013-04-09  1:16 ` bugzilla-daemon
2013-04-09  1:34 ` bugzilla-daemon
2013-04-09  4:16 ` bugzilla-daemon
2013-04-09 12:52 ` bugzilla-daemon
2013-04-09 23:56 ` bugzilla-daemon
2013-04-10  0:11 ` bugzilla-daemon
2013-04-10  0:18 ` bugzilla-daemon
2013-04-10  1:20 ` bugzilla-daemon
2013-04-10  2:05 ` bugzilla-daemon
2013-04-10 13:06 ` bugzilla-daemon
2013-04-10 13:21 ` bugzilla-daemon
2013-04-10 22:54 ` bugzilla-daemon
2013-04-11  1:04 ` bugzilla-daemon
2013-04-11 13:45 ` bugzilla-daemon
2013-04-14 14:28 ` bugzilla-daemon
2013-04-20  7:54 ` bugzilla-daemon
2013-04-20 14:44 ` bugzilla-daemon
2013-04-20 14:52 ` bugzilla-daemon
2013-04-20 15:58 ` bugzilla-daemon
2013-04-20 16:08 ` bugzilla-daemon
2013-04-20 16:10 ` bugzilla-daemon
2013-04-20 16:19 ` bugzilla-daemon
2013-04-20 16:35 ` bugzilla-daemon
2013-04-20 16:41 ` bugzilla-daemon
2013-04-20 17:00 ` bugzilla-daemon
2013-04-20 17:08 ` bugzilla-daemon
2013-04-21  6:24 ` bugzilla-daemon
2013-04-21  7:20 ` bugzilla-daemon
2013-04-21 13:45 ` bugzilla-daemon
2013-04-21 15:36 ` bugzilla-daemon
2013-04-21 16:44 ` bugzilla-daemon
2013-04-21 18:08 ` bugzilla-daemon
2013-04-22 15:08 ` bugzilla-daemon
2013-04-24  2:31 ` bugzilla-daemon
2013-04-24 13:11 ` bugzilla-daemon
2013-04-24 13:21 ` bugzilla-daemon
2013-04-24 13:30 ` bugzilla-daemon
2013-04-24 13:42 ` bugzilla-daemon
2013-04-24 14:51 ` bugzilla-daemon
2013-04-24 15:07 ` bugzilla-daemon
2013-04-25 14:04 ` bugzilla-daemon
2013-04-27 15:04 ` bugzilla-daemon
2013-04-27 15:09 ` bugzilla-daemon
2013-04-27 15:16 ` bugzilla-daemon
2013-05-09  9:28 ` bugzilla-daemon
2013-06-09  7:04 ` bugzilla-daemon
2013-07-14  1:10 ` bugzilla-daemon
2013-07-15 10:36 ` bugzilla-daemon
2013-07-15 10:44 ` bugzilla-daemon
2013-07-15 12:24 ` bugzilla-daemon
2013-07-15 12:30 ` bugzilla-daemon
2013-07-15 13:44 ` bugzilla-daemon
2013-07-15 13:50 ` bugzilla-daemon
2013-07-15 14:17 ` bugzilla-daemon
2013-07-15 19:43 ` 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-62959-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.