| Summary: | Opencl random lockups whilst running tstellar's opencl-examples | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | klondike <klondike> |
| Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 9.2 | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | Backported commit fixing the lockups | ||
|
Description
klondike
2013-09-12 01:39:38 UTC
Can you test this with the latest version of Mesa from git? I was able to reproduce this on the 9.2 branch by running three separate instances of the run_tests.sh script at the same time as the Lightsmark demo. However, I could not reproduce this on master, so maybe it has been fixed. Hi Tom, managed to get some time to test and it seems to be as you say. With development version of mesa + libdrm the issue seems to be gone. I'll try test development version of mesa 9.2 branch and if it also fails I'll try to bisect the issue so we can backport the fix to mesa 9.2.1 Thanks for the hint :) Created attachment 86824 [details] [review] Backported commit fixing the lockups Hi Tom, after manually checking the differences between the 9.2.0 and my working version of the git sources* I have tracked it down to these lines which are present on 9.2.0 but not on git The file is src/gallium/drivers/r600/evergreen_compute.c The relevant commit with the fix is this: http://cgit.freedesktop.org/mesa/mesa/commit/src/gallium/drivers/r600/evergreen_compute.c?id=f0435ebb07d01a77ca0d98967a002898811a5206 Keep in mind that ctx->b.flags = 0; should be changed by ctx->flags = 0; (and similar changes where be needed too). Anyways, patch for 9.2.0 attached :) * Yeah, I know bisect may have been faster, but for random appearing problems I prefer to do stuff the good old way. 9.2.0 is EOL and it's fixed upstream |
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.