All of lore.kernel.org
 help / color / mirror / Atom feed
From: "petter@technux.se" <petter@technux.se>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"pkshih@realtek.com" <pkshih@realtek.com>,
	"tony0620emma@gmail.com" <tony0620emma@gmail.com>
Subject: rtw88: rtw8822cu (LM842) -> failed to get tx report from firmware
Date: Thu, 6 Apr 2023 10:41:20 +0000	[thread overview]
Message-ID: <188007.70407276-sendEmail@petterwork> (raw)

[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]

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'm using below fw:
  $ sudo dmesg | grep 8822c
  [   19.282167] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_fw.bin
  [   19.299025] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_config.bin
  [   19.628570] rtw_8822cu 1-1:1.2: WOW Firmware version 9.9.4, H2C version 15
  [   19.641604] rtw_8822cu 1-1:1.2: Firmware version 9.9.15, H2C version 15


$ iperf -s -u
------------------------------------------------------------
Server listening on UDP port 5001
UDP buffer size:  176 KByte (default)
------------------------------------------------------------
[  415.791320] rtw_8822cu 1-1:1.2: failed to get rx_queue, overflow
[  415.797443] rtw_8822cu 1-1:1.2: failed to get rx_queue, overflow
[  415.803511] rtw_8822cu 1-1:1.2: failed to get rx_queue, overflow
[  415.809635] rtw_8822cu 1-1:1.2: failed to get rx_queue, overflow
[  438.102270] rtw_8822cu 1-1:1.2: failed to get tx report from firmware
[  441.446726] rtw_8822cu 1-1:1.2: failed to send h2c command
[  471.480932] rtw_8822cu 1-1:1.2: firmware failed to report density after scan


Any ideas what might be the cause of this? I have also tried to use the latest patch from Sascha that seems to be aimed to fix some issue I thought might have been related to this(https://lore.kernel.org/linux-wireless/20230404072508.578056-1-s.hauer@pengutronix.de/T/#m54b7c8c604b91cfce470fcec8fc7d4c20f3056c9), but still get same behavior.

BR,
Petter Mabäcker


             reply	other threads:[~2023-04-06 10:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 10:41 petter [this message]
2023-04-11 12:48 ` rtw88: rtw8822cu (LM842) -> failed to get tx report from firmware 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
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=188007.70407276-sendEmail@petterwork \
    --to=petter@technux.se \
    --cc=20230220101740.i7wxzzvte3xnwht4@fatal.se \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=s.hauer@pengutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.