I have seen some releases take more than 24 hours to fail. If it fails, then it does, but if it doesn't, you may have to go two full days before you can start thinking that you found it. --- Graham
== On Wednesday, July 29, 2015 at 1:44:08 PM UTC-5, Graham wrote: > > OK. Understand. > If you need help testing a version, send me a note. > --- Graham > > == > > On Wednesday, July 29, 2015 at 12:33:10 PM UTC-5, RobertCNelson wrote: >> >> On Wed, Jul 29, 2015 at 11:05 AM, Nuno Gonçalves <nun...@gmail.com> >> wrote: >> > I can also probe the board with a logic analyzer, wait to the event to >> occur >> > and figure where in the hardware it started. Just don't want to be >> doing >> > something that have already been discarded. >> > >> > Robert: could you please put us in the loop about your investigation so >> we >> > can team efforts? >> >> Well right now it's.. >> >> git bisect start >> git bisect good v3.14 >> git bisect bad v4.12-rc4 >> >> rebuild... >> >> run for 24 hours (or if it resets earlier)... retest.. >> >> Wish we could trigger it faster.. but it's going to take awhile.. >> >> 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.
