[OpenWrt-Devel] 5GHz wifi is broken

Ben Greear greearb at candelatech.com
Sat Feb 16 16:42:28 EST 2019



On 02/16/2019 01:36 PM, Christian Lamparter wrote:
> Hello,
>
> On Thursday, February 14, 2019 6:43:26 PM CET e9hack wrote:
>> a change somewhere between 8.Feb and 10.Feb breaks the usage of the 5GHz WiFi on my Archer C7 router.
>> I get the following entries in the log file:
>>
>> Firmware is:
>> ath10k_pci 0000:00:00.0: firmware ver 10.1-ct-8x-__fW-022-1bbfa151 api 2 features
>> wmi-10.x,has-wmi-mgmt-tx,mfp,txstatus-noack,wmi-10.x-CT,ratemask-CT,txrate-CT,get-temp-CT,tx-rc-CT,cust-stats-CT,retry-gt2-CT,txrate2-CT
>> crc32 66e0dff7
>>
>> Thu Feb 14 18:27:01 2019 daemon.err hostapd: Failed to set beacon parameters
>> Thu Feb 14 18:27:01 2019 daemon.err hostapd: Interface initialization failed
>> Thu Feb 14 18:27:01 2019 daemon.notice hostapd: wlan0: interface state DFS->DISABLED
>> Thu Feb 14 18:27:01 2019 daemon.notice hostapd: wlan0: AP-DISABLED
>> Thu Feb 14 18:27:01 2019 daemon.notice hostapd: wlan0: interface state DISABLED->DISABLED
>> Thu Feb 14 18:27:01 2019 daemon.notice hostapd: wlan0-2: AP-DISABLED
>> Thu Feb 14 18:27:01 2019 daemon.notice hostapd: wlan0-2: CTRL-EVENT-TERMINATING
>> Thu Feb 14 18:27:01 2019 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0-2 wasn't started
>> Thu Feb 14 18:27:01 2019 daemon.notice hostapd: wlan0-1: AP-DISABLED
>> Thu Feb 14 18:27:01 2019 daemon.notice hostapd: wlan0-1: CTRL-EVENT-TERMINATING
>> Thu Feb 14 18:27:01 2019 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0-1 wasn't started
>> Thu Feb 14 18:27:01 2019 daemon.notice hostapd: wlan0: AP-DISABLED
>> Thu Feb 14 18:27:01 2019 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
>> Thu Feb 14 18:27:01 2019 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
>> Thu Feb 14 18:27:01 2019 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
>> Thu Feb 14 18:27:01 2019 kern.info kernel: [  162.919267] device wlan0 left promiscuous mode
>> Thu Feb 14 18:27:01 2019 kern.info kernel: [  162.923985] br-lan: port 2(wlan0) entered disabled state
>> Thu Feb 14 18:27:02 2019 daemon.notice hostapd: ELOOP: remaining socket: sock=23 eloop_data=0x77f9cc40 user_data=0
>> handler=0x556a2d91
>> Thu Feb 14 18:27:02 2019 daemon.notice netifd: radio0 (2540): cat: can't open '/var/run/wifi-phy0.pid': No such file or
>> directory
>> Thu Feb 14 18:27:02 2019 daemon.notice netifd: radio0 (2540): WARNING (wireless_add_process): executable path
>> /usr/sbin/hostapd does not match process  path (/proc/exe)
>> Thu Feb 14 18:27:02 2019 daemon.notice netifd: radio0 (2540): Command failed: Invalid argument
>> Thu Feb 14 18:27:03 2019 kern.warn kernel: [  164.791404] ath10k_pci 0000:00:00.0: 10.1 wmi init: vdevs: 16  peers: 127
>> tid: 256
>> Thu Feb 14 18:27:03 2019 kern.info kernel: [  164.808256] ath10k_pci 0000:00:00.0: wmi print 'P 128 V 8 T 410'
>> Thu Feb 14 18:27:03 2019 kern.info kernel: [  164.814618] ath10k_pci 0000:00:00.0: wmi print 'msdu-desc: 1424  sw-crypt:
>> 0 ct-sta: 0'
>> Thu Feb 14 18:27:03 2019 kern.info kernel: [  164.822797] ath10k_pci 0000:00:00.0: wmi print 'alloc rem: 24616 iram: 26584'
>
>> Thu Feb 14 18:27:03 2019 kern.warn kernel: [  164.900521] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
>> Thu Feb 14 18:27:03 2019 kern.info kernel: [  164.925384] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
>> Thu Feb 14 18:27:04 2019 daemon.notice netifd: radio0 (2540): Cannot find device "wlan0-1"
>> Thu Feb 14 18:27:04 2019 daemon.notice netifd: radio0 (2540): Interface 1 setup failed: IFUP_ERROR
>> Thu Feb 14 18:27:05 2019 daemon.notice netifd: radio0 (2540): Cannot find device "wlan0-2"
>> Thu Feb 14 18:27:05 2019 daemon.notice netifd: radio0 (2540): Interface 2 setup failed: IFUP_ERROR
>> Thu Feb 14 18:27:05 2019 kern.info kernel: [  166.183839] br-lan: port 2(wlan0) entered blocking state
>> Thu Feb 14 18:27:05 2019 kern.info kernel: [  166.189311] br-lan: port 2(wlan0) entered disabled state
>> Thu Feb 14 18:27:05 2019 kern.info kernel: [  166.195048] device wlan0 entered promiscuous mode
>
> "between 8.Feb and 10.Feb"
>
> https://github.com/openwrt/openwrt/commits/master/package/kernel/ath10k-ct
>
> so maybe it was:
>
> https://github.com/openwrt/openwrt/commit/835fc08ae3fb9e27db0f095a10fbff24f87ee1a9
> (Although, github says it was commited on the 11th)
>
> Can you please post your /etc/config/wireless and try to revert the patch to test if
> this helps with the situation?
>
> If it is indeed the patch (and not a unsupported configuration):
>
> @Ben can you please take a peek into your wave-1 firmware and check if the
> mgmt_rate WMI (WMI_10X_VDEV_PARAM_MGMT_RATE) is supported, or if there is
> a bad interaction somewhere else?
>
> (This "pdev param 0 not supported by firmware" was mentioned in
> https://bugs.openwrt.org/index.php?do=details&task_id=1920 so probably not the problem)

Hopefully the user can bisect to the exact bad commit, and then I'll be happy to
try to figure out what is the issue.

I have not made many changes to the wave-1 firmware recently.  I have some API
to set the management rates, but not sure it uses the same API as whatever that
patch in question is using.

Thanks,
Ben

>
> Cheers,
> Christian
>
>

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel



More information about the openwrt-devel mailing list