Bug 213937
Summary: | ath11k: QCA6390: crash in ath11k_mac_op_unassign_vif_chanctx upon connect to 5 GHz network | ||
---|---|---|---|
Product: | Drivers | Reporter: | Dr. Jan-Philip Gehrcke (jgehrcke) |
Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | kvalo |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 5.13.5 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Dr. Jan-Philip Gehrcke
2021-08-01 16:43:46 UTC
I wanted to see if the difference between 2.4 GHz and 5 GHz matters. To that end I removed the 'saved' 5 GHz Wifi connection via $ nmcli connection delete id <connection uuid> I then rebooted to confirm again that `dmesg` does not show a crash as long as I don't connect to a wireless network. The last few ath11k-related lines in dmesg output: [ 14.034352] ath11k_pci 0000:6c:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0xffffffff [ 14.034355] ath11k_pci 0000:6c:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id [ 14.223440] ath11k_pci 0000:6c:00.0 wlp108s0: renamed from wlan0 I then browsed the wireless networks and connected to a 2.4 GHz network. No crash. Relevant lines from `dmesg`: [ 122.869683] wlp108s0: authenticate with 2c:91:ab:75:cf:bd [ 123.027099] wlp108s0: send auth to 2c:91:ab:75:cf:bd (try 1/3) [ 123.032424] wlp108s0: authenticated [ 123.034883] wlp108s0: associate with 2c:91:ab:75:cf:bd (try 1/3) [ 123.039912] wlp108s0: RX AssocResp from 2c:91:ab:75:cf:bd (capab=0x1431 status=0 aid=131) [ 123.061465] wlp108s0: associated [ 123.100517] wlp108s0: Limiting TX power to 20 (20 - 0) dBm as advertised by 2c:91:ab:75:cf:bd [ 125.360926] IPv6: ADDRCONF(NETDEV_CHANGE): wlp108s0: link becomes ready I then disconnected wired network and at least for basic communication the 2.4 GHz connectivity works: $ ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=12.7 ms ... I then searched specifically about 5 Ghz issues and found https://bugzilla.kernel.org/show_bug.cgi?id=212059. Which might be the actual underlying issue here. I am updating the title of this issue here. *** This bug has been marked as a duplicate of bug 212059 *** |