[Bug 91577] [HD Graphics 4000] Segfault accessing rq->bo->handle
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Aug 7 02:55:52 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=91577
--- Comment #13 from Chris Wilson <chris at chris-wilson.co.uk> ---
Cursor doesn't do anything for me with links in the terminal. Do you mind
sending me the complete debug log, I want to see how we end up 64k buffers? In
the meantime,
commit 69d8edc11173df021aa2e158b2530257113141fd
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date: Fri Aug 7 10:08:17 2015 +0100
sna: Handle batch allocation failure
Whilst we currently do not try and submit a failed batch buffer
allocation, we still treat it as a valid request. This explodes much
later when we inspect the NULL rq->bo.
References: https://bugs.freedesktop.org/show_bug.cgi?id=91577
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
commit 8c465d0fbf84b1d29c54d620f09063d2b7ccfeb8
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date: Fri Aug 7 10:15:42 2015 +0100
sna: Fallback after a bo allocation failure for the batch
If we fail to allocate the next bo to use for the next_request, we can
just fallback to the delayed allocation used by !llc.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91577
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
commit ca71199679cac9cc161c84cb09d12f133abf8a64
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date: Fri Aug 7 10:40:30 2015 +0100
sna: Harden batch allocation against resource starvation
If the batch allocation fails, retire the oldest request and try again.
References: https://bugs.freedesktop.org/show_bug.cgi?id=91577
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
should prevent the allocation failure, or if we can't prevent it, handle it
correctly.
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150807/5babad52/attachment.html>
More information about the intel-gfx-bugs
mailing list