Thanks for the logs. There was one suspicious line from the syslog:
Jun 4 20:11:33 dragonfly wpa_supplicant[1023]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:24:d4:69:f4:14 reason=4
Reason 4 is "WLAN_REASON_DISASSOC_DUE_TO_INACTIVITY" - the AP kicked out the associated station.
But, right before the disconnect, we see this:
Jun 4 20:11:25 dragonfly kernel: [ 224.978454] ath: phy0: tx hung, resetting the chip
Another weird line:
Jun 4 20:07:46 dragonfly kernel: [ 4.423684] ath: phy0: UNDEFINED -> AWAKE Jun 4 20:07:46 dragonfly kernel: [ 4.423754] ath: phy0: serialize_regmode is 0 Jun 4 20:07:46 dragonfly kernel: [ 4.425939] ath: phy0: timeout (1000 us) on reg 0x15f18: 0x00000000 & 0x00000007 != 0x00000004
Since you mentioned that things work with ANI disabled, I'll prepare some test patches for ANI against mainline.
Thanks for the logs. There was one suspicious line from the syslog:
Jun 4 20:11:33 dragonfly wpa_supplicant[ 1023]: wlan0: CTRL-EVENT- DISCONNECTED bssid=00: 24:d4:69: f4:14 reason=4
Reason 4 is "WLAN_REASON_ DISASSOC_ DUE_TO_ INACTIVITY" - the AP kicked out the associated station.
But, right before the disconnect, we see this:
Jun 4 20:11:25 dragonfly kernel: [ 224.978454] ath: phy0: tx hung, resetting the chip
Another weird line:
Jun 4 20:07:46 dragonfly kernel: [ 4.423684] ath: phy0: UNDEFINED -> AWAKE
Jun 4 20:07:46 dragonfly kernel: [ 4.423754] ath: phy0: serialize_regmode is 0
Jun 4 20:07:46 dragonfly kernel: [ 4.425939] ath: phy0: timeout (1000 us) on reg 0x15f18: 0x00000000 & 0x00000007 != 0x00000004
Since you mentioned that things work with ANI disabled, I'll prepare some test patches for ANI against mainline.