Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion

For Developers
852

Everything was solid until I changed the SSIDs from 'AP[1-6]' to their "production" SSIDs. Now granted, devices around the house started to connect to the SSIDs when they became available, so it's more likely tied to that. Luckily, I captured the crash via logread:

Before kernel error:

Sun Feb 12 15:36:58 2023 kern.info kernel: [ 7326.149374] device phy0-ap0 left promiscuous mode
Sun Feb 12 15:36:58 2023 kern.info kernel: [ 7326.149489] br-wan: port 3(phy0-ap0) entered disabled state
Sun Feb 12 15:36:58 2023 kern.info kernel: [ 7326.207991] device phy1-ap2 left promiscuous mode
Sun Feb 12 15:36:58 2023 kern.info kernel: [ 7326.208122] br-wan: port 5(phy1-ap2) entered disabled state
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: Remove interface 'phy0-ap0'
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: phy0-ap0: interface state ENABLED->DISABLED
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: phy0-ap1: AP-DISABLED
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: phy0-ap1: CTRL-EVENT-TERMINATING
Sun Feb 12 15:36:58 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sun Feb 12 15:36:58 2023 daemon.info avahi-daemon[2629]: Interface phy0-ap1.IPv6 no longer relevant for mDNS.
Sun Feb 12 15:36:58 2023 daemon.info avahi-daemon[2629]: Leaving mDNS multicast group on interface phy0-ap1.IPv6 with address fe80::2cea:dcff:fe85:e87d.
Sun Feb 12 15:36:58 2023 daemon.notice netifd: Network device 'phy0-ap1' link is down
Sun Feb 12 15:36:58 2023 kern.info kernel: [ 7326.339522] br-wan: port 7(phy0-ap1) entered disabled state
Sun Feb 12 15:36:58 2023 kern.info kernel: [ 7326.407025] device phy0-ap1 left promiscuous mode
Sun Feb 12 15:36:58 2023 kern.info kernel: [ 7326.407073] br-wan: port 7(phy0-ap1) entered disabled state
Sun Feb 12 15:36:58 2023 daemon.info avahi-daemon[2629]: Withdrawing address record for fe80::2cea:dcff:fe85:e87d on phy0-ap1.
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: nl80211: Failed to remove interface phy0-ap1 from bridge br-wan: No such device
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: phy0-ap0: AP-DISABLED
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: phy0-ap0: CTRL-EVENT-TERMINATING
Sun Feb 12 15:36:58 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: nl80211: deinit ifname=phy0-ap0 disabled_11b_rates=0
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: nl80211: Failed to remove interface phy0-ap0 from bridge br-wan: Invalid argument
Sun Feb 12 15:36:58 2023 daemon.info avahi-daemon[2629]: Interface phy0-ap0.IPv6 no longer relevant for mDNS.
Sun Feb 12 15:36:58 2023 daemon.info avahi-daemon[2629]: Leaving mDNS multicast group on interface phy0-ap0.IPv6 with address fe80::2eea:dcff:fe85:e87d.
Sun Feb 12 15:36:58 2023 daemon.info avahi-daemon[2629]: Withdrawing address record for fe80::2eea:dcff:fe85:e87d on phy0-ap0.
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: Remove interface 'phy1-ap0'
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: phy1-ap0: interface state ENABLED->DISABLED
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: phy1-ap3: AP-DISABLED
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: phy1-ap3: CTRL-EVENT-TERMINATING
Sun Feb 12 15:36:58 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sun Feb 12 15:36:58 2023 daemon.info avahi-daemon[2629]: Interface phy1-ap3.IPv6 no longer relevant for mDNS.
Sun Feb 12 15:36:58 2023 daemon.info avahi-daemon[2629]: Leaving mDNS multicast group on interface phy1-ap3.IPv6 with address fe80::24ea:dcff:fe85:e87e.
Sun Feb 12 15:36:58 2023 daemon.notice netifd: Network device 'phy1-ap3' link is down
Sun Feb 12 15:36:58 2023 kern.info kernel: [ 7326.769588] br-wan: port 6(phy1-ap3) entered disabled state
Sun Feb 12 15:36:58 2023 kern.info kernel: [ 7326.816963] device phy1-ap3 left promiscuous mode
Sun Feb 12 15:36:58 2023 kern.info kernel: [ 7326.817007] br-wan: port 6(phy1-ap3) entered disabled state
Sun Feb 12 15:36:58 2023 daemon.info avahi-daemon[2629]: Withdrawing address record for fe80::24ea:dcff:fe85:e87e on phy1-ap3.
Sun Feb 12 15:36:58 2023 daemon.notice netifd: Wireless device 'radio0' is now down
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: nl80211: Failed to remove interface phy1-ap3 from bridge br-wan: No such device
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: phy1-ap2: AP-DISABLED
Sun Feb 12 15:36:58 2023 daemon.notice hostapd: phy1-ap2: CTRL-EVENT-TERMINATING
Sun Feb 12 15:36:58 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sun Feb 12 15:36:59 2023 daemon.info avahi-daemon[2629]: Interface phy1-ap2.IPv6 no longer relevant for mDNS.
Sun Feb 12 15:36:59 2023 daemon.info avahi-daemon[2629]: Leaving mDNS multicast group on interface phy1-ap2.IPv6 with address fe80::28ea:dcff:fe85:e87e.
Sun Feb 12 15:36:59 2023 daemon.info avahi-daemon[2629]: Withdrawing address record for fe80::28ea:dcff:fe85:e87e on phy1-ap2.
Sun Feb 12 15:36:59 2023 daemon.notice hostapd: nl80211: Failed to remove interface phy1-ap2 from bridge br-wan: No such device
Sun Feb 12 15:36:59 2023 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED e0:46:9a:XX:XX:XX
Sun Feb 12 15:36:59 2023 daemon.notice hostapd: phy1-ap1: AP-DISABLED
Sun Feb 12 15:36:59 2023 daemon.notice hostapd: phy1-ap1: CTRL-EVENT-TERMINATING
Sun Feb 12 15:36:59 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sun Feb 12 15:36:59 2023 daemon.info avahi-daemon[2629]: Interface phy1-ap1.IPv6 no longer relevant for mDNS.
Sun Feb 12 15:36:59 2023 daemon.notice netifd: Network device 'phy1-ap1' link is down
Sun Feb 12 15:36:59 2023 daemon.info avahi-daemon[2629]: Leaving mDNS multicast group on interface phy1-ap1.IPv6 with address fe80::2cea:dcff:fe85:e87e.
Sun Feb 12 15:36:59 2023 kern.info kernel: [ 7327.529166] br-wan: port 4(phy1-ap1) entered disabled state
Sun Feb 12 15:36:59 2023 kern.info kernel: [ 7327.586952] device phy1-ap1 left promiscuous mode
Sun Feb 12 15:36:59 2023 kern.info kernel: [ 7327.586993] br-wan: port 4(phy1-ap1) entered disabled state
Sun Feb 12 15:36:59 2023 daemon.warn dawn: Client / BSSID = E0:46:9A:XX:XX:XX / 2E:EA:DC:XX:XX:XX: BEACON REQUEST failed
Sun Feb 12 15:36:59 2023 daemon.info avahi-daemon[2629]: Withdrawing address record for fe80::2cea:dcff:fe85:e87e on phy1-ap1.
Sun Feb 12 15:36:59 2023 daemon.notice hostapd: nl80211: Failed to remove interface phy1-ap1 from bridge br-wan: No such device
Sun Feb 12 15:36:59 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 7a:68:ba:XX:XX:XX
Sun Feb 12 15:36:59 2023 daemon.notice hostapd: phy1-ap0: AP-DISABLED
Sun Feb 12 15:36:59 2023 daemon.notice hostapd: phy1-ap0: CTRL-EVENT-TERMINATING
Sun Feb 12 15:36:59 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sun Feb 12 15:36:59 2023 daemon.notice hostapd: nl80211: deinit ifname=phy1-ap0 disabled_11b_rates=0
Sun Feb 12 15:36:59 2023 kern.info kernel: [ 7327.796473] device phy1-ap0 left promiscuous mode
Sun Feb 12 15:36:59 2023 kern.info kernel: [ 7327.796616] br-wan: port 2(phy1-ap0) entered disabled state
Sun Feb 12 15:37:00 2023 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Sun Feb 12 15:37:00 2023 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 4 names
Sun Feb 12 15:37:00 2023 daemon.info dnsmasq[1]: read /tmp/hosts/odhcpd - 0 names
Sun Feb 12 15:37:00 2023 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Sun Feb 12 15:37:00 2023 daemon.notice netifd: Network device 'phy1-ap0' link is down
Sun Feb 12 15:37:04 2023 kern.warn kernel: [ 7332.956344] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 4
Sun Feb 12 15:37:05 2023 daemon.info avahi-daemon[2629]: Interface phy1-ap0.IPv6 no longer relevant for mDNS.
Sun Feb 12 15:37:05 2023 daemon.info avahi-daemon[2629]: Leaving mDNS multicast group on interface phy1-ap0.IPv6 with address fe80::2eea:dcff:fe85:e87e.
Sun Feb 12 15:37:05 2023 daemon.info avahi-daemon[2629]: Withdrawing address record for fe80::2eea:dcff:fe85:e87e on phy1-ap0.
Sun Feb 12 15:37:05 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy phy0-ap0) --> new PHY
Sun Feb 12 15:37:05 2023 daemon.notice netifd: Wireless device 'radio1' is now down
Sun Feb 12 15:37:05 2023 kern.info kernel: [ 7333.167264] br-wan: port 2(phy0-ap0) entered blocking state
Sun Feb 12 15:37:05 2023 kern.info kernel: [ 7333.167314] br-wan: port 2(phy0-ap0) entered disabled state
Sun Feb 12 15:37:05 2023 kern.info kernel: [ 7333.171951] device phy0-ap0 entered promiscuous mode
Sun Feb 12 15:37:05 2023 daemon.notice hostapd: phy0-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE
Sun Feb 12 15:37:05 2023 daemon.notice hostapd: phy0-ap0: interface state COUNTRY_UPDATE->HT_SCAN
Sun Feb 12 15:37:05 2023 daemon.notice netifd: radio0 (13050): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 1956 path ()
Sun Feb 12 15:37:05 2023 daemon.warn netifd: Wireless device 'radio0' setup failed, retry=3
Sun Feb 12 15:37:06 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy1.conf (phy phy1-ap0) --> new PHY
Sun Feb 12 15:37:06 2023 kern.info kernel: [ 7334.207846] br-wan: port 3(phy1-ap0) entered blocking state
Sun Feb 12 15:37:06 2023 kern.info kernel: [ 7334.207890] br-wan: port 3(phy1-ap0) entered disabled state
Sun Feb 12 15:37:06 2023 kern.info kernel: [ 7334.212484] device phy1-ap0 entered promiscuous mode
Sun Feb 12 15:37:06 2023 daemon.notice hostapd: phy1-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE
Sun Feb 12 15:37:06 2023 daemon.notice hostapd: phy1-ap0: interface state COUNTRY_UPDATE->HT_SCAN
Sun Feb 12 15:37:07 2023 daemon.notice netifd: Wireless device 'radio1' is now up
Sun Feb 12 15:37:07 2023 daemon.notice hostapd: 20/40 MHz operation not permitted on channel pri=6 sec=10 based on overlapping BSSes
Sun Feb 12 15:37:07 2023 daemon.notice hostapd: Fallback to 20 MHz
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.134783] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap0: link becomes ready
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.134977] br-wan: port 3(phy1-ap0) entered blocking state
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.140235] br-wan: port 3(phy1-ap0) entered forwarding state
Sun Feb 12 15:37:08 2023 daemon.notice netifd: Network device 'phy1-ap0' link is up
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.239455] br-wan: port 4(phy1-ap1) entered blocking state
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.239504] br-wan: port 4(phy1-ap1) entered disabled state
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.244124] device phy1-ap1 entered promiscuous mode
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.251159] br-wan: port 4(phy1-ap1) entered blocking state
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.254614] br-wan: port 4(phy1-ap1) entered forwarding state
Sun Feb 12 15:37:08 2023 daemon.notice netifd: Network device 'phy1-ap1' link is up
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.388060] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap1: link becomes ready
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.509282] br-wan: port 5(phy1-ap2) entered blocking state
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.509328] br-wan: port 5(phy1-ap2) entered disabled state
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.513933] device phy1-ap2 entered promiscuous mode
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.522435] br-wan: port 5(phy1-ap2) entered blocking state
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.524440] br-wan: port 5(phy1-ap2) entered forwarding state
Sun Feb 12 15:37:08 2023 daemon.notice netifd: Network device 'phy1-ap2' link is up
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.708056] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap2: link becomes ready
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.829242] br-wan: port 6(phy1-ap3) entered blocking state
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.829307] br-wan: port 6(phy1-ap3) entered disabled state
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.833905] device phy1-ap3 entered promiscuous mode
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.842035] br-wan: port 6(phy1-ap3) entered blocking state
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.844426] br-wan: port 6(phy1-ap3) entered forwarding state
Sun Feb 12 15:37:08 2023 daemon.notice netifd: Network device 'phy1-ap3' link is up
Sun Feb 12 15:37:08 2023 kern.info kernel: [ 7336.978072] IPv6: ADDRCONF(NETDEV_CHANGE): phy1-ap3: link becomes ready
Sun Feb 12 15:37:09 2023 daemon.notice hostapd: phy1-ap0: interface state HT_SCAN->ENABLED
Sun Feb 12 15:37:09 2023 daemon.notice hostapd: phy1-ap0: AP-ENABLED
Sun Feb 12 15:37:14 2023 daemon.warn dawn: Failed to lookup ID!
Sun Feb 12 15:37:14 2023 daemon.warn dawn: Failed to lookup ID!
Sun Feb 12 15:37:16 2023 daemon.info hostapd: phy1-ap1: STA e0:46:9a:XX:XX:XX IEEE 802.11: authenticated
Sun Feb 12 15:37:16 2023 daemon.info hostapd: phy1-ap1: STA e0:46:9a:XX:XX:XX IEEE 802.11: associated (aid 1)
Sun Feb 12 15:37:16 2023 daemon.notice netifd: Wireless device 'radio0' is now down
Sun Feb 12 15:37:17 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy phy0-ap0) --> new PHY
Sun Feb 12 15:37:17 2023 kern.info kernel: [ 7345.756667] br-wan: port 2(phy0-ap0) entered disabled state
Sun Feb 12 15:37:17 2023 daemon.notice hostapd: phy0-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE
Sun Feb 12 15:37:17 2023 daemon.notice hostapd: phy0-ap0: interface state COUNTRY_UPDATE->HT_SCAN
Sun Feb 12 15:37:18 2023 daemon.notice hostapd: phy0-ap0: interface state HT_SCAN->DFS
Sun Feb 12 15:37:18 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-START freq=5180 chan=36 sec_chan=1, width=2, seg0=50, seg1=0, cac_time=60s
Sun Feb 12 15:37:18 2023 daemon.notice hostapd: phy1-ap1: AP-STA-CONNECTED e0:46:9a:XX:XX:XX auth_alg=open
Sun Feb 12 15:37:18 2023 daemon.info hostapd: phy1-ap1: STA e0:46:9a:XX:XX:XX RADIUS: starting accounting session A823CF5C3C6A718B
Sun Feb 12 15:37:18 2023 daemon.info hostapd: phy1-ap1: STA e0:46:9a:XX:XX:XX WPA: pairwise key handshake completed (RSN)
Sun Feb 12 15:37:18 2023 daemon.notice hostapd: phy1-ap1: EAPOL-4WAY-HS-COMPLETED e0:46:9a:XX:XX:XX
Sun Feb 12 15:37:18 2023 daemon.notice netifd: Wireless device 'radio0' is now up
Sun Feb 12 15:37:19 2023 daemon.notice hostapd: phy1-ap2: STA 94:b9:7e:XX:XX:XX IEEE 802.11: did not acknowledge authentication response
Sun Feb 12 15:37:29 2023 daemon.notice hostapd: phy1-ap2: STA 94:b9:7e:XX:XX:XX IEEE 802.11: did not acknowledge authentication response
Sun Feb 12 15:37:32 2023 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED e0:46:9a:XX:XX:XX
Sun Feb 12 15:37:32 2023 daemon.info hostapd: phy1-ap1: STA e0:46:9a:XX:XX:XX IEEE 802.11: authenticated
Sun Feb 12 15:37:32 2023 daemon.info hostapd: phy1-ap1: STA e0:46:9a:XX:XX:XX IEEE 802.11: associated (aid 1)
Sun Feb 12 15:37:33 2023 daemon.notice hostapd: phy1-ap1: AP-STA-CONNECTED e0:46:9a:XX:XX:XX auth_alg=open
Sun Feb 12 15:37:33 2023 daemon.info hostapd: phy1-ap1: STA e0:46:9a:XX:XX:XX RADIUS: starting accounting session A823CF5C3C6A718B
Sun Feb 12 15:37:33 2023 daemon.info hostapd: phy1-ap1: STA e0:46:9a:XX:XX:XX WPA: pairwise key handshake completed (RSN)
Sun Feb 12 15:37:33 2023 daemon.notice hostapd: phy1-ap1: EAPOL-4WAY-HS-COMPLETED e0:46:9a:XX:XX:XX
Sun Feb 12 15:37:39 2023 daemon.warn dawn: Failed to lookup ID!
Sun Feb 12 15:37:39 2023 daemon.warn dawn: Failed to lookup ID!
Sun Feb 12 15:37:39 2023 daemon.notice hostapd: phy1-ap2: STA 94:b9:7e:XX:XX:XX IEEE 802.11: did not acknowledge authentication response
Sun Feb 12 15:37:39 2023 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED e0:46:9a:XX:XX:XX
853

