Update:
also the "old" board with Nuno's #41 has rebooted.
Hard to make a statistic from this, but it means that "new" boards are
booting 5 times more often then "old" ones
--
Günter
Am 08.08.2015 um 19:16 schrieb Nuno Gonçalves:
So, this build works fine for all boards:
9e204d885a6d0ae3696284bacd86e2b94dd936c8 # v4.0-rc3-40-g9e204d8
usb: musb: dsps: use msecs_to_jiffies instead
This commit is the first introducing the reboot problem. The problem
is also confirmed to only happen in some board versions:
ad78c918602cb7cce0fab5d5813213853a6f351d # v4.0-rc3-41-gad78c91
usb: musb: dsps: just start polling already
We can't discard a silicon problem, but this is way over my pay grade.
Hope Balbi can give us any hint about any possible reasons this commit
is creating this issue, since the code doesn't appear to have any
evident problem...
Thanks,
Nuno
On Sat, Aug 8, 2015 at 6:08 PM, Koellner Guenter <dl4...@yahoo.de> wrote:
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 <gra...@flex-radio.com> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
