Comment # 5
on bug 112008
from Babblebones@gmail.com
(In reply to Alex Deucher from comment #4) > Can you use git bisect the issue and find the exact commit that broke it or > narrow down when the regression happened? E.g., working in 4.17-rc3 and > broken in 4.17-rc4? I have two commits that break my EDID reading and cause the exact same issue so far. bisected the mainline to try and find the issue, trailed into your drm-next git... The first commit I found that broke my EDID read: https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-drm-next&id=8a61bc085ffab3071c59efcbeff4044c034e7490 Was later reverted. Followed more commits after this one down a branch and into here... https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86-urgent-for-linus&id=bd4caed47a19f25fe8674344ea06d469c27ac314 Surprisingly, swapping out the memory allocs actually breaks the EDID read in this commit/ branch too. I know for a fact Ubuntu's old kernel 4.18 reverted this specific and the treewide memory allocation change, which worked!? I stopped about here, my head was starting to spin as to why THAT would do anything. I am ready and able to fork over any binary/parameter/debug dumps to help solve this.
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
