[Bug 105509] SIGBUS, Bus error during command buffer recording

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Mar 17 05:26:15 UTC 2018


--- Comment #5 from Jason Ekstrand <jason at jlekstrand.net> ---
(In reply to Vyacheslav from comment #4)
> Workaround is to use one command buffer per frame (or per thread). Just
> record everything inside primary command buffer. It is worse for performance
> but it is better for mmap and it solved the problem.

If you are using enough secondary command buffers to blow past the 1GB limit,
then you are probably going to get garbage performance anyway.  We have to do a
full GPU on every vkCmdExecuteCommands so, while performance is probably fine
if secondary command buffers are used sparingly, over-use of them can cause
significant perf problems.

I think there still is something of a driver bug here in that we really should
be throwing VK_ERROR_OUT_OF_DEVICE_MEMORY instead of asserting or getting you
int a situation where you can get SIGBUS.

You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20180317/88562268/attachment.html>

More information about the intel-3d-bugs mailing list