Comment # 9
on bug 105113
from Jan Vesely
(In reply to Maciej S. Szmigiero from comment #8) > Aren't program@execute@calls-struct and program@execute@tail-calls tests > from comment 4 examples of this behavior? > These seem to run but return wrong results, or am I not parsing the piglit > test results correctly? This is more of a piglit problem. piglit uses a combination of enqueue and clFinish. However, the error happens on kernel launch. thus; 1.) clEnqueueNDRangeKernel -- success 2.) The driver tries to launch the kernel and fails on relocations 3.) application(piglit) calls clFinish depending on the order of 2. and 3. clFinish can either see an empty queue and succeed or try to wait for kernel execution and fail. The following series should address that: https://patchwork.freedesktop.org/series/52857/ > This would explain why "amdgpu" seemed to not even attempt to reset the GPU > after a crash. > > However, I think I've got at least one lockup when testing this issue half a > year ago on "radeon" driver ("amdgpu" is still marked as experimental for SI > parts). > If I am able to reproduce it in the future I will report it then. comment #1 shows an example of a successful restart using radeon.ko, so I guess it worked for at least some ASICs. at any rate, restarting GPU is a separate, kernel, problem. Feel free to remove the relocation guard if you want to investigate GPU reset.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