Kernel error:

Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] qcom-q6v5-wcss-pil cd00000.q6v5_wcss: fatal error received:
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] QC Image Version: QC_IMAGE_VERSION_STRING=WLAN.HK.2.5.0.1-01208-QCAHKSWPL_SILICONZ-1
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] Image Variant : IMAGE_VARIANT_STRING=8074.wlanfw.eval_v2Q
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493]
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] ar_wal_peer.c:2462 Assertion is_graceful_to_handle failedparam0 :zero, param1 :zero, param2 :zero.
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] Thread ID      : 0x00000060  Thread name    : WLAN RT1  Process ID     : 0
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] Register:
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] SP : 0x4c135128
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] FP : 0x4c135130
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] PC : 0x4b195a10
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] SSR : 0x00000008
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] BADVA : 0x00020000
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] LR : 0x4b1951ac
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493]
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] Stack Dump
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] from : 0x4c135128
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493] to   : 0x4c135980
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.151493]
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.200122] remoteproc remoteproc0: crash detected in cd00000.q6v5_wcss: type fatal error
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.222465] remoteproc remoteproc0: handling crash #1 in cd00000.q6v5_wcss
Sun Feb 12 15:37:40 2023 kern.err kernel: [ 7368.230511] remoteproc remoteproc0: recovering cd00000.q6v5_wcss
Sun Feb 12 15:37:40 2023 kern.info kernel: [ 7368.263115] remoteproc remoteproc0: stopped remote processor cd00000.q6v5_wcss
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.536591] ath11k c000000.wifi: failed to find peer e0:46:9a:XX:XX:XX on vdev 3 after creation
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.536638] ath11k c000000.wifi: failed to find peer vdev_id 3 addr e0:46:9a:XX:XX:XX in delete
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.544105] ath11k c000000.wifi: failed peer e0:46:9a:XX:XX:XX delete vdev_id 3 fallback ret -22
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.552804] ath11k c000000.wifi: Failed to add peer: e0:46:9a:XX:XX:XX for VDEV: 3
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.561818] ath11k c000000.wifi: Failed to add station: e0:46:9a:XX:XX:XX for VDEV: 3
Sun Feb 12 15:37:40 2023 daemon.notice hostapd: phy1-ap2: STA e0:46:9a:XX:XX:XX IEEE 802.11: Could not add STA to kernel driver
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.676627] ath11k c000000.wifi: failed to send WMI_PEER_DELETE cmd
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.676662] ath11k c000000.wifi: failed to delete peer vdev_id 2 addr e0:46:9a:XX:XX:XX ret -108
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.681706] ath11k c000000.wifi: Failed to delete peer: e0:46:9a:XX:XX:XX for VDEV: 2
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.690756] ath11k c000000.wifi: Found peer entry 2e:ea:dc:XX:XX:XX n vdev 2 after it was supposedly removed
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.698524] ------------[ cut here ]------------
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.708345] WARNING: CPU: 2 PID: 13827 at sta_set_sinfo+0xba4/0xbc0 [mac80211]
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.712951] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet batman_adv ath11k_ahb ath11k pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_objref nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_counter nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mac80211 cfg80211 slhc qrtr_smd qrtr qmi_helpers ns nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c hwmon crc_ccitt compat ip6_gre ip_gre gre ip6_tunnel tunnel6 ip_tunnel seqiv jitterentropy_rng drbg michael_mic hmac cmac leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_qcom qca_nss_dp qca_ssdk gpio_button_hotplug crc32c_generic
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.769186] CPU: 2 PID: 13827 Comm: hostapd Not tainted 5.15.93 #0
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.791421] Hardware name: Dynalink DL-WRX36 (DT)
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.797409] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.802186] pc : sta_set_sinfo+0xba4/0xbc0 [mac80211]
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.808954] lr : sta_set_sinfo+0xba0/0xbc0 [mac80211]
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.814162] sp : ffffffc00e903840
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.819193] x29: ffffffc00e903840 x28: ffffff8002b83ac0 x27: ffffffc00e903dd0
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.822499] x26: ffffff8001cae880 x25: ffffffc008ba0680 x24: ffffffc000a82000
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.829617] x23: ffffffc00e903a38 x22: ffffff8007fee900 x21: ffffff8018ed08c0
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.836735] x20: ffffff8006358880 x19: ffffff80027f5000 x18: ffffffc008aa7b08
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.843854] x17: 322076656476206e x16: 2065373a38653a35 x15: 0000000000000819
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.850972] x14: 00000000000002b3 x13: ffffffc00e903378 x12: ffffffc008affb08
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.858090] x11: 0000000000000004 x10: ffffffc008affb08 x9 : 0000000000000000
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.865208] x8 : ffffffc008aa7ab8 x7 : ffffffc008aa7b08 x6 : 0000000000008e08
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.872325] x5 : 00000000d16931a4 x4 : 0000000000000000 x3 : ffffff8002b83ac0
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.879445] x2 : 0000000000000000 x1 : ffffff8002b83ac0 x0 : 00000000ffffff94
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.886563] Call trace:
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.893671]  sta_set_sinfo+0xba4/0xbc0 [mac80211]
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.895933]  sta_info_destroy_addr_bss+0x50/0x7c [mac80211]
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.900794]  ieee80211_color_change_finish+0x1d78/0x2030 [mac80211]
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.906178]  cfg80211_check_station_change+0x1408/0x4970 [cfg80211]
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.912428]  genl_family_rcv_msg_doit+0xb8/0x11c
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.918675]  genl_rcv_msg+0xd4/0x1cc
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.923533]  netlink_rcv_skb+0x5c/0x130
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.927093]  genl_rcv+0x38/0x50
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.930651]  netlink_unicast+0x1f8/0x2f4
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.933778]  netlink_sendmsg+0x1a0/0x3dc
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.937945]  ____sys_sendmsg+0x288/0x2c0
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.941851]  ___sys_sendmsg+0x84/0xf0
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.945756]  __sys_sendmsg+0x48/0xb0
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.949316]  __arm64_sys_sendmsg+0x24/0x30
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.952962]  invoke_syscall.constprop.0+0x5c/0x104
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.956869]  do_el0_svc+0x6c/0x15c
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.961640]  el0_svc+0x18/0x54
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.965026]  el0t_64_sync_handler+0xe8/0x114
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.968066]  el0t_64_sync+0x184/0x188
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.972493] ---[ end trace 5f1f57cbe1331bb0 ]---
Sun Feb 12 15:37:44 2023 kern.warn kernel: [ 7372.132466] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sun Feb 12 15:37:45 2023 daemon.info hostapd: phy1-ap1: STA e0:46:9a:XX:XX:XX IEEE 802.11: deauthenticated due to local deauth request
Sun Feb 12 15:37:45 2023 kern.err kernel: [ 7373.516629] qcom-q6v5-wcss-pil cd00000.q6v5_wcss: start timed out
Sun Feb 12 15:37:45 2023 kern.err kernel: [ 7373.516678] remoteproc remoteproc0: can't start rproc cd00000.q6v5_wcss: -110
Sun Feb 12 15:37:50 2023 kern.warn kernel: [ 7378.136302] ath11k_warn: 159 callbacks suppressed
Sun Feb 12 15:37:50 2023 kern.warn kernel: [ 7378.136322] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sun Feb 12 15:37:50 2023 kern.warn kernel: [ 7378.140041] ath11k c000000.wifi: failed to send pdev bss chan info request
Sun Feb 12 15:37:50 2023 kern.warn kernel: [ 7378.147752] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Sun Feb 12 15:37:50 2023 kern.warn kernel: [ 7378.154334] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 1
Sun Feb 12 15:37:50 2023 kern.warn kernel: [ 7378.160878] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID
Sun Feb 12 15:37:50 2023 kern.warn kernel: [ 7378.167367] ath11k c000000.wifi: failed to submit beacon template command: -108
Sun Feb 12 15:37:50 2023 kern.warn kernel: [ 7378.173517] ath11k c000000.wifi: failed to update bcn template: -108
Sun Feb 12 15:37:50 2023 kern.warn kernel: [ 7378.180744] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sun Feb 12 15:37:50 2023 kern.warn kernel: [ 7378.187345] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 1
Sun Feb 12 15:37:50 2023 kern.warn kernel: [ 7378.194006] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sun Feb 12 15:37:54 2023 daemon.warn dawn: Failed to lookup ID!
Sun Feb 12 15:37:54 2023 daemon.warn dawn: Failed to lookup ID!
Sun Feb 12 15:37:56 2023 kern.warn kernel: [ 7384.201555] ath11k_warn: 402 callbacks suppressed
Sun Feb 12 15:37:56 2023 kern.warn kernel: [ 7384.201575] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sun Feb 12 15:37:56 2023 kern.warn kernel: [ 7384.205267] ath11k c000000.wifi: failed to send pdev bss chan info request
Sun Feb 12 15:37:56 2023 kern.warn kernel: [ 7384.212988] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Sun Feb 12 15:37:56 2023 kern.warn kernel: [ 7384.219606] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 1
Sun Feb 12 15:37:56 2023 kern.warn kernel: [ 7384.226112] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID
Sun Feb 12 15:37:56 2023 kern.warn kernel: [ 7384.232619] ath11k c000000.wifi: failed to submit beacon template command: -108
Sun Feb 12 15:37:56 2023 kern.warn kernel: [ 7384.238791] ath11k c000000.wifi: failed to update bcn template: -108
Sun Feb 12 15:37:56 2023 kern.warn kernel: [ 7384.245977] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sun Feb 12 15:37:56 2023 kern.warn kernel: [ 7384.252599] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 1
Sun Feb 12 15:37:56 2023 kern.warn kernel: [ 7384.259267] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sun Feb 12 15:38:02 2023 kern.warn kernel: [ 7390.271040] ath11k_warn: 74 callbacks suppressed
Sun Feb 12 15:38:02 2023 kern.warn kernel: [ 7390.271060] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sun Feb 12 15:38:02 2023 kern.warn kernel: [ 7390.274751] ath11k c000000.wifi: failed to send pdev bss chan info request
Sun Feb 12 15:38:02 2023 kern.warn kernel: [ 7390.282395] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Sun Feb 12 15:38:02 2023 kern.warn kernel: [ 7390.289012] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 1
Sun Feb 12 15:38:02 2023 kern.warn kernel: [ 7390.295513] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID
Sun Feb 12 15:38:02 2023 kern.warn kernel: [ 7390.302017] ath11k c000000.wifi: failed to submit beacon template command: -108
Sun Feb 12 15:38:02 2023 kern.warn kernel: [ 7390.308192] ath11k c000000.wifi: failed to update bcn template: -108
Sun Feb 12 15:38:02 2023 kern.warn kernel: [ 7390.315377] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sun Feb 12 15:38:02 2023 kern.warn kernel: [ 7390.322001] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 1
Sun Feb 12 15:38:02 2023 kern.warn kernel: [ 7390.328666] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sun Feb 12 15:38:07 2023 kern.warn kernel: [ 7395.293730] ath11k_warn: 74 callbacks suppressed
Sun Feb 12 15:38:07 2023 kern.warn kernel: [ 7395.293750] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sun Feb 12 15:38:07 2023 kern.warn kernel: [ 7395.297478] ath11k c000000.wifi: failed to send pdev bss chan info request
Sun Feb 12 15:38:07 2023 kern.warn kernel: [ 7395.305409] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sun Feb 12 15:38:07 2023 kern.warn kernel: [ 7395.311708] ath11k c000000.wifi: failed to send pdev bss chan info request
Sun Feb 12 15:38:07 2023 kern.warn kernel: [ 7395.320472] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sun Feb 12 15:38:07 2023 kern.warn kernel: [ 7395.326088] ath11k c000000.wifi: failed to send pdev bss chan info request
Sun Feb 12 15:38:07 2023 kern.warn kernel: [ 7395.334293] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sun Feb 12 15:38:07 2023 kern.warn kernel: [ 7395.340524] ath11k c000000.wifi: failed to send pdev bss chan info request
Sun Feb 12 15:38:07 2023 kern.warn kernel: [ 7395.349074] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sun Feb 12 15:38:07 2023 kern.warn kernel: [ 7395.354905] ath11k c000000.wifi: failed to send pdev bss chan info request
Sun Feb 12 15:38:09 2023 daemon.warn dawn: Failed to lookup ID!
Sun Feb 12 15:38:09 2023 daemon.warn dawn: Failed to lookup ID!
Sun Feb 12 15:38:14 2023 daemon.warn dnsmasq-dhcp[1]: DHCP packet received on br-wan.XX which has no address
Sun Feb 12 15:38:14 2023 kern.warn kernel: [ 7402.341001] ath11k_warn: 422 callbacks suppressed
Sun Feb 12 15:38:14 2023 kern.warn kernel: [ 7402.341021] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sun Feb 12 15:38:14 2023 kern.warn kernel: [ 7402.344712] ath11k c000000.wifi: failed to send pdev bss chan info request
Sun Feb 12 15:38:14 2023 kern.warn kernel: [ 7402.352429] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Sun Feb 12 15:38:14 2023 kern.warn kernel: [ 7402.359059] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 1
Sun Feb 12 15:38:14 2023 kern.warn kernel: [ 7402.365559] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID
Sun Feb 12 15:38:14 2023 kern.warn kernel: [ 7402.372066] ath11k c000000.wifi: failed to submit beacon template command: -108
Sun Feb 12 15:38:14 2023 kern.warn kernel: [ 7402.378237] ath11k c000000.wifi: failed to update bcn template: -108
Sun Feb 12 15:38:14 2023 kern.warn kernel: [ 7402.385424] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sun Feb 12 15:38:14 2023 kern.warn kernel: [ 7402.392048] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 1
Sun Feb 12 15:38:14 2023 kern.warn kernel: [ 7402.398713] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sun Feb 12 15:38:20 2023 kern.warn kernel: [ 7408.409653] ath11k_warn: 74 callbacks suppressed
Sun Feb 12 15:38:20 2023 kern.warn kernel: [ 7408.409671] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sun Feb 12 15:38:20 2023 kern.warn kernel: [ 7408.413360] ath11k c000000.wifi: failed to send pdev bss chan info request
Sun Feb 12 15:38:20 2023 kern.warn kernel: [ 7408.420995] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Sun Feb 12 15:38:20 2023 kern.warn kernel: [ 7408.427615] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 1
Sun Feb 12 15:38:20 2023 kern.warn kernel: [ 7408.434121] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID
Sun Feb 12 15:38:20 2023 kern.warn kernel: [ 7408.440628] ath11k c000000.wifi: failed to submit beacon template command: -108
Sun Feb 12 15:38:20 2023 kern.warn kernel: [ 7408.446779] ath11k c000000.wifi: failed to update bcn template: -108
Sun Feb 12 15:38:20 2023 kern.warn kernel: [ 7408.454006] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sun Feb 12 15:38:20 2023 kern.warn kernel: [ 7408.460608] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 1
Sun Feb 12 15:38:20 2023 kern.warn kernel: [ 7408.467275] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sun Feb 12 15:38:23 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-COMPLETED success=1 freq=5180 ht_enabled=0 chan_offset=0 chan_width=5 cf1=5250 cf2=0
Sun Feb 12 15:38:23 2023 daemon.warn hostapd: Can't set DFS state for freq 5180 MHz
Sun Feb 12 15:38:23 2023 daemon.warn hostapd: Can't set DFS state for freq 5200 MHz
Sun Feb 12 15:38:23 2023 daemon.warn hostapd: Can't set DFS state for freq 5220 MHz
Sun Feb 12 15:38:23 2023 daemon.warn hostapd: Can't set DFS state for freq 5240 MHz
Sun Feb 12 15:38:23 2023 kern.err kernel: [ 7411.816873] phy0-ap0: failed to set key (1, ff:ff:ff:ff:ff:ff) to hardware (-108)
Sun Feb 12 15:38:23 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Sun Feb 12 15:38:23 2023 daemon.err hostapd: Interface initialization failed
Sun Feb 12 15:38:23 2023 daemon.notice hostapd: phy0-ap0: interface state DFS->DISABLED
Sun Feb 12 15:38:23 2023 daemon.notice hostapd: phy0-ap0: AP-DISABLED
Sun Feb 12 15:38:24 2023 daemon.warn dawn: Failed to lookup ID!
Sun Feb 12 15:38:24 2023 daemon.warn dawn: Failed to lookup ID!
Sun Feb 12 15:38:25 2023 kern.warn kernel: [ 7413.757046] ath11k_warn: 414 callbacks suppressed
Sun Feb 12 15:38:25 2023 kern.warn kernel: [ 7413.757066] ath11k c000000.wifi: failed to send WMI_REQUEST_STATS cmd
Sun Feb 12 15:38:25 2023 kern.warn kernel: [ 7413.760754] ath11k c000000.wifi: could not request fw stats (-108)
Sun Feb 12 15:38:25 2023 kern.warn kernel: [ 7413.767201] ath11k c000000.wifi: failed to request fw pdev stats: -108
Sun Feb 12 15:38:25 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5260 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5260 cf2=0
Sun Feb 12 15:38:25 2023 kern.warn kernel: [ 7413.773606] ath11k c000000.wifi: failed to send WMI_REQUEST_STATS cmd
Sun Feb 12 15:38:25 2023 kern.warn kernel: [ 7413.779786] ath11k c000000.wifi: could not request fw stats (-108)
Sun Feb 12 15:38:25 2023 kern.warn kernel: [ 7413.786271] ath11k c000000.wifi: failed to request fw pdev stats: -108
Sun Feb 12 15:38:25 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5280 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5280 cf2=0
Sun Feb 12 15:38:25 2023 kern.warn kernel: [ 7413.792594] ath11k c000000.wifi: failed to send WMI_REQUEST_STATS cmd
Sun Feb 12 15:38:25 2023 kern.warn kernel: [ 7413.798876] ath11k c000000.wifi: could not request fw stats (-108)
Sun Feb 12 15:38:25 2023 kern.warn kernel: [ 7413.805370] ath11k c000000.wifi: failed to request fw pdev stats: -108
Sun Feb 12 15:38:25 2023 kern.warn kernel: [ 7413.811662] ath11k c000000.wifi: failed to send WMI_REQUEST_STATS cmd
Sun Feb 12 15:38:25 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5300 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5300 cf2=0
Sun Feb 12 15:38:25 2023 daemon.notice hostapd: phy0-ap0: DFS-PRE-CAC-EXPIRED freq=5320 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5320 cf2=0
Sun Feb 12 15:38:32 2023 kern.warn kernel: [ 7420.479706] ath11k_warn: 86 callbacks suppressed
Sun Feb 12 15:38:32 2023 kern.warn kernel: [ 7420.479726] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sun Feb 12 15:38:32 2023 kern.warn kernel: [ 7420.483418] ath11k c000000.wifi: failed to send pdev bss chan info request
Sun Feb 12 15:38:32 2023 kern.warn kernel: [ 7420.491112] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Sun Feb 12 15:38:32 2023 kern.warn kernel: [ 7420.497676] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 1
Sun Feb 12 15:38:32 2023 kern.warn kernel: [ 7420.504178] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID
Sun Feb 12 15:38:32 2023 kern.warn kernel: [ 7420.510685] ath11k c000000.wifi: failed to submit beacon template command: -108
Sun Feb 12 15:38:32 2023 kern.warn kernel: [ 7420.516836] ath11k c000000.wifi: failed to update bcn template: -108
Sun Feb 12 15:38:32 2023 kern.warn kernel: [ 7420.524065] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sun Feb 12 15:38:32 2023 kern.warn kernel: [ 7420.530660] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 1
Sun Feb 12 15:38:32 2023 kern.warn kernel: [ 7420.537332] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sun Feb 12 15:38:38 2023 kern.warn kernel: [ 7426.546314] ath11k_warn: 258 callbacks suppressed
Sun Feb 12 15:38:38 2023 kern.warn kernel: [ 7426.546335] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sun Feb 12 15:38:38 2023 kern.warn kernel: [ 7426.550055] ath11k c000000.wifi: failed to send pdev bss chan info request
Sun Feb 12 15:38:38 2023 kern.warn kernel: [ 7426.557773] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Sun Feb 12 15:38:38 2023 kern.warn kernel: [ 7426.564347] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 1
Sun Feb 12 15:38:38 2023 kern.warn kernel: [ 7426.570890] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID
Sun Feb 12 15:38:38 2023 kern.warn kernel: [ 7426.577380] ath11k c000000.wifi: failed to submit beacon template command: -108
Sun Feb 12 15:38:38 2023 kern.warn kernel: [ 7426.583533] ath11k c000000.wifi: failed to update bcn template: -108
Sun Feb 12 15:38:38 2023 kern.warn kernel: [ 7426.590778] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sun Feb 12 15:38:38 2023 kern.warn kernel: [ 7426.597360] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 1
Sun Feb 12 15:38:38 2023 kern.warn kernel: [ 7426.604018] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
854

