[Bug 105873] [i915]Failed to release pages: bind_count=1, pages_pin_count=1, pin_display=0 on kernel 4.14.20

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=105873

Joonas Lahtinen <joonas.lahtinen at linux.intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|major                       |enhancement

--- Comment #17 from Joonas Lahtinen <joonas.lahtinen at linux.intel.com> ---
Right, so this is not a regression, but trying to find which patches fix the
issue in new kernels. So tagging this as enhancement, which it is.

The referred patch here itself has a Fixes: tag, so it should be applied only
on top of the previously applied patch. That means if picking only this patch
helps, then it is through incredible luck only. And if the pointed patch was in
LTS, the Fixes: tag should have made it get picked up automatically.

Also, from the bisect log, we got:

"first bad commit: [010e3e68cd9cb65ea50c0af605e966cda333cb2a] drm/i915: Remove
vma from object on destroy, not close"

That would mean that introducing this patch actually breaks the usecase, so I'm
having trouble following why it is suggested as the fix? Please provide a
proper bisect log where you actually build each suggested commit and run your
testcase for each step, tagging it as good or bad depending on if your testcase
passes or fails (if the testcase can't be reproduce the issue 100% of the time,
then do enough runs on EACH step to make sure you have good confidence).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
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-gfx-bugs/attachments/20180604/6d47f9d5/attachment.html>