Bug 214231 - iwlwifi dies during transfer of large amount of data
Summary: iwlwifi dies during transfer of large amount of data
Status: CLOSED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless-intel (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: Default virtual assignee for network-wireless-intel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-30 21:04 UTC by Olaf Hering
Modified: 2023-10-12 08:17 UTC (History)
1 user (show)

See Also:
Kernel Version: 5.3, 5.13
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg-5.13.13-lp153.5.g6339fac-default.txt.xz (50.21 KB, application/x-xz)
2021-08-30 21:04 UTC, Olaf Hering
Details
lspci-5.13.13-lp153.5.g6339fac-default.txt.xz (3.88 KB, application/x-xz)
2021-08-30 21:05 UTC, Olaf Hering
Details
dmesg-5.15.6-lp153.2.gc2ce213-default.txt.gz (43.53 KB, application/gzip)
2021-12-03 19:37 UTC, Olaf Hering
Details
dmesg-6.0.10-lp153.4.g1004618-default.txt (93.83 KB, text/plain)
2022-12-03 07:50 UTC, Olaf Hering
Details

Description Olaf Hering 2021-08-30 21:04:43 UTC
Created attachment 298541 [details]
dmesg-5.13.13-lp153.5.g6339fac-default.txt.xz

I have a ZBox with iwlwifi which is supposed to act as a backup storage for data from phones. It receives files fine from a Galaxy S5, but fails to receive from a Pixel 3a.

First I worked with the S5 (SM-G900FD / klteduos), transferring to "SMS Backup+" worked fine. Also transferring several GiB of data with syncthing worked fine.
Second I worked with the 3a, transferring data to "SMS Backup+" worked fine. But transferring the photos/videos kills the WiFi connection.

Device in the ZBox is:
01:00.0 0280: 8086:3165 (rev 81)
        Subsystem: 8086:4010

I tried kernel 5.3 which is included in Leap 15.3, and also kernel 5.13.13. Both show the same symptoms. Synthing can transfer its metadata, but transferring the actual files does not happen. After a while dmesg shows:

[   11.559720] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[   11.598545] iwlwifi 0000:01:00.0: Found debug destination: EXTERNAL_DRAM
[   11.610988] iwlwifi 0000:01:00.0: Found debug configuration: 0
[   11.618169] iwlwifi 0000:01:00.0: loaded firmware version 29.4063824552.0 7265D-29.ucode op_mode iwlmvm
[   11.805436] iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC 3165, REV=0x210
[   11.875543] iwlwifi 0000:01:00.0: Applying debug destination EXTERNAL_DRAM
[   11.884527] iwlwifi 0000:01:00.0: Allocated 0x00400000 bytes for firmware monitor.
...
[  107.412187] iwlwifi 0000:01:00.0: Applying debug destination EXTERNAL_DRAM
[  107.498387] iwlwifi 0000:01:00.0: Applying debug destination EXTERNAL_DRAM
[  107.507912] iwlwifi 0000:01:00.0: FW already configured (0) - re-configuring
[  386.070859] ------------[ cut here ]------------
[  386.076572] WARNING: CPU: 1 PID: 542 at drivers/net/wireless/intel/iwlwifi/mvm/tx.c:1453 iwl_mvm_rx_tx_cmd+0x6e2/0xac0 [iwlmvm]
[  386.089622] Modules linked in: ccm dm_crypt essiv authenc trusted asn1_encoder tee dm_mod af_packet bridge stp llc iscsi_ibft iscsi_b>
[  386.089702]  aesni_intel r8169 processor_thermal_device processor_thermal_rfim processor_thermal_mbox crypto_simd i2c_i801 cec snd_ti>
[  386.180508] CPU: 1 PID: 542 Comm: irq/129-iwlwifi Kdump: loaded Not tainted 5.13.13-lp153.5.g6339fac-default #1 openSUSE Tumbleweed (>
[  386.180512] Hardware name: NA NA/Default string, BIOS 5.13 09/18/2020
[  386.180514] RIP: 0010:iwl_mvm_rx_tx_cmd+0x6e2/0xac0 [iwlmvm]
[  386.180534] Code: 89 ef 4c 89 4c 24 08 e8 8c 70 ff ff 4c 8b 4c 24 08 88 85 56 18 00 00 e9 e7 fe ff ff 66 81 fb 8e 00 41 0f 94 c5 e9 c>
[  386.180537] RSP: 0018:ffffa4d140104d50 EFLAGS: 00010246
[  386.180539] RAX: 0000000000000000 RBX: 0000000000000088 RCX: ffffffff8558dd82
[  386.180541] RDX: 000000008020001a RSI: ffffffffc0ffeffd RDI: 0000000000000000
[  386.180542] RBP: ffff8eeb30011f48 R08: 0000000000000001 R09: ffff8eeb31871430
[  386.180544] R10: ffff8eea00000000 R11: 00000001316c20fc R12: ffff8eeb316c20e4
[  386.180545] R13: ffffa4d140104e90 R14: ffff8eeb31871400 R15: ffff8eeb31819000
[  386.180547] FS:  0000000000000000(0000) GS:ffff8eec7f480000(0000) knlGS:0000000000000000
[  386.180549] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  386.180551] CR2: 00007f1c5149c000 CR3: 0000000201210000 CR4: 0000000000350ee0
[  386.180553] Call Trace:
[  386.180558]  <IRQ>
[  386.180560]  ? rs_drv_get_rate+0x43/0xe0 [iwlmvm]
[  386.392429]  ? rate_control_get_rate+0xe6/0x140 [mac80211]
[  386.399085]  iwl_mvm_rx_common+0xf6/0x2b0 [iwlmvm]
[  386.399124]  iwl_pcie_rx_handle+0x3a7/0x970 [iwlwifi]
[  386.399149]  iwl_pcie_napi_poll+0x2a/0x130 [iwlwifi]
[  386.399167]  __napi_poll+0x27/0x150
[  386.399174]  net_rx_action+0x24c/0x2a0
[  386.399178]  __do_softirq+0xc2/0x275
[  386.399184]  do_softirq+0x78/0x90
....

