I have now been running 22 hours without a reset - this is a first. Yesterday at 3:17pm I changed out power supplies. I also killed wicp. So now I'm suspicious of wicp as the culprit. I added 'auto eth0' in /etc/network/interfaces since I'm hard wire connected and wicp was bringing up eth0 far too late in the boot sequence so that dhclient and ntp were both looping looking for the network (which wasn't up yet) but I still had wicp starting up at boot. I suppose I can shutdown and put the other power supply back on and see what happens with wicp removed.
On Monday, September 15, 2014 8:33:15 AM UTC-4, Thomas O wrote: > > Well we are seeing exactly the same problems as Greg has experienced. We > have 10 bbb running for a project and we are seeing on avg a crash per 24 > hours or maybe rather a reboot. > We have tested the 3.14. 3.15 and 3.16 kernels built via Roberts build > environment as well as installing the ti kernels wtih the same result. > > We have ruled out the powers since we are now running all the boards from > a profesional lab supply with measured ripple and performance way above the > specs for the board. > We have had serial cables connected to the uart0 and have not seen > anything strange in the dmesg or the serial console. No trace of oops or > panic just restarts... > >> >> -- 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.
