From: Sascha Hauer <s.hauer@pengutronix.de>
To: Petter Mabacker <petter@technux.se>
Cc: linux-wireless@vger.kernel.org, pkshih@realtek.com,
tony0620emma@gmail.com
Subject: Re: rtw88: rtw8822cu (LM842) -> failed to get tx report from firmware
Date: Mon, 8 May 2023 15:46:26 +0200 [thread overview]
Message-ID: <20230508134626.GZ29365@pengutronix.de> (raw)
In-Reply-To: <20230508132901.44137-1-petter@technux.se>
On Mon, May 08, 2023 at 03:29:01PM +0200, Petter Mabacker wrote:
> I'm working with a Linux 6.1 based track, but with all the mentioned bug fixes cherry-picked to that track. They have all made the LM842 a lot more stabile, but the issue I see with "tx report failed" is currently blocking me from using the LM842, since the mender upgrade is a crucial part for my use-case.
>
> I have been trying to find a better way to reproduce the issue, without any success so far. For me it takes just 10-30 sec with above mention flooding using iperf to at least trigger a similar case.
>
> ...
> [ 671.908527] rtw_8822cu 1-1:1.2: failed to get rx_queue, overflow
> [ 671.914632] rtw_8822cu 1-1:1.2: failed to get rx_queue, overflow
> [ 671.920750] rtw_8822cu 1-1:1.2: failed to get rx_queue, overflow
> [ 671.926792] rtw_8822cu 1-1:1.2: failed to get rx_queue, overflow
> [ 671.932924] rtw_8822cu 1-1:1.2: failed to get rx_queue, overflow
I am still not sure what to do about this. It happens with high RX load.
One way would be to just drop the log level of this message.
Otherwise this message should be harmless.
>
> [ 694.709045] rtw_8822cu 1-1:1.2: failed to get tx report from firmware
>
> [ 710.169496] rtw_8822cu 1-1:1.2: firmware failed to report density after scan
> [ 717.701235] rtw_8822cu 1-1:1.2: failed to send h2c command
>
> I can also mention that I'm running this in a i.MX6 SoloX based board.
>
> I will let you guys know if I find a better way to reproduce the
> issue. But if you have any good ideas what above error (that brings
> down the entire interface) really mean (for example does it indicate
> kernel or firmware issue), please feel free to share some information
> about it and it might help me in troubleshooting the issue further.
Please try reproducing this with a recent mainline vanilla kernel. It
shouldn't be too hard to bring up a i.MX6 board with a vanilla kernel.
Regards,
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-08 13:46 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 [this message]
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
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=20230508134626.GZ29365@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).