Thank you very much for sharing!

I can reproduce.

Lan: connected
Wan: not connected
After setting fw_setenv console_unlock 1, reboot, press a key and got to u-boot shell.

Bootloader Changed! Write correct version to environment
Hit any key to stop autoboot:  0 

Net:   MAC0 addr:2c:ea:dc:c3:98:5
PHY ID1: 0x4d
PHY ID2: 0xd0b1
PHY ID1: 0x4d
PHY ID2: 0xd101
EDMA ver 1 hw init
Num rings - TxDesc:1 (0-0) TxCmpl:1 (7-7)
RxDesc:1 (15-15) RxFill:1 (7-7)
ipq807x_edma_alloc_rings: successfull
ipq807x_edma_setup_ring_resources: successfull
ipq807x_edma_configure_rings: successfull
ipq807x_edma_hw_init: successfull
eth0
IPQ807x#

I do not have a tftp server running, but I got this when trying the tftp commands

PQ807x# setenv ipaddr 192.168.10.10
IPQ807x# setenv serverip 192.168.10.1
IPQ807x# tftpboot
ipq807x_eth_halt: done
eth0 PHY0 up Speed :1000 Full duplex
eth0 PHY1 Down Speed :10 Half duplex
eth0 PHY2 Down Speed :10 Half duplex
eth0 PHY3 Down Speed :10 Half duplex
eth0 PHY4 Down Speed :10 Half duplex
eth0 PHY5 Down Speed :10 Half duplex
ipq807x_eth_init: done
*** Warning: no boot file name; using 'C0A80A0A.img'
Using eth0 device
TFTP from server 192.168.10.1; our IP address is 192.168.10.10
Filename 'C0A80A0A.img'.
Load address: 0x44000000
Loading: *
3 Likes
855

