https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #282 from Kajzer kap3tan@gmail.com --- (In reply to Alex Deucher from comment #280)
You don't need to start the bisect again. `git bisect reset` will clean up the bisect and reset your current HEAD to where it was when started the bisect. At that point just run `git reset --hard 77497f2735ad6e29c55475e15e9790dbfa2c2ef8` or 'git checkout -b testing 77497f2735ad6e29c55475e15e9790dbfa2c2ef8` to checkout the specific commit you want to test. The second method creates a new branch called testing with HEAD set to the specified commit. The reset command resets the HEAD of the current tree to the specified commit.
I'm running now on kernel compiled with first method, if previous bisect was indeed done right I don't expect dpm freeze.
Anyway, thanks for the second method, if I understood you correctly, basically I can test if Michel's commit is bad or not by running : $ git bisect reset $ git checkout -b testing 02376d8282b88f07d0716da6155094c8760b1a13
Of course after I'm done with current test. Please correct me if I'm wrong.