All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76487] New: [PIGLIT,radeonsi] spec/{EXT_texture_array/fbo-generatemipmap-array, ARB_framebuffer_object/fbo-generatemipmap-3d} RGB9_E5 crashes
Date: Sat, 22 Mar 2014 18:33:52 +0000	[thread overview]
Message-ID: <bug-76487-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 76487
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [PIGLIT,radeonsi]
                    spec/{EXT_texture_array/fbo-generatemipmap-array,ARB_f
                    ramebuffer_object/fbo-generatemipmap-3d} RGB9_E5
                    crashes
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: kai@dev.carbon-project.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

Created attachment 96212
  --> https://bugs.freedesktop.org/attachment.cgi?id=96212&action=edit
GDB backtrace and register info of the crash

For the first time ever, since I'm having a PITCAIRN GPU I was able to run a
full Piglit quick test without crashing my X (hooray for that). During the test
I came across two similar crashes in
"spec/EXT_texture_array/fbo-generatemipmap-array RGB9_E5" and
"spec/ARB_framebuffer_object/fbo-generatemipmap-3d RGB9_E5" (see the attached
GDB backtrace; the backtrace is for
spec/EXT_texture_array/fbo-generatemipmap-array RGB9_E5", but the second
crashed in the same function on the same line and as it's the same format, that
is tested, I guess, these are related, if not, I'm happy to provide a backtrace
for the second case as well and split the bugs).
I can't tell whether this is a regression or not, since this was the first time
I was able to run Piglit on this machine without getting a corrupted results
file, due to the crash of the X server.

My graphics stack is:
GPU: "PITCAIRN" (ChipID = 0x6819)
Linux: 3.13.6
libdrm: 2.4.52-1
LLVM: SVN:trunk/r204517
libclc: Git:master/1e278a7b04
Mesa: Git:master/4c79f088c0
GLAMOR: Git:master/a4fbc7732a (Standalone)
DDX: Git:master/ea6d0affe5
X: 1.15.0-2

Let me know if you need further information.

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

[-- Attachment #1.2: Type: text/html, Size: 3562 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:[~2014-03-22 18:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-22 18:33 bugzilla-daemon [this message]
2014-03-22 18:48 ` [Bug 76487] [PIGLIT,radeonsi] spec/{EXT_texture_array/fbo-generatemipmap-array, ARB_framebuffer_object/fbo-generatemipmap-3d} RGB9_E5 crashes bugzilla-daemon
2014-03-22 19:55 ` bugzilla-daemon
2014-03-22 21:26 ` bugzilla-daemon
2014-03-22 21:51 ` bugzilla-daemon
2015-02-19 15:52 ` 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-76487-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.