AP30 unstable since 9.401

Hi,

(currently running 9.402-7)

My AP30 frequently seems to reboot, after moving from 9.355 with VLANs to a new VM running 9.401 without VLANs.

Sometimes, I get email messages from the UTM "WARN-728 Access Point is Offline".

Here's the wireless.log entries from the last occurance:

2016:05:27-00:22:00 192.168.211.211 hostapd: wlan1: STA 1c:5c:f2:9b:34:79 IEEE 802.11: authenticated
2016:05:27-00:22:00 192.168.211.211 hostapd: wlan1: STA 1c:5c:f2:9b:34:79 IEEE 802.11: associated (aid 5)
2016:05:27-00:22:00 192.168.211.211 awelogger[1477]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="WIFIWIFI2" ssid_id="WLAN2.0" bssid="00:1a:8c:29:77:81" sta="1c:5c:f2:9b:34:79" status_code="0"
2016:05:27-00:22:00 192.168.211.211 awelogger[1477]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="WIFIWIFI2" ssid_id="WLAN2.0" bssid="00:1a:8c:29:77:81" sta="1c:5c:f2:9b:34:79" status_code="0"
2016:05:27-00:22:00 192.168.211.211 hostapd: wlan1: STA 1c:5c:f2:9b:34:79 WPA: pairwise key handshake completed (RSN)
2016:05:27-00:22:00 192.168.211.211 awelogger[1477]: id="4101" severity="info" sys="System" sub="WiFi" name="STA connected" ssid="WIFIWIFI2" ssid_id="WLAN2.0" bssid="00:1a:8c:29:77:81" sta="1c:5c:f2:9b:34:79"
2016:05:27-00:23:51 192.168.211.211 hostapd: wlan1: STA 0c:d7:46:ab:84:00 IEEE 802.11: disassociated due to inactivity
2016:05:27-00:23:51 192.168.211.211 awelogger[1477]: id="4102" severity="info" sys="System" sub="WiFi" name="STA disconnected" ssid="WIFIWIFI2" ssid_id="WLAN2.0" bssid="00:1a:8c:29:77:81" sta="0c:d7:46:ab:84:00"
2016:05:27-00:23:52 192.168.211.211 hostapd: wlan1: STA 0c:d7:46:ab:84:00 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] kswapd0: page allocation failure: order:0, mode:0x20
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] CPU: 0 PID: 99 Comm: kswapd0 Not tainted 3.10.49 #3
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] Stack : 00000000 00000000 00000000 00000000 8054a0de 00000033 8182b3e8 00000000
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] 	  80237544 8026c673 00000063 805437fc 8182b3e8 00000000 00000000 00000000
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] 	  00000000 801e73cc 00000000 8015b69c 00000006 00000000 80239070 819a5a9c
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] 	  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] 	  00000000 00000000 00000000 00000000 00000000 00000000 00000000 819a5a28
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] 	  ...
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] Call Trace:
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] [<80193870>] show_stack+0x48/0x70
2016:05:27-00:25:54 192.168.211.211 kernel: [  549.240000] [<801f8b7c>] warn_alloc_failed+0x108/0x12c
2016:05:27-00:26:40 fw awed[22827]: [A4000BE4D4BC5D2] ll_read: dead socket: Resource temporarily unavailable
2016:05:27-00:26:40 fw awed[22827]: [A4000BE4D4BC5D2] disconnected. Close socket and kill process.
2016:05:27-00:26:44 fw awed[4687]: [MASTER] new connection from 192.168.211.211:41002
2016:05:27-00:26:45 fw awed[23793]: [A4000BE4D4BC5D2] AP30 from 192.168.211.211:41002 identified as A4000BE4D4BC5D2
2016:05:27-00:26:45 fw awed[23793]: [A4000BE4D4BC5D2] (Re-)loaded identity and/or configuration