From: "s.hauer@pengutronix.de" <s.hauer@pengutronix.de>
To: "petter@technux.se" <petter@technux.se>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"pkshih@realtek.com" <pkshih@realtek.com>,
"tony0620emma@gmail.com" <tony0620emma@gmail.com>
Subject: Re: rtw88: rtw8822cu (LM842) -> failed to get tx report from firmware
Date: Wed, 24 May 2023 12:45:10 +0200 [thread overview]
Message-ID: <20230524104510.GV15436@pengutronix.de> (raw)
In-Reply-To: <188007.70407276-sendEmail@petterwork>
Hi Petter,
On Thu, Apr 06, 2023 at 10:41:20AM +0000, petter@technux.se wrote:
> Hi,
>
> I have seen a very similar issue as Andreas. It was found when streaming a mender file (using mender install <url> from my arm device. But I have also managed to reproduce a similar issue by flooding the interface using iperf.
>
> on target:
> $ sudo iperf -s -u
>
> On host:
> $ iperf -c <ip> -u -b 200M -t 300
>
> Then it will almost instantly get problems causing the lm842 dongle to stop working.
I could finally reproduce this problem by placing an access point close
enough to my device. Only then the incoming packet rate is high enough
that the "failed to get rx_queue, overflow" message triggers.
In my case the time it takes to print this message many times is enough
to confuse the device so that it finally responds with:
[ 126.449305] rtw_8822cu 1-1:1.2: failed to get tx report from firmware
[ 142.081419] rtw_8822cu 1-1:1.2: firmware failed to report density after scan
[ 175.929407] rtw_8822cu 1-1:1.2: firmware failed to report density after scan
I just sent a patch printing the message with dev_dbg_ratelimited
instead which fixes that problem for me, you're on Cc.
It likely won't fix Andreas' problem though, as I don't see this message
in his bug report.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-05-24 10:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 10:41 rtw88: rtw8822cu (LM842) -> failed to get tx report from firmware petter
2023-04-11 12:48 ` s.hauer
2023-05-08 13:29 ` Petter Mabacker
2023-05-08 13:46 ` Sascha Hauer
2023-05-09 7:43 ` Petter Mabacker
2023-05-09 9:08 ` Sascha Hauer
2023-05-09 15:08 ` Gabriel Tisan
2023-05-11 13:26 ` Petter Mabacker
2023-05-12 7:29 ` Gabriel Tisan
2023-05-24 10:45 ` s.hauer [this message]
2023-05-26 5:55 ` Petter Mabacker
2023-06-30 16:47 ` petter
-- strict thread matches above, loose matches on Subject: below --
2023-02-20 10:17 Andreas Henriksson
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=20230524104510.GV15436@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-wireless@vger.kernel.org \
--cc=petter@technux.se \
--cc=pkshih@realtek.com \
--cc=tony0620emma@gmail.com \
/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).