@missingcharacter and @sampson, the issue with TFTP and any network-related command on this device is that the network needs to be initialized first for them to work, but there is no command to initialize it.

Network is automatically initialized when automatic boot is interrupted and before entering the U-Boot shell.
That means it's not available for automatic boot.

For example, setting bootcmd to something like "tftpboot" won't work.
That is the reason the second installation option uses an USB flash drive instead of TFTP.

Having said that, it would be great if someone finds a way to enable the network on automatic boot (maybe the updated U-Boot has support for it).

856

@robimarko, @frollic and @luaraneda,

Do we at least have enough information to make this device suitable for recommendation?

857

Thank you, I rebooted and tried again and got the same output as you

IPQ807x# setenv ipaddr 192.168.10.10
IPQ807x# setenv serverip 192.168.10.1
IPQ807x# tftpboot
ipq807x_eth_halt: done
eth0 PHY0 Down Speed :10 Half duplex
eth0 PHY1 Down Speed :10 Half duplex
eth0 PHY2 Down Speed :10 Half duplex
eth0 PHY3 Down Speed :10 Half duplex
eth0 PHY4 Down Speed :10 Half duplex
eth0 PHY5 up Speed :1000 Full duplex
ipq807x_eth_init: done
*** Warning: no boot file name; using 'C0A80A0A.img'
Using eth0 device
TFTP from server 192.168.10.1; our IP address is 192.168.10.10
Filename 'C0A80A0A.img'.
Load address: 0x44000000
Loading: ipq807x_eth_halt: done

