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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
