Summary: | luxrays/slg4 hangs GPU (CEDAR) | ||
---|---|---|---|
Product: | Mesa | Reporter: | Aaron Watry <awatry> |
Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 99553 | ||
Attachments: |
luxrays diff/patch to disable image support while reproducing bug.
Kernel source for luxrays dmesg from luxrays GPU hang/reset bitcode, assembly, and rest of stderr from slg4 run |
Description
Aaron Watry
2014-07-03 22:06:38 UTC
Created attachment 102223 [details]
Kernel source for luxrays
Created attachment 102224 [details]
dmesg from luxrays GPU hang/reset
Grumble.. I was just attempting to get the bitcode since I had lost my previous dump of that... and now for some reason the GPU's not locking and I'm instead getting an LLVM diagnostic handler and a segfault due to invalid reads (according to valgrind). I'm pretty sure I'll be able to reproduce this, but part of my software stack needs to be rebuild first. Created attachment 102226 [details]
bitcode, assembly, and rest of stderr from slg4 run
This contains the llvm bitcode, R600 assembly, and the rest of the stdout as generated from:
R600_DUMP_SHADERS=1 RADEON_DUMP_SHADERS=1 R600_DEBUG=cs,compute,trace_cs bin/slg4 2> bitcode.ll
The bitcode and hangs were all reproduced with luxrays commit 2099 (hg up -r 2099) and the image support disabling patch applied. Commit 2099 is the same as was used for the luxrender_v1.3.1 tag. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/515. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.