linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Ma <aaron.ma@canonical.com>
To: pkshih@realtek.com
Cc: kvalo@codeaurora.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 00/24] rtw89: add Realtek 802.11ax driver
Date: Wed, 30 Jun 2021 12:52:04 +0800	[thread overview]
Message-ID: <f1caa1a2-55c7-a69f-070a-a49b345e4550@canonical.com> (raw)
In-Reply-To: <20210623062909.24409-1-aaron.ma@canonical.com>

Hi,

Previous result is from a single antenna PCI card of 8852AE.
After test on another Laptop with 8852AE, it works fine.
Result:
AP ASUS AX86u: TX 660M RX 880M

AP Netgear R7800: TX 500M RX 561M
Looks like the performance is affected by antenna.

The error log is not reproduced again.

Tested-by: Aaron Ma <aaron.ma@canonical.com>

Aaron

On 6/23/21 2:29 PM, Aaron Ma wrote:
> Hi Ping-Ke,
> 
> After applied your patches on 5.17-rc7, tested on pci device:
> 04:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:8852]
> 
> I found the performance is a bit poor on TX especially.
> Tested on Intel AX210, it's result is TX 461Mb/s and RX 547Mb/s at the same position.
> 
> $ iperf3 -c 192.168.1.7
> Connecting to host 192.168.1.7, port 5201
> [  5] local 192.168.1.6 port 40942 connected to 192.168.1.7 port 5201
> [ ID] Interval           Transfer     Bitrate         Retr  Cwnd
> [  5]   0.00-1.00   sec  26.2 MBytes   220 Mbits/sec    0   1.12 MBytes
> [  5]   1.00-2.00   sec  21.2 MBytes   178 Mbits/sec    0   1.76 MBytes
> [  5]   2.00-3.00   sec  33.8 MBytes   283 Mbits/sec    0   2.00 MBytes
> [  5]   3.00-4.00   sec  31.2 MBytes   262 Mbits/sec    0   2.12 MBytes
> [  5]   4.00-5.00   sec  30.0 MBytes   252 Mbits/sec    0   2.38 MBytes
> [  5]   5.00-6.00   sec  31.2 MBytes   262 Mbits/sec    0   2.56 MBytes
> [  5]   6.00-7.00   sec  31.2 MBytes   262 Mbits/sec    0   2.56 MBytes
> [  5]   7.00-8.00   sec  27.5 MBytes   231 Mbits/sec    0   2.56 MBytes
> [  5]   8.00-9.00   sec  35.0 MBytes   294 Mbits/sec    0   2.56 MBytes
> [  5]   9.00-10.00  sec  31.2 MBytes   262 Mbits/sec    0   2.69 MBytes
> - - - - - - - - - - - - - - - - - - - - - - - - -
> [ ID] Interval           Transfer     Bitrate         Retr
> [  5]   0.00-10.00  sec   299 MBytes   251 Mbits/sec    0             sender
> [  5]   0.00-10.01  sec   296 MBytes   248 Mbits/sec                  receiver
> 
> iperf Done.
> 
> $ iperf3 -c 192.168.1.7 -R
> Connecting to host 192.168.1.7, port 5201
> Reverse mode, remote host 192.168.1.7 is sending
> [  5] local 192.168.1.6 port 40946 connected to 192.168.1.7 port 5201
> [ ID] Interval           Transfer     Bitrate
> [  5]   0.00-1.00   sec  46.4 MBytes   389 Mbits/sec
> [  5]   1.00-2.00   sec  48.7 MBytes   408 Mbits/sec
> [  5]   2.00-3.00   sec  48.5 MBytes   407 Mbits/sec
> [  5]   3.00-4.00   sec  51.9 MBytes   435 Mbits/sec
> [  5]   4.00-5.00   sec  47.8 MBytes   401 Mbits/sec
> [  5]   5.00-6.00   sec  50.7 MBytes   426 Mbits/sec
> [  5]   6.00-7.00   sec  48.2 MBytes   404 Mbits/sec
> [  5]   7.00-8.00   sec  48.2 MBytes   405 Mbits/sec
> [  5]   8.00-9.00   sec  51.0 MBytes   428 Mbits/sec
> [  5]   9.00-10.00  sec  52.0 MBytes   436 Mbits/sec
> - - - - - - - - - - - - - - - - - - - - - - - - -
> [ ID] Interval           Transfer     Bitrate         Retr
> [  5]   0.00-10.00  sec   497 MBytes   417 Mbits/sec  126             sender
> [  5]   0.00-10.00  sec   493 MBytes   414 Mbits/sec                  receiver
> 
> iperf Done.
> 
> 
> Also I found some errors when stress test, not sure how to reproduce yet, copy log here:
> 
> kernel: rtw89_pci 0000:04:00.0: Firmware version 0.13.24.0, cmd version 0, type 1
> kernel: rtw89_pci 0000:04:00.0: Firmware version 0.13.24.0, cmd version 0, type 3
> kernel: rtw89_pci 0000:04:00.0: chip rfe_type is 1
> kernel: initcall rtw89_pci_driver_init+0x0/0x1000 [rtw89_pci] returned 0 after 26621 usecs
> kernel: rtw89_pci 0000:04:00.0 wlp4s0: renamed from wlan0
> kernel: wlp4s0: authenticate with 9c:d3:6d:a3:b2:e7
> kernel: wlp4s0: send auth to 9c:d3:6d:a3:b2:e7 (try 1/3)
> kernel: wlp4s0: send auth to 9c:d3:6d:a3:b2:e7 (try 2/3)
> kernel: wlp4s0: send auth to 9c:d3:6d:a3:b2:e7 (try 3/3)
> kernel: wlp4s0: authentication with 9c:d3:6d:a3:b2:e7 timed out
> kernel: wlp4s0: authenticate with 9c:d3:6d:a3:b2:e7
> kernel: wlp4s0: send auth to 9c:d3:6d:a3:b2:e7 (try 1/3)
> kernel: wlp4s0: authenticated
> kernel: wlp4s0: associate with 9c:d3:6d:a3:b2:e7 (try 1/3)
> kernel: wlp4s0: RX AssocResp from 9c:d3:6d:a3:b2:e7 (capab=0x11 status=0 aid=9)
> kernel: wlp4s0: associated
> kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> kernel: rtw89_pci 0000:04:00.0: FW status = 0xb9001100
> kernel: rtw89_pci 0000:04:00.0: FW BADADDR = 0x0
> kernel: rtw89_pci 0000:04:00.0: FW EPC/RA = 0x0
> kernel: rtw89_pci 0000:04:00.0: FW MISC = 0xb8990c7b
> kernel: rtw89_pci 0000:04:00.0: R_AX_HALT_C2H = 0x10
> kernel: rtw89_pci 0000:04:00.0: R_AX_SER_DBG_INFO = 0x41000001
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xb8991bcb
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xb8991bd5
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xb8991acb
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xbfc00180
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xb8991bf9
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xb8991ba7
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xb8991bd3
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xb8991ae3
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xb8991aad
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xb8991ba7
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xb8991bd1
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xb8991ac5
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xb8991ba7
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xb8991ad1
> kernel: rtw89_pci 0000:04:00.0: [ERR]fw PC = 0xb8991bbb
> kernel: rtw89_pci 0000:04:00.0: --->
>          err=0x10
> 

      reply	other threads:[~2021-06-30  4:52 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18  6:46 [PATCH 00/24] rtw89: add Realtek 802.11ax driver Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 01/24] rtw89: add CAM files Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 02/24] rtw89: add BT coexistence files Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 03/24] rtw89: add core and trx files Ping-Ke Shih