Abort

Filename seems to be C0A80A0A.img

which seems to be this:

image
image1740×210 18.6 KB 

$ strings mtd15-appsbl | grep -B3 -A3 '\.img'
TFTP timeout (%ld ms) too low, set min = 1000 ms
tftptimeoutcountmax
TFTP timeout count max (%d ms) negative, set to 0
%02X%02X%02X%02X.img
*** Warning: no boot file name; using '%s'
TFTP %s server %pI4; our IP address is %pI4
; sending through gateway %pI4
858

You still have some complexity. At least avahi and dawn are running???
Dawn might be more critical here, as it is wireless related..
(and there are dawn related warnings)

Looking at the logs, some things pop up:

  • driver apparently prevents HT40 due to too much traffic. Might well set it to 20 by yourself.
Sun Feb 12 15:37:07 2023 daemon.notice hostapd: 20/40 MHz operation not permitted on channel pri=6 sec=10 based on overlapping BSSes
Sun Feb 12 15:37:07 2023 daemon.notice hostapd: Fallback to 20 MHz
  • DFS scan is started a few seconds before the crash. DFS-CAC-START.
    Radio is unusable for a minute, after which there should be DFS-CAC-COMPLETED.
Sun Feb 12 15:37:18 2023 daemon.notice hostapd: phy0-ap0: interface state HT_SCAN->DFS
Sun Feb 12 15:37:18 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-START freq=5180 chan=36 sec_chan=1, width=2, seg0=50, seg1=0, cac_time=60s
  • During that scan priod dawn tries to do something and fails. Possibly because the radio is unusable, in DFS scaninng mode.
