From: Fabio Estevam <festevam@gmail.com>
To: alagusankar@silex-india.com, erik.stromdahl@gmail.com
Cc: ath10k@lists.infradead.org, Kalle Valo <kvalo@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
wgong@codeaurora.org, Peter Oh <peter.oh@eero.com>
Subject: ath10k: Incorrect MTU size for SDIO
Date: Thu, 19 Aug 2021 14:29:26 -0300 [thread overview]
Message-ID: <CAOMZO5CHuYX6heA-3+jJ+wHUOBFcLsiy43E9qOoOx3WuJ_kP_g@mail.gmail.com> (raw)
Hi,
On a i.MX7-based board with QCA9377 chip, I received the following
report from a user running kernel 5.10.48:
"Doing scp or just pipe through files with >10 lines I get stalls and
error logs. The ath10k_sdio errors look like this:
[ 196.822363] ath10k_sdio mmc2:0001:1: failed to transmit packet, dropping: -12
[ 196.830109] ath10k_sdio mmc2:0001:1: failed to submit frame: -12
[ 196.836279] ath10k_sdio mmc2:0001:1: failed to push frame: -12
[ 196.925452] ath10k_sdio mmc2:0001:1: failed to transmit packet, dropping: -12
[ 196.933090] ath10k_sdio mmc2:0001:1: failed to submit frame: -12
[ 196.939334] ath10k_sdio mmc2:0001:1: failed to push frame: -12
I am able to reliably reproduce the issue by sending a lot of data
from the i.MX7 board to a host connected via the AP:
printf '=%.0s' {1..24000} | nc 192.168.0.2 1234
I was able to narrow the issue down to the mtu. If I set the mtu for
the wlan0 device to 1486 instead of 1500, the issue does not happen.
The size of frames that I see on Wireshark is exactly 1500 after
setting it to 1486."
Is this a known issue?
Alagu/Erik,
Have you ever observed such an issue?
Thanks
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2021-08-19 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 17:29 Fabio Estevam [this message]
2021-09-15 0:04 ` ath10k: Incorrect MTU size for SDIO Fabio Estevam
2021-09-15 0:56 ` Fabio Estevam
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=CAOMZO5CHuYX6heA-3+jJ+wHUOBFcLsiy43E9qOoOx3WuJ_kP_g@mail.gmail.com \
--to=festevam@gmail.com \
--cc=alagusankar@silex-india.com \
--cc=ath10k@lists.infradead.org \
--cc=erik.stromdahl@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=peter.oh@eero.com \
--cc=wgong@codeaurora.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).