From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31246] New: Reproducible hangs on piglit tests with 5850
Date: Sat, 30 Oct 2010 19:15:34 -0700 (PDT) [thread overview]
Message-ID: <bug-31246-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=31246
Summary: Reproducible hangs on piglit tests with 5850
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: temp9476-freedesktop@yahoo.no
Ignoring the occasional random hang, I have found that the following tests
create a lockup of the system every time:
glsl-fs-main-return
glsl-vs-main-return
glsl-max-varyings
glsl-fs-vec4-indexing-temp-dst-in-nested-loop-combined
glsl-vs-vec4-indexing-temp-dst-in-nested-loop-combined
How would I go about debugging these further? It would be very nice if the
piglit tests would at least fail, not hang...
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-10-31 2:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 2:15 bugzilla-daemon [this message]
2010-11-02 17:28 ` [Bug 31246] Reproducible hangs on piglit tests with 5850 bugzilla-daemon
2010-11-06 19:44 ` bugzilla-daemon
2010-11-07 13:13 ` bugzilla-daemon
2011-02-09 15:52 ` [Bug 31246] [RADEON::CYPRESS:R600C] reproducible hangs on piglit tests with HD5850 bugzilla-daemon
2011-02-22 17:01 ` bugzilla-daemon
2011-06-01 17:26 ` bugzilla-daemon
2011-06-01 21:22 ` bugzilla-daemon
2011-06-11 16:20 ` bugzilla-daemon
2012-09-12 15:02 ` 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-31246-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.