https://bugs.freedesktop.org/show_bug.cgi?id=101179
--- Comment #7 from Peter Hutterer <peter.hutte...@who-t.net> ---
Bisecting a kernel is easier than you'd expect, at least the basic approach:
https://01.org/linuxgraphics/gfx-docs/drm/admin-guide/bug-bisect.html
I suspect the biggest difficulty is figuring out what to do with builds that
don''t build but you can do a git bisect skip on those. Plus, there's a high
chance you can narrow the bisect to drivers/input, which should only give you a
few revisions to look at.
Attach an evemu-record of such a sequence though with a broken kernel, that
should pinpoint what the problem is, which then may show what the cause could
be.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
