https://bugzilla.kernel.org/show_bug.cgi?id=196197 --- Comment #3 from Michel Dänzer (michel@xxxxxxxxxxx) --- (In reply to Andreas Brogle from comment #2) > # git bisect log > git bisect start > # bad: [c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201] Linux 4.11-rc1 > git bisect bad c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201 > # good: [7089db84e356562f8ba737c29e472cc42d530dbc] Linux 4.10-rc8 > git bisect good 7089db84e356562f8ba737c29e472cc42d530dbc That's just the start of bisecting. Now you need to keep testing the kernel built from the next commit checked out by git bisect. If the ring test failure happens, run "git bisect bad". If it doesn't happen and the GPU works normally after bootup, run "git bisect good". If anything else happens, e.g. the compiled kernel doesn't boot at all, run "git bisect skip". After repeating this a number (normally about tens) of times, git bisect will either specify the first bad commit or the minimum range of candidates. -- 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
