Hi,
last Friday I got two bisecting builds from Nuno, which I have tested on
my pool of BB-Black.
The current pool consists of two BB-Black which are from one of the
first BB-Black productions done by Embest around 2014. These boards are
named "old"
Plus there are 4+1 new BB-Black from Embest manufactured around
April/May 2015, named "new"
Prior to testing Nuno's builds, I had installed 4.0.4-bone4 on them for
more than 36h without a reboot, concluding that 4.0.4-bone4 is stable on
all.
*Results:**
*_
Nuno's bisecting build #40:__
_bbde39 (old): stable - uptime 1 day 1 hour
bbe0ae + bb77e6 (new): stable - uptime 1 day 1 hour
_
Nuno's bisecting build #41:__
___bbc1a1 (old): stable - uptime 1 day 1 hour
bb6bce + bb6a6f: *unstable*: both boards had 5 reboots over the last 25h
I addition I left one "new" board bbd14b run with 4.0.4-bone4 which
meanwhile has an uptime of 2 days 22 hours
It much seems to be as not all of the hardware of BB-Black is suffering
from this problem.
--
Günter (dl4mea)
Am 31.07.2015 um 16:40 schrieb Robert Nelson:
On Fri, Jul 31, 2015 at 9:19 AM, Graham <[email protected]> wrote:
Well, that is progress.
I don't think I have ever done a git bisect where it takes one or two days
to tell good from bad.
I know this is painful for you.
Thanks for grinding on it.
--- Graham
When we get down to a kernel git bisect i have a script ready that'll
take all the pain out of it.. ;) and right now it's looking v4.0.0
<-> v4.1.0...
I'm current keeping track of things here:
https://gist.github.com/RobertCNelson/b52f8318e9798625b655
I'm helping out grandma this weekend, so i'll be updating that gist
when i can. (As long as the boards don't need a "hard power reset")
Regards,
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
