On Wed, Sep 23, 2015 at 11:30:04AM +0000, Lukas Göstl via Devel wrote: > The Mesh Network runs well for about 2 - 3 hours. Then some wireless > adapters get stuck and do not response anymore. They need a Powercycle > to work again. > > Has anybody an idea why this happens or what`s the best way to debug > such a problem? I don't get any output in syslog.
Just the adapters but not the OS on the mesh node? Does re-plugging the device without rebooting recover? If so, it's probably a firmware or driver bug then, which are unfortunately harder to debug. One option is to get access to the UART on the device and then hookup a serial console, then you can at least add adf_os_print() calls in the firmware to debug [1]. I've seen these devices get stuck in a state where they stop sending any frames at all, which you can see in debugfs on the host -- one of the files (can't remember the filename right now) shows available TX slots and it quickly fills completely up without anything going over the air. But I never root-caused this and haven't reproduced it recently. [1] See http://bobcopeland.com/blog/2015/05/dwm-w034-uart/ and http://bobcopeland.com/blog/2015/05/reserialized/ for two devices where UART access is not too hard. -- Bob Copeland %% http://bobcopeland.com/ _______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
