BTW, my "cure" for this has been "shutdown now -h", and then manually
powering the board back up. However, while it did help the problem
drastically, it does not completely fix the problem.

On Thu, Apr 2, 2015 at 11:56 AM, William Hermans <[email protected]> wrote:

> That covers intentional reboots, where 1 in 10 the board just does not
> come up correctly ?
>
> On Thu, Apr 2, 2015 at 11:48 AM, Robert Nelson <[email protected]>
> wrote:
>
>> On Thu, Apr 2, 2015 at 1:46 PM, William Hermans <[email protected]>
>> wrote:
>> > @Robert,
>> >
>> > Any idea what is causing this ? I seem to recall some talk a long time
>> ago
>> > about perhaps the PMIC is causing this. Our A5A's exhibit this also,
>> like
>> > once in 10 boots or so.
>> >
>> > Hopefully, it is not related to the older kernels. . .
>>
>> For random reboots, it's this fix:
>>
>>
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/am335x-bone-common.dtsi?id=67fd14b3eca63b14429350e9eadc5fab709a8821
>>
>> 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 [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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.

Reply via email to