I believe is better to run several boards with the same kernel to reduce the mean time to a BAD evidence.
Otherwise we have seen already times up to 3 days for a single board to reboot. So I would suggest to try instead only 2 levels at once, so 3 kernel revisions, with 8 boards running at the same time each revision for a total of 24 boards, hopping that we can advance 2 bisect levels / day. Your git repo will be much appreciated. Thanks. Nuno On Thursday, July 30, 2015 at 8:23:26 PM UTC+1, RobertCNelson wrote: > > On Thu, Jul 30, 2015 at 12:05 PM, dl4mea <dl4...@yahoo.de <javascript:>> > wrote: > > I can set up easily 24 boards, and with some additional work even 48, if > > that helps. > > > > ---- Günter (dl4mea) > > Thanks Günter, right now i'm trying to get it between two pure > mainline good/bad commits.. > > Then we can start a distributed git bisect. I'll setup a git repo, to > help automate it.. > > With a 24-36 hour test, each git bisect step is x^2 > > C > B G > B G B G > > So with 7 boards you can quickly do the first 4 steps.. At-least the > fails are quick. ;) > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
