Posted: Mon Oct 25, 2021 9:36 Post subject: New Build - 10/25/2021 - r47596
[WARNING]: This thread is only for feedback on this beta release for developers and the community's benefit.
DO NOT flash this beta release unless you understand the risks involved and device specificrecovery methods.
Avoid discussions! Create threads for questions, general problems or use search; this thread is not for support.
Please list router model & revision, operating & wireless mode(s) and exact filename/firmware image flashed.
Issues:
• Show us your findings with steps to reproduce, configuration, output, logs and important information below!
Important:
• For issues provide applicable info: 'dmesg', 'cat /tmp/var/log/messages', syslog, klog, serial, strace, tcpdump, wireshark etc.
• Any firewall NAT or WAN issues, show output: 'iptables -vnL', 'iptables -t nat -vnL', 'iptables -t mangle -vnL' and /tmp/.ipt file.
• Search SVN tickets & discuss in forum before opening. Before reporting: reset & manually set up, not restore from a backup.
• Please include operating & wireless modes (e.g. Gateway, Router, AP, CB, WDS, Mesh) & relevant configuration information.
Joined: 16 Nov 2015 Posts: 6410 Location: UK, London, just across the river..
Posted: Mon Oct 25, 2021 19:29 Post subject:
Router Model TP-Link WR1043ND V2
Firmware Version DD-WRT v3.0-r47596 std (10/25/21)
Kernel Version Linux 3.18.140-d6 #128996 Mon Oct 25 06:47:39 +07 2021 mips
update: CLI r47528 > r47596
reset: NO/YES
mode: Gateway
status: NON Operational
errors: since 47528 something broke on this router...
currently the last working build for this unit is 47528..if i update to 47581 or 47596 without reset, unit goes in bootloop...
if i do a reset it doesn't go on loop, but its not functional...even with basic set up, there is no NTP resolving, no DNS and no Internet at all..
If i redo all my settings manually, it goes on bootloop again...
i have a syslog output from 47596 log in to see the attachment ...
while on 47528 im running this set up..
TP-Link WR1043NDv2 -DD-WRT 47528 - GTW,NAT,AP Isolation,Ad-Block,Firewall,Local DNS,Forced DNS,DoT,VPN,VLAN via start up script _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Last edited by Alozaros on Mon Oct 25, 2021 23:23; edited 2 times in total
Joined: 16 Nov 2015 Posts: 6410 Location: UK, London, just across the river..
Posted: Mon Oct 25, 2021 20:12 Post subject:
kernel-panic69 wrote:
It would be great to know at what point the bootloop occurs; what specific setting or feature being enabled, etc. I will email BS.
i know, but its a lot of a hassle to find it and takes time that i don't have ATM...
I have a syslog form reseted 47596 with very basic setup that its not operational...for some reason...
I couldn't get the bootloop syslog, as i don't have serial on this unit, nor i've my adaptor with me..
it loops about 1-2 min of use... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Router/Version: TP-LINK Archer C7 v5 (US)
File/Kernel: DD-WRT v3.0-r47596 std (10/25/21)
Previous/Reset: DD-WRT v3.0-r47581 std (10/20/21) / No Reset
Mode/Status: Gateway / Working (see note below)
NOTE:
DDWRT firmware version not working, using VANILLA.
Here's a syslog:
Code:
Oct 25 23:41:53 MAIN syslog.info syslogd started: BusyBox v1.34.1
Oct 25 23:41:53 MAIN user.info : [syslogd] : daemon successfully started
Oct 25 23:41:53 MAIN user.info : [sfe] : shortcut forwarding engine successfully stopped
Oct 25 23:41:53 MAIN user.info : [sfe] : shortcut forwarding engine successfully started
Oct 25 23:41:54 MAIN user.info : [sfe] : shortcut forwarding engine successfully stopped
Oct 25 23:41:55 MAIN user.info : [vpn modules] : vpn modules successfully unloaded
Oct 25 23:41:55 MAIN user.info : [vpn modules] : nf_conntrack_proto_gre successfully loaded
Oct 25 23:41:55 MAIN user.info : [vpn modules] : nf_nat_proto_gre successfully loaded
Oct 25 23:41:55 MAIN user.info : [vpn modules] : nf_conntrack_pptp successfully loaded
Oct 25 23:41:55 MAIN user.info : [vpn modules] : nf_nat_pptp successfully loaded
Oct 25 23:41:56 MAIN user.info : [sfe] : shortcut forwarding engine successfully started
Oct 25 23:41:56 MAIN user.info : [sfe] : shortcut forwarding engine successfully started
Oct 25 23:41:57 MAIN user.info : [hwmon] : successfully started
Oct 25 23:41:57 MAIN user.info : [dnsmasq] : daemon successfully stopped
Oct 25 23:41:57 MAIN user.info : [pptpd] : daemon successfully stopped
Oct 25 23:41:57 MAIN user.info : [dnsmasq] : daemon successfully started
Oct 25 23:41:57 MAIN user.info : [sfe] : shortcut forwarding engine successfully stopped
Oct 25 23:41:57 MAIN user.info : [sfe] : shortcut forwarding engine successfully started
Oct 25 23:41:58 MAIN user.info : [sfe] : shortcut forwarding engine successfully stopped
Oct 25 23:41:59 MAIN user.info : [vpn modules] : vpn modules successfully unloaded
Oct 25 23:41:59 MAIN user.info : [vpn modules] : nf_conntrack_proto_gre successfully loaded
Oct 25 23:41:59 MAIN user.info : [vpn modules] : nf_nat_proto_gre successfully loaded
Oct 25 23:41:59 MAIN user.info : [vpn modules] : nf_conntrack_pptp successfully loaded
Oct 25 23:41:59 MAIN user.info : [vpn modules] : nf_nat_pptp successfully loaded
Oct 25 23:41:59 MAIN user.info : [sfe] : shortcut forwarding engine successfully started
Oct 25 23:42:00 MAIN user.info : [sfe] : shortcut forwarding engine successfully started
Oct 25 23:42:24 MAIN daemon.err httpd[3806]: [httpd] : Request Error Code 404: The file style//style.css was not found.
Oct 25 23:42:29 MAIN user.info : [servicemanager] : waiting for services to finish (1)...
---Here is when I switched from Vanilla to DDWRT, each error coincides with a connection drop---
Oct 25 23:42:29 MAIN user.info : [bridge] : interface vlan1 successfully deleted from bridge br0
Oct 25 23:42:29 MAIN user.info : [bridge] : interface wlan0 successfully deleted from bridge br0
Oct 25 23:42:29 MAIN user.info : [bridge] : interface wlan1 successfully deleted from bridge br0
Oct 25 23:42:29 MAIN user.info : [bridge] : bridge br0 successfully deleted
Oct 25 23:42:29 MAIN user.info : [hostapd] : hostapd daemon successfully stopped
Oct 25 23:42:29 MAIN user.info : [bridge] : interface wlan0 successfully deleted from bridge br0
Oct 25 23:42:29 MAIN user.info : [bridge] : interface wlan1 successfully deleted from bridge br0
Oct 25 23:42:30 MAIN user.info : [bridge] : bridge br0 successfully added
Oct 25 23:42:30 MAIN user.info : [bridge] : interface vlan1 successfully added to bridge br0
Oct 25 23:42:32 MAIN user.info : [bridge] : interface wlan0 successfully added to bridge br0
Oct 25 23:42:38 MAIN user.info : [bridge] : interface wlan1 successfully added to bridge br0
Oct 25 23:42:39 MAIN user.info : [dnsmasq] : daemon successfully stopped
Oct 25 23:42:39 MAIN daemon.err httpd[3806]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:42:39 MAIN user.info : [dnsmasq] : daemon successfully started
Oct 25 23:42:43 MAIN user.info : [httpd] : daemon successfully stopped
Oct 25 23:42:43 MAIN daemon.info httpd[3806]: [httpd] : httpd server shutdown
Oct 25 23:42:43 MAIN daemon.info httpd[5438]: [httpd] : httpd server started at port 80
Oct 25 23:42:43 MAIN user.info : [httpd] : http daemon successfully started
Oct 25 23:44:13 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:44:45 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:44:45 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:44:45 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:44:47 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:46:11 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:46:43 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:46:43 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:46:43 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Joined: 06 Jun 2006 Posts: 7463 Location: Dresden, Germany
Posted: Tue Oct 26, 2021 6:25 Post subject:
herkow wrote:
Router/Version: TP-LINK Archer C7 v5 (US)
File/Kernel: DD-WRT v3.0-r47596 std (10/25/21)
Previous/Reset: DD-WRT v3.0-r47581 std (10/20/21) / No Reset
Mode/Status: Gateway / Working (see note below)
NOTE:
DDWRT firmware version not working, using VANILLA.
Here's a syslog:
Code:
Oct 25 23:41:53 MAIN syslog.info syslogd started: BusyBox v1.34.1
Oct 25 23:41:53 MAIN user.info : [syslogd] : daemon successfully started
Oct 25 23:41:53 MAIN user.info : [sfe] : shortcut forwarding engine successfully stopped
Oct 25 23:41:53 MAIN user.info : [sfe] : shortcut forwarding engine successfully started
Oct 25 23:41:54 MAIN user.info : [sfe] : shortcut forwarding engine successfully stopped
Oct 25 23:41:55 MAIN user.info : [vpn modules] : vpn modules successfully unloaded
Oct 25 23:41:55 MAIN user.info : [vpn modules] : nf_conntrack_proto_gre successfully loaded
Oct 25 23:41:55 MAIN user.info : [vpn modules] : nf_nat_proto_gre successfully loaded
Oct 25 23:41:55 MAIN user.info : [vpn modules] : nf_conntrack_pptp successfully loaded
Oct 25 23:41:55 MAIN user.info : [vpn modules] : nf_nat_pptp successfully loaded
Oct 25 23:41:56 MAIN user.info : [sfe] : shortcut forwarding engine successfully started
Oct 25 23:41:56 MAIN user.info : [sfe] : shortcut forwarding engine successfully started
Oct 25 23:41:57 MAIN user.info : [hwmon] : successfully started
Oct 25 23:41:57 MAIN user.info : [dnsmasq] : daemon successfully stopped
Oct 25 23:41:57 MAIN user.info : [pptpd] : daemon successfully stopped
Oct 25 23:41:57 MAIN user.info : [dnsmasq] : daemon successfully started
Oct 25 23:41:57 MAIN user.info : [sfe] : shortcut forwarding engine successfully stopped
Oct 25 23:41:57 MAIN user.info : [sfe] : shortcut forwarding engine successfully started
Oct 25 23:41:58 MAIN user.info : [sfe] : shortcut forwarding engine successfully stopped
Oct 25 23:41:59 MAIN user.info : [vpn modules] : vpn modules successfully unloaded
Oct 25 23:41:59 MAIN user.info : [vpn modules] : nf_conntrack_proto_gre successfully loaded
Oct 25 23:41:59 MAIN user.info : [vpn modules] : nf_nat_proto_gre successfully loaded
Oct 25 23:41:59 MAIN user.info : [vpn modules] : nf_conntrack_pptp successfully loaded
Oct 25 23:41:59 MAIN user.info : [vpn modules] : nf_nat_pptp successfully loaded
Oct 25 23:41:59 MAIN user.info : [sfe] : shortcut forwarding engine successfully started
Oct 25 23:42:00 MAIN user.info : [sfe] : shortcut forwarding engine successfully started
Oct 25 23:42:24 MAIN daemon.err httpd[3806]: [httpd] : Request Error Code 404: The file style//style.css was not found.
Oct 25 23:42:29 MAIN user.info : [servicemanager] : waiting for services to finish (1)...
---Here is when I switched from Vanilla to DDWRT, each error coincides with a connection drop---
Oct 25 23:42:29 MAIN user.info : [bridge] : interface vlan1 successfully deleted from bridge br0
Oct 25 23:42:29 MAIN user.info : [bridge] : interface wlan0 successfully deleted from bridge br0
Oct 25 23:42:29 MAIN user.info : [bridge] : interface wlan1 successfully deleted from bridge br0
Oct 25 23:42:29 MAIN user.info : [bridge] : bridge br0 successfully deleted
Oct 25 23:42:29 MAIN user.info : [hostapd] : hostapd daemon successfully stopped
Oct 25 23:42:29 MAIN user.info : [bridge] : interface wlan0 successfully deleted from bridge br0
Oct 25 23:42:29 MAIN user.info : [bridge] : interface wlan1 successfully deleted from bridge br0
Oct 25 23:42:30 MAIN user.info : [bridge] : bridge br0 successfully added
Oct 25 23:42:30 MAIN user.info : [bridge] : interface vlan1 successfully added to bridge br0
Oct 25 23:42:32 MAIN user.info : [bridge] : interface wlan0 successfully added to bridge br0
Oct 25 23:42:38 MAIN user.info : [bridge] : interface wlan1 successfully added to bridge br0
Oct 25 23:42:39 MAIN user.info : [dnsmasq] : daemon successfully stopped
Oct 25 23:42:39 MAIN daemon.err httpd[3806]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:42:39 MAIN user.info : [dnsmasq] : daemon successfully started
Oct 25 23:42:43 MAIN user.info : [httpd] : daemon successfully stopped
Oct 25 23:42:43 MAIN daemon.info httpd[3806]: [httpd] : httpd server shutdown
Oct 25 23:42:43 MAIN daemon.info httpd[5438]: [httpd] : httpd server started at port 80
Oct 25 23:42:43 MAIN user.info : [httpd] : http daemon successfully started
Oct 25 23:44:13 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:44:45 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:44:45 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:44:45 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:44:47 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:46:11 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:46:43 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:46:43 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
Oct 25 23:46:43 MAIN daemon.err httpd[5444]: [httpd] : Request Error Code 408: No request appeared within a reasonable time period.
include the kernel log next time. you just enabled syslog.
i tested vanilla and it works _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 06 Jun 2006 Posts: 7463 Location: Dresden, Germany
Posted: Tue Oct 26, 2021 6:26 Post subject:
MLandi wrote:
Update method: SSH / CLI
Router/Version: Netgear R9000 Nighthawk X10
File/Kernel: DD-WRT v3.0-r47596 std (10/25/21)
Previous/Reset: DD-WRT v3.0-r47581 std (10/20/21) / No
Mode/Status: Gateway / Working Normally
Issues/Errors: Incoming & Outgoing logs show nothing (not a new issue)
Thanks, BS!
eable logging first. otherwise you cannot see anything and its also just relevant if wan is enabled _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
eable logging first. otherwise you cannot see anything and its also just relevant if wan is enabled
I do have it enabled, and level set to High. I can use cat /tmp/var/log/messages|more to view the log but I thought the UI would be easier to read. _________________ Netgear R9000
DD-WRT v3.0-r55460 std (03/25/24)
Linux 4.9.337 #715 SMP Mon Mar 25 06:15:53 +07 2024 armv7l
Gateway, AP, DNSMasq, Clock 2000MHz
VAP on wlan1 for internet devices
IPv4 & IPv6 (Prefix Delegation)
Static Leases & DHCP
CloudFlare, no SFE, SmartDNS, no QoS
2.4GHz: Vanilla, Airtime Fairness, NG-Mixed, ACK Timing 3150, WPA2 w/AES & WPA3
5GHz: Vanilla, Airtime Fairness, AC/N Mixed, ACK Timing 3150, WPA2 w/AES & WPA3
2 Netgear AX1800 WiFi Mesh Extenders
Xfinity 1.2Gbps/35Mbps
include the kernel log next time. you just enabled syslog.
i tested vanilla and it works
Yes, vanilla actually works, maybe I wasn't clear in the last post, but vanilla works perfectly. Here's the log with klog enabled:
Code:
This is the (almost) exact moment when I switched from Vanilla to DDWRT
Oct 26 16:02:02 MAIN user.info : [servicemanager] : waiting for services to finish (1)...
Oct 26 16:02:02 MAIN user.info : [bridge] : interface vlan1 successfully deleted from bridge br0
Oct 26 16:02:02 MAIN kern.info kernel: [60576.670000] device vlan1 left promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60576.680000] device eth0 left promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60576.680000] br0: port 1(vlan1) entered disabled state
Oct 26 16:02:02 MAIN user.info : [bridge] : interface wlan0 successfully deleted from bridge br0
Oct 26 16:02:02 MAIN kern.info kernel: [60576.690000] device wlan0 left promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60576.700000] br0: port 2(wlan0) entered disabled state
Oct 26 16:02:02 MAIN user.info : [bridge] : interface wlan1 successfully deleted from bridge br0
Oct 26 16:02:02 MAIN kern.info kernel: [60576.720000] device wlan1 left promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60576.720000] br0: port 3(wlan1) entered disabled state
Oct 26 16:02:02 MAIN user.info : [bridge] : bridge br0 successfully deleted
Oct 26 16:02:02 MAIN user.info : [hostapd] : hostapd daemon successfully stopped
Oct 26 16:02:02 MAIN user.info : [bridge] : interface wlan0 successfully deleted from bridge br0
Oct 26 16:02:02 MAIN user.info : [bridge] : interface wlan1 successfully deleted from bridge br0
Oct 26 16:02:02 MAIN user.info : [bridge] : bridge br0 successfully added
Oct 26 16:02:02 MAIN kern.info kernel: [60577.130000] device br0 entered promiscuous mode
Oct 26 16:02:02 MAIN user.info : [bridge] : interface vlan1 successfully added to bridge br0
Oct 26 16:02:02 MAIN kern.info kernel: [60577.220000] device vlan1 entered promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60577.230000] device eth0 entered promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60577.230000] br0: port 1(vlan1) entered forwarding state
Oct 26 16:02:02 MAIN kern.info kernel: [60577.240000] br0: port 1(vlan1) entered forwarding state
Oct 26 16:02:02 MAIN kern.info kernel: [60577.280000] device br0 left promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60577.290000] device br0 entered promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60577.310000] device br0 left promiscuous mode
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: EEPROM regdomain: 0x8348
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: EEPROM indicates we should expect a country code
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: doing EEPROM country->regdmn map search
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: country maps to regdmn code: 0x3a
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: Country alpha2 being used: US
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: Regpair used: 0x3a
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: regdomain 0x8348 dynamically updated by user
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: EEPROM regdomain: 0x8348
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: EEPROM indicates we should expect a country code
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: doing EEPROM country->regdmn map search
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: country maps to regdmn code: 0x3a
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: Country alpha2 being used: US
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: Regpair used: 0x3a
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: regdomain 0x8348 dynamically updated by user
Oct 26 16:02:03 MAIN kern.info kernel: [60577.730000] device wlan0 entered promiscuous mode
Oct 26 16:02:05 MAIN kern.info kernel: [60579.410000] br0: port 2(wlan0) entered forwarding state
Oct 26 16:02:05 MAIN kern.info kernel: [60579.410000] br0: port 2(wlan0) entered forwarding state
Oct 26 16:02:05 MAIN user.info : [bridge] : interface wlan0 successfully added to bridge br0
Oct 26 16:02:05 MAIN kern.info kernel: [60579.500000] ath10k_pci 0000:00:00.0: user requested fw restart
Oct 26 16:02:05 MAIN kern.warn kernel: [60579.610000] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:00:00.0.bin failed with error -2
Oct 26 16:02:05 MAIN kern.warn kernel: [60579.620000] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/cal-pci-0000:00:00.0.bin failed with error -2
Oct 26 16:02:05 MAIN kern.warn kernel: [60579.630000] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-6.bin failed with error -2
Oct 26 16:02:05 MAIN kern.info kernel: [60579.640000] ath10k_pci 0000:00:00.0: found firmware features ie (4 B)
Oct 26 16:02:05 MAIN kern.info kernel: [60579.650000] ath10k_pci 0000:00:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
Oct 26 16:02:05 MAIN kern.info kernel: [60579.660000] ath10k_pci 0000:00:00.0: kconfig debug 1 debugfs 1 tracing 0 dfs 0 testmode 0
Oct 26 16:02:05 MAIN kern.info kernel: [60579.670000] ath10k_pci 0000:00:00.0: firmware ver 10.2.4-97.2-ddwrt-6301M api 5 features wmi-10.x,no-p2p,wmi-10.2,raw-mode,mfp,allows-mesh-bcast,peer-fixed-rate crc32 69ddfd64
Oct 26 16:02:05 MAIN kern.info kernel: [60579.710000] ath10k_pci 0000:00:00.0: boot get otp board id result 0x00000001 board_id 0 chip_id 0 ext_bid_support 0
Oct 26 16:02:05 MAIN kern.info kernel: [60579.730000] ath10k_pci 0000:00:00.0: board id does not exist in otp, ignore it (-2144456272)
Oct 26 16:02:05 MAIN kern.info kernel: [60579.730000] ath10k_pci 0000:00:00.0: boot using board name 'bus=pci,vendor=168c,device=003c,subsystem-vendor=0000,subsystem-device=0000'
Oct 26 16:02:05 MAIN kern.info kernel: [60579.750000] ath10k_pci 0000:00:00.0: boot using board name 'bus=pci,vendor=168c,device=003c,subsystem-vendor=0000,subsystem-device=0000'
Oct 26 16:02:05 MAIN kern.warn kernel: [60579.760000] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
Oct 26 16:02:05 MAIN kern.info kernel: [60579.770000] ath10k_pci 0000:00:00.0: board_file api 1 bmi_id N/A crc32 aaa71214
Oct 26 16:02:05 MAIN kern.info kernel: [60579.790000] ath10k_pci 0000:00:00.0: boot upload otp to 0x1234 len 6209
Oct 26 16:02:05 MAIN kern.warn kernel: [60579.820000] ath10k_pci 0000:00:00.0: otp stream is empty, using board.bin contents
Oct 26 16:02:06 MAIN kern.info kernel: [60580.730000] ath10k_pci 0000:00:00.0: Init Max Stations to 118
Oct 26 16:02:06 MAIN kern.info kernel: [60580.740000] ath10k_pci 0000:00:00.0: P 135 V 16 T 433
Oct 26 16:02:06 MAIN kern.info kernel: [60580.750000] ath10k_pci 0000:00:00.0: alloc rem: 9492 iram: 42308
Oct 26 16:02:06 MAIN kern.info kernel: [60580.760000] ath10k_pci 0000:00:00.0: wmi event ready sw_version 0x41000061 abi_version 1 mac_addr d8:47:32:59:93:d3 status 0
Oct 26 16:02:06 MAIN kern.info kernel: [60580.770000] ath10k_pci 0000:00:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 118 raw 0 hwcrypto 1
Oct 26 16:02:09 MAIN kern.warn kernel: [60583.920000] ath10k_pci 0000:00:00.0: wmi command 36870 timeout, restarting hardware
Oct 26 16:02:09 MAIN kern.warn kernel: [60583.920000] ath10k_pci 0000:00:00.0: ani_enable failed from debugfs: -11
Oct 26 16:02:09 MAIN kern.warn kernel: [60583.930000] ath10k_pci 0000:00:00.0: cannot restart a device that hasn't been started
Oct 26 16:02:09 MAIN kern.info kernel: [60584.260000] ath10k_pci 0000:00:00.0: boot upload otp to 0x1234 len 6209
Oct 26 16:02:09 MAIN kern.warn kernel: [60584.300000] ath10k_pci 0000:00:00.0: otp stream is empty, using board.bin contents
Oct 26 16:02:10 MAIN kern.info kernel: [60585.200000] ath10k_pci 0000:00:00.0: Init Max Stations to 118
Oct 26 16:02:10 MAIN kern.info kernel: [60585.210000] ath10k_pci 0000:00:00.0: P 135 V 16 T 433
Oct 26 16:02:10 MAIN kern.info kernel: [60585.220000] ath10k_pci 0000:00:00.0: alloc rem: 9492 iram: 42308
Oct 26 16:02:10 MAIN kern.info kernel: [60585.230000] ath10k_pci 0000:00:00.0: wmi event ready sw_version 0x41000061 abi_version 1 mac_addr d8:47:32:59:93:d3 status 0
Oct 26 16:02:10 MAIN kern.warn kernel: [60585.240000] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
Oct 26 16:02:10 MAIN kern.warn kernel: [60585.260000] ath10k_pci 0000:00:00.0: failed to set vdev 0 tx encap mode: -122
Oct 26 16:02:10 MAIN kern.info kernel: [60585.280000] device wlan1 entered promiscuous mode
Oct 26 16:02:10 MAIN kern.info kernel: [60585.280000] br0: port 3(wlan1) entered forwarding state
Oct 26 16:02:10 MAIN kern.info kernel: [60585.290000] br0: port 3(wlan1) entered forwarding state
Oct 26 16:02:10 MAIN kern.info kernel: [60585.290000] br0: port 3(wlan1) entered disabled state
Oct 26 16:02:11 MAIN kern.info kernel: [60585.730000] br0: port 3(wlan1) entered forwarding state
Oct 26 16:02:11 MAIN kern.info kernel: [60585.740000] br0: port 3(wlan1) entered forwarding state
Oct 26 16:02:11 MAIN user.info : [bridge] : interface wlan1 successfully added to bridge br0
Oct 26 16:02:11 MAIN user.info : [dnsmasq] : daemon successfully stopped
Oct 26 16:02:12 MAIN user.info : [dnsmasq] : daemon successfully started
Oct 26 16:02:15 MAIN user.info : [httpd] : daemon successfully stopped
Oct 26 16:02:15 MAIN daemon.info httpd[6086]: [httpd] : httpd server shutdown
Oct 26 16:02:15 MAIN daemon.info httpd[26909]: [httpd] : httpd server started at port 80
Oct 26 16:02:15 MAIN user.info : [httpd] : http daemon successfully started
Oct 26 16:02:17 MAIN kern.info kernel: [60592.280000] br0: port 1(vlan1) entered forwarding state
Oct 26 16:02:20 MAIN kern.info kernel: [60594.440000] br0: port 2(wlan0) entered forwarding state
Oct 26 16:02:26 MAIN kern.info kernel: [60600.760000] br0: port 3(wlan1) entered forwarding state
Oct 26 16:05:20 MAIN kern.info kernel: [60774.510000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:26 MAIN kern.info kernel: [60780.890000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:30 MAIN kern.info kernel: [60784.730000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:33 MAIN kern.info kernel: [60788.120000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:34 MAIN kern.info kernel: [60788.820000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:34 MAIN kern.info kernel: [60789.160000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:38 MAIN kern.info kernel: [60792.580000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:38 MAIN kern.info kernel: [60793.050000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:39 MAIN kern.info kernel: [60793.390000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:39 MAIN kern.info kernel: [60793.860000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:39 MAIN kern.info kernel: [60794.200000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:53 MAIN kern.info kernel: [60807.790000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:53 MAIN kern.info kernel: [60808.260000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:54 MAIN kern.info kernel: [60808.600000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:54 MAIN kern.info kernel: [60809.070000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:55 MAIN kern.info kernel: [60809.400000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:04 MAIN kern.info kernel: [60818.530000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:04 MAIN kern.info kernel: [60819.000000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:04 MAIN kern.info kernel: [60819.350000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:05 MAIN kern.info kernel: [60819.810000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:05 MAIN kern.info kernel: [60820.140000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:23 MAIN kern.info kernel: [60837.520000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:23 MAIN kern.info kernel: [60837.890000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:23 MAIN kern.info kernel: [60838.230000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:24 MAIN kern.info kernel: [60839.080000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:25 MAIN kern.info kernel: [60839.550000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:25 MAIN kern.info kernel: [60839.890000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:25 MAIN kern.info kernel: [60840.350000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:26 MAIN kern.info kernel: [60840.680000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:33 MAIN kern.info kernel: [60848.000000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:33 MAIN kern.info kernel: [60848.260000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:34 MAIN kern.info kernel: [60848.530000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:35 MAIN kern.info kernel: [60849.430000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:37 MAIN kern.info kernel: [60851.560000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:40 MAIN kern.info kernel: [60854.870000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:43 MAIN kern.info kernel: [60858.340000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:51 MAIN kern.info kernel: [60865.810000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:57 MAIN kern.info kernel: [60872.240000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:58 MAIN kern.info kernel: [60872.850000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:58 MAIN kern.info kernel: [60873.190000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:07:02 MAIN kern.info kernel: [60876.660000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:07:10 MAIN kern.info kernel: [60885.250000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:07:11 MAIN kern.info kernel: [60885.800000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:07:11 MAIN kern.info kernel: [60886.130000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:07:12 MAIN kern.info kernel: [60886.830000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:07:12 MAIN kern.info kernel: [60887.170000] ath10k_pci 0000:00:00.0: consec fail!!
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Oct 26, 2021 17:32 Post subject:
herkow wrote:
BrainSlayer wrote:
include the kernel log next time. you just enabled syslog.
i tested vanilla and it works
Yes, vanilla actually works, maybe I wasn't clear in the last post, but vanilla works perfectly. Here's the log with klog enabled:
Code:
This is the (almost) exact moment when I switched from Vanilla to DDWRT
Oct 26 16:02:02 MAIN user.info : [servicemanager] : waiting for services to finish (1)...
Oct 26 16:02:02 MAIN user.info : [bridge] : interface vlan1 successfully deleted from bridge br0
Oct 26 16:02:02 MAIN kern.info kernel: [60576.670000] device vlan1 left promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60576.680000] device eth0 left promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60576.680000] br0: port 1(vlan1) entered disabled state
Oct 26 16:02:02 MAIN user.info : [bridge] : interface wlan0 successfully deleted from bridge br0
Oct 26 16:02:02 MAIN kern.info kernel: [60576.690000] device wlan0 left promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60576.700000] br0: port 2(wlan0) entered disabled state
Oct 26 16:02:02 MAIN user.info : [bridge] : interface wlan1 successfully deleted from bridge br0
Oct 26 16:02:02 MAIN kern.info kernel: [60576.720000] device wlan1 left promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60576.720000] br0: port 3(wlan1) entered disabled state
Oct 26 16:02:02 MAIN user.info : [bridge] : bridge br0 successfully deleted
Oct 26 16:02:02 MAIN user.info : [hostapd] : hostapd daemon successfully stopped
Oct 26 16:02:02 MAIN user.info : [bridge] : interface wlan0 successfully deleted from bridge br0
Oct 26 16:02:02 MAIN user.info : [bridge] : interface wlan1 successfully deleted from bridge br0
Oct 26 16:02:02 MAIN user.info : [bridge] : bridge br0 successfully added
Oct 26 16:02:02 MAIN kern.info kernel: [60577.130000] device br0 entered promiscuous mode
Oct 26 16:02:02 MAIN user.info : [bridge] : interface vlan1 successfully added to bridge br0
Oct 26 16:02:02 MAIN kern.info kernel: [60577.220000] device vlan1 entered promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60577.230000] device eth0 entered promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60577.230000] br0: port 1(vlan1) entered forwarding state
Oct 26 16:02:02 MAIN kern.info kernel: [60577.240000] br0: port 1(vlan1) entered forwarding state
Oct 26 16:02:02 MAIN kern.info kernel: [60577.280000] device br0 left promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60577.290000] device br0 entered promiscuous mode
Oct 26 16:02:02 MAIN kern.info kernel: [60577.310000] device br0 left promiscuous mode
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: EEPROM regdomain: 0x8348
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: EEPROM indicates we should expect a country code
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: doing EEPROM country->regdmn map search
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: country maps to regdmn code: 0x3a
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: Country alpha2 being used: US
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: Regpair used: 0x3a
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: regdomain 0x8348 dynamically updated by user
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: EEPROM regdomain: 0x8348
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: EEPROM indicates we should expect a country code
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: doing EEPROM country->regdmn map search
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: country maps to regdmn code: 0x3a
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: Country alpha2 being used: US
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: Regpair used: 0x3a
Oct 26 16:02:03 MAIN kern.debug kernel: [60577.440000] ath: regdomain 0x8348 dynamically updated by user
Oct 26 16:02:03 MAIN kern.info kernel: [60577.730000] device wlan0 entered promiscuous mode
Oct 26 16:02:05 MAIN kern.info kernel: [60579.410000] br0: port 2(wlan0) entered forwarding state
Oct 26 16:02:05 MAIN kern.info kernel: [60579.410000] br0: port 2(wlan0) entered forwarding state
Oct 26 16:02:05 MAIN user.info : [bridge] : interface wlan0 successfully added to bridge br0
Oct 26 16:02:05 MAIN kern.info kernel: [60579.500000] ath10k_pci 0000:00:00.0: user requested fw restart
Oct 26 16:02:05 MAIN kern.warn kernel: [60579.610000] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:00:00.0.bin failed with error -2
Oct 26 16:02:05 MAIN kern.warn kernel: [60579.620000] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/cal-pci-0000:00:00.0.bin failed with error -2
Oct 26 16:02:05 MAIN kern.warn kernel: [60579.630000] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-6.bin failed with error -2
Oct 26 16:02:05 MAIN kern.info kernel: [60579.640000] ath10k_pci 0000:00:00.0: found firmware features ie (4 B)
Oct 26 16:02:05 MAIN kern.info kernel: [60579.650000] ath10k_pci 0000:00:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
Oct 26 16:02:05 MAIN kern.info kernel: [60579.660000] ath10k_pci 0000:00:00.0: kconfig debug 1 debugfs 1 tracing 0 dfs 0 testmode 0
Oct 26 16:02:05 MAIN kern.info kernel: [60579.670000] ath10k_pci 0000:00:00.0: firmware ver 10.2.4-97.2-ddwrt-6301M api 5 features wmi-10.x,no-p2p,wmi-10.2,raw-mode,mfp,allows-mesh-bcast,peer-fixed-rate crc32 69ddfd64
Oct 26 16:02:05 MAIN kern.info kernel: [60579.710000] ath10k_pci 0000:00:00.0: boot get otp board id result 0x00000001 board_id 0 chip_id 0 ext_bid_support 0
Oct 26 16:02:05 MAIN kern.info kernel: [60579.730000] ath10k_pci 0000:00:00.0: board id does not exist in otp, ignore it (-2144456272)
Oct 26 16:02:05 MAIN kern.info kernel: [60579.730000] ath10k_pci 0000:00:00.0: boot using board name 'bus=pci,vendor=168c,device=003c,subsystem-vendor=0000,subsystem-device=0000'
Oct 26 16:02:05 MAIN kern.info kernel: [60579.750000] ath10k_pci 0000:00:00.0: boot using board name 'bus=pci,vendor=168c,device=003c,subsystem-vendor=0000,subsystem-device=0000'
Oct 26 16:02:05 MAIN kern.warn kernel: [60579.760000] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
Oct 26 16:02:05 MAIN kern.info kernel: [60579.770000] ath10k_pci 0000:00:00.0: board_file api 1 bmi_id N/A crc32 aaa71214
Oct 26 16:02:05 MAIN kern.info kernel: [60579.790000] ath10k_pci 0000:00:00.0: boot upload otp to 0x1234 len 6209
Oct 26 16:02:05 MAIN kern.warn kernel: [60579.820000] ath10k_pci 0000:00:00.0: otp stream is empty, using board.bin contents
Oct 26 16:02:06 MAIN kern.info kernel: [60580.730000] ath10k_pci 0000:00:00.0: Init Max Stations to 118
Oct 26 16:02:06 MAIN kern.info kernel: [60580.740000] ath10k_pci 0000:00:00.0: P 135 V 16 T 433
Oct 26 16:02:06 MAIN kern.info kernel: [60580.750000] ath10k_pci 0000:00:00.0: alloc rem: 9492 iram: 42308
Oct 26 16:02:06 MAIN kern.info kernel: [60580.760000] ath10k_pci 0000:00:00.0: wmi event ready sw_version 0x41000061 abi_version 1 mac_addr d8:47:32:59:93:d3 status 0
Oct 26 16:02:06 MAIN kern.info kernel: [60580.770000] ath10k_pci 0000:00:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 118 raw 0 hwcrypto 1
Oct 26 16:02:09 MAIN kern.warn kernel: [60583.920000] ath10k_pci 0000:00:00.0: wmi command 36870 timeout, restarting hardware
Oct 26 16:02:09 MAIN kern.warn kernel: [60583.920000] ath10k_pci 0000:00:00.0: ani_enable failed from debugfs: -11
Oct 26 16:02:09 MAIN kern.warn kernel: [60583.930000] ath10k_pci 0000:00:00.0: cannot restart a device that hasn't been started
Oct 26 16:02:09 MAIN kern.info kernel: [60584.260000] ath10k_pci 0000:00:00.0: boot upload otp to 0x1234 len 6209
Oct 26 16:02:09 MAIN kern.warn kernel: [60584.300000] ath10k_pci 0000:00:00.0: otp stream is empty, using board.bin contents
Oct 26 16:02:10 MAIN kern.info kernel: [60585.200000] ath10k_pci 0000:00:00.0: Init Max Stations to 118
Oct 26 16:02:10 MAIN kern.info kernel: [60585.210000] ath10k_pci 0000:00:00.0: P 135 V 16 T 433
Oct 26 16:02:10 MAIN kern.info kernel: [60585.220000] ath10k_pci 0000:00:00.0: alloc rem: 9492 iram: 42308
Oct 26 16:02:10 MAIN kern.info kernel: [60585.230000] ath10k_pci 0000:00:00.0: wmi event ready sw_version 0x41000061 abi_version 1 mac_addr d8:47:32:59:93:d3 status 0
Oct 26 16:02:10 MAIN kern.warn kernel: [60585.240000] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
Oct 26 16:02:10 MAIN kern.warn kernel: [60585.260000] ath10k_pci 0000:00:00.0: failed to set vdev 0 tx encap mode: -122
Oct 26 16:02:10 MAIN kern.info kernel: [60585.280000] device wlan1 entered promiscuous mode
Oct 26 16:02:10 MAIN kern.info kernel: [60585.280000] br0: port 3(wlan1) entered forwarding state
Oct 26 16:02:10 MAIN kern.info kernel: [60585.290000] br0: port 3(wlan1) entered forwarding state
Oct 26 16:02:10 MAIN kern.info kernel: [60585.290000] br0: port 3(wlan1) entered disabled state
Oct 26 16:02:11 MAIN kern.info kernel: [60585.730000] br0: port 3(wlan1) entered forwarding state
Oct 26 16:02:11 MAIN kern.info kernel: [60585.740000] br0: port 3(wlan1) entered forwarding state
Oct 26 16:02:11 MAIN user.info : [bridge] : interface wlan1 successfully added to bridge br0
Oct 26 16:02:11 MAIN user.info : [dnsmasq] : daemon successfully stopped
Oct 26 16:02:12 MAIN user.info : [dnsmasq] : daemon successfully started
Oct 26 16:02:15 MAIN user.info : [httpd] : daemon successfully stopped
Oct 26 16:02:15 MAIN daemon.info httpd[6086]: [httpd] : httpd server shutdown
Oct 26 16:02:15 MAIN daemon.info httpd[26909]: [httpd] : httpd server started at port 80
Oct 26 16:02:15 MAIN user.info : [httpd] : http daemon successfully started
Oct 26 16:02:17 MAIN kern.info kernel: [60592.280000] br0: port 1(vlan1) entered forwarding state
Oct 26 16:02:20 MAIN kern.info kernel: [60594.440000] br0: port 2(wlan0) entered forwarding state
Oct 26 16:02:26 MAIN kern.info kernel: [60600.760000] br0: port 3(wlan1) entered forwarding state
Oct 26 16:05:20 MAIN kern.info kernel: [60774.510000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:26 MAIN kern.info kernel: [60780.890000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:30 MAIN kern.info kernel: [60784.730000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:33 MAIN kern.info kernel: [60788.120000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:34 MAIN kern.info kernel: [60788.820000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:34 MAIN kern.info kernel: [60789.160000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:38 MAIN kern.info kernel: [60792.580000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:38 MAIN kern.info kernel: [60793.050000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:39 MAIN kern.info kernel: [60793.390000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:39 MAIN kern.info kernel: [60793.860000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:39 MAIN kern.info kernel: [60794.200000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:53 MAIN kern.info kernel: [60807.790000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:53 MAIN kern.info kernel: [60808.260000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:54 MAIN kern.info kernel: [60808.600000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:54 MAIN kern.info kernel: [60809.070000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:05:55 MAIN kern.info kernel: [60809.400000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:04 MAIN kern.info kernel: [60818.530000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:04 MAIN kern.info kernel: [60819.000000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:04 MAIN kern.info kernel: [60819.350000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:05 MAIN kern.info kernel: [60819.810000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:05 MAIN kern.info kernel: [60820.140000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:23 MAIN kern.info kernel: [60837.520000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:23 MAIN kern.info kernel: [60837.890000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:23 MAIN kern.info kernel: [60838.230000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:24 MAIN kern.info kernel: [60839.080000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:25 MAIN kern.info kernel: [60839.550000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:25 MAIN kern.info kernel: [60839.890000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:25 MAIN kern.info kernel: [60840.350000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:26 MAIN kern.info kernel: [60840.680000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:33 MAIN kern.info kernel: [60848.000000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:33 MAIN kern.info kernel: [60848.260000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:34 MAIN kern.info kernel: [60848.530000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:35 MAIN kern.info kernel: [60849.430000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:37 MAIN kern.info kernel: [60851.560000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:40 MAIN kern.info kernel: [60854.870000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:43 MAIN kern.info kernel: [60858.340000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:51 MAIN kern.info kernel: [60865.810000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:57 MAIN kern.info kernel: [60872.240000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:58 MAIN kern.info kernel: [60872.850000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:06:58 MAIN kern.info kernel: [60873.190000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:07:02 MAIN kern.info kernel: [60876.660000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:07:10 MAIN kern.info kernel: [60885.250000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:07:11 MAIN kern.info kernel: [60885.800000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:07:11 MAIN kern.info kernel: [60886.130000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:07:12 MAIN kern.info kernel: [60886.830000] ath10k_pci 0000:00:00.0: consec fail!!
Oct 26 16:07:12 MAIN kern.info kernel: [60887.170000] ath10k_pci 0000:00:00.0: consec fail!!
ddwrt ath10k fw (both qca988x and 99xx) is bad, poor latency, jittery throughput, and other issues like this