This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AP55 issue - ath10k: SWBA overrun on vdev 0

Hi all,

I am Home license user with a Sophos AP55 connected directly to my UTM hardware running on ASG software v9.312-8. AP has the latest firmware from what I can tell:

I am getting an ominous-looking error usually once a day in my wireless.log that appears to be a buffer overrun. See log snippet below. I can provide full daily logs if it would help.

Has anyone else seen this particular behavior? It seems to crop up, then all is well. I have had this behavior once, though, require me to power cycle the AP.

As a home license user who purchased an AP through a reseller, what is my recourse to investigate this through support?

2015:06:10-11:33:13 192.168.2.2 kernel: [88837.740000] ath10k: SWBA overrun on vdev 2

2015:06:10-11:33:13 192.168.2.2 kernel: [88837.790000] ath10k: SWBA overrun on vdev 0

2015:06:10-11:33:13 192.168.2.2 kernel: [88837.850000] ath10k: SWBA overrun on vdev 2

2015:06:10-11:33:13 192.168.2.2 kernel: [88837.900000] ath10k: SWBA overrun on vdev 0

2015:06:10-11:33:13 192.168.2.2 kernel: [88837.950000] ath10k: SWBA overrun on vdev 2

2015:06:10-11:33:13 192.168.2.2 kernel: [88838.000000] ath10k: SWBA overrun on vdev 0

2015:06:10-11:33:13 192.168.2.2 kernel: [88838.050000] ath10k: SWBA overrun on vdev 2

2015:06:10-11:33:13 192.168.2.2 kernel: [88838.100000] ath10k: SWBA overrun on vdev 0

2015:06:10-11:33:13 192.168.2.2 kernel: [88838.150000] ath10k: SWBA overrun on vdev 2

2015:06:10-11:33:16 192.168.2.2 kernel: [88840.610000] wlan8: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-11)

2015:06:10-11:33:18 192.168.2.2 kernel: [88842.760000] net_ratelimit: 90 callbacks suppressed

2015:06:10-11:33:18 192.168.2.2 kernel: [88842.770000] ath10k: SWBA overrun on vdev 2

2015:06:10-11:33:18 192.168.2.2 kernel: [88842.810000] ath10k: SWBA overrun on vdev 0

2015:06:10-11:33:18 192.168.2.2 kernel: [88842.860000] ath10k: SWBA overrun on vdev 2

2015:06:10-11:33:18 192.168.2.2 kernel: [88842.910000] ath10k: SWBA overrun on vdev 0

2015:06:10-11:33:18 192.168.2.2 kernel: [88842.970000] ath10k: SWBA overrun on vdev 2

2015:06:10-11:33:18 192.168.2.2 kernel: [88843.020000] ath10k: SWBA overrun on vdev 0

2015:06:10-11:33:18 192.168.2.2 kernel: [88843.070000] ath10k: SWBA overrun on vdev 2

2015:06:10-11:33:18 192.168.2.2 kernel: [88843.120000] ath10k: SWBA overrun on vdev 0

2015:06:10-11:33:18 192.168.2.2 kernel: [88843.170000] ath10k: SWBA overrun on vdev 2

2015:06:10-11:33:18 192.168.2.2 kernel: [88843.220000] ath10k: SWBA overrun on vdev 0

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.610000] ------------[ cut here ]------------

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.610000] WARNING: at /var/tmp/rpmbuild-rpmbuild/firmware-wifi/build_dir/target-mips_34kc_uClibc-0.9.33.2/linux-ar71xx_generic/compat-wireless-2014-05-22/net/mac80211/sta_info.c:889 sta_info_move_state+0x4d8/0x604 [mac80211]()

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.630000] Modules linked in: ath10k_pci ath10k_core ath9k ath9k_common ath9k_hw ath mac80211 cfg80211 compat arc4 crypto_blkcipher gpio_button_hotplug

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.640000] CPU: 0 PID: 1678 Comm: hostapd Not tainted 3.10.49 #3

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.650000] Stack : 00000000 00000000 00000000 00000000 8069aa5e 00000035 8782a328 00000000

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.650000] 	  802ae818 802e883b 0000068e 8069399c 8782a328 00000000 00000004 00000028

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.650000] 	  00000008 8025a930 00000003 801c8228 866497c8 00000000 802b033c 85ce3acc

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.650000] 	  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.650000] 	  00000000 00000000 00000000 00000000 00000000 00000000 00000000 85ce3a58

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.650000] 	  ...

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.690000] Call Trace:

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.690000] [] show_stack+0x48/0x70

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.690000] [] warn_slowpath_common+0x78/0xa8

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.700000] [] warn_slowpath_null+0x18/0x24

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.710000] [] sta_info_move_state+0x4d8/0x604 [mac80211]

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.710000] 

