From: Ben Greear <greearb@candelatech.com>
To: Vincent RUBY <vruby@cube-technologies.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Kernel crash when scanning for APs in huge WiFi environment - Ath10K - ARMV7 - Linux 4.14.73
Date: Fri, 9 Jul 2021 08:58:51 -0700 [thread overview]
Message-ID: <c2f66f16-3800-b127-4c58-704a29ec693d@candelatech.com> (raw)
In-Reply-To: <e23f3f12dcab42ea9ab4b7384080cdf2@Cube-mail.cube.local>
On 7/9/21 8:48 AM, Vincent RUBY wrote:
> Hi,
>
> I apologize in advance if I am writing at the wrong place.
> We have developed a custom embedded board based on ARMV7. On the board there is a Telit WE866C3-P Wifi module (based on ath10k).
> Linux : 4.14.73 (YOCTO/poky)
> Microcontroller : SAMA5D27
>
> The board is working perfectly in a normal Wifi environment (e.g., at office).
> But when the board is put in a huge Wifi environment (e.g., 350 APs with 2 antennas each with more than 600 visible BSSIDS) the Linux kernel crashes when attempting to connect to a Wifi network using wpa_supplicant.
> When the Wifi antenna is attenuated with some electromagnetic obstacle (e.g., hand or metallic shield), the board connects without any problem.
>
> The problem is the same when running a scan from wpa_cli .
>
> Do you have any idea where I can find some clue to resolve this issue?
>
> Many thanks in advance !
>
> VinceCube
>
Please show the details of the kernel crash. And either way, answer is probably to try more
recent kernel and see if problem is already fixed.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2021-07-09 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1cef8054e4e447f2ba02d1de1e6afdf8@Cube-mail.cube.local>
2021-07-09 15:48 ` Kernel crash when scanning for APs in huge WiFi environment - Ath10K - ARMV7 - Linux 4.14.73 Vincent RUBY
2021-07-09 15:58 ` Ben Greear [this message]
2021-07-09 16:15 ` Vincent RUBY
2021-07-09 16:34 ` Ben Greear
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=c2f66f16-3800-b127-4c58-704a29ec693d@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=vruby@cube-technologies.net \
/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