#18794: ath10k: Spurious quick kickout for STA
---------------------------------------------+-----------------------------
Reporter: Anton van Bohemen <avbohemen@…> | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Chaos Calmer
Component: base system | (trunk)
Keywords: | Version: Trunk
---------------------------------------------+-----------------------------
Running a TP-Link Archer C7 v2 with CC r43790, my kernel log is filling up
with these messages, every second:
{{{
[168037.910000] ath10k_pci 0000:01:00.0: Spurious quick kickout for STA
f4:f1:5a:cd:73:7c
[168038.910000] ath10k_pci 0000:01:00.0: Spurious quick kickout for STA
f4:f1:5a:cd:73:7c
[168039.910000] ath10k_pci 0000:01:00.0: Spurious quick kickout for STA
f4:f1:5a:cd:73:7c
}}}
System memory is also filling up slowly when these messages occur. CPU
usage is negligible (according to collectd). The only way to clear this
situation is to do "wifi down; wifi", after which the 'stale peer' MAC is
removed:
{{{
[168040.800000] device wlan1 left promiscuous mode
[168040.800000] br-lan: port 3(wlan1) entered disabled state
[168040.840000] device wlan0 left promiscuous mode
[168040.840000] br-lan: port 2(wlan0) entered disabled state
[168040.850000] ath10k_pci 0000:01:00.0: removing stale peer
f4:f1:5a:cd:73:7c from vdev_id 0
[168040.860000] ath10k_pci 0000:01:00.0: received addba event for invalid
peer_id: 30
[168040.870000] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id
30
[168042.850000] ath10k_pci 0000:01:00.0: otp stream is empty, using
board.bin contents
[168043.870000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[168043.890000] device wlan0 entered promiscuous mode
[168043.950000] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[168043.970000] device wlan1 entered promiscuous mode
[168043.970000] br-lan: port 3(wlan1) entered forwarding state
[168043.980000] br-lan: port 3(wlan1) entered forwarding state
[168045.520000] br-lan: port 3(wlan1) entered disabled state
[168045.520000] br-lan: port 2(wlan0) entered forwarding state
[168045.530000] br-lan: port 2(wlan0) entered forwarding state
[168045.530000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[168045.560000] br-lan: port 3(wlan1) entered forwarding state
[168045.560000] br-lan: port 3(wlan1) entered forwarding state
[168045.570000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[168047.530000] br-lan: port 2(wlan0) entered forwarding state
[168047.560000] br-lan: port 3(wlan1) entered forwarding state
}}}
BTW, the device in question is an iPhone 5, running IOS 8.1.2. It probably
connected and left the AP many times. My guess is the 'stale peer' should
be cleaned more quickly (i.e. directly after it disconnects from the AP)?
--
Ticket URL: <https://dev.openwrt.org/ticket/18794>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
