Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp5500885rwr; Tue, 9 May 2023 02:18:25 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4c1tVcAMvWXJ4YSM8Xk2hxdiDrGOrFJoiAwMW3INesJV5Pel5njk1Xa8HCCvihx6nsIhHn X-Received: by 2002:a17:90a:2981:b0:247:6be7:8cc0 with SMTP id h1-20020a17090a298100b002476be78cc0mr12898789pjd.35.1683623905635; Tue, 09 May 2023 02:18:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683623905; cv=none; d=google.com; s=arc-20160816; b=oo4Pt7tSBFSZpfp18uVDtL6g1Oxz6bEF6ud6egO9OG7pFtZhDyXH4HKhrcnMdXw3ow Lj4txk3tHZgoC1LUR8TtRJsOC/nlwr7WlNukZP/uLJy3T+V3xwlFZZsZN4TuYiZgytiW AnQtLNHO5VHt/uTQw0xvhY5UNiSLl8hY2OUTGxMQC9zKD39y56gvoazd/Q7XnyYNjxGl C9s1HTsQZEHXQCLSkPltCNyrBVCw7J3eQOz6/pSvjT6cNzRxI4fsWwBqmtZTbqA8vwRo JmwWFro8UO8O3qC07mscn9L2PmU7q7oBhd2w2jWWtzSjunHs8WfFcnHpQ1qPHQdk1XuB 2bkA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=DZQPj3UfpzNIrxTfSwHZ/8BkFDEWN1SmsmA98MT/SW8=; b=hQ+taEJjjsulYHCjCA9Nng9XWbOVEdT6W+4mCyMVCODUkSi62nLh0tgfbGXLk07i1C 0Rz69Ksq4OCGC0WIirDJMpK2FTXKWai+hm6zDm/UdLVbumAbziOGUneKFa1X1wpaERnO V9vQmH9YzXpnu4cPCs1FYPse7K7lzC8VkqVyS+q6Etgzqev27soqnJdbXCuvNaz+FVEB lxDBMlOg9yONEb2V784fu7OE/b+2efYqWWuVz2BvrF93LEuOG8xA2joJX0wJ53DBdoDc 57jh94p7itImIUPhttNcIQjnM+4wDLkzJIOM43zjoxYm3rmESJ4vjm8Gaek+z7SfLTGB fbNw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k71-20020a63844a000000b0050fb7c5a656si1081374pgd.190.2023.05.09.02.18.15; Tue, 09 May 2023 02:18:25 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233586AbjEIJIr (ORCPT + 62 others); Tue, 9 May 2023 05:08:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36850 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229773AbjEIJIq (ORCPT ); Tue, 9 May 2023 05:08:46 -0400 Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [IPv6:2001:67c:670:201:290:27ff:fe1d:cc33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3BD17D2 for ; Tue, 9 May 2023 02:08:45 -0700 (PDT) Received: from ptx.hi.pengutronix.de ([2001:67c:670:100:1d::c0]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pwJKt-0002yS-I3; Tue, 09 May 2023 11:08:43 +0200 Received: from sha by ptx.hi.pengutronix.de with local (Exim 4.92) (envelope-from ) id 1pwJKr-0003sa-KO; Tue, 09 May 2023 11:08:41 +0200 Date: Tue, 9 May 2023 11:08:41 +0200 From: Sascha Hauer To: Petter Mabacker Cc: linux-wireless@vger.kernel.org, pkshih@realtek.com, tony0620emma@gmail.com Subject: Re: rtw88: rtw8822cu (LM842) -> failed to get tx report from firmware Message-ID: <20230509090841.GE29365@pengutronix.de> References: <20230508134626.GZ29365@pengutronix.de> <20230509074350.2862571-1-petter@technux.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230509074350.2862571-1-petter@technux.se> X-Sent-From: Pengutronix Hildesheim X-URL: http://www.pengutronix.de/ X-Accept-Language: de,en X-Accept-Content-Type: text/plain User-Agent: Mutt/1.10.1 (2018-07-13) X-SA-Exim-Connect-IP: 2001:67c:670:100:1d::c0 X-SA-Exim-Mail-From: sha@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-wireless@vger.kernel.org X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org 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="2023-05-09T06:48:17Z" level=error msg="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 |