Bug 218838 - [ath11k] invalid HE MCS bw:6, ru:6 in cfg80211_calculate_bitrate_he
Summary: [ath11k] invalid HE MCS bw:6, ru:6 in cfg80211_calculate_bitrate_he
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P3 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-14 18:28 UTC by Mikko Tiihonen
Modified: 2024-12-17 08:54 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Mikko Tiihonen 2024-05-14 18:28:12 UTC 
I'm unable to connect to my Wifi 7 AP on 6GHz band using my Lenovo P14s Gen 4 laptop.

Sometimes when the connection fails the following appears on the logs


invalid HE MCS: bw:6, ru:6
WARNING: CPU: 13 PID: 1242 at net/wireless/util.c:1551 cfg80211_calculate_bitrate_he+0x1b7/0x3c0 [cfg80211]
CPU: 13 PID: 1242 Comm: NetworkManager Not tainted 6.9.0-0.rc7.20240510git448b3fe5a0ea.62.fc41.x86_64 #1
Hardware name: LENOVO 21K5000DMX/21K5000DMX, BIOS R2FET56W (1.36 ) 03/13/2024
RIP: 0010:cfg80211_calculate_bitrate_he+0x1b7/0x3c0 [cfg80211]
Code: 00 40 80 fe 06 0f 84 a1 00 00 00 40 80 fe 03 0f 84 d6 00 00 00 40 84 f6 0f 84 0b 01 00 00 48 c7 c7 41 33 96 c1 e8 59 cd 8d e8 <0f> 0b 31 c0 eb 53 44 0f b6 e8 3c 02 0f 87 62 01 00 00 42 8b 44 ac
RSP: 0018:ffffa5f2c6df7320 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffffa5f2c6df7518 RCX: 0000000000000027
RDX: ffff9166df0a18c8 RSI: 0000000000000001 RDI: ffff9166df0a18c0
RBP: 0000000000000002 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffffc196335e R11: 0000000000000001 R12: 0000000000000009
R13: ffff91580eae0000 R14: ffff915b0ed33ef0 R15: ffff915a8b051b00
FS:  00007f7d396cd580(0000) GS:ffff9166df080000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00003d7c6e07d000 CR3: 0000000137282000 CR4: 0000000000f50ef0
PKRU: 55555554
Call Trace:
 <TASK>
 ? cfg80211_calculate_bitrate_he+0x1b7/0x3c0 [cfg80211]
 ? __warn.cold+0x8e/0xe8
 ? cfg80211_calculate_bitrate_he+0x1b7/0x3c0 [cfg80211]
 ? report_bug+0xff/0x140
 ? handle_bug+0x3c/0x80
 ? exc_invalid_op+0x17/0x70
 ? asm_exc_invalid_op+0x1a/0x20
 ? cfg80211_calculate_bitrate_he+0x1b7/0x3c0 [cfg80211]
 nl80211_put_sta_rate+0x5b/0x4f0 [cfg80211]
 nl80211_send_station+0x9f0/0x1060 [cfg80211]
 nl80211_dump_station+0xef/0x280 [cfg80211]
 genl_dumpit+0x33/0x90
 netlink_dump+0x151/0x3b0
 __netlink_dump_start+0x1eb/0x310
 genl_family_rcv_msg_dumpit+0x9a/0x100
 ? __pfx_genl_start+0x10/0x10
 ? __pfx_genl_dumpit+0x10/0x10
 ? __pfx_genl_done+0x10/0x10
 genl_rcv_msg+0x149/0x2c0
 ? __pfx_nl80211_dump_station+0x10/0x10 [cfg80211]
 ? __pfx_genl_rcv_msg+0x10/0x10
 netlink_rcv_skb+0x50/0x100
 genl_rcv+0x28/0x40
 netlink_unicast+0x240/0x370
 netlink_sendmsg+0x21b/0x470
 ____sys_sendmsg+0x396/0x3d0
 ? srso_alias_return_thunk+0x5/0xfbef5
 ___sys_sendmsg+0x9a/0xe0
 __sys_sendmsg+0xcc/0x100
 do_syscall_64+0x82/0x160
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? __x64_sys_epoll_wait+0x71/0x110
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? syscall_exit_to_user_mode+0x75/0x230
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? do_syscall_64+0x8e/0x160
 ? __pfx_pollwake+0x10/0x10
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? sched_mm_cid_remote_clear+0x66/0x110
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? __rseq_handle_notify_resume+0xa6/0x4d0
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? switch_fpu_return+0x4e/0xd0
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? syscall_exit_to_user_mode+0x75/0x230
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? do_syscall_64+0x8e/0x160
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? do_syscall_64+0x8e/0x160
 ? handle_softirqs+0x1b8/0x340
 ? sched_clock_cpu+0xf/0x1f0
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? __irq_exit_rcu+0x4a/0xb0
 ? srso_alias_return_thunk+0x5/0xfbef5
 entry_SYSCALL_64_after_hwframe+0x76/0x7e
RIP: 0033:0x7f7d3a05c79b
Code: 48 89 e5 48 83 ec 20 89 55 ec 48 89 75 f0 89 7d f8 e8 49 7a f7 ff 8b 55 ec 48 8b 75 f0 41 89 c0 8b 7d f8 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 45 f8 e8 a1 7a f7 ff 48 8b
RSP: 002b:00007ffc00fc2060 EFLAGS: 00000293 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00005603a93035c0 RCX: 00007f7d3a05c79b
RDX: 0000000000000000 RSI: 00007ffc00fc20a0 RDI: 000000000000000b
RBP: 00007ffc00fc2080 R08: 0000000000000000 R09: 00005603a933ed40
R10: 00007f7d3a126250 R11: 0000000000000293 R12: 00005603a93b52d0
R13: 00007ffc00fc2130 R14: 00005603a93035c0 R15: 00007ffc00fc2394
 </TASK>


Device:
Network controller: Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter (rev 01)

AP:
TP-Link Wifi 7 router: https://www.tp-link.com/fi/home-networking/wifi-router/archer-be800/

Firmware loading:
ath11k_pci 0000:02:00.0: fw_version 0x1106196e fw_build_timestamp 2024-01-12 11:30 fw_build_id WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37
ath11k_pci 0000:02:00.0: chip_id 0x12 chip_family 0xb board_id 0xff soc_id 0x400c1211
Comment 1 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-05-18 09:11:37 UTC 
Did this worked with 6.8.y kernels? I'm wondering if this is the same issue as the one these fixes address: https://lore.kernel.org/linux-wireless/20240424064019.4847-1-quic_bqiang@quicinc.com/

Alternative fix: https://lore.kernel.org/all/20240506214536.310434f55f76.I6aca291ee06265e3f63e0f9024ba19a850b53a33@changeid/#t
Comment 2 Mikko Tiihonen 2024-05-18 12:36:26 UTC 
Unfortunately I was already running 6.9rc kernels when I got the Wifi7 AP so I have no data on older kernels.

But if it helps I can try to run 6.10 rc build from Fedora. Did the alternative fix get already merged in?
Comment 3 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-05-18 16:48:49 UTC 
(In reply to Mikko Tiihonen from comment #2)
> Unfortunately I was already running 6.9rc kernels when I got the Wifi7 AP 

Okay

> Did the alternative fix get already merged in?

Don't think so, so it's likely not worth testing 6.10-prereleases currently
Comment 4 Mikko Tiihonen 2024-08-09 07:14:12 UTC 
I have not seen this occur anymore after switching to 6.10.3 kernel.
Note You need to log in before you can comment on or make changes to this bug.