2015:06:10-11:33:19 192.168.2.2 kernel: [88843.710000] ---[ end trace 31940838d4d3b03f ]---

Thanks!

Andy

This thread was automatically locked due to age.

Parents

0 Scott_Klassen over 9 years ago

Is there not a defined support forum for home license users?
These forums are it.  The home license and paid license use the exact same software.  Just post in the forum that matches the functionality that you're having issues with.  These forums are a mix of home users, paid license users, and a few resellers.

Do support engineers just cruise the forums from time to time?
Officially these forums are user-to-user.  There are a small number of Sophos employees who participate here on and off a little, but they do so unofficially on their own time and cannot  act upon things they find here at work excepting if it is something verifiable, replicatable, that they believe may be affecting multiple paid license users.  They are here strictly as users.  Currently, none of these who've participated recently are support people.

I wanted to report the issue I'm seeing so that I could provide logs to support/development. They didn't even seem interested in that
Sophos is designed for business usage.  The idea behind the Home Usage license is as a marketing tool so that IT Pros would use it at home, thereby recommending it to their workplaces.  The pure home user is just considered a tag along.  There just isn't any way for the home license user to get Sophos resources expended on them, because Sophos, as a corporate entity, does not want that.  The exception to this is during public betas for upcoming versions, where all comers are welcome and is the main time to get access to Sophos devs officially.

I finally got sick of it and made a reservation as a workaround
If you are using the UTM for DHCP, which I assume you are, make certain that the "reservation" (static mapping in UTM-speak) is outside the scope of addresses being offered by the DHCP Server instance.  UTM doesn't do true reservations and if you create a static mapping within the DHCP scope, other addresses may still be offered.

I also have a AP15 in service and I have NOT seen this same buffer overrun with that AP
Different firmware branch, as it is manufactured by a different OEM.  Probably doesn't have the same code bug.

__________________
ACE v8/SCA v9.3

...still have a v5 install disk in a box somewhere.

http://xkcd.com
http://www.tedgoff.com/mb
http://www.projectcartoon.com/cartoon/1
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Scott_Klassen over 9 years ago

Is there not a defined support forum for home license users?
These forums are it.  The home license and paid license use the exact same software.  Just post in the forum that matches the functionality that you're having issues with.  These forums are a mix of home users, paid license users, and a few resellers.

Do support engineers just cruise the forums from time to time?
Officially these forums are user-to-user.  There are a small number of Sophos employees who participate here on and off a little, but they do so unofficially on their own time and cannot  act upon things they find here at work excepting if it is something verifiable, replicatable, that they believe may be affecting multiple paid license users.  They are here strictly as users.  Currently, none of these who've participated recently are support people.

I wanted to report the issue I'm seeing so that I could provide logs to support/development. They didn't even seem interested in that
Sophos is designed for business usage.  The idea behind the Home Usage license is as a marketing tool so that IT Pros would use it at home, thereby recommending it to their workplaces.  The pure home user is just considered a tag along.  There just isn't any way for the home license user to get Sophos resources expended on them, because Sophos, as a corporate entity, does not want that.  The exception to this is during public betas for upcoming versions, where all comers are welcome and is the main time to get access to Sophos devs officially.

I finally got sick of it and made a reservation as a workaround
If you are using the UTM for DHCP, which I assume you are, make certain that the "reservation" (static mapping in UTM-speak) is outside the scope of addresses being offered by the DHCP Server instance.  UTM doesn't do true reservations and if you create a static mapping within the DHCP scope, other addresses may still be offered.