Sun Feb 12 15:37:39 2023 daemon.warn dawn: Failed to lookup ID!

Crash apparently happens soon after that.

Regarding the crash itself, similarly as in the previous crash there, the function ieee80211_color_change_finish is visible in the stack trace.

Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.893671]  sta_set_sinfo+0xba4/0xbc0 [mac80211]
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.895933]  sta_info_destroy_addr_bss+0x50/0x7c [mac80211]
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.900794]  ieee80211_color_change_finish+0x1d78/0x2030 [mac80211]
Sun Feb 12 15:37:40 2023 kern.warn kernel: [ 7368.906178]  cfg80211_check_station_change+0x1408/0x4970 [cfg80211]

Are you manipulating the bss_color? If yes, you might drop that setting and test if stability grows.

Could be that dawn or something else tries to force something to happen while the radio is locked into the scanning mode, and the operation fails, but that is not handled gracefully. Or something like that.

  • there is message about the processor being stopped:
remoteproc remoteproc0: stopped remote processor cd00000.q6v5_wcs

The chip is shut down there? and remains off after that??? Might be the reason why a power-off is needed.

EDIT:
I would drop at the least Dawn from the equation at this point.

859

Thnx, I was curious if uboot had some default server and own IPs defined, or if they actually had to be set for tftpboot to work.

