https://bugzilla.kernel.org/show_bug.cgi?id=70171
--- Comment #42 from Alex Deucher <alexdeucher at gmail.com> --- Just google for "git bisect howto". There are lots of good examples. Here's one: http://webchick.net/node/99 You need a kernel git tree. The closer you can narrow the breakage down, the faster it will be. Basically, if you know that 3.12 was good and 3.13 was broken, you'd start like this: git bisect start git bisect bad v3.13 git bisect good v3.12 Then build and test the kernel for each iteration until it arrives at the problematic commit. -- You are receiving this mail because: You are watching the assignee of the bug.