The WiFi connection then permanently drops.

Is there a way to "downgrade" the connection to a type that is used by the S5? I assume a phone from 2014 uses different standards than a phone from 2020.

Let me know if any other information is missing.
Comment 1 Olaf Hering 2021-08-30 21:05:11 UTC
Created attachment 298543 [details]
lspci-5.13.13-lp153.5.g6339fac-default.txt.xz
Comment 2 Miri Korenblit 2021-12-02 13:50:56 UTC
Hi

Can you please provide the driver version?

do:
modinfo iwlwifi and check the output in the field "version", please.

Thanks
Comment 3 Olaf Hering 2021-12-02 14:55:37 UTC
modinfo iwlwifi | grep -w version returns nothing.
Other than that, the used source is whatever can be found here:
https://github.com/gregkh/linux/tree/v5.13.3/drivers/net/wireless/intel/iwlwifi
Comment 4 Olaf Hering 2021-12-03 19:37:52 UTC
Created attachment 299855 [details]
dmesg-5.15.6-lp153.2.gc2ce213-default.txt.gz

Fails also with 5.15.6
See "v5.15.6" tag on git.kernel.org for the actual sources.
Comment 5 Miri Korenblit 2022-11-13 07:10:47 UTC
Hi,

Sorry for the late response.

We have a fix now that removes that WARNING.
I think that the WIFI stops because of a big amount of warnings.
Please upgrade your kernel version and check if that helps.

Thanks,
Miri
Comment 6 Olaf Hering 2022-11-13 07:23:19 UTC
Thank you for the update.
Is there a reference to the change?
In other words, will v6.1 or v6.2 have this change?
Comment 7 Miri Korenblit 2022-11-13 07:38:57 UTC
yes, both of them
Comment 8 Olaf Hering 2022-12-03 07:50:48 UTC
Created attachment 303345 [details]
dmesg-6.0.10-lp153.4.g1004618-default.txt

6.0.10 reported firmware errors (maybe this can be trimmed, avoiding dups), but apparently syncthing succeeded. But the amount of data to sync was small (80MB).

I will check how it goes with a huge amount of dirty data to sync.
Comment 9 Emmanuel Grumbach 2023-10-12 08:16:59 UTC
Closing this for now.
You can re-open of needed

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