frankd wrote: > ...In principle, it works very well. I have roughly 100 interrupts a > day, and it mitigates 99. However 1 out of 100 are not captured and the > radio goes offline. ... This is the first report of the mitigation not working in every case. How many times has this happened? What wlanpoke version are you running?
To investigate this, the log files are a first step, but they will be lost if the radio is rebooted. Could you please upload the logs for the affected period to your pc, then compress and post them here? You could try moving and connecting to an Ethernet cable, or if no battery, running a temporary cable to the radio. Alternatively, a wired serial connection to a TTL level serial adapter would work, and you could try various methods to restart the wireless. A second unload and reload might do it. wlanpoke should do this on its own, but that has never been documented. I don't believe the extra activity saving the logs has any effect on the connectivity loss, and the logs are not saved until the connection is lost anyway. You can use top and uptime to quickly check out the processor load. Your file system should not be full. ------------------------------------------------------------------------ POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=109953 _______________________________________________ Radio mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/radio
