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:     s.hauer@pengutronix.de
Cc:     linux-wireless@vger.kernel.org, petter@technux.se,
        pkshih@realtek.com, tony0620emma@gmail.com
Subject: Re: rtw88: rtw8822cu (LM842) -> failed to get tx report from firmware
Date:   Mon,  8 May 2023 15:29:01 +0200
Message-Id: <20230508132901.44137-1-petter@technux.se>
In-Reply-To: <20230411124836.GM19113@pengutronix.de>
References: <20230411124836.GM19113@pengutronix.de>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

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

[  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.

BR Petter