@Graham Wow! I hadn’t yet thought of Ethernet as a point of failure. Apart from the (“It doesn’t always soft-reset" issue — see outline I.B.1.b) I’d guess you could solve this with the onboard watchdog timer. Run some kind of daemon that periodically “Checks for good ethernet” (a bit vague, I know), if found, it tickles the watchdog, if not, it provokes a reboot. But yes, the problem remains that the reboot doesn’t always complete.
Of course if your ethernet got fried, that’d turn into a reboot cycle without some logic to notify you of the problem, and stop after a number of cycles. > On May 16, 2016, at 7:56 PM, Graham <[email protected]> wrote: > > It all depends on what you are worried about. > > I have several BBBs that I use as servers, and I want them to be robust. > > So while working through power backup and an external hardware watchdog per > all the previous discussions, we have a thunderstorm roll through the area. > > No close strikes, but the Ethernet network interface went catatonic, would > not send or receive, but didn't throw any errors. > > I could not SSH into the command line. > > But the local serial port/command line worked fine. The kernel seemed to be > happily running, and not worried about anything in particular. > > The system logs looked like someone had disconnected the Ethernet cable > during the storm, but the network was still physically connected, with the > RJ-45 socket lights blinking. > > A power cycle reestablished everything. > > So, probably some kind of transient flipped a few configuration register bits > and stopped the Ethernet interface. > No physical damage. > > This kind of thing can not be unique, because I note that there are Ethernet > controlled power strips with "Auto-Ping." > Stated feature is “Auto-Ping” feature to intelligently reboot a locked-up AP, > router, VoIP phone, server, camera. or other device automatically. > > Web Power Switch 7. http://www.digital-loggers.com/lpc.html > > So either I can go buy a $115 smart AC power switch, or use an Ethernet-PIC > instead of the MSP430. > > --- Graham > > == > > > -- > For more options, visit http://beagleboard.org/discuss > <http://beagleboard.org/discuss> > --- > You received this message because you are subscribed to a topic in the Google > Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/RaFm9AT7-2c/unsubscribe > <https://groups.google.com/d/topic/beagleboard/RaFm9AT7-2c/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/47e04409-af30-4c62-9b3b-445a82036380%40googlegroups.com > > <https://groups.google.com/d/msgid/beagleboard/47e04409-af30-4c62-9b3b-445a82036380%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/AA5B0956-374D-45E8-9336-22899699F9E7%40gmail.com. For more options, visit https://groups.google.com/d/optout.
