New all-in-ones are coming with 2.5G ports (the speed is hardware limited). None of these are supported by openwrt yet. An x86_64 solution is the ultimate routing solution to support multi-gig speed with a quality multi-gig adapter (ex: intel).
My attempts to play with the voltages have failed ..
- setting the
l2-volthigher failed, while the router does handle better the traffic and doesn't crash after 10-15 minutes, it does cause some weird reboots - meaning, it may be stable for 20 hours, but then it reboots every 2-3 minutes, then after few reboots, it stabilize itself. - discovered that the NSS voltages are controlled by
nss_core_vdd_nominalandnss_core_vdd_high. I set the nss_core_vdd_nominal to 1150000 (to bump it up from 1100000) and indeed, the regulator output now reports 1150mV. But same scenario as above. It may handle large traffic, or it may start rebooting every 20 minutes with very low traffic (for example, a 30 minutes youtube video).
However, playing with the voltages changed a bit the output of the dumps ... while before I was seeing only 'invalid address' type of crashes, now the crashes are different - they complain about trapped threads. Below 4 new intercepted ones:
oops - 1
<1>[ 510.935653] NSS core 0 signal COREDUMP COMPLETE 4000
<1>[ 510.935739]
<1>[ 510.935739] 00092c57: Starting NSS-FW logbuffer dump for core 0
<1>[ 510.939717] 00092c57: Warn: trap[620]: Trapped: TRAP_TD(00000080) DCAPT(3C000080)
<1>[ 510.947163] 00092c57: Warn: trap[645]: Trapped: Thread: 7, reason: 00000008, PC: 40045EA4, previous PC: 40046940
<1>[ 510.954526] 00092c57: Warn: trap[594]: A0_3: 3F02F974 3F02F8F4 3F02FA74 3F02FAB8
<1>[ 510.964709] 00092c57: Warn: trap[594]: A4_7: 591A5E00 40046944 00000002 3F0087A4
<1>[ 510.972087] 00092c57: Warn: trap[599]: D0_3: 3F02F8F4 0000007F 00000001 0000007F
<1>[ 510.979466] 00092c57: Warn: trap[599]: D4_7: 00000052 00000006 00000030 00000000
<1>[ 510.986844] 00092c57: Warn: trap[599]: D8_11: 00000000 00000000 00000000 00000000
<1>[ 510.994289] 00092c57: Warn: trap[599]: D12_15: 00000000 00000000 00000000 00000000
<1>[ 511.001603] 00092c57: Warn: trap[701]: Trapped: thread[7]: still has unhandled trapreason: 0x00000008, PC: 40045EA4, previous PC: 40046940
<1>[ 511.009074] 00092c57: Warn: trap[332]: trapped cause decode: src1 address decode error
<1>[ 511.025384] NSS core 1 signal COREDUMP COMPLETE 4000
<1>[ 511.029366]
<1>[ 511.029366] 0bda0377: Starting NSS-FW logbuffer dump for core 1
<0>[ 511.034500] Kernel panic - not syncing: NSS FW coredump: bringing system down
<2>[ 511.041880] CPU1: stopping
<4>[ 511.048909] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.4.108 #0
<4>[ 511.051502] Hardware name: Generic DT based system
<4>[ 511.057695] [<c030f954>] (unwind_backtrace) from [<c030b968>] (show_stack+0x14/0x20)
<4>[ 511.062285] [<c030b968>] (show_stack) from [<c0901ee0>] (dump_stack+0x94/0xa8)
<4>[ 511.070181] [<c0901ee0>] (dump_stack) from [<c030eb80>] (handle_IPI+0x184/0x1b8)
<4>[ 511.077225] [<c030eb80>] (handle_IPI) from [<c05e17c8>] (gic_handle_irq+0xb4/0xb8)
<4>[ 511.084773] [<c05e17c8>] (gic_handle_irq) from [<c0301a8c>] (__irq_svc+0x6c/0x90)
<4>[ 511.092132] Exception stack(0xd846bf18 to 0xd846bf60)
<4>[ 511.099686] bf00: 00000000 00000076
<4>[ 511.104748] bf20: 18112000 d8c52a80 d87eb400 00000000 d8c51e30 00000076 00000076 00000000
<4>[ 511.112906] bf40: fc77f600 fc0d7140 00000015 d846bf68 c0732e50 c0732e54 80000013 ffffffff
<4>[ 511.121062] [<c0301a8c>] (__irq_svc) from [<c0732e54>] (cpuidle_enter_state+0x94/0x498)
<4>[ 511.129216] [<c0732e54>] (cpuidle_enter_state) from [<c073329c>] (cpuidle_enter+0x30/0x4c)
<4>[ 511.137024] [<c073329c>] (cpuidle_enter) from [<c034acdc>] (do_idle+0x1d8/0x240)
<4>[ 511.145354] [<c034acdc>] (do_idle) from [<c034afec>] (cpu_startup_entry+0x1c/0x20)
<4>[ 511.152904] [<c034afec>] (cpu_startup_entry) from [<423024cc>] (0x423024cc)
oops - 2
<1>[ 316.917452] NSS core 1 signal COREDUMP COMPLETE 4000
<1>[ 316.917586]
<1>[ 316.917586] 7de9eb10: Starting NSS-FW logbuffer dump for core 1
<1>[ 316.921575] 7de9eb10: Warn: trap[813]: Trap on CHIP ID 00050000
<1>[ 316.928973] 7de9eb10: Warn: trap[620]: Trapped: TRAP_TD(00000800) DCAPT(3C000080)
<1>[ 316.934573] 7de9eb10: Warn: trap[645]: Trapped: Thread: 11, reason: 00000010, PC: 40814554, previous PC: 4081455C
<1>[ 316.942206] 7de9eb10: Warn: trap[594]: A0_3: 4085F1E0 00000000 3F01D7C0 4085F224
<1>[ 316.952532] 7de9eb10: Warn: trap[594]: A4_7: 3F02FA44 4085F000 4085F07C 3F0047A8
<1>[ 316.959910] 7de9eb10: Warn: trap[599]: D0_3: 000090AE 00000000 0004D4F5 00000000
<1>[ 316.967288] 7de9eb10: Warn: trap[599]: D4_7: 4085F220 00000000 00000000 00000001
<1>[ 316.974668] 7de9eb10: Warn: trap[599]: D8_11: 00000008 0000000A 00000000 00000000
<1>[ 316.982044] 7de9eb10: Warn: trap[599]: D12_15: 00000000 00000000 00000000 00000000
<1>[ 316.989422] 7de9eb10: Warn: trap[649]: Thread_11 has non-recoverable trap
<1>[ 317.000877] NSS core 0 signal COREDUMP COMPLETE 4000
<1>[ 317.003741]
<1>[ 317.003741] 8fa72052: Starting NSS-FW logbuffer dump for core 0
<0>[ 317.008777] Kernel panic - not syncing: NSS FW coredump: bringing system down
<2>[ 317.016161] CPU1: stopping
<4>[ 317.023194] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.4.108 #0
<4>[ 317.025790] Hardware name: Generic DT based system
<4>[ 317.031982] [<c030f954>] (unwind_backtrace) from [<c030b968>] (show_stack+0x14/0x20)
<4>[ 317.036573] [<c030b968>] (show_stack) from [<c0901ee0>] (dump_stack+0x94/0xa8)
<4>[ 317.044470] [<c0901ee0>] (dump_stack) from [<c030eb80>] (handle_IPI+0x184/0x1b8)
<4>[ 317.051514] [<c030eb80>] (handle_IPI) from [<c05e17c8>] (gic_handle_irq+0xb4/0xb8)
<4>[ 317.059059] [<c05e17c8>] (gic_handle_irq) from [<c0301a8c>] (__irq_svc+0x6c/0x90)
<4>[ 317.066419] Exception stack(0xd846bf18 to 0xd846bf60)
<4>[ 317.073973] bf00: 00000000 00000049
<4>[ 317.079035] bf20: 18112000 d8c52a80 d87eb400 00000000 d8c51e30 00000049 00000049 00000000
<4>[ 317.087193] bf40: cfa28640 cf8acbe0 00000015 d846bf68 c0732e50 c0732e54 80000013 ffffffff
<4>[ 317.095350] [<c0301a8c>] (__irq_svc) from [<c0732e54>] (cpuidle_enter_state+0x94/0x498)
<4>[ 317.103502] [<c0732e54>] (cpuidle_enter_state) from [<c073329c>] (cpuidle_enter+0x30/0x4c)
<4>[ 317.111312] [<c073329c>] (cpuidle_enter) from [<c034acdc>] (do_idle+0x1d8/0x240)
<4>[ 317.119640] [<c034acdc>] (do_idle) from [<c034afec>] (cpu_startup_entry+0x1c/0x20)
<4>[ 317.127192] [<c034afec>] (cpu_startup_entry) from [<423024cc>] (0x423024cc)
oops - 3
<1>[ 1049.732937] NSS core 0 signal COREDUMP COMPLETE 4000
<1>[ 1049.733011]
<1>[ 1049.733011] 662acf88: Starting NSS-FW logbuffer dump for core 0
<1>[ 1049.737016] 662acf88: Warn: trap[620]: Trapped: TRAP_TD(00000800) DCAPT(3C000080)
<1>[ 1049.744492] 662acf88: Warn: trap[645]: Trapped: Thread: 11, reason: 00000004, PC: 02117FC1, previous PC: 3F0003FC
<1>[ 1049.751761] 662acf88: Warn: trap[594]: A0_3: 3F024458 00000000 3F024530 02117FC1
<1>[ 1049.762066] 662acf88: Warn: trap[594]: A4_7: 3F024450 3F000400 3F024430 3F0067B8
<1>[ 1049.769532] 662acf88: Warn: trap[599]: D0_3: 00000000 00000000 00000000 00000800
<1>[ 1049.776879] 662acf88: Warn: trap[599]: D4_7: 3F025514 00000000 00000000 00000000
<1>[ 1049.784275] 662acf88: Warn: trap[599]: D8_11: 00000008 0000000A 00000000 00000000
<1>[ 1049.791580] 662acf88: Warn: trap[599]: D12_15: 00000000 00000000 00000000 00000000
<1>[ 1049.799020] 662acf88: Warn: trap[701]: Trapped: thread[11]: still has unhandled trapreason: 0x00000004, PC: 02117FC1, previous PC: 3F0003FC
<1>[ 1049.806486] 662acf88: Warn: trap[332]: trapped cause decode: inst illegal
<1>[ 1049.822766] NSS core 1 signal COREDUMP COMPLETE 4000
<1>[ 1049.825780]
<1>[ 1049.825780] 5ca17eb5: Starting NSS-FW logbuffer dump for core 1
<0>[ 1049.830817] Kernel panic - not syncing: NSS FW coredump: bringing system down
<2>[ 1049.838215] CPU1: stopping
<4>[ 1049.845244] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.4.108 #0
<4>[ 1049.847835] Hardware name: Generic DT based system
<4>[ 1049.854030] [<c030f954>] (unwind_backtrace) from [<c030b968>] (show_stack+0x14/0x20)
<4>[ 1049.858621] [<c030b968>] (show_stack) from [<c0901ee0>] (dump_stack+0x94/0xa8)
<4>[ 1049.866516] [<c0901ee0>] (dump_stack) from [<c030eb80>] (handle_IPI+0x184/0x1b8)
<4>[ 1049.873562] [<c030eb80>] (handle_IPI) from [<c05e17c8>] (gic_handle_irq+0xb4/0xb8)
<4>[ 1049.881105] [<c05e17c8>] (gic_handle_irq) from [<c0301a8c>] (__irq_svc+0x6c/0x90)
<4>[ 1049.888467] Exception stack(0xd846bf18 to 0xd846bf60)
<4>[ 1049.896021] bf00: 00000000 000000f4
<4>[ 1049.901082] bf20: 18112000 d8c52a80 d87eb400 00000000 d8c51e30 000000f4 000000f4 00000000
<4>[ 1049.909241] bf40: 6f3b9200 6ee88b00 00000015 d846bf68 c0732e50 c0732e54 00000013 ffffffff
<4>[ 1049.917396] [<c0301a8c>] (__irq_svc) from [<c0732e54>] (cpuidle_enter_state+0x94/0x498)
<4>[ 1049.925550] [<c0732e54>] (cpuidle_enter_state) from [<c073329c>] (cpuidle_enter+0x30/0x4c)
<4>[ 1049.933358] [<c073329c>] (cpuidle_enter) from [<c034acdc>] (do_idle+0x1d8/0x240)
<4>[ 1049.941688] [<c034acdc>] (do_idle) from [<c034afec>] (cpu_startup_entry+0x1c/0x20)
<4>[ 1049.949239] [<c034afec>] (cpu_startup_entry) from [<423024cc>] (0x423024cc)
oops - 4
<1>[ 865.220478] NSS core 0 signal COREDUMP COMPLETE 4000
<1>[ 865.220521]
<1>[ 865.220521] 8e7673a1: Starting NSS-FW logbuffer dump for core 0
<1>[ 865.224596] 8e7673a1: Warn: trap[813]: Trap on CHIP ID 00050000
<1>[ 865.231893] 8e7673a1: Warn: trap[620]: Trapped: TRAP_TD(00000800) DCAPT(3C000080)
<1>[ 865.237603] 8e7673a1: Warn: trap[645]: Trapped: Thread: 11, reason: 00000010, PC: 4003EDAC, previous PC: 4003EDAC
<1>[ 865.245256] 8e7673a1: Warn: trap[594]: A0_3: 54651400 4008A4BC 54651400 3F006778
<1>[ 865.255473] 8e7673a1: Warn: trap[594]: A4_7: 4003ED04 4000E254 3F025624 3F00675C
<1>[ 865.262950] 8e7673a1: Warn: trap[599]: D0_3: 3F006770 00000000 00000014 00000005
<1>[ 865.270262] 8e7673a1: Warn: trap[599]: D4_7: 3F025514 00000001 00000001 00000000
<1>[ 865.277714] 8e7673a1: Warn: trap[599]: D8_11: 0000000C 0000000F 00000000 00000000
<1>[ 865.285087] 8e7673a1: Warn: trap[599]: D12_15: 00000000 00000000 00000000 00000000
<1>[ 865.292399] 8e7673a1: Warn: trap[649]: Thread_11 has non-recoverable trap
<1>[ 865.303057] NSS core 1 signal COREDUMP COMPLETE 4000
<1>[ 865.306713]
<1>[ 865.306713] 651cea4c: Starting NSS-FW logbuffer dump for core 1
<0>[ 865.311763] Kernel panic - not syncing: NSS FW coredump: bringing system down
<2>[ 865.319139] CPU1: stopping
<4>[ 865.326162] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.4.108 #0
<4>[ 865.328763] Hardware name: Generic DT based system
<4>[ 865.334945] [<c030f954>] (unwind_backtrace) from [<c030b968>] (show_stack+0x14/0x20)
<4>[ 865.339540] [<c030b968>] (show_stack) from [<c0901ee0>] (dump_stack+0x94/0xa8)
<4>[ 865.347437] [<c0901ee0>] (dump_stack) from [<c030eb80>] (handle_IPI+0x184/0x1b8)
<4>[ 865.354478] [<c030eb80>] (handle_IPI) from [<c05e17c8>] (gic_handle_irq+0xb4/0xb8)
<4>[ 865.362025] [<c05e17c8>] (gic_handle_irq) from [<c0301a8c>] (__irq_svc+0x6c/0x90)
<4>[ 865.369392] Exception stack(0xd846bf18 to 0xd846bf60)
<4>[ 865.376944] bf00: 00000000 000000c9
<4>[ 865.381997] bf20: 18112000 d8c52a80 d87eb400 00000000 d8c51e30 000000c9 000000c9 00000000
<4>[ 865.390154] bf40: 790a09e0 77e6d0c0 00000015 d846bf68 c0732e50 c0732e54 00000013 ffffffff
<4>[ 865.398313] [<c0301a8c>] (__irq_svc) from [<c0732e54>] (cpuidle_enter_state+0x94/0x498)
<4>[ 865.406469] [<c0732e54>] (cpuidle_enter_state) from [<c073329c>] (cpuidle_enter+0x30/0x4c)
<4>[ 865.414280] [<c073329c>] (cpuidle_enter) from [<c034acdc>] (do_idle+0x1d8/0x240)
<4>[ 865.422609] [<c034acdc>] (do_idle) from [<c034afec>] (cpu_startup_entry+0x1c/0x20)
<4>[ 865.430162] [<c034afec>] (cpu_startup_entry) from [<423024cc>] (0x423024cc)
I've also tried to set the governor to performance, disable irqbalance, nope, reboots are still there. I will have to roll back the NSS core scaling since I need the router to be more stable during the day...
I hope this answers @Ansuel's question about NSS scaling ...
2 Likes
That's what I thought. I'm thinking of building such a solution using a 10 gig that scales down to 5 2.5 1 and 100mb.
I'm also considering to put dual wireless AX devices in it. Do either of you guys know of any suitable ITX builds that can handle two mini slots? I'm sure I can get a custom case made to put my radios in it.
I would like to have one card that does dual 10 gig, onboard gig management, M2 raid and the other slot. Sata SSD just for boot & on board and twos as well for the AX radios etc.
I would be happy to provide a bootstrap for such a solution using NGinx etc as a front end. I just need to locate the gear first 
that behavior is familiar to me. stable one day or close and quick reboots etc. once rebooted, it never lasts long again. what sense does it make ??
Not sure ... what to make of it either 
What sounds troubling is that there are random reboots reports from people running stock firmware (on Netgear website, on Amazon, or Reddit, etc). If you search for "R7800 random reboots" there are many ... seems consensus is that older firmware are more stable (to the point where advice is either just buy the router and never flash it).
My Router never got to call home, I flashed it with 18.06 the moment I got it and kept updating it, then a long time after made the jump to 19.07.02 with the larger partition, and it was rock stable (>90 days uptime, and under lots of different loads, never one glitch). So let's hope 
I'm on the official 19.07.7 build, and it also can't last more than a couple days without rebooting. I'm seeding a lot of torrents with a lot of connections, but the load isn't particularly high (<0.1).
I wouldn't be surprised if the reboots we're discussing here were unrelated to NSS.
Don't underestimate the heat dissipation and power requirements (above the limits of mini-PCIe) of 802.11ax cards and consider the need for a third card to support 6 GHz in the near future. At this point it's better and considerably cheaper (vs. 200+250+250 USD for three 802.11ax cards, plus somewhere between 8-12 pigtails and antennas, which easily add another 100+ USD) to outsource the AP functionality to a dedicated device.
That's true. The cards aren't too expensive these days but you could also make things modular too like this:
https://www.amazon.com/dp/B08DFKWB9L/ref=cm_sw_r_cp_apa_glc_fabc_RY5M8B9W9GY4JJEFT3NS
You currently can't configure 80+80 through webif, haven't looked into it. But adding support should be possible.
1 Like
Cli wise what's the config - am not a GUI guy
should be 80+80
https://openwrt.org/docs/guide-user/network/wifi/basic
I don't see that listed as a width here ? I assume it takes the bottom half and top half of choice and makes 160 aggregated ?
Your DD-WRT builds were legendary on stability. The last one still running great. Nice to have your wisdom now on OpenWrt. Only if your builds were leaner to get only the basics functions for router and customize with needed packages from your repo.
3 Likes
Going to remove a couple of features for the next upload, as I don't use them anymore and it is pretty easy to install them anyways.
1 Like
@KONG @ACwifidude @Ansuel Is this how to set 80+80 ? (/etc/config/wireless)
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11a'
option path 'soc/1b500000.pci/pci0000:00/0000:00:00.0/0000:01:00.0'
option country 'US'
option cell_density '0'
option channel 'auto'
option htmode 'VHT80+80'
Should i choose channel 100 as well ? (It's legal where I am... does AUTO work with 80+80 ? )
I also run a large peer to peer mesh - since I re-enabled it on this build, I am dropping LAN packets now like mad. Any ideas guys ? Is there a known issue w WG on these builds? 21.xx ?
pinging google.com and lots of drops...
Reply from 142.250.64.68: bytes=32 time=2ms TTL=120
Reply from 142.250.64.68: bytes=32 time=2ms TTL=120
Reply from 142.250.64.68: bytes=32 time=2ms TTL=120
Request timed out.
Request timed out.
Request timed out.
Reply from 142.250.64.68: bytes=32 time=2ms TTL=120
Reply from 142.250.64.68: bytes=32 time=2ms TTL=120
Reply from 142.250.64.68: bytes=32 time=2ms TTL=120
Reply from 142.250.64.68: bytes=32 time=1ms TTL=120
Seems to be the LAN not the WAN dropping this, but the wan does jump up randomly ?
64 bytes from 172.217.165.132: seq=112 ttl=121 time=1.625 ms
64 bytes from 172.217.165.132: seq=113 ttl=121 time=1.874 ms
64 bytes from 172.217.165.132: seq=114 ttl=121 time=1.746 ms
64 bytes from 172.217.165.132: seq=115 ttl=121 time=1.810 ms
64 bytes from 172.217.165.132: seq=116 ttl=121 time=1.634 ms
64 bytes from 172.217.165.132: seq=117 ttl=121 time=1.811 ms
64 bytes from 172.217.165.132: seq=118 ttl=121 time=1.808 ms
64 bytes from 172.217.165.132: seq=119 ttl=121 time=1.779 ms
64 bytes from 172.217.165.132: seq=120 ttl=121 time=2456.509 ms
64 bytes from 172.217.165.132: seq=121 ttl=121 time=1456.293 ms
64 bytes from 172.217.165.132: seq=122 ttl=121 time=456.097 ms
64 bytes from 172.217.165.132: seq=123 ttl=121 time=1.625 ms
64 bytes from 172.217.165.132: seq=124 ttl=121 time=1.761 ms
64 bytes from 172.217.165.132: seq=125 ttl=121 time=1.732 ms
same ping... odd....
When it happens, CLI hangs even briefly to type etc,
Kernel log shows me this...
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.390408] [<c031e81c>] (__warn) from [<c031e888>] (warn_slowpath_fmt+0x50/0x90)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.397277] [<c031e888>] (warn_slowpath_fmt) from [<bf5f0254>] (nf_rtcache_forward4+0x16c/0x1cc [nf_conntrack_rtcache])
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.404831] [<bf5f0254>] (nf_rtcache_forward4 [nf_conntrack_rtcache]) from [<c07eae7c>] (nf_hook_slow+0x48/0xdc)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.415411] [<c07eae7c>] (nf_hook_slow) from [<c08eb97c>] (br_nf_forward_ip+0x31c/0x418)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.425825] [<c08eb97c>] (br_nf_forward_ip) from [<c07eae7c>] (nf_hook_slow+0x48/0xdc)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.433900] [<c07eae7c>] (nf_hook_slow) from [<c08d37dc>] (__br_forward+0xa0/0x12c)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.441623] [<c08d37dc>] (__br_forward) from [<c08d38a4>] (deliver_clone+0x3c/0x64)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.449175] [<c08d38a4>] (deliver_clone) from [<c08d594c>] (br_handle_frame_finish+0x374/0x48c)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.456815] [<c08d594c>] (br_handle_frame_finish) from [<c08eb254>] (br_nf_hook_thresh+0xdc/0xf0)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.465496] [<c08eb254>] (br_nf_hook_thresh) from [<c08ebbb0>] (br_nf_pre_routing_finish+0x138/0x344)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.474523] [<c08ebbb0>] (br_nf_pre_routing_finish) from [<c08ec218>] (br_nf_pre_routing+0x45c/0x47c)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.483726] [<c08ec218>] (br_nf_pre_routing) from [<c08d5be4>] (br_handle_frame+0x180/0x3d0)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.492928] [<c08d5be4>] (br_handle_frame) from [<c07896e4>] (__netif_receive_skb_core+0x240/0xb90)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.501434] [<c07896e4>] (__netif_receive_skb_core) from [<c078a05c>] (__netif_receive_skb_one_core+0x28/0x60)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.510202] [<c078a05c>] (__netif_receive_skb_one_core) from [<c078a290>] (process_backlog+0xa0/0x160)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.520269] [<c078a290>] (process_backlog) from [<c078b5b0>] (__napi_poll+0x34/0x120)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.529557] [<c078b5b0>] (__napi_poll) from [<c078b854>] (net_rx_action+0x108/0x2a0)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.537457] [<c078b854>] (net_rx_action) from [<c0302298>] (__do_softirq+0x130/0x2d4)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.545269] [<c0302298>] (__do_softirq) from [<c0322c04>] (irq_exit+0xbc/0xe0)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.552993] [<c0322c04>] (irq_exit) from [<c036f620>] (__handle_domain_irq+0x6c/0xd0)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.560116] [<c036f620>] (__handle_domain_irq) from [<c05dc29c>] (gic_handle_irq+0x5c/0xb8)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.568012] [<c05dc29c>] (gic_handle_irq) from [<c0301a8c>] (__irq_svc+0x6c/0x90)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.576168] Exception stack(0xc0c01ee0 to 0xc0c01f28)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.583813] 1ee0: 00000000 0000003e 1ce4f000 dd98fa80 dd7e3000 00000000 dd98ee30 0000003e
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.588854] 1f00: 0000003e 00000000 ac22f0c0 ac225c00 00000015 c0c01f30 c072d980 c072d984
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.597005] 1f20: 80000013 ffffffff
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.605160] [<c0301a8c>] (__irq_svc) from [<c072d984>] (cpuidle_enter_state+0x94/0x498)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.608464] [<c072d984>] (cpuidle_enter_state) from [<c072ddcc>] (cpuidle_enter+0x30/0x4c)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.616450] [<c072ddcc>] (cpuidle_enter) from [<c034acdc>] (do_idle+0x1d8/0x240)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.624781] [<c034acdc>] (do_idle) from [<c034afec>] (cpu_startup_entry+0x1c/0x20)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.632337] [<c034afec>] (cpu_startup_entry) from [<c0b00e5c>] (start_kernel+0x4dc/0x4ec)
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.639771] ---[ end trace 158c52072bd5a3eb ]---
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.650007] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 0, skipped old beacon
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.652667] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 1, skipped old beacon
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.659749] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 0, skipped old beacon
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.666985] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 1, skipped old beacon
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.674337] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 0, skipped old beacon
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.681615] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 1, skipped old beacon
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.688930] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 0, skipped old beacon
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.696171] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 1, skipped old beacon
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.703515] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 0, skipped old beacon
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.710793] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 1, skipped old beacon
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.718041] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 0, skipped old beacon
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.725384] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 1, skipped old beacon
Wed Apr 7 02:34:27 2021 kern.warn kernel: [ 270.732666] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 0, skipped old beacon
Well that looks like the good old 'non-ct' ath10k firmware problem. This is why I use ct firmware.
1 Like
I am thinking perhaps that the setting in SQM for ethernet needs to be in place as this is what i have of 44 if i remember. How do i do this? in LUCI it exists but i know that isn't compatible with what you have. How would i set this via CLI ? This is wired not wireless by the way
root@OpenWrt:~# opkg list-installed | grep -i ath
ath10k-board-qca9984 - 20201118-3
ath10k-firmware-qca9984-ct - 2020-11-08-1
kmod-ath - 5.4.108+5.10.16-1-1
kmod-ath10k-ct - 5.4.108+2021-01-11-9fe1df7d-2
This is Wired as noted. Super odd but it's not reliable now i enabled WG heavily. its really flaky. My desktop loses internet connection even every now and then.
I also cant get 80+80 going for the life of me lol .... no clue in /etc/config/wireless which option should say 80+80 and is it VHT80+80