2021-07-09 17:32   ` Oleksij Rempel
2021-07-12  6:23     ` Pkshih
2021-07-15 18:57   ` Brian Norris
2021-07-16  2:00     ` Pkshih
2021-06-18  6:46 ` [PATCH 04/24] rtw89: add debug files Ping-Ke Shih
2021-07-02  7:23   ` Oleksij Rempel
2021-07-02 17:08     ` Brian Norris
2021-07-02 17:57       ` Oleksij Rempel
2021-07-02 18:38         ` Brian Norris
2021-07-02 19:32           ` Oleksij Rempel
2021-07-02 20:00             ` Brian Norris
2021-07-03  4:15               ` Oleksij Rempel
2021-07-13  1:40                 ` Brian Norris
2021-07-05  8:58           ` Pkshih
2021-07-05  9:09             ` Oleksij Rempel
2021-07-05  8:08         ` Kalle Valo
2021-07-05  9:23           ` Oleksij Rempel
2021-07-05  8:58     ` Pkshih
2021-07-13  1:57       ` Brian Norris
2021-07-13  4:50         ` Oleksij Rempel
2021-07-13 11:26           ` Pkshih
2021-06-18  6:46 ` [PATCH 05/24] rtw89: add efuse files Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 06/24] rtw89: add files to download and communicate with firmware Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 07/24] rtw89: add MAC files Ping-Ke Shih
2021-07-09 17:38   ` Oleksij Rempel
2021-07-09 18:16     ` Johannes Berg
2021-07-10  4:58       ` Oleksij Rempel
2021-07-12  1:51         ` Pkshih
2021-07-12  6:23     ` Pkshih
2021-06-18  6:46 ` [PATCH 08/24] rtw89: implement mac80211 ops Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 09/24] rtw89: add pci files Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 10/24] rtw89: add phy files Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 11/24] rtw89: define register names Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 12/24] rtw89: add regulatory support Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 13/24] rtw89: 8852a: add 8852a specific files Ping-Ke Shih
2021-07-10  5:27   ` Oleksij Rempel
2021-07-12  6:24     ` Pkshih
2021-06-18  6:46 ` [PATCH 14/24] rtw89: 8852a: add 8852a RFK files Ping-Ke Shih
2021-07-09 17:41   ` Oleksij Rempel
2021-07-12  6:23     ` Pkshih
2021-07-15  3:33     ` Pkshih
2021-07-15  3:59       ` Oleksij Rempel
2021-06-18  6:46 ` [PATCH 15/24] rtw89: 8852a: add 8852a RFK tables Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 16/24] rtw89: 8852a: add 8852a tables (1 of 5) Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 17/24] rtw89: 8852a: add 8852a tables (2 " Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 18/24] rtw89: 8852a: add 8852a tables (3 " Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 19/24] rtw89: 8852a: add 8852a tables (4 " Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 20/24] rtw89: 8852a: add 8852a tables (5 " Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 21/24] rtw89: add ser to recover error reported by firmware Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 22/24] rtw89: add PS files Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 23/24] rtw89: add SAR files Ping-Ke Shih
2021-06-18  6:46 ` [PATCH 24/24] rtw89: add Kconfig and Makefile Ping-Ke Shih
2021-06-19  3:18   ` kernel test robot
2021-06-25  8:54     ` Pkshih
2021-06-19  3:18   ` kernel test robot
2021-06-18  7:11 ` [PATCH 00/24] rtw89: add Realtek 802.11ax driver Pkshih
2021-06-23  6:29 ` Aaron Ma
2021-06-30  4:52   ` Aaron Ma [this message]

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=f1caa1a2-55c7-a69f-070a-a49b345e4550@canonical.com \
    --to=aaron.ma@canonical.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.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).