I hear you guys might be trying to track this down...
This is from one of the higher level nodes on the Santa Barbara network.
I'm wondering if there is actually something wrong with the device due to very very poor performance.
I am seeing the "OLSR restarts" area in the bottom left corner of the status page.
I've never seen this before on our network. I also went around to all our nodes and only this one that has this message on it's status page.
OLSR restarts 2
runtime 2 - 16:04:20
This node also appears to have rebooted it self in the last day or so... I am glad I got the support data before that happened. Very odd behavior.
I don't think there is away to attach to this post, so please find the support data here:
https://beachcabin.r1de.net/supportdata-K6TZ-LCP-NSM2-W60-201703201751.tgz
73 and thank you!
kg6wxc
A support data file can be easily attached to your Forum post by clicking 1) Choose File button and then 2) the Upload button in the Support File Attachments section at the bottom of your new Forum posting just above the Save button for the post. See example below.
[ 209.850000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[13105.850000] ath: phy0: Failed to stop TX DMA, queues=0x00a!
[23763.570000] ath: phy0: Failed to stop TX DMA, queues=0x00a!
[27315.500000] ath: phy0: Failed to stop TX DMA, queues=0x00a!
[28777.910000] ath: phy0: Failed to stop TX DMA, queues=0x002!
[28990.960000] ath: phy0: Failed to stop TX DMA, queues=0x00a!
...
...
Baseband Hang: 0
Baseband Watchdog: 0
Fatal HW Error: 0
TX HW error: 0
Transmit timeout: 0
TX Path Hang: 11
PLL RX Hang: 0
MAC Hang: 0
Stuck Beacon: 1228
MCI Reset: 0
Calibration error: 0
"Stuck Beacon" doesn't sound good at all. That is from a different node than the previous Support File. It also has quite a string of those same errors in dmesg output. Just wondering what it all means. Thanks Darryl!
I do recall there are numerous fixes for this type of error in the next release of OpenWrt (Chaos Calmer) which is what our develop/snapshot builds are using.
If these errors are consistent, you may want to consider loading the develop build to see if things improve. Caveat: develop builds are not supported nor intended for production environments.