^ that's what git bisect does; you mark a good and bad commit and it starts halving the list of commits until you find the problem one
Understood. So it still may take ~50 builds to get close to the problem even when taking the half-way points! ...darn.
From previous posts it sounds like it will be much easier to bisect the kernel on a Generic x86 machine that hits the problem - which I do have.
I'd be happy to have a go at performing the bisects and compiling/testing some builds. Not something I've done before though so if anyone could provide assistance, or point me at some reliable links/documentation to get me started then I'll try my best to figure it out.
However, if it's simply going to be too difficult for a novice then I'll step back and hope someone else with suitable expertise is able to debug the issue.