Bug 205061 - iwlwifi: ax200 : SYSASSERT 103C when UDP UL is more than 120Mbps
Summary: iwlwifi: ax200 : SYSASSERT 103C when UDP UL is more than 120Mbps
Status: NEEDINFO
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: Intel Linux Wireless
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-01 09:30 UTC by Ivan Klokov
Modified: 2019-11-20 19:41 UTC (History)
4 users (show)

See Also:
Kernel Version: Linux 5.2.11-050211-generic #201908290731 SMP Thu Aug 29 07:33:42 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux19 x86_64 x86_64 x86_64 GNU/Linux
Tree: Mainline
Regression: No


Attachments
kernel dmesg log (79.97 KB, text/plain)
2019-10-01 09:30 UTC, Ivan Klokov
Details
dmesg after crash. UDP upstream, 4 parallel client streams (62.71 KB, text/plain)
2019-10-09 18:23 UTC, robert.carter
Details

Description Ivan Klokov 2019-10-01 09:30:21 UTC
Created attachment 285273 [details]
kernel dmesg log

We are testing ax200ngw using iperf. When iperf generates 100Mbps UDP uplink, then all looks good. However when UDP UL traffic is 120Mbps, firwmare crashes. Here is an iperf command: 
$ iperf -i 0.5 -u -y c -w 1M -c 192.168.1.21 -t 60 -b 120M -e -p 10001

Firmware version:
$ ethtool -i wlo1 | grep firmware
firmware-version: 48.4fa0041f.0

Kernel log is attached.
Note that the issue can be reproduced with both 11ac and 11ax AP.

Best regards,
Ivan
Comment 1 robert.carter 2019-10-09 18:23:23 UTC
Created attachment 285435 [details]
dmesg after crash. UDP upstream, 4  parallel client streams

I get a slightly different assert code, 0xEDC:

  Loaded firmware version: 48.4fa0041f.0
  0x00000EDC | ADVANCED_SYSASSERT
Comment 2 Luca Coelho 2019-11-20 19:41:49 UTC
Today I found a bug in the driver that causes problems during high TX throughput (or rather, high number of frames that would cause mac80211 to use AMSDU).  Can you please try this patch and see if it helps with the issue you are experiencing?

https://patchwork.kernel.org/patch/11253471/

Note You need to log in before you can comment on or make changes to this bug.