Archer C7 v2: Kernel warn: Comm: wpa_supplicant Not tainted 4.14.156

Catfriend1 · January 3, 2020, 3:50pm

Hi,

I need help on this. I'm using OpenWrt 19.07-rc.2 and experiencing this crash since setting up batman-adv on a separate radio (5 Ghz - radio0) in ad-hoc mode.

------------[ cut here ]------------
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.749696] WARNING: CPU: 0 PID: 2097 at /builder/shared-workdir/build/build_dir/target-mips_24kc_musl/linux-ath79_generic/ath10k-ct-2019-09-09-5e8cd86f/ath10k-4.19/mac.c:6598 0x8700bd24 [ath10k_core@87000000+0x5d210]
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.769293] Modules linked in: ath9k ath9k_common pppoe ppp_async batman_adv ath9k_hw ath10k_pci ath10k_core ath pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack libcrc32c iptable_mangle iptable_filter ip_tables crc_ccitt compat ledtrig_usbport nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 msdos vfat fat ntfs nls_utf8 nls_iso8859_1 nls_cp437 usb_storage sd_mod
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.841416]  scsi_mod ext4 mbcache jbd2 crc16 crc32c_generic crypto_hash ehci_platform ehci_hcd gpio_button_hotplug usbcore nls_base usb_common
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.854513] CPU: 0 PID: 2097 Comm: wpa_supplicant Not tainted 4.14.156 #0
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.861393] Stack : 000000f8 800b2a94 80500000 804af544 00000000 00000000 00000000 00000000
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.869894]         00000000 00000000 00000000 00000000 00000000 00000001 8654f9d8 e25e8e0b
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.878389]         8654fa70 00000000 00000000 00006448 00000038 80447958 00000008 00000000
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.886887]         00000120 9c56a2d2 0000011f 00000000 8654f9b8 80000000 00000000 8704e480
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.895379]         8700bd24 000019c6 8726ad28 87420000 00000000 8027f944 00000000 80630000
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.903860]         ...
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.906353] Call Trace:
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.906362] [<800b2a94>] 0x800b2a94
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.912374] [<80500000>] 0x80500000
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.915925] [<80447958>] 0x80447958
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.919464] [<8700bd24>] 0x8700bd24 [ath10k_core@87000000+0x5d210]
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.925775] [<8027f944>] 0x8027f944
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.929313] [<8006a56c>] 0x8006a56c
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.932851] [<8006a574>] 0x8006a574
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.936401] [<80084c20>] 0x80084c20
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.939939] [<8700bd24>] 0x8700bd24 [ath10k_core@87000000+0x5d210]
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.946239] [<80084d08>] 0x80084d08
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.949777] [<8700bd24>] 0x8700bd24 [ath10k_core@87000000+0x5d210]
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.956084] [<87795f70>] 0x87795f70 [mac80211@87780000+0x6c280]
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.962094] [<876ed0d0>] 0x876ed0d0 [cfg80211@876c0000+0x363f0]
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.968130] [<876e941c>] 0x876e941c [cfg80211@876c0000+0x363f0]
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.974171] [<876dddc0>] 0x876dddc0 [cfg80211@876c0000+0x363f0]
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.980200] [<80350498>] 0x80350498
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.983732] [<802aba6c>] 0x802aba6c
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.987318] [<803501ac>] 0x803501ac
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.990856] [<8034eb44>] 0x8034eb44
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.994405] [<8034f410>] 0x8034f410
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   40.997944] [<8034c9bc>] 0x8034c9bc
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.001491] [<8034e208>] 0x8034e208
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.005044] [<8034e6e4>] 0x8034e6e4
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.008593] [<802f7c1c>] 0x802f7c1c
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.012142] [<8034e308>] 0x8034e308
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.015689] [<802f7e7c>] 0x802f7e7c
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.019223] [<800f0cfc>] 0x800f0cfc
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.022760] [<8011d6bc>] 0x8011d6bc
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.026319] [<8011d79c>] 0x8011d79c
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.029858] [<8011dedc>] 0x8011dedc
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.033422] [<80071808>] 0x80071808
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.036967] [<802f681c>] 0x802f681c
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.040501] [<8013fd78>] 0x8013fd78
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.044050] [<802fd5c0>] 0x802fd5c0
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.047596] [<802f8704>] 0x802f8704
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.051131] [<802f6718>] 0x802f6718
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.054686] [<8006f72c>] 0x8006f72c
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.058227] [<802f84a4>] 0x802f84a4
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.061764]
Fri Jan  3 15:21:05 2020 kern.warn kernel: [   41.063275] ---[ end trace e82a5933fdea7f6e ]---
Fri Jan  3 15:21:05 2020 kern.info kernel: [   41.070647] wlan0: Created IBSS using preconfigured BSSID xxx

/etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option hwmode '11a'
	option country 'DE'
	option txpower '20'
	option htmode 'VHT80'
	option legacy_rates '0'
	option noscan '1'
	option channel '36'
	option path 'pci0000:00/0000:00:00.0'

config wifi-device 'radio1'
	option type 'mac80211'
	option hwmode '11g'
	option htmode 'HT40'
	option txpower '20'
	option country 'DE'
	option legacy_rates '0'
	option noscan '1'
	option disabled '0'
	option path 'platform/ahb/ahb:apb/18100000.wmac'
	option channel '10'
	option disabled '1'

config wifi-iface 'wifinet0'
	option device 'radio0'
	option mode 'adhoc'
	option ssid 'Permakultur'
	option encryption 'psk2+ccmp'
	option bssid 'xx:xx:xx:xx:xx:xx'
	option dtim_period '1'
	option disassoc_low_ack '0'
	option key 'REDACTED'
	option network 'nwi_mesh0'

References:

https://bugs.openwrt.org/index.php?do=details&task_id=2702 (I've listed my installed packages there)

Similar issue:

Thank you for your help.

Kind regards
Catfriend1

Catfriend1 · January 5, 2020, 11:22am

Hi again,
I've found my 2.4 ghz radio doesn't work anymore. Using wifianalyzer on a phone, it shows 2.4g/5g both available and then short after only 5g. I suspect this could have to be related to the crashed wpa_supplicant? Remember: I have ap and ad-hoc running both fine on 5ghz radio.

As soon as I disable the ad-hoc via luci web ui, my 2.4ghz radio works again and the phones all show 2.4/5g for my ssid available.

mk24 · January 5, 2020, 1:48pm

The configuration you posted has an option disable '1' line on the 2.4 radio. There are several other things in that file that are redundant and/or not applicable to the mode being used. It is best not to mix the GUI and CLI methods of configuration, use one or the other (and setting up a mesh will probably require CLI).

It is ath10k that is crashing. (On most routers the 2.4 radio is ath9k although a few with ipq ARM chips use ath10k for both radios.) There are two versions of ath10k, the ct version developed by a private company, and the non-ct version from the mainline Linux kernel. They have different capabilities and limitations. Since both are OpenWrt packages is easy to switch back and forth by using opkg to remove / install the kmod and the firmware.

I don't know if either one supports adhoc mode at all well. Generally for new mesh deployments the 802.11s mode should be used instead.

Catfriend1 · January 5, 2020, 2:47pm

Hi @mk24 !

Thanks for your reply. I've used the 2.4ghz interface on the other router (= the partner IBSS ad-hoc device). I will try to swap packages as you suggested to go for testing with "ath10k" instead of the "ath10k-ct" version.

So far, ad-hoc mode was running fine with 400 MBit/s throughput despite having the crash in the log. It just affects 2.4 ghz radio to cease working for a reason I don't understand. Maybe wpa_supplicant is somehow "crashed"?

I'm using CLI config now, fyi, luci displays the whole configured AP+IBSS mix correctly as multiple SSIDs configured to the two radios.

Is there also a way I could put a "firmware.bin" to my TP Link Archer C7 v2 device to test with another radio firmware version? If so, where to grab it and how does it need to be uploaded to /... to be recognized?

Currently my firmware is this:

cat /sys/kernel/debug/ieee80211/phy2/ath10k/firmware_info
directory: ath10k/QCA988X/hw2.0
firmware:  firmware-2.bin
fwcfg:     fwcfg-pci-0000:00:00.0.txt
bus:       0000:00:00.0
features:  wmi-10.x,has-wmi-mgmt-tx,mfp,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT,get-temp-CT,tx-rc-CT,cust-stats-CT,retry-gt2-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT
version:   10.1-ct-8x-__fW-022-64cc8007
hw_rev:    988x
board:     board.bin

Catfriend1 · January 8, 2020, 3:44pm

Again, thanks for your help!
I was able to set up multiple AP SSIDs and an encrypted mesh SSID on radio0 5 GHz of my TP Link Archer C7 v2 device with 802.11s using OpenWrt 19.07.0. (Ref.: Archer C7 v2/5: Cannot setup mesh beside AP SSIDs with wpad-mesh )

system · January 18, 2020, 3:44pm

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.