https://bugzilla.kernel.org/show_bug.cgi?id=198511 --- Comment #10 from Barto (mister.freeman@xxxxxxxxxxx) --- I think I found the real "first bad commit", it's : commit 648bc3574716400acc06f99915815f80d9563783 Author: Christian König <christian.koenig@xxxxxxx> Date: Thu Jul 6 09:59:43 2017 +0200 drm/ttm: add transparent huge page support for DMA allocations v2 Try to allocate huge pages when it makes sense. v2: fix comment and use ifdef Signed-off-by: Christian König <christian.koenig@xxxxxxx> Reviewed-by: Felix Kuehling <Felix.Kuehling@xxxxxxx> Signed-off-by: Alex Deucher <alexander.deucher@xxxxxxx> because the previous commit( d188bfa5532ce5b426681d8530ff1a9683eea0ad ) before this bad commit doesn't have the bug, so I can conclude that the first bad commit which introduces the bug is 648bc3574716400acc06f99915815f80d9563783, I have made a new bisect which confirms the same thing, so what do you think Alex ? I tried to revert 648bc3574716400acc06f99915815f80d9563783 but git refuses to revert this commit because of conflict file, it seems that later one developper has edited one or several files modified previoulsy by commit 648bc3574716400acc06f99915815f80d9563783 -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
