From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85579] New: [bisected] piglit test crashes in spec/glsl-1.50/execution/geometry/max-input-components
Date: Wed, 29 Oct 2014 01:11:05 +0000 [thread overview]
Message-ID: <bug-85579-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1294 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=85579
Bug ID: 85579
Summary: [bisected] piglit test crashes in
spec/glsl-1.50/execution/geometry/max-input-components
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: commendsarnex@gmail.com
Created attachment 108602
--> https://bugs.freedesktop.org/attachment.cgi?id=108602&action=edit
log when the test fails
Hi again guys. I've been getting some very weird piglit crashes, including one
lockup, which I haven't yet been able to bisect.
Anyway, here's one I've been able to bisect.
The test spec/glsl-1.50/execution/geometry/max-input-components fails before
commit 54de7099115502c561f5f51095e08dc0a52c71b7, and always crashes on commits
after.
I have attached the piglit result logs from both versions. I'm not sure if the
LLVM Register Spilling spam is relating to my other problems, or not.
Let me know if you need any more information.
Thanks,
sarnex
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2681 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:[~2014-10-29 1:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 1:11 bugzilla-daemon [this message]
2014-10-29 1:11 ` [Bug 85579] [bisected] piglit test crashes in spec/glsl-1.50/execution/geometry/max-input-components bugzilla-daemon
2014-10-29 8:43 ` bugzilla-daemon
2014-10-29 12:34 ` bugzilla-daemon
2014-10-29 14:52 ` bugzilla-daemon
2014-10-29 19:52 ` bugzilla-daemon
2014-10-30 3:08 ` bugzilla-daemon
2014-10-30 3:30 ` bugzilla-daemon
2014-10-30 3:33 ` bugzilla-daemon
2014-11-02 11:19 ` bugzilla-daemon
2017-05-24 8:06 ` 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-85579-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 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).