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.
https://bugs.freedesktop.org/show_bug.cgi?id=76487
--- Comment #1 from Marek Olšák maraeo@gmail.com --- This fix is on the mailing list: http://patchwork.freedesktop.org/patch/22223/
https://bugs.freedesktop.org/show_bug.cgi?id=76487
--- Comment #2 from Kai kai@dev.carbon-project.org --- (In reply to comment #1)
This fix is on the mailing list: http://patchwork.freedesktop.org/patch/22223/
Oh, nice to hear! Do I need just that patch or the entire series? And what about Brian's remark regarding memory consumption? Am I about to totally trash my performance, if I apply this patch/series or is this path hit only rarely?
https://bugs.freedesktop.org/show_bug.cgi?id=76487
--- Comment #3 from Marek Olšák maraeo@gmail.com --- In theory, yes, you will need more memory. I'm going to rework the patch, but not today.
https://bugs.freedesktop.org/show_bug.cgi?id=76487
--- Comment #4 from Kai kai@dev.carbon-project.org --- Ok, then I'll wait. Let me know when there's a reworked version and I gladly test it.
https://bugs.freedesktop.org/show_bug.cgi?id=76487
smoki smoki00790@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #5 from smoki smoki00790@gmail.com ---
This seems long time fixed with commit 26c41398cc47c0f72259a34406831443238b7ba9
Closing.
dri-devel@lists.freedesktop.org