Hello,
router: zyxel nbg6817
build: r11001-ce6311d301
gcc: 9.2.0
kernel: 4.14.143
lib: glibc
build platform arch linux (latest)
config: copyed over with defconf from build r10401-63e3c3d2a2
Symptoms: Wifi is not comming up / Spontaneous reboots / Bootloop
I was about to make a new build for my zyxel. My last build for this router is 4.14.131 r10401-63e3c3d2a2. It is working without any issues.
With the new build I have several issues. Main issue is: Wifi is not comming up!
Here is the log (cut version):
[ 29.093419] ath10k_pci 0000:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
[ 29.093454] ath10k_pci 0000:01:00.0: kconfig debug 1 debugfs 1 tracing 0 dfs 1 testmode 0
[ 29.104715] ath10k_pci 0000:01:00.0: firmware ver 10.4b-ct-9984-fW-012-c7b0f3f98 api 5 features mfp,peer-flow-ctrl,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,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 8ddd86e1
[ 31.423316] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id 0:1 crc32 85498734
[ 37.223033] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
[ 37.223062] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
[ 37.303492] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
[ 37.304331] ath10k_pci 0000:01:00.0: wmi print 'free: 81768 iram: 23348 sram: 14184'
[ 37.557923] ath10k_pci 0000:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 32 raw 0 hwcrypto 1
[ 37.652629] ath: EEPROM regdomain: 0x0
[ 37.652642] ath: EEPROM indicates default country code should be used
[ 37.652652] ath: doing EEPROM country->regdmn map search
[ 37.652668] ath: country maps to regdmn code: 0x3a
[ 37.652680] ath: Country alpha2 being used: US
[ 37.652690] ath: Regpair used: 0x3a
...
[ 60.249650] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 68.027134] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
[ 68.027167] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
[ 68.107718] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
[ 68.108542] ath10k_pci 0000:01:00.0: wmi print 'free: 81768 iram: 23348 sram: 14184'
[ 68.448768] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[ 68.449003] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 69.025612] ath10k_pci 0000:01:00.0: NOTE: Firmware DBGLOG output disabled in debug_mask: 0x10000000
[ 74.400386] ath10k_pci 0001:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
[ 74.400417] ath10k_pci 0001:01:00.0: msdu-desc: 2500 skid: 32
[ 74.482858] ath10k_pci 0001:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
[ 74.483717] ath10k_pci 0001:01:00.0: wmi print 'free: 81768 iram: 23348 sram: 14184'
[ 74.831127] ath10k_pci 0001:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[ 74.831404] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 74.831576] br-lan: port 2(wlan0) entered blocking state
[ 74.831594] br-lan: port 2(wlan0) entered disabled state
[ 74.831994] device wlan0 entered promiscuous mode
[ 74.845655] br-lan: port 3(wlan1) entered blocking state
[ 74.845682] br-lan: port 3(wlan1) entered disabled state
[ 74.846202] device wlan1 entered promiscuous mode
[ 75.477606] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 75.477862] br-lan: port 2(wlan0) entered blocking state
[ 75.477881] br-lan: port 2(wlan0) entered forwarding state
[ 76.282711] device wlan0 left promiscuous mode
[ 76.282844] br-lan: port 2(wlan0) entered disabled state
[ 76.338021] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[ 76.338166] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[ 77.010719] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[ 77.010922] br-lan: port 3(wlan1) entered blocking state
[ 77.010936] br-lan: port 3(wlan1) entered forwarding state
[ 77.028568] IPv6: ADDRCONF(NETDEV_UP): wlan1-1: link is not ready
[ 77.228627] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1-1: link becomes ready
[ 87.635155] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[ 87.635179] ath10k_pci 0001:01:00.0: no vif for vdev_id 1 found
[ 87.685726] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[ 87.685750] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[ 87.843875] device wlan1 left promiscuous mode
[ 87.844379] br-lan: port 3(wlan1) entered disabled state
[ 87.937897] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
[ 87.937933] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
What I've checked so far. I realized that firmware got an update. I was compiling with the firmware from 4.14.131/ath10k-firmware-2018-10-10-d366b80d/6f40ea358b3ffba26b9f972d0efacc47 also. Firmware is loaded w/o any error (like before) but same issue. No Wifi.
If I try to bring up the interface with "ip" LEDs are comming up. "hostapd" is strange ...
hostapd -P /var/run/wifi-phy1.pid -B /var/run/hostapd-phy1.conf
Configuration file: /var/run/hostapd-phy1.conf
wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
wlan1: interface state COUNTRY_UPDATE->HT_SCAN
20/40 MHz operation not permitted on channel pri=11 sec=7 based on overlapping BSSes
Using interface wlan1 with hwaddr 60:31:97:xx:xx:xx and ssid "WLANxxx"
Using interface wlan1-1 with hwaddr 60:31:97:xx:xx:xx and ssid "WLANxxx"
wlan1: interface state HT_SCAN->ENABLED
wlan1: AP-ENABLED
hostapd -P /var/run/wifi-phy0.pid -B /var/run/hostapd-phy0.conf
Configuration file: /var/run/hostapd-phy0.conf
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Could not read interface wlan0 flags: No such device
nl80211 driver initialization failed.
wlan0: interface state UNINITIALIZED->DISABLED
wlan0: AP-DISABLED
wlan0: CTRL-EVENT-TERMINATING
hostapd_free_hapd_data: Interface wlan0 wasn't started
Sometimes i can bring up wlan1 (like above). Wlan0 is never comming up. If wlan1 is started the router reboots after a few seconds into a Bootloop! Mostly hostapd is just throwing an issue about "cannot write to hostapd-phy0.conf" ...
Sth. has changed what I've overseen? 
... If I make a glibc/gcc9 build without any modifications I get the same error. Next I will do a standard build with musl/gcc8 to see if there is the same error.
I would appreciate any hint to fix this.
Well then I will wait and stick with my last working build.