https://bugs.winehq.org/show_bug.cgi?id=38953
--- Comment #3 from Austin English austinenglish@gmail.com --- (In reply to Armin Altorffer from comment #2)
Moreover as in this particular case, the list of commits that is involved in this phenomenon occurring is rather extensive. 4.1.2 is the last known working kernel; 4.2.rc1 already sees it failing. The list of individual commits for 4.2.rc1 is quite extensive; it is one of the larger rc's in the history of the Linux kernel. And as there are no individual compiles for each and every individual commit, I would have to personally bisect the entire 4.2 rc1 kernel, each individual commit. Compiling manually for every bisect attempt. Obviously, it can be narrowed down a bit, but still, there are numerous possible causes. Personally bisecting this on a less than cutting edge machine is probably going to take weeks.
You don't need to test every individual commit. Essentially, git bisect automates the process of dividing the list of changes in half and testing the midway point to find the broken commit, greatly reducing the needed number of compiles (last time I bisected the kernel, I think it was around 15 compiles).