https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #10 from Bernd Steinhauser (li...@bernd-steinhauser.de) --- Unfortunately this turns out to be much harder than expected, because about 1/3 of the revs to test just won't boot at all (like instant kernel panic and not responding). This problem was fixed somewhere in the release candidates of 4.19, but I first need to track down the fix so I can properly continue with the bisect. Of the rest, another 1/3 of the revs do boot, but only with a black screen. While I can ssh into the system and check for memleaks, I don't think it's a proper test, because it seems to me as if amdgpu failed to initialize properly. So I need to track down the fix for this (again somewhere in the release candidates of 4.19) as well. So far, all I can be sure of is that the responsible commit was before v4.19-rc5 was backmerged into drm-next and drm-misc-next (7b76d0588477d4b6097a9048b42835a45caf5c48). But that still leaves quite a few commits to test. -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
