Openwrt 19.07.2 qca9980 non-ct howto & how to get 1 GBit/s

Dear openwrt community,

Two wifi topics where I'm looking for your help / experience :slight_smile:

  1. On my Archers c2600 (dumb AP's) I've realised some hang-ups / freezes of the wifi or even the whole AP (no GUI access anymore).

thanks to the topic on r7800 (qca9984)


I realised it may be worth to try the non-ct version and see if stability goes up.

However for the r7800 (qca9984) it's not the same firmware and therefore I'm looking for help how to replace the ct-version with the non-ct version via command line ?

  1. On my APU2e4 (also dumb AP) I have 2 x Compex WLE900VX (both qca9980).
    I set each Compex on 5 GHz only (distinct SSID's),
  • first Compex on LAN (lan port 1) (channel 100, 80 MHz)
  • second Compex (channel 52, 80 MHz) on VLAN (lan port 2)
    I expected to get 1 GBit (I have 1 GBit internet, typ. 933 MBit) cumulated, but I get only 550ish (the same speed as when I run each Compex alone). Why ?
    (my topology is Router (19.07.2) - switch - switch - AP2 (19.07.2), whereas router and ap2 have lan on port 1 and vlan on port 2, the switches are connected via lacp)
    Is this expected behaviour or can I do some setting to get nearly 1 GBit/s ?

Many thanks ! and

cheers blinton

Can you post the output of this command please (this has to be run from the CLI) on the Archer C2600:

opkg list-installed | grep ath10k

About your C2600:

opkg update
opkg install wget ath10k-firmware-qca99x0 kmod-ath10k
opkg remove ath10k-firmware-qca99x0-ct kmod-ath10k-ct
cd /lib/firmware/ath10k/QCA99X0/hw2.0/
mv firmware-5.bin firmware-5.bin.bk
wget -O firmware-5.bin https://github.com/kvalo/ath10k-firmware/raw/master/QCA99X0/hw2.0/firmware-5.bin_10.4.1.00030-1 --no-check-certificate

EDIT: I've changed the order of install/remove... If the install part doesn't work, don't do the remove part and stop right there.

No signs of the board.bin nor the board-2.bin files anywhere on KValo's repository for this firmware thought... Maybe you will have to get those from the latest OpenWrt 18 version.

You're most likely hitting 100% utilization on one of the four cores. You can try using irqbalance + tweaking the cpu frequency management values to squeeze more performance out of it.

Regarding crashing: My C2600 has been crashing every 10 to 100 hours regularly since version 17.01. I never managed to find out a cause, but I've noticed if there is high WiFi traffic it tends to crash early and often. With no WiFi traffic, it might last a week or two. No difference between CT/Non CT ath10k firmware.

1 Like

Thanks a lot for your help.

I've tried the non-ct version (and verified the right one is installed).
Unfortunately the wifi speed was lousy.

So I installed the ct-htt version and turned on 802.11r and had to turn off 802.11w (else roaming wouldn't work correctly, behaves exactly like here https://github.com/openwrt/mt76/issues/278 )
-> let's see how long it will be stable, I'll give an update on that

Also installed irqbalance, but cat /proc/interrupts is telling me it's actually still on one cpu.
The reason may be that I'm using the two Archer c2600 as dumb AP's with two VLANs, whereas both VLANs are on the same cpu (else it didn't work for whatever reason).
I could easily see whether irqbalance is doing something by comparing with my main router, which is a quad-core i5-3470 running openwrt and irqbalance as well, where you can see it's nicely distributed over 4 cpu cores.
-> Is there a way I can force irqbalance to work properly on the c2600's ?
cat /proc/interrupts

CPU0       CPU1       
 16:     450770     181462     GIC-0  18 Edge      gp_timer
 18:         33          0     GIC-0  51 Edge      qcom_rpm_ack
 19:          0          0     GIC-0  53 Edge      qcom_rpm_err
 20:          0          0     GIC-0  54 Edge      qcom_rpm_wakeup
 26:          0          0     GIC-0 210 Edge      tsens_interrupt
 27:    1489421          0     GIC-0  67 Edge      qcom-pcie-msi
 28:    2005067          0     GIC-0  89 Edge      qcom-pcie-msi
 29:          0          0     GIC-0 202 Edge      adm_dma
 31:     960957          0     GIC-0 258 Level     eth1
 32:          0          0     GIC-0 130 Level     bam_dma
 33:          0          0     GIC-0 128 Level     bam_dma
 34:          0          0   PCI-MSI   0 Edge      aerdrv
 35:    1489421          0   PCI-MSI   1 Edge      ath10k_pci
 67:          0          0   PCI-MSI   0 Edge      aerdrv
 68:    2005067          0   PCI-MSI   1 Edge      ath10k_pci
100:          8          0     GIC-0 184 Level     msm_serial0
101:     263318          0     GIC-0 187 Level     1a280000.spi
102:          2          0   msmgpio  49 Edge      keys
103:          2          0   msmgpio  64 Edge      keys
104:          2          0   msmgpio  65 Edge      keys
105:          2          0   msmgpio  16 Edge      keys
106:          0          0     GIC-0 142 Level     xhci-hcd:usb1
107:          0          0     GIC-0 237 Level     xhci-hcd:usb3
IPI0:          0          0  CPU wakeup interrupts
IPI1:          0          0  Timer broadcast interrupts
IPI2:      22965     193393  Rescheduling interrupts
IPI3:         56     993529  Function call interrupts
IPI4:          0          0  CPU stop interrupts
IPI5:     245873     203476  IRQ work interrupts
IPI6:          0          0  completion interrupts
Err:          0

whereas for i5-3470 it give

           CPU0       CPU1       CPU2       CPU3       
  0:         12          0          0          0   IO-APIC   2-edge      timer
  1:          5          0          0          0   IO-APIC   1-edge      i8042
  8:          1          0          0          0   IO-APIC   8-edge      rtc0
  9:          0          0          4          0   IO-APIC   9-fasteoi   acpi
 12:          1          1          2          1   IO-APIC  12-edge      i8042
 16:         24          0          0          6   IO-APIC  16-fasteoi   ehci_hcd:usb1
 23:         26          3          0          5   IO-APIC  23-fasteoi   ehci_hcd:usb2
 24:          8          6          4          6   PCI-MSI 32768-edge      i915
 25:        338         89         58         70   PCI-MSI 512000-edge      ahci[0000:00:1f.2]
 26:          0          0          0          0   PCI-MSI 327680-edge      xhci_hcd
 27:          2          2          6          7   PCI-MSI 524288-edge      eth0
 28:    8406617    3478069    2717981    2429853   PCI-MSI 524289-edge      eth0-TxRx-0
 29:    6761750    3574095    2333545    2712452   PCI-MSI 524290-edge      eth0-TxRx-1
 30:    6703977    2829182    4294729    4434517   PCI-MSI 524291-edge      eth0-TxRx-2
 31:    4088976    1091994    1625409     998005   PCI-MSI 524292-edge      eth0-TxRx-3
 32:          1          0          0          0   PCI-MSI 1572864-edge      eth1
 33:   11232463    9334978    7603132    4465689   PCI-MSI 1572865-edge      eth1-TxRx-0
 34:    9649742    5109275    9934728    4388764   PCI-MSI 1572866-edge      eth1-TxRx-1
 35:   13283828   12518289    8529260    4736710   PCI-MSI 1572867-edge      eth1-TxRx-2
 36:    3538200     943714    1267188     959313   PCI-MSI 1572868-edge      eth1-TxRx-3
 37:          1          0          0          0   PCI-MSI 2097152-edge      eth2
 38:   20425927    7691291   11478264   17225065   PCI-MSI 2097153-edge      eth2-TxRx-0
 39:   14321004    6697321    6029455   11234075   PCI-MSI 2097154-edge      eth2-TxRx-1
 40:   15643856   11264090    6524162    9302937   PCI-MSI 2097155-edge      eth2-TxRx-2
 41:   10396303    3447866    3358708    3469946   PCI-MSI 2097156-edge      eth2-TxRx-3
NMI:          0          0          0          0   Non-maskable interrupts
LOC:   77773403   77948871   77869516   77588322   Local timer interrupts
SPU:          0          0          0          0   Spurious interrupts
PMI:          0          0          0          0   Performance monitoring interrupts
IWI:          0          0          0          0   IRQ work interrupts
RTR:          0          0          0          0   APIC ICR read retries
RES:      49746      63972      67008      71736   Rescheduling interrupts
CAL:       1161   34014725   33130419   39001649   Function call interrupts
TLB:          0          0          0          0   TLB shootdowns
TRM:          0          0          0          0   Thermal event interrupts
THR:          0          0          0          0   Threshold APIC interrupts
DFR:          0          0          0          0   Deferred Error APIC interrupts
MCE:          0          0          0          0   Machine check exceptions
MCP:       2552       2552       2552       2552   Machine check polls
HYP:          0          0          0          0   Hypervisor callback interrupts
ERR:          0
MIS:          0
PIN:          0          0          0          0   Posted-interrupt notification event
NPI:          0          0          0          0   Nested posted-interrupt event
PIW:          0          0          0          0   Posted-interrupt wakeup event

Many thanks ! and

cheers blinton

I have two C2600 and they too crash on heavy WiFi. Sorry to hear you have the same problem but happy to know I'm not the only one. Misery loves company.

I've managed to make them last longer by bringing WiFi down and back up every few days with a cron, but that causes some issues to clients and the C2600s eventually fail at usually the worst of times.

What is more annoying is that the router fails but the switch still works. The device becomes a dumb switch and clients suddenly start receiving IPs from an upstream router.

I've been dreaming of building a custom image with crash logging but don't have a build machine set up nor really the time to do it.

Any suggestions on what might be worth trying? Are the non-CT drivers worth trying out?

Strange I have 2x c2600's (both v1.1) and never had a problem with irqbalance and it using both cores.
I simply have it setup like this for 19.07.x

cat /etc/config/irqbalance

config irqbalance 'irqbalance'
        option enabled '1'

cat /proc/interrupts

           CPU0       CPU1
 16:    1645118    2311267     GIC-0  18 Edge      gp_timer
 18:         33          0     GIC-0  51 Edge      qcom_rpm_ack
 19:          0          0     GIC-0  53 Edge      qcom_rpm_err
 20:          0          0     GIC-0  54 Edge      qcom_rpm_wakeup
 26:          0          0     GIC-0 210 Edge      tsens_interrupt
 27:   11421904    5427133     GIC-0  67 Edge      qcom-pcie-msi
 28:    4238296    3960502     GIC-0  89 Edge      qcom-pcie-msi
 29:          0          0     GIC-0 202 Edge      adm_dma
 30:    2652619    6468922     GIC-0 255 Level     eth0
 31:        351        193     GIC-0 258 Level     eth1
 32:          0          0     GIC-0 130 Level     bam_dma
 33:          0          0     GIC-0 128 Level     bam_dma
 34:          0          0   PCI-MSI   0 Edge      aerdrv
 35:   11421904    5427133   PCI-MSI   1 Edge      ath10k_pci
 67:          0          0   PCI-MSI   0 Edge      aerdrv
 68:    4238296    3960502   PCI-MSI   1 Edge      ath10k_pci
100:          8          0     GIC-0 184 Level     msm_serial0
101:     720429      10854     GIC-0 187 Level     1a280000.spi
102:          2          0   msmgpio  49 Edge      keys
103:          2          0   msmgpio  64 Edge      keys
104:          2          0   msmgpio  65 Edge      keys
105:          2          0   msmgpio  16 Edge      keys
106:      62645      31213     GIC-0 142 Level     xhci-hcd:usb1
107:         20          0     GIC-0 237 Level     xhci-hcd:usb3
IPI0:          0          0  CPU wakeup interrupts
IPI1:          0          0  Timer broadcast interrupts
IPI2:   13416121     435385  Rescheduling interrupts
IPI3:        944    5566672  Function call interrupts
IPI4:          0          0  CPU stop interrupts
IPI5:    1408335     956287  IRQ work interrupts
IPI6:          0          0  completion interrupts
Err:          0

I really don't have any issues with WiFi (both 2.4 & 5GHz) using the -ct drivers bundled with 19.07.2 release. i.e. no WiFi freezes and unresponsive router (in my case).

1 Like

The non-ct (or more concretely -ct drivers) are installed by default as part of th in e openwrt image. I switched to the -ct-htt drivers (enabled 802.11r) which worked 7d on 2 x c2600 (v1.1) nicely. I haven‘t tested longer yet.
Thanks otnert, I forgot to enable irqbalance (what a stupid error I made... shame on me).
I‘ll update in a few weeks on stability, at least for my config with 2 x c2600 as dumb AP‘s with 2 VLANs and running 802.11r.

Do you have experience with my problem with 2 separate wifi miniPCIe cards which seem to be unable to work in parallel, ie 2x 500MBit/s on two distinct VLANs ?

cheers blinton

Sorry mate that one's out of my league.

Now I got some kernel log entries on both AP's.

First AP (3d):

[34777.160084] ath10k_pci 0000:01:00.0: No VIF found for vdev 1
[34777.160138] ath10k_pci 0000:01:00.0: received addba event for invalid vdev_id: 1
[34777.166638] ath10k_pci 0000:01:00.0: No VIF found for vdev 1
[34777.172344] ath10k_pci 0000:01:00.0: received addba event for invalid vdev_id: 1
[34777.177864] ath10k_pci 0000:01:00.0: No VIF found for vdev 1
[34777.185340] ath10k_pci 0000:01:00.0: received addba event for invalid vdev_id: 1
[34777.191002] ath10k_pci 0000:01:00.0: No VIF found for vdev 1
[34777.198248] ath10k_pci 0000:01:00.0: received addba event for invalid vdev_id: 1
[34777.204530] ath10k_pci 0000:01:00.0: No VIF found for vdev 1
[34777.211339] ath10k_pci 0000:01:00.0: no vif for vdev_id 1 found
[34777.227308] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
[34777.227360] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1

blabla

[34777.510143] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[34777.510363] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[34778.884407] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
[34778.884438] ath10k_pci 0000:01:00.0: msdu-desc: 2500  skid: 32
[34778.960376] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
[34778.961148] ath10k_pci 0000:01:00.0: wmi print 'free: 34244 iram: 33204 sram: 6508'
[34779.296113] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4

Second AP (wifi still working, 3d):

[149914.389595] ath10k_pci 0000:01:00.0: No VIF found for vdev 1
[149914.389643] ath10k_pci 0000:01:00.0: no vif for vdev_id 1 found
[149914.433124] ath10k_pci 0000:01:00.0: No VIF found for vdev 1
[149914.433152] ath10k_pci 0000:01:00.0: received addba event for invalid vdev_id: 1
[149914.439142] ath10k_pci 0000:01:00.0: No VIF found for vdev 1
[149914.445403] ath10k_pci 0000:01:00.0: received addba event for invalid vdev_id: 1
[149914.451124] ath10k_pci 0000:01:00.0: No VIF found for vdev 1
[149914.458504] ath10k_pci 0000:01:00.0: received addba event for invalid vdev_id: 1
[149914.465809] ath10k_pci 0000:01:00.0: No VIF found for vdev 1
[149914.471776] ath10k_pci 0000:01:00.0: received addba event for invalid vdev_id: 1
[149914.478757] ath10k_pci 0000:01:00.0: No VIF found for vdev 1
[149914.484965] ath10k_pci 0000:01:00.0: received addba event for invalid vdev_id: 1
[149914.490702] ath10k_pci 0000:01:00.0: No VIF found for vdev 1
[149914.498100] ath10k_pci 0000:01:00.0: received addba event for invalid vdev_id: 1
[149914.503893] ath10k_pci 0000:01:00.0: No VIF found for vdev 1
[149914.511348] ath10k_pci 0000:01:00.0: received addba event for invalid vdev_id: 1
[149914.517169] ath10k_pci 0000:01:00.0: No VIF found for vdev 1
[149914.524543] ath10k_pci 0000:01:00.0: no vif for vdev_id 1 found
[149914.533025] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
[149914.536344] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1

blabla

[149914.843318] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[149914.843393] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[149914.849104] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[149914.864205] ath10k_pci 0000:01:00.0: firmware crashed! (guid blabla)
[149914.864251] ath10k_pci 0000:01:00.0: qca99x0 hw2.0 target 0x01000000 chip_id 0x003b01ff sub 168c:0002
[149914.872161] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[149914.883958] ath10k_pci 0000:01:00.0: firmware ver 10.4b-ct-9980-fH-012-17ba9833 api 5 features mfp,peer-flow-ctrl,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,htt-mgt-CT,set-special-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 fcda7b5d
[149914.897494] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id 1:1 crc32 08fa09f2
[149914.919536] ath10k_pci 0000:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 32 raw 0 hwcrypto 1
[149914.938936] ath10k_pci 0000:01:00.0: failed to get memcpy hi address for firmware address 4: -16
[149914.938968] ath10k_pci 0000:01:00.0: failed to read firmware dump area: -16
[149914.946865] ath10k_pci 0000:01:00.0: in crash-regs-harder
[149915.729788] ath10k_pci 0000:01:00.0: in crash-regs-harder, firmware did not provide indicator: 0xdeadbeef
[149915.729822] ath10k_pci 0000:01:00.0: Copy Engine register dump:
[149915.738401] ath10k_pci 0000:01:00.0: [00]: 0x0004a000 3735928559 3735928559 3735928559 3735928559
[149915.744586] ath10k_pci 0000:01:00.0: [01]: 0x0004a400 3735928559 3735928559 3735928559 3735928559
[149915.753332] ath10k_pci 0000:01:00.0: [02]: 0x0004a800 3735928559 3735928559 3735928559 3735928559
[149915.762266] ath10k_pci 0000:01:00.0: [03]: 0x0004ac00 3735928559 3735928559 3735928559 3735928559
[149915.771232] ath10k_pci 0000:01:00.0: [04]: 0x0004b000 3735928559 3735928559 3735928559 3735928559
[149915.780091] ath10k_pci 0000:01:00.0: [05]: 0x0004b400 3735928559 3735928559 3735928559 3735928559
[149915.789101] ath10k_pci 0000:01:00.0: [06]: 0x0004b800 3735928559 3735928559 3735928559 3735928559
[149915.798036] ath10k_pci 0000:01:00.0: [07]: 0x0004bc00 3735928559 3735928559 3735928559 3735928559
[149915.806971] ath10k_pci 0000:01:00.0: [08]: 0x0004c000 3735928559 3735928559 3735928559 3735928559
[149915.815938] ath10k_pci 0000:01:00.0: [09]: 0x0004c400 3735928559 3735928559 3735928559 3735928559
[149915.824871] ath10k_pci 0000:01:00.0: [10]: 0x0004c800 3735928559 3735928559 3735928559 3735928559
[149915.833806] ath10k_pci 0000:01:00.0: [11]: 0x0004cc00 3735928559 3735928559 3735928559 3735928559
[149915.842744] ath10k_pci 0000:01:00.0: failed to get memcpy hi address for firmware address 8: -28
[149915.851671] ath10k_pci 0000:01:00.0: failed to dump debug log area: -28
[149915.860610] ath10k_pci 0000:01:00.0: failed to get memcpy hi address for firmware address 72: -28
[149915.867329] ath10k_pci 0000:01:00.0: failed to get memcpy hi address for firmware address 72: -28
[149915.876167] ath10k_pci 0000:01:00.0: failed to get memcpy hi address for firmware address 76: -28
[149915.885102] ath10k_pci 0000:01:00.0: failed to get memcpy hi address for firmware address 76: -28
[149915.894040] ath10k_pci 0000:01:00.0: failed to read firmware RAM BSS memory from 4275264 (23656 B): -28
[149915.903003] ath10k_pci 0000:01:00.0: failed to read firmware ROM BSS memory from 4197376 (12008 B): -28
[149915.912986] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 1, skipped old beacon
[149915.922110] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[149915.929401] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 1, skipped old beacon
[149915.936841] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[149915.944213] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 1, skipped old beacon
[149915.951588] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[149915.958949] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 1, skipped old beacon
[149915.966398] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[149915.970208] ath10k_pci 0000:01:00.0: cannot restart a device that hasn't been started
[149917.267171] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
[149917.267202] ath10k_pci 0000:01:00.0: msdu-desc: 2500  skid: 32
[149917.343104] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
[149917.343861] ath10k_pci 0000:01:00.0: wmi print 'free: 34244 iram: 33204 sram: 6508'
[149917.678495] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4

Second one looks somehow more risky. Any idea what this means, given that those AP's have 512MB RAM each and I didn't see that without irqbalance (maybe coincidence) after 6 d uptime?

Should I use non-DFS channels only ? acc. to this Netgear R7800 wifi internet connectivity drops

cheers blinton

Interesting. My crashy C2600 is a v1.0 model. Is yours v1.1 by any chance? Other than that, I know the CT firmware had specific issues with certain device/wifi chipset types as wifi clients in the past but those were mostly solved by the devs behind it.

Either my C2600 is defective, or one of my wireless clients is causing a bug to rear it's ugly head. Today the entire router hard locked and had to be manually power cycled.

Mines are v1.1. I didn't have to power cycle them, they still work, somehow recovered themselves, strange.
I found something about configuration files in https://github.com/greearb/ath10k-ct/issues/93
and especially here http://www.candelatech.com/ath10k-10.4.php#config

However, I may turn off irqbalance, at least in my case I didn't have any "internal" crashes in 7d, nor any swba errors. I'll give it try in the next few days and report if got better.

Yes c2600 v1.1
mmm I spoke too soon... my c2600 rebooted overnight! :face_with_raised_eyebrow: I have no idea why?

OK!...
on my 2nd c2600v1.1, I've uninstalled the '-ct' drivers and installed the 'non -ct' drivers, see how this goes?

opkg update
opkg remove  ath10k-firmware-qca99x0-ct kmod-ath10k-ct
opkg install ath10k-firmware-qca99x0    kmod-ath10k

Dear all,

Just checked both of my AP's Archer c2600 after more than 7 days uptime.
I didn't change anything in the configuration, i.e. still the same (using ct-htt and irqbalance).
No errors (in contrast to my previous post).
Fingers crossed, I'll update after another week, if still no (kernel) errors.

cheers blinton

2 Likes

Dear all,

Day 8 :frowning:

  • One of the AP's crashed, no WLAN, Luci web interface down. Had to power off/on.
  • The other AP still working, no (kernel) errors.
    It's interesting, because the AP which is still working is using both 2.4 GHz and 5 GHz with much more traffic than the one which crashed (and only 5 GHz, but more ethernet clients connected).
    Also interesting, the timing with errors was around the same as for my fist post, just somewhere after day 7.

cheers blinton.

1 Like

take a look at this threads title:Archer c7 v5 back to the original software

that is your answer