You probably need a firmware with mgt over htt.  CT firmware has this, but you 
have to run our
kernel patches to allow CT htt-mgt firmware to work.

Upstream may have it as well in latest firmware...I'm not sure exactly what 
versions
do support that though.

Thanks,
Ben


On 09/09/2015 10:13 AM, Cedric VONCKEN wrote:
        I'm using compat-wireless 2015-03-09 from openwrt.

        At the power up, these equipments worked in AP mode and several sta can 
do an association.
        Randomly it is not possible to make association to several AP.

        If I look the log file I see cyclically these error messages.
Wed Sep  9 10:29:49 2015 kern.warn kernel: [17654.116104] ath10k_warn: 186 
callbacks suppressed
Wed Sep  9 10:29:49 2015 kern.warn kernel: [17654.133185] ath10k_pci 
0001:02:00.0: SWBA overrun on vdev 3, skipped old beacon
Wed Sep  9 10:29:49 2015 kern.warn kernel: [17654.153058] ath10k_pci 
0001:02:00.0: SWBA overrun on vdev 0, skipped old beacon
Wed Sep  9 10:29:49 2015 kern.warn kernel: [17654.157255] ath10k_pci 
0001:02:00.0: reached WMI management transmit queue limit
Wed Sep  9 10:29:49 2015 kern.warn kernel: [17654.157260] ath10k_pci 
0001:02:00.0: failed to transmit packet, dropping: -16
Wed Sep  9 10:29:49 2015 kern.warn kernel: [17654.212297] ath10k_pci 
0001:02:00.0: SWBA overrun on vdev 2, skipped old beacon
Wed Sep  9 10:29:49 2015 kern.warn kernel: [17654.232087] ath10k_pci 
0001:02:00.0: SWBA overrun on vdev 3, skipped old beacon
Wed Sep  9 10:29:49 2015 kern.warn kernel: [17654.252874] ath10k_pci 
0001:02:00.0: SWBA overrun on vdev 0, skipped old beacon
Wed Sep  9 10:29:49 2015 kern.warn kernel: [17654.286774] ath10k_pci 
0001:02:00.0: SWBA overrun on vdev 2, skipped old beacon
Wed Sep  9 10:29:49 2015 kern.warn kernel: [17654.320914] ath10k_pci 
0001:02:00.0: SWBA overrun on vdev 3, skipped old beacon
Wed Sep  9 10:29:49 2015 kern.warn kernel: [17654.355043] ath10k_pci 
0001:02:00.0: SWBA overrun on vdev 0, skipped old beacon
Wed Sep  9 10:29:54 2015 kern.warn kernel: [17659.167694] ath10k_warn: 193 
callbacks suppressed
Wed Sep  9 10:29:54 2015 kern.warn kernel: [17659.184778] ath10k_pci 
0001:02:00.0: SWBA overrun on vdev 0, skipped old beacon
Wed Sep  9 10:29:54 2015 kern.warn kernel: [17659.204514] ath10k_pci 
0001:02:00.0: SWBA overrun on vdev 2, skipped old beacon
Wed Sep  9 10:29:54 2015 kern.warn kernel: [17659.225098] ath10k_pci 
0001:02:00.0: reached WMI management transmit queue limit
Wed Sep  9 10:29:54 2015 kern.warn kernel: [17659.235968] ath10k_pci 
0001:02:00.0: SWBA overrun on vdev 3, skipped old beacon
Wed Sep  9 10:29:54 2015 kern.warn kernel: [17659.264524] ath10k_pci 
0001:02:00.0: failed to transmit packet, dropping: -16
Wed Sep  9 10:29:54 2015 kern.warn kernel: [17659.270094] ath10k_pci 
0001:02:00.0: SWBA overrun on vdev 0, skipped old beacon
Wed Sep  9 10:29:54 2015 kern.warn kernel: [17659.303945] ath10k_pci 
0001:02:00.0: failed to transmit management frame via WMI: -11
Wed Sep  9 10:29:54 2015 kern.warn kernel: [17659.304408] ath10k_pci 
0001:02:00.0: reached WMI management transmit queue limit
Wed Sep  9 10:29:54 2015 kern.warn kernel: [17659.304414] ath10k_pci 
0001:02:00.0: failed to transmit packet, dropping: -16
Wed Sep  9 10:29:54 2015 kern.warn kernel: [17659.363876] ath10k_pci 
0001:02:00.0: SWBA overrun on vdev 2, skipped old beacon
Wed Sep  9 10:29:59 2015 kern.warn kernel: [17664.219316] ath10k_warn: 208 
callbacks suppressed

        To reestablish my access point I need to restart the Wifi (wifi up in 
openwrt).

        Have you any idea of this issue?

        Regards.

Cédric Voncken.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html



--
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to