From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: ath10k number-of-peers exceeded (hacked 3.17, CT firmware)
Date: Wed, 18 Feb 2015 11:21:21 -0800 [thread overview]
Message-ID: <54E4E631.70800@candelatech.com> (raw)
One of the users of CT firmware (and my 3.17 kernel backported to their 3.14)
reported this. This system is also having bad WMI mgt timeout issues, and
firmware crashed before these logs started (due to WMI tx hang), so possibly
that is the root cause of the peer issues. The user believes he has only
a few stations connected to this AP.
There may be additional patches to the driver/kernel as well..some of this looks
a bit strange to me.
I am curious if there are known bugs in the 3.17 era with peer counter
mis-management?
Feb 18 09:31:00 wlan1: AP-STA-CONNECTED 00:1f:3b:11:b1:25
Feb 18 09:31:00 hostapd: wlan1: STA 00:1f:3b:11:b1:25 IEEE 802.11: associated (aid 8)
Feb 18 09:31:00 kernel: [84594.723772] ath10k_pci 0000:07:00.0: state: 1 number of peers exceeded: peers number 64 (max peers 64)
Feb 18 09:31:00 wlan1: NEW-STA-CONNECTED 00:1f:3b:11:b1:25
Feb 18 09:31:00 wlan1: STA 00:1f:3b:11:b1:25 IEEE 802.11: Could not add STA to kernel driver
Feb 18 09:31:00 wlan1: AP-STA-DISCONNECTED 00:1f:3b:11:b1:25
Feb 18 09:31:00 hostapd: wlan1: STA 00:1f:3b:11:b1:25 IEEE 802.11: Could not add STA to kernel driver
Feb 18 09:31:00 wlan1: AUTH-RECEIVED 00:1f:3b:11:b1:25|04:f0:21:0f:3d:57|-41|9999|
Feb 18 09:31:00 wlan1: STA 00:1f:3b:11:b1:25 IEEE 802.11: authenticated
Feb 18 09:31:00 hostapd: wlan1: STA 00:1f:3b:11:b1:25 IEEE 802.11: authenticated
Feb 18 09:31:00 wlan1: STA 00:1f:3b:11:b1:25 IEEE 802.11: associated (aid 8)
Feb 18 09:31:00 wlan1: AP-STA-CONNECTED 00:1f:3b:11:b1:25
Feb 18 09:31:00 hostapd: wlan1: STA 00:1f:3b:11:b1:25 IEEE 802.11: associated (aid 8)
Feb 18 09:31:00 kernel: [84594.776796] ath10k_pci 0000:07:00.0: state: 1 number of peers exceeded: peers number 64 (max peers 64)
Feb 18 09:31:00 wlan1: NEW-STA-CONNECTED 00:1f:3b:11:b1:25
Feb 18 09:31:00 wlan1: STA 00:1f:3b:11:b1:25 IEEE 802.11: Could not add STA to kernel driver
Feb 18 09:31:00 hostapd: wlan1: STA 00:1f:3b:11:b1:25 IEEE 802.11: Could not add STA to kernel driver
Feb 18 09:31:00 wlan1: AP-STA-DISCONNECTED 00:1f:3b:11:b1:25
Feb 18 09:31:00 wlan1: AUTH-RECEIVED 00:1f:3b:11:b1:25|04:f0:21:0f:3d:57|-39|9999|
Feb 18 09:31:00 wlan1: STA 00:1f:3b:11:b1:25 IEEE 802.11: authenticated
Feb 18 09:31:00 hostapd: wlan1: STA 00:1f:3b:11:b1:25 IEEE 802.11: authenticated
Feb 18 09:31:00 wlan1: AUTH-RECEIVED 00:21:6a:5f:3f:c2|04:f0:21:0f:3d:57|-34|9999|
Feb 18 09:31:00 wlan1: STA 00:21:6a:5f:3f:c2 IEEE 802.11: authenticated
Feb 18 09:31:00 hostapd: wlan1: STA 00:21:6a:5f:3f:c2 IEEE 802.11: authenticated
Feb 18 09:31:00 wlan1: STA 00:1f:3b:11:b1:25 IEEE 802.11: associated (aid 8)
Feb 18 09:31:00 wlan1: AP-STA-CONNECTED 00:1f:3b:11:b1:25
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
reply other threads:[~2015-02-18 19:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54E4E631.70800@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).