I also have a AP15 in service and I have NOT seen this same buffer overrun with that AP
Different firmware branch, as it is manufactured by a different OEM.  Probably doesn't have the same code bug.

__________________
ACE v8/SCA v9.3

...still have a v5 install disk in a box somewhere.

http://xkcd.com
http://www.tedgoff.com/mb
http://www.projectcartoon.com/cartoon/1
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 30mpg over 9 years ago in reply to Scott_Klassen

bump - any updates or anyone else experiencing similar?

We seem to have a similar or the same problem on one of our two AP55C's. Have not contacted support yet but plan to shortly. Just upgraded to the latest firmware and the problem seems to persist.

2015:07:15-03:12:57 10.0.0.114 kernel: [2125442.570000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:12:57 10.0.0.114 kernel: [2125442.620000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:12:57 10.0.0.114 kernel: [2125442.670000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:12:57 10.0.0.114 kernel: [2125442.730000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:02 10.0.0.114 kernel: [2125447.540000] net_ratelimit: 119 callbacks suppressed
2015:07:15-03:13:02 10.0.0.114 kernel: [2125447.540000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:02 10.0.0.114 kernel: [2125447.570000] ath10k: failed to transmit management frame via WMI: -11
2015:07:15-03:13:02 10.0.0.114 kernel: [2125447.590000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:02 10.0.0.114 kernel: [2125447.640000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:02 10.0.0.114 kernel: [2125447.690000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:02 10.0.0.114 kernel: [2125447.740000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:02 10.0.0.114 kernel: [2125447.790000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:02 10.0.0.114 kernel: [2125447.850000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:02 10.0.0.114 kernel: [2125447.900000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:03 10.0.0.114 kernel: [2125447.950000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:07 10.0.0.114 kernel: [2125452.610000] net_ratelimit: 132 callbacks suppressed
2015:07:15-03:13:07 10.0.0.114 kernel: [2125452.610000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:07 10.0.0.114 kernel: [2125452.660000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:07 10.0.0.114 kernel: [2125452.710000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:07 10.0.0.114 kernel: [2125452.760000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:07 10.0.0.114 kernel: [2125452.810000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:07 10.0.0.114 kernel: [2125452.860000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:07 10.0.0.114 kernel: [2125452.910000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:07 10.0.0.114 kernel: [2125452.970000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:07 10.0.0.114 kernel: [2125453.020000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:08 10.0.0.114 kernel: [2125453.070000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:09 10.0.0.114 hostapd: wlan1: STA 20:16[:D]8:f0:cf:3d IEEE 802.11: authenticated
2015:07:15-03:13:09 10.0.0.114 hostapd: wlan1: STA 20:16[:D]8:f0:cf:3d IEEE 802.11: associated (aid 1)
2015:07:15-03:13:09 10.0.0.114 hostapd: wlan1: STA 20:16[:D]8:f0:cf:3d WPA: pairwise key handshake completed (RSN)
2015:07:15-03:13:09 10.0.0.114 awelogger[10409]: id="4103" severity="info" sys="System" sub="WiFi" name="STA authentication" ssid="Arxxus" ssid_id="WLAN1.0" bssid="00:1a:8c:8d:08:a5" sta="20:16[:D]8:f0:cf:3d" status_code="0"
2015:07:15-03:13:09 10.0.0.114 awelogger[10409]: id="4104" severity="info" sys="System" sub="WiFi" name="STA association" ssid="Arxxus" ssid_id="WLAN1.0" bssid="00:1a:8c:8d:08:a5" sta="20:16[:D]8:f0:cf:3d" status_code="0"
2015:07:15-03:13:12 10.0.0.114 kernel: [2125457.680000] net_ratelimit: 124 callbacks suppressed
2015:07:15-03:13:12 10.0.0.114 kernel: [2125457.680000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:12 10.0.0.114 kernel: [2125457.730000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:12 10.0.0.114 kernel: [2125457.780000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:12 10.0.0.114 kernel: [2125457.830000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:12 10.0.0.114 kernel: [2125457.880000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:12 10.0.0.114 kernel: [2125457.930000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:12 10.0.0.114 kernel: [2125457.980000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:12 10.0.0.114 kernel: [2125458.030000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:13 10.0.0.114 kernel: [2125458.090000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:13 10.0.0.114 kernel: [2125458.140000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:17 10.0.0.114 kernel: [2125462.740000] net_ratelimit: 180 callbacks suppressed
2015:07:15-03:13:17 10.0.0.114 kernel: [2125462.750000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:17 10.0.0.114 kernel: [2125462.800000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:17 10.0.0.114 kernel: [2125462.850000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:17 10.0.0.114 kernel: [2125462.900000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:17 10.0.0.114 kernel: [2125462.950000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:17 10.0.0.114 kernel: [2125463.000000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:17 10.0.0.114 kernel: [2125463.050000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:18 10.0.0.114 kernel: [2125463.100000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:18 10.0.0.114 kernel: [2125463.150000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:18 10.0.0.114 kernel: [2125463.210000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:22 10.0.0.114 kernel: [2125467.810000] net_ratelimit: 121 callbacks suppressed
2015:07:15-03:13:22 10.0.0.114 kernel: [2125467.820000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:22 10.0.0.114 kernel: [2125467.860000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:22 10.0.0.114 kernel: [2125467.920000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:22 10.0.0.114 kernel: [2125467.970000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:22 10.0.0.114 kernel: [2125468.020000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:22 10.0.0.114 kernel: [2125468.070000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:22 10.0.0.114 kernel: [2125468.120000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:22 10.0.0.114 kernel: [2125468.170000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:23 10.0.0.114 kernel: [2125468.220000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:23 10.0.0.114 kernel: [2125468.270000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:27 10.0.0.114 kernel: [2125472.880000] net_ratelimit: 116 callbacks suppressed
2015:07:15-03:13:27 10.0.0.114 kernel: [2125472.890000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:27 10.0.0.114 kernel: [2125472.930000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:27 10.0.0.114 kernel: [2125472.980000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:27 10.0.0.114 kernel: [2125473.040000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:27 10.0.0.114 kernel: [2125473.090000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:27 10.0.0.114 kernel: [2125473.140000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:28 10.0.0.114 kernel: [2125473.190000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:28 10.0.0.114 kernel: [2125473.240000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:28 10.0.0.114 kernel: [2125473.290000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:28 10.0.0.114 kernel: [2125473.340000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:32 10.0.0.114 kernel: [2125477.950000] net_ratelimit: 126 callbacks suppressed
2015:07:15-03:13:32 10.0.0.114 kernel: [2125477.960000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:32 10.0.0.114 kernel: [2125478.000000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:32 10.0.0.114 kernel: [2125478.050000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:32 10.0.0.114 kernel: [2125478.070000] ath10k: reached WMI management tranmist queue limit
2015:07:15-03:13:32 10.0.0.114 kernel: [2125478.080000] ath10k: failed to transmit packet, dropping: -16
2015:07:15-03:13:32 10.0.0.114 kernel: [2125478.090000] ath10k: reached WMI management tranmist queue limit
2015:07:15-03:13:32 10.0.0.114 kernel: [2125478.090000] ath10k: failed to transmit packet, dropping: -16
2015:07:15-03:13:32 10.0.0.114 kernel: [2125478.110000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:32 10.0.0.114 kernel: [2125478.160000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:33 10.0.0.114 kernel: [2125478.210000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:37 10.0.0.114 kernel: [2125483.020000] net_ratelimit: 123 callbacks suppressed
2015:07:15-03:13:37 10.0.0.114 kernel: [2125483.030000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:37 10.0.0.114 kernel: [2125483.070000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:37 10.0.0.114 kernel: [2125483.120000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:37 10.0.0.114 kernel: [2125483.170000] ath10k: SWBA overrun on vdev 0
2015:07:15-03:13:37 10.0.0.114 kernel: [2125483.230000] ath10k: SWBA overrun on vdev 2
2015:07:15-03:13:37 10.0.0.114 kernel: [2125483.280000] ath10k: SWBA overrun on vdev 0
Cancel
Vote Up 0 Vote Down

Cancel