860

Killed DAWN, seems to be stable. Interesting how DAWN didn't kick in and ruin things until I modified the SSIDs.

I am not, could that be DAWN too? I honestly haven't had time to fine-tune DAWN yet so I'm not too knowledgeable on the subject.

1 Like
861

Why are you even using it?

862

Maybe @PolynomialDivision might be able to help you there. Curious, if either ath11k wifi driver or your setting might affect something in Dawn, so that its actions can crash/lock your radio.

Based on your logs, one possible thing is that something is tried to be done forcefully during the DFS scanning period, when the radio is unusable to large extent.

EDIT: corrected ath11k

863

I was going to use it for better AP transitioning on legacy devices, smart switches, sensors, etc. but hadn't really dug into it yet.

Worth reporting to @PolynomialDivision as removing DAWN from my builds seems to have eliminated my problems.

2 Likes
864

Did a little playing with the IRQ's... I noticed that everything was basically pulling from CPU0. irqbalance didn't seem to do anything, so I manually moved some of them around based on feedback from the Xiaomi AX3600 thread since the hardware is extremely comparable.

Below you will see what I added to the startup script, and what the outcome was. Previously everything was on CPU0. Definitely balances the load and I notice less latency as well. Processor frequencies ramp up evenly (generally speaking) across the CPUs now also. Next I may play with the processor frequencies and responsiveness to see if I can further accelerate. If anyone has any feedback or requests on what I've done, let me know!

#assign 4 rx interrupts to each cores
echo 8 > /proc/irq/50/smp_affinity
echo 4 > /proc/irq/51/smp_affinity
echo 2 > /proc/irq/52/smp_affinity
echo 1 > /proc/irq/53/smp_affinity

#assign 3 tcl completions to 3 CPUs
echo 4 > /proc/irq/73/smp_affinity
echo 2 > /proc/irq/74/smp_affinity
echo 1 > /proc/irq/75/smp_affinity

root@OpenWrt:~# cat /proc/interrupts
           CPU0       CPU1       CPU2       CPU3       
  9:          0          0          0          0     GIC-0  39 Level     arch_mem_timer
 13:   52555543   10352022   19393113   13975357     GIC-0  20 Level     arch_timer
 16:          2          0          0          0     GIC-0 354 Edge      smp2p
 17:          0          0          0          0     GIC-0 216 Level     4a9000.thermal-sensor
 18:          0          0          0          0     GIC-0 239 Level     bam_dma
 21:          0          0          0          0     GIC-0 270 Level     bam_dma
 22:          6          0          0          0     GIC-0 340 Level     msm_serial0
 23:      57057          0          0          0     GIC-0 178 Level     bam_dma
 24:          0          0          0          0     GIC-0  35 Edge      wdt_bark
 25:          0          0          0          0     GIC-0 357 Edge      q6v5 wdog
 29:          5          0          0          0     GIC-0 348 Edge      ce0
 30:   64186812          0          0          0     GIC-0 347 Edge      ce1
 31:    7329517          0          0          0     GIC-0 346 Edge      ce2
 32:     158815          0          0          0     GIC-0 343 Edge      ce3
 34:        688          0          0          0     GIC-0 443 Edge      ce5
 36:     124780          0          0          0     GIC-0  72 Edge      ce7
 38:          0          0          0          0     GIC-0 334 Edge      ce9
 39:          0          0          0          0     GIC-0 333 Edge      ce10
 40:          0          0          0          0     GIC-0  69 Edge      ce11
 47:          0          0          0          0     GIC-0 323 Edge      reo2ost-exception
 48:    1686954          0          0          0     GIC-0 322 Edge      wbm2host-rx-release
 49:       2067          0          0          0     GIC-0 321 Edge      reo2host-status
 50:          0          0          0    4516536     GIC-0 320 Edge      reo2host-destination-ring4
 51:          2          0    3737029          0     GIC-0 271 Edge      reo2host-destination-ring3
 52:          0    2951387          0          0     GIC-0 268 Edge      reo2host-destination-ring2
 53:    1931130          0          0          0     GIC-0 267 Edge      reo2host-destination-ring1
 57:    5646371          0          0          0     GIC-0 263 Edge      ppdu-end-interrupts-mac3
 58:          0          0          0          0     GIC-0 262 Edge      ppdu-end-interrupts-mac2
 59:   21969296          0          0          0     GIC-0 261 Edge      ppdu-end-interrupts-mac1
 60:          1          0          0          0     GIC-0 260 Edge      rxdma2host-monitor-status-ring-mac3
 61:          0          0          0          0     GIC-0 256 Edge      rxdma2host-monitor-status-ring-mac2
 62:          1          0          0          0     GIC-0 255 Edge      rxdma2host-monitor-status-ring-mac1
 63:          1          0          0          0     GIC-0 235 Edge      host2rxdma-host-buf-ring-mac3
 64:          0          0          0          0     GIC-0 215 Edge      host2rxdma-host-buf-ring-mac2
 65:          1          0          0          0     GIC-0 212 Edge      host2rxdma-host-buf-ring-mac1
 66:          0          0          0          0     GIC-0 211 Edge      rxdma2host-destination-ring-mac3
 67:          0          0          0          0     GIC-0 210 Edge      rxdma2host-destination-ring-mac2
 68:          0          0          0          0     GIC-0 209 Edge      rxdma2host-destination-ring-mac1
 73:          0          0     197806          0     GIC-0 191 Edge      wbm2host-tx-completions-ring3
 74:          1     126375          0          0     GIC-0 190 Edge      wbm2host-tx-completions-ring2
 75:   11096332          0          0          0     GIC-0 189 Edge      wbm2host-tx-completions-ring1
 77:         20          0          0          0     GIC-0  47 Edge      cpr3
 78:   21994960          0          0          0     GIC-0 377 Level     edma_txcmpl
 79:          0          0          0          0     GIC-0 385 Level     edma_rxfill
 80:   38117855          0          0          0     GIC-0 393 Level     edma_rxdesc
 81:          0          0          0          0     GIC-0 376 Level     edma_misc
 82:          0          0          0          0  pmic_arb 51380237 Edge      pm-adc5
 83:          0          0          0          0     smp2p   0 Edge      q6v5 fatal
 84:          1          0          0          0     smp2p   1 Edge      q6v5 ready
 85:          0          0          0          0     smp2p   2 Edge      q6v5 handover
 86:          0          0          0          0     smp2p   3 Edge      q6v5 stop
 87:          0          0          0          0   msmgpio  34 Edge      keys
 88:          0          0          0          0   msmgpio  63 Edge      keys
 89:          0          0          0          0     GIC-0 172 Level     xhci-hcd:usb1
 90:         64          0          0          0     GIC-0 353 Edge      glink-native
IPI0:     59290      63469      78156      97112       Rescheduling interrupts
IPI1:   2178892   22114276   11563475    8193955       Function call interrupts
IPI2:         0          0          0          0       CPU stop interrupts
IPI3:         0          0          0          0       CPU stop (for crash dump) interrupts
IPI4:         0          0          0          0       Timer broadcast interrupts
IPI5:     38784      41950      40609      35496       IRQ work interrupts
IPI6:         0          0          0          0       CPU wake-up interrupts
Err:          0
4 Likes
865

Please keep us updated with your final results and instruction on how to apply it, Thank you,

Just a quick question: do you have any test result by changing software /hardware flow offloading and packet steering? (possibly no effect with hardware offloading as this hardware does not support it)

866

I do not at present - no. My previous dealings with both of those has tended to be less than optimal, but that was with @ACwifidude NSS builds for the R7800. I will test with this router as time proceeds.

867

So everything basically uses a single core? Darn its a fast router then...because i get 250+ wireguard speed together with a mesh. Had other routers that gave up at 150 with wireguard.

868

You surely know, that this just the hex-encoded client IP: 192.168.10.10

Looks like there is a bootfile parameter which maybe would control the TFTP filename:

root@DL-WRX36-7DE ~ # strings /dev/mtd15 | grep boot | grep file 
.callbacks:callbacks,.flags:flags,baudrate:baudrate,bootfile:bootfile,ipaddr:ipaddr,gatewayip:gatewayip,netmask:netmask,serverip:serverip,nvlan:nvlan,vlan:vlan,ethaddr:ethaddr,loadaddr:loadaddr,stdin:console,stdout:console,stderr:console,
bootfile
** No boot file defined **
No valid device tree binary found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED. For sandbox, use -d <file.dtb>
*** Warning: no boot file name; using '%s'

By the way the U-Boot won't enter automatically to this TFTP recovery if one keeps pushing the RESET or the WPS button while powering on the device?

1 Like
869

Nicely spotted. :wink:
They have funny humor.

870

They have! :grinning:

I had to learn it in the hard way with the AX3600, as it does DHCP while TFTP recovery, so if one configure DHCP differently then it would request the file with different name. :sweat_smile:

871

Well, then is actually maybe not hard-coded, but based on logic regarding the IP.
Might be that if u-boot is configured differently regarding the IPs, its TFTP module might search other filename.