From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Bug report for ath10k and scanning many ssids.
Date: Wed, 02 Mar 2016 19:52:49 -0800 [thread overview]
Message-ID: <56D7B511.3040406@candelatech.com> (raw)
There is a bug in at least 10.1 ath10k firmware where the scan machine
cannot send more than 5 or so probe requests due to running out of firmware
management buffers.. Stock firmware is not smart enough to
wait a bit and send them later. To reproduce, use a supplicant file like
this (below). Maybe there is a way to work around it in the driver, but probably
better to just fix the firmware... A quick glance at 10.4 firmware makes
me think the bug is very likely there as well.
Thanks,
Ben
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
country=US
autoscan=periodic:10
network={
ssid="nonexist1"
scan_ssid=1
key_mgmt=NONE
}
network={
ssid="nonexist2"
scan_ssid=1
key_mgmt=NONE
}
network={
ssid="nonexist3"
scan_ssid=1
key_mgmt=NONE
}
network={
ssid="nonexist4"
scan_ssid=1
key_mgmt=NONE
}
network={
ssid="nonexist5"
scan_ssid=1
key_mgmt=NONE
}
network={
ssid="nonexist6"
scan_ssid=1
key_mgmt=NONE
}
network={
ssid="nonexist7"
scan_ssid=1
key_mgmt=NONE
}
network={
ssid="nonexist8"
scan_ssid=1
key_mgmt=NONE
}
network={
ssid="nonexist9"
scan_ssid=1
key_mgmt=NONE
}
network={
ssid="dd-wrt-ath1"
scan_ssid=1
key_mgmt=NONE
}
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
reply other threads:[~2016-03-03 3:52 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=56D7B511.3040406@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).