However, not enoug of a difference apparently. I just had a sudden reset 
occur. This is on a 3.18-rc2-bone1 with both a Dymo labelwriter and a 
smartcard reader attached through USB. 

The boot log after reset can be found at http://pastebin.com/YGnNpJyQ

Op zaterdag 8 november 2014 10:37:51 UTC+1 schreef Ives van der Flaas:
>
> Setting the usb0 dr_mode to peripheral and disabling OTG in the .config 
> definitely makes a big difference. I have a 3.18-rc2-bone1 currently 
> running for almost 24 hours with this patch, much more than I've ever 
> previously achieved with 3.18 or 3.17. 
>
> Op woensdag 5 november 2014 01:36:09 UTC+1 schreef Jens Peter Schroer:
>>
>> I followed up on the USB OTG hint as mentioned in my previous post. I 
>> patched the dtb for the bbb so that the mini usb port runs as peripheral 
>> and not as OTG. The patch was deployed to 7 systems so far and they all are 
>> stable (no reboot) since then on any of the systems. The uptime is more 
>> than 3 days now. 
>> If interested, I can post more details.
>>
>> On Tuesday, November 4, 2014 3:01:53 PM UTC+1, Ives van der Flaas wrote:
>>>
>>> Have you had *any* resets since the upgrade to the new u-boot version? 
>>> I've also been suspecting u-boot, hence my "Meaning that I'm also running 
>>> an old u-boot. " in the last post. 
>>>
>>> Op dinsdag 4 november 2014 00:18:43 UTC+1 schreef david turvene:
>>>>
>>>> On Saturday, November 1, 2014 3:24:33 PM UTC-4, david turvene wrote:
>>>>>
>>>>> The system runs fine when I'm not messing around with the plugs, 
>>>>> changing the wifi properties, or sniffing.  When I do any of these the 
>>>>> system occasionally silently reboots - I've been able to test up to 20 
>>>>> sniffing sessions before it reboots, sometimes it will reboot immediately 
>>>>> when I start an monitor session.
>>>>> * I run the BBB headless, generally using SSH xterm.
>>>>> * The silent reboot happens with NO indication.  NOTHING.  The uart 
>>>>> console just shows a system restart.
>>>>> * I triggered a watchdog NMI (it takes 22 seconds) and it showed a lot 
>>>>> of diagnostic info - so that's not it.
>>>>>
>>>>
>>>> Further research - similar behavior was reported last year.  Lot's of 
>>>> red herrings (USB control appeared to be the most suspicious because 
>>>> that's 
>>>> my main interface but also long threads blaming the power management 
>>>> unit.) 
>>>>  Someone found that another clock source was needed for low-power state 
>>>> and 
>>>> moved the new code into u-boot.  I was running with a local build from 
>>>> RCN's git repo described at:
>>>>
>>>>
>>>> https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot
>>>>
>>>> and 2014.7 baseline.  I noticed it is now at 2014.10 so I rebuilt and 
>>>> installed on target.  The system is much more stable after testing for a 
>>>> lot longer than I could before.  And I'm pretty sure the clocking/power is 
>>>> the root cause of the silent reboots so I'm checking how the clock change, 
>>>> to the RTC32K clock, works.
>>>>
>>>> Also, since I'm running from emmc, I used am335x_boneblack_defconfig to 
>>>> build u-boot.  The only difference is it sets EMMC_BOOT but a quick grep 
>>>> shows it changes logic in a couple places.
>>>>
>>>> Anyway, it's a start...
>>>>
>>>>

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