Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Authorized-sender: petter@technux.se
From:   Petter Mabacker <petter@technux.se>
To:     gabriel.tisan@gmail.com
Cc:     linux-wireless@vger.kernel.org, petter@technux.se,
        pkshih@realtek.com, s.hauer@pengutronix.de, tony0620emma@gmail.com
Subject: Re: rtw88: rtw8822cu (LM842) -> failed to get tx report from firmware
Date:   Thu, 11 May 2023 15:26:07 +0200
Message-Id: <20230511132607.2908454-1-petter@technux.se>
In-Reply-To: <CAD9ZU8BHTOA9=V7NQvkGBLK4DV2NRvk2rDxJX6qr6unZsg-QdA@mail.gmail.com>
References: <CAD9ZU8BHTOA9=V7NQvkGBLK4DV2NRvk2rDxJX6qr6unZsg-QdA@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

>Actually there is a recent firmware 9.9.15.
>Petter use that, is displayed in the first email.

>I have also an LM482 with 9.9.15 firmware. I used iperf with TCP and I
>could not reproduce that.
>I will try iperf with UDP like in your case.
>How do you use LM482 when running iperf ? As station or AP ?

>Gabriel

Yes, I have been using 9.9.15, but I have also tested using 9.9.14 firmware.
I'm running it as a station. Please let me know if you manage to reproduce a similar behaviour by flooding the udp like in my example.

Thanks.
BR Petter

On Tue, May 9, 2023 at 11:18=E2=80=AFAM Sascha Hauer <s.hauer@pengutronix.d=
e> wrote:
>>
>> On Tue, May 09, 2023 at 09:43:50AM +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.
>> >
>> > Like stated in earlier mails, the initial problem was found during a
>> > mender upgrade (streaming a ~200MB file). In that case the problem
>> > occurs without any high RX load warnings. So that is not really
>> > related (at least I don't think so).
>> >
>> > The real problem is that the driver ends-up in a not working state
>> > after this. Not even hot-plugging the dongle will help. Instead a
>> > reboot or reset of the driver (rmmod/insmod etc) is required.
>> >
>> > >>
>> > >> [  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.
>> >
>> > Just to be sure, I have tried this using latest kernel tree as you suggested:
>> >
>> > ~# uname -r
>> > 6.4.0-rc1-g5ca44e46dff4
>> >
>> > However I get the very same behavior (in this case it's from the failed mender upgrade):
>> > [  724.788270] rtw_8822cu 1-1:1.2: failed to get tx report from firmware
>> > [  728.499480] rtw_8822cu 1-1:1.2: failed to send h2c command
>> > [  758.558511] rtw_8822cu 1-1:1.2: firmware failed to report density after scan
>> > May 09 06:48:17 iotgw mender[643]: time=3D"2023-05-09T06:48:17Z" level=3Derror msg=3D"Download connection broken: read tcp 192.168.68.113:54072->52.239.140.42:443: read: connection timed out"
>> > [  796.975782] rtw_8822cu 1-1:1.2: firmware failed to report density after scan
>> > [  835.251656] rtw_8822cu 1-1:1.2: firmware failed to report density after scan
>> > [  843.586421] rtw_8822cu 1-1:1.2: failed to send h2c command
>>
>> Unfortunately it looks like this very often when something goes wrong in
>> the RTW88 driver. These messages seem to be a general sign for the
>> device to say that we have touched it wrong somehow and it's stuck now.
>>
>> >
>> > When I try to hotplug the dongle (that still don't solve the issue). I
>> > can see below printout, any ideas what it really mean? (I never see
>> > this before the problem occurs, only when hotplugging after the
>> > problem occurs):
>> >
>> > [ 2298.729359] wlx34c9f08deb60: Limiting TX power to 23 (23 - 0) dBm as advertised by 1c:3b:f3:55:59:93
>> >
>> > Since you cannot reproduce the similar (perhaps not even the same root
>> > issue) issue I saw using iperf, I will focus on trying to reproduce it
>> > using something similar as the streaming procedure done by mender. Any
>> > other suggestions from your side, or any logs etc that could be of
>> > interest?
>>
>> You could verify that you are using a recent firmware. The driver prints
>> it during initialization. It should be 9.9.11.
>>
>> Other than that I don't have any good idea, sorry.
>>
>> 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 |