Searching around a bit, I wonder if an old u-boot version might have anything to do with it? From what I can tell, I'm still using an u-boot release from 2013.07 . Should I be updating this? If so, what would be the safest way to do so? In /boot/uboot/tools, I noticed a couple of scripts (bootloader_update, update and update_boot_files). Would any of these work or should I get a more recent version?
On Monday, October 13, 2014 12:23:29 PM UTC+2, Sebastian H wrote: > > @Micka: > I'm not sure how to check for increased memory usage as it's completely > unpredictable when it's going to reboot. Is there some kind of logging I > can enable for memory usage so it would get logged to my netconsole? > As for logs, the netconsole log has nothing before the reboot occurs (just > like the previous reports on this thread, including the one from > RobertCNelson). Here <http://pastebin.com/P2zuPbAJ>'s the kernel log from > when it booted up after the sudden reboot. > I also checked the syslog and there's nothing out of the ordinary in it. > It appears as if some killed the power for a second and the system just > boots up again. > Is there any other log I could look for? > > @lisarden: > How would I go about checking the PMIC? Looking at the kernel log from the > boot I can only see this: > [ 5.761536] sr_init: No PMIC hook to init smartreflex > [ 5.767135] sr_init: platform driver register failed for SR > I've also checked my past kernel logs and it's always the same line. > > Checking the kernel config, I'm not seeing any obvious setting to enable. > Can you point me in the correct direction? > > Thanks to both of you for your replies. > > On Monday, October 13, 2014 10:55:40 AM UTC+2, Mickae1 wrote: >> >> Did you check if memory usage is increasing ? Log file ? >> >> Micka, >> >> On Mon, Oct 13, 2014 at 10:49 AM, Sebastian H <sho...@gmail.com> wrote: >> >>> For the record, even with the watchdog package removed, my BBB rebooted >>> on me again after just 7 hours of uptime. :-( >>> Here <http://pastebin.com/UwF2fsRB>'s the kernel config I used. >>> Searching for watchdog, there are only two entries. This is the one still >>> enabled: >>> CONFIG_OMAP_REMOTEPROC_WATCHDOG=y >>> Should I disable that as well? >>> >>> On Sunday, October 12, 2014 6:29:26 PM UTC+2, Sebastian H wrote: >>>> >>>> The issue still happened even using the kernel compiled without any >>>> watchdog support. The netconsole log didn't include any details. It just >>>> rebooted again without any indication why. That was about 24 hours after >>>> the last restart. >>>> I still had the watchdog package installed (but with even the software >>>> watchdog disabled in the kernel, I didn't think it would do anything). >>>> Well, I now removed that, but I'm not convinced that it did cause the >>>> reboot. >>>> >>>> >>>> On Thursday, October 9, 2014 5:54:40 PM UTC+2, Sebastian H wrote: >>>>> >>>>> I switched over from kernel 3.8.13 to 3.14.19-ti-r28 (compiled with >>>>> netconsole support) and after a little over 24 hours uptime, my BBB >>>>> rebooted without any entries in the netconsole log or any logs on the BBB >>>>> that I could find. >>>>> >>>>> Did anyone have any luck in troubleshooting this issue any further? >>>>> >>>>> In the meantime, I guess I'll try your suggestion of disabling the >>>>> watchdog for now. >>>>> >>>>> >>>>> On Thursday, September 18, 2014 11:48:22 AM UTC+2, William Hermans >>>>> wrote: >>>>>> >>>>>> Short term, you can disable the hardware watchdog in kernel config. >>>>>> That should temporarily fix your problem, and if it does not . . . >>>>>> bigger >>>>>> mystery. >>>>>> >>>>>> Long term, it would be good to figure out what is triggering the >>>>>> watchdog. strace on the watchdog PID will not work - I tested this >>>>>> myself. >>>>>> >>>>>> The only one thing I can think of off hand is perhaps modifying the >>>>>> watchdog module to output a debug message before rebooting the system. >>>>>> As >>>>>> to which process triggered a shutdown, and why. If possible . . . >>>>>> >>>>>> Will research more tomorrow it is very late ( actually early ) here. >>>>>> >>>>>> On Thu, Sep 18, 2014 at 12:57 AM, Thomas Olofsson <skjo...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> >>>>>>>> Forget about claiming its a hardware issue. Because it is not. >>>>>>>> We've had two beaglebone blacks for close to a year, and a half now. >>>>>>>> Both >>>>>>>> are rock solid, running off barrel jack power, or USB( one of each ). >>>>>>>> >>>>>>>> Ok well just stating facts that bbw is not rebooting and BBB is >>>>>>> with the same kernel >>>>>>> >>>>>>> Ok i would be happy to stop guessing and actually find the problem. >>>>>>> Could you give me some real advise on HOW to use the serial module >>>>>>> appropriately. i do have it connected to the serial console and i have >>>>>>> event built a kernel with verbosed debugging on i am just not seeing >>>>>>> anything. >>>>>>> >>>>>>> So if you would like any information or dumps or whatever i am happy >>>>>>> to provide that. >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> 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...@googlegroups.com. >>>>>>> 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 beagleboard...@googlegroups.com. >>> 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
