On Tue, Aug 18, 2015 at 01:58:13PM +0100, The Gluglug wrote: > For the git repository, this would probably require manually > maintaining the scripts for each run in the bisect. > > For testing purposes, it doesn't matter since those blobs won't be > loaded on your system (unless you have the Intel wifi or something, or > some device you inserted that might use them). Just make sure to > switch back to linux-libre afterwards.
Thank you for pointing me in the right direction. I just cloned the sources from https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git Then I started bisecting, but the bad news is that the versioning system is designed in such a way that one can only bisect between major revisions: so I could not mark "v4.0.7" as 'good'. So I marked v4.0 as 'good' and v4.1 as 'bad'. This way, I have 6282 revisions left to test, which can take roughly 13 steps. To each of these steps, I have to add the compilation time (over an hour I think), and the time needed to make the laptop freeze. Am I right here? Is there is a better way to proceed?
signature.asc
Description: PGP signature
