Comment # 6
on bug 104300
from Mariusz Mazur
I found it! Before I knew 4.14 worked fine and 4.15+ introduced this bug. Now I know precisely which patches: - 4.14.35 works correctly - 4.14.36 exhibits this behavior There are only a few amdgpu patches in there, one by Bas Nieuwenhuizen @chromium and a few by Alex Deucher @amd. Now I need to figure out how to set up a kernel-building env and test which patch in particular is the one that breaks everything.
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
