search

greearb / ath10k-ct

Stand-alone ath10k driver based on Candela Technologies Linux kernel.
111 stars 40 forks source link

Excessive latency on R7800 / OpenWrt with ath10k-ct-smallbuffers driver and ath10k-ct beta firmware #149

Open Fail-Safe opened 4 years ago

Fail-Safe commented 4 years ago

Description of the problem (how to configure, how to reproduce, how often it happens). Multiple 5Ghz connected Apple devices exhibit an issue with excessive latency and packet loss. The issue is most visible when said devices are "idle" in the sense that they are not involved in a consistent data flow (such as an audio/video stream or active download).

Tested & Affected Devices (within my possession): 2019 iMac 2019 MacBook Pro 16" 2019 MacBook Pro 15" 2019 MacBook Pro 13"

Example Scenario:

--- 192.168.9.83 ping statistics --- 60 packets transmitted, 50 packets received, 16% packet loss round-trip min/avg/max = 1.776/1210.483/4577.430 ms


**Software (OS, Firmware version, kernel, driver, etc)**

OpenWrt SNAPSHOT, r14101-5d8fded26a

root@OpenWrt:~# cat /etc/os-release NAME="OpenWrt" VERSION="SNAPSHOT" ID="openwrt" ID_LIKE="lede openwrt" PRETTY_NAME="OpenWrt SNAPSHOT" VERSION_ID="snapshot" HOME_URL="https://openwrt.org/" BUG_URL="https://bugs.openwrt.org/" SUPPORT_URL="https://forum.openwrt.org/" BUILD_ID="r14101-5d8fded26a" OPENWRT_BOARD="ipq806x/generic" OPENWRT_ARCH="arm_cortex-a15_neon-vfpv4" OPENWRT_TAINTS="no-all busybox" OPENWRT_DEVICE_MANUFACTURER="OpenWrt" OPENWRT_DEVICE_MANUFACTURER_URL="https://openwrt.org/" OPENWRT_DEVICE_PRODUCT="Generic" OPENWRT_DEVICE_REVISION="v0" OPENWRT_RELEASE="OpenWrt SNAPSHOT r14101-5d8fded26a"

root@OpenWrt:~# uname -a Linux OpenWrt 5.4.52 #0 SMP Sun Aug 9 12:01:52 2020 armv7l GNU/Linux

root@OpenWrt:~# opkg list | grep kmod-ath10k kmod-ath10k-ct-smallbuffers - 5.4.52+2020-06-30-edfbf916-1


Firmware:
`firmware ver 10.4b-ct-9984-tH-13-795874169`

**Hardware (NIC chipset, platform, etc)**
* R7800 IPQ8065
* QCA9984

**Logs (dmesg, maybe supplicant and/or hostap)**

root@OpenWrt:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.4.52 (user@b16a8da35c64) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r13674-cbb66f9edb)) #0 SMP Sun Aug 9 12:01:52 2020 [ 0.000000] CPU: ARMv7 Processor [512f04d0] revision 0 (ARMv7), cr=10c5787d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.000000] OF: fdt: Machine model: Netgear Nighthawk X4S R7800 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] On node 0 totalpages: 122880 [ 0.000000] Normal zone: 1080 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 122880 pages, LIFO batch:31 [ 0.000000] percpu: Embedded 15 pages/cpu s30092 r8192 d23156 u61440 [ 0.000000] pcpu-alloc: s30092 r8192 d23156 u61440 alloc=15*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 121800 [ 0.000000] Kernel command line: [ 0.000000] Bootloader command line (ignored): console=ttyHSL1,115200n8 [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] Memory: 474844K/491520K available (5945K kernel code, 190K rwdata, 1512K rodata, 1024K init, 228K bss, 16676K reserved, 0K cma-reserved, 0K highmem) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] rcu: Hierarchical RCU implementation. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] random: get_random_bytes called from start_kernel+0x340/0x4e8 with crng_init=0 [ 0.000000] clocksource: dg_timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 305801671480 ns [ 0.000006] sched_clock: 32 bits at 6MHz, resolution 160ns, wraps every 343597383600ns [ 0.000022] Switching to timer-based delay loop, resolution 160ns [ 0.000228] Calibrating delay loop (skipped), value calculated using timer frequency.. 12.50 BogoMIPS (lpj=62500) [ 0.000248] pid_max: default: 32768 minimum: 301 [ 0.000449] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) [ 0.000468] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) [ 0.001530] CPU: Testing write buffer coherency: ok [ 0.002664] Setting up static identity map for 0x42300000 - 0x42300060 [ 0.002838] rcu: Hierarchical SRCU implementation. [ 0.003334] smp: Bringing up secondary CPUs ... [ 0.005240] smp: Brought up 1 node, 2 CPUs [ 0.005256] SMP: Total of 2 processors activated (25.00 BogoMIPS). [ 0.005266] CPU: All CPU(s) started in SVC mode. [ 0.015513] VFP support v0.3: implementor 51 architecture 64 part 4d variant 2 rev 0 [ 0.015674] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.015701] futex hash table entries: 512 (order: 3, 32768 bytes, linear) [ 0.015873] pinctrl core: initialized pinctrl subsystem [ 0.017037] NET: Registered protocol family 16 [ 0.017325] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.018662] cpuidle: using governor ladder [ 0.018730] cpuidle: using governor menu [ 0.049457] usbcore: registered new interface driver usbfs [ 0.049536] usbcore: registered new interface driver hub [ 0.049636] usbcore: registered new device driver usb [ 0.049696] pps_core: LinuxPPS API ver. 1 registered [ 0.049711] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti giometti@linux.it [ 0.049754] PTP clock support registered [ 0.051456] clocksource: Switched to clocksource dg_timer [ 0.052503] thermal_sys: Registered thermal governor 'step_wise' [ 0.054881] NET: Registered protocol family 2 [ 0.055457] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear) [ 0.055501] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear) [ 0.055545] TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear) [ 0.055601] TCP: Hash tables configured (established 4096 bind 4096) [ 0.055708] UDP hash table entries: 256 (order: 1, 8192 bytes, linear) [ 0.055740] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear) [ 0.055978] NET: Registered protocol family 1 [ 0.056028] PCI: CLS 0 bytes, default 64 [ 0.057320] workingset: timestamp_bits=14 max_order=17 bucket_order=3 [ 0.063936] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.063954] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 0.104679] qcom-pcie 1b500000.pci: 1b500000.pci supply vdda not found, using dummy regulator [ 0.104826] qcom-pcie 1b500000.pci: 1b500000.pci supply vdda_phy not found, using dummy regulator [ 0.104939] qcom-pcie 1b500000.pci: 1b500000.pci supply vdda_refclk not found, using dummy regulator [ 0.105222] qcom-pcie 1b500000.pci: host bridge /soc/pci@1b500000 ranges: [ 0.105247] qcom-pcie 1b500000.pci: Parsing ranges property... [ 0.105293] qcom-pcie 1b500000.pci: IO 0x0fe00000..0x0fefffff -> 0x0fe00000 [ 0.105331] qcom-pcie 1b500000.pci: MEM 0x08000000..0x0fdfffff -> 0x08000000 [ 0.327159] qcom-pcie 1b500000.pci: Link up [ 0.327328] qcom-pcie 1b500000.pci: PCI host bridge to bus 0000:00 [ 0.327354] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.327374] pci_bus 0000:00: root bus resource [io 0x0000-0xfffff] (bus address [0xfe00000-0xfefffff]) [ 0.327391] pci_bus 0000:00: root bus resource [mem 0x08000000-0x0fdfffff] [ 0.327408] pci_bus 0000:00: scanning bus [ 0.327456] pci 0000:00:00.0: [17cb:0101] type 01 class 0xff0000 [ 0.327626] pci 0000:00:00.0: supports D1 [ 0.327640] pci 0000:00:00.0: PME# supported from D0 D1 D3hot [ 0.327661] pci 0000:00:00.0: PME# disabled [ 0.331636] pci_bus 0000:00: fixups for bus [ 0.331775] PCI: bus0: Fast back to back transfers disabled [ 0.331796] pci 0000:00:00.0: scanning [bus 01-ff] behind bridge, pass 0 [ 0.331941] pci_bus 0000:01: scanning bus [ 0.332121] pci 0000:01:00.0: [168c:0046] type 00 class 0x028000 [ 0.332478] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit] [ 0.333628] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold [ 0.333676] pci 0000:01:00.0: PME# disabled [ 0.337808] pci_bus 0000:01: fixups for bus [ 0.337880] PCI: bus1: Fast back to back transfers disabled [ 0.337897] pci_bus 0000:01: bus scan returning with max=01 [ 0.337915] pci 0000:00:00.0: scanning [bus 01-ff] behind bridge, pass 1 [ 0.337934] pci_bus 0000:00: bus scan returning with max=ff [ 0.337968] pci 0000:00:00.0: BAR 8: assigned [mem 0x08000000-0x081fffff] [ 0.337992] pci 0000:01:00.0: BAR 0: assigned [mem 0x08000000-0x081fffff 64bit] [ 0.338122] pci 0000:00:00.0: PCI bridge to [bus 01-ff] [ 0.338148] pci 0000:00:00.0: bridge window [mem 0x08000000-0x081fffff] [ 0.338367] pcieport 0000:00:00.0: assign IRQ: got 35 [ 0.338910] pcieport 0000:00:00.0: AER: enabled with IRQ 36 [ 0.339544] qcom-pcie 1b700000.pci: 1b700000.pci supply vdda not found, using dummy regulator [ 0.339672] qcom-pcie 1b700000.pci: 1b700000.pci supply vdda_phy not found, using dummy regulator [ 0.339804] qcom-pcie 1b700000.pci: 1b700000.pci supply vdda_refclk not found, using dummy regulator [ 0.340063] qcom-pcie 1b700000.pci: host bridge /soc/pci@1b700000 ranges: [ 0.340084] qcom-pcie 1b700000.pci: Parsing ranges property... [ 0.340128] qcom-pcie 1b700000.pci: IO 0x31e00000..0x31efffff -> 0x31e00000 [ 0.340162] qcom-pcie 1b700000.pci: MEM 0x2e000000..0x31dfffff -> 0x2e000000 [ 0.568862] qcom-pcie 1b700000.pci: Link up [ 0.569012] qcom-pcie 1b700000.pci: PCI host bridge to bus 0001:00 [ 0.569034] pci_bus 0001:00: root bus resource [bus 00-ff] [ 0.569050] pci_bus 0001:00: root bus resource [mem 0x2e000000-0x31dfffff] [ 0.569064] pci_bus 0001:00: scanning bus [ 0.569106] pci 0001:00:00.0: [17cb:0101] type 01 class 0xff0000 [ 0.569257] pci 0001:00:00.0: supports D1 [ 0.569271] pci 0001:00:00.0: PME# supported from D0 D1 D3hot [ 0.569289] pci 0001:00:00.0: PME# disabled [ 0.573301] pci_bus 0001:00: fixups for bus [ 0.573323] PCI: bus0: Fast back to back transfers disabled [ 0.573340] pci 0001:00:00.0: scanning [bus 01-ff] behind bridge, pass 0 [ 0.573485] pci_bus 0001:01: scanning bus [ 0.573676] pci 0001:01:00.0: [168c:0046] type 00 class 0x028000 [ 0.574054] pci 0001:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit] [ 0.575289] pci 0001:01:00.0: PME# supported from D0 D3hot D3cold [ 0.575337] pci 0001:01:00.0: PME# disabled [ 0.575592] pci 0001:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x1 link at 0001:00:00.0 (capable of 4.000 Gb/s with 5 GT/s x1 link) [ 0.579503] pci_bus 0001:01: fixups for bus [ 0.579579] PCI: bus1: Fast back to back transfers disabled [ 0.579595] pci_bus 0001:01: bus scan returning with max=01 [ 0.579611] pci 0001:00:00.0: scanning [bus 01-ff] behind bridge, pass 1 [ 0.579628] pci_bus 0001:00: bus scan returning with max=ff [ 0.579654] pci 0001:00:00.0: BAR 8: assigned [mem 0x2e000000-0x2e1fffff] [ 0.579676] pci 0001:01:00.0: BAR 0: assigned [mem 0x2e000000-0x2e1fffff 64bit] [ 0.579809] pci 0001:00:00.0: PCI bridge to [bus 01-ff] [ 0.579829] pci 0001:00:00.0: bridge window [mem 0x2e000000-0x2e1fffff] [ 0.580053] pcieport 0001:00:00.0: assign IRQ: got 37 [ 0.580668] pcieport 0001:00:00.0: AER: enabled with IRQ 38 [ 0.583316] L2 @ QSB rate. Forcing new rate. [ 0.583542] L2 @ 384000 KHz [ 0.583727] CPU0 @ 800000 KHz [ 0.583741] CPU1 @ QSB rate. Forcing new rate. [ 0.583870] CPU1 @ 384000 KHz [ 0.587526] gsbi 16300000.gsbi: GSBI port protocol: 6 crci: 0 [ 0.589756] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 0.590539] msm_serial 16340000.serial: msm_serial: detected port #0 [ 0.590590] msm_serial 16340000.serial: uartclk = 7372800 [ 0.590663] 16340000.serial: ttyMSM0 at MMIO 0x16340000 (irq = 39, base_baud = 460800) is a MSM [ 0.590697] msm_serial: console setup on port #0 [ 1.357033] printk: console [ttyMSM0] enabled [ 1.362109] msm_serial: driver initialized [ 1.371168] loop: module loaded [ 1.372854] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xa1 [ 1.373120] nand: Micron MT29F1G08ABBEAH4 [ 1.379715] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [ 1.383825] 8 fixed-partitions partitions found on MTD device qcom_nand.0 [ 1.391090] Creating 8 MTD partitions on "qcom_nand.0": [ 1.398049] 0x000000000000-0x000000c80000 : "qcadata" [ 1.408274] random: fast init done [ 1.424494] 0x000000c80000-0x000001180000 : "APPSBL" [ 1.433648] 0x000001180000-0x000001200000 : "APPSBLENV" [ 1.435373] 0x000001200000-0x000001340000 : "art" [ 1.440646] 0x000001340000-0x000001480000 : "artbak" [ 1.445577] 0x000001480000-0x000001880000 : "kernel" [ 1.454990] 0x000001880000-0x000007900000 : "ubi" [ 1.613314] 0x000007900000-0x000008000000 : "reserve" [ 1.627231] libphy: ipq8064_mdio_bus: probed [ 1.642349] switch0: Atheros AR8337 rev. 2 switch registered on 37000000.mdio-mii [ 2.488155] ar8327: qca,phy-rgmii-en is not specified [ 2.488573] libphy: Fixed MDIO Bus: probed [ 2.492993] ipq806x-gmac-dwmac 37200000.ethernet: IRQ eth_wake_irq not found [ 2.496186] ipq806x-gmac-dwmac 37200000.ethernet: IRQ eth_lpi not found [ 2.504218] ipq806x-gmac-dwmac 37200000.ethernet: PTP uses main clock [ 2.510377] ipq806x-gmac-dwmac 37200000.ethernet: User ID: 0x10, Synopsys ID: 0x37 [ 2.516415] ipq806x-gmac-dwmac 37200000.ethernet: DWMAC1000 [ 2.523864] ipq806x-gmac-dwmac 37200000.ethernet: DMA HW capability register supported [ 2.529607] ipq806x-gmac-dwmac 37200000.ethernet: RX Checksum Offload Engine supported [ 2.537419] ipq806x-gmac-dwmac 37200000.ethernet: COE Type 2 [ 2.545289] ipq806x-gmac-dwmac 37200000.ethernet: TX Checksum insertion supported [ 2.551044] ipq806x-gmac-dwmac 37200000.ethernet: Wake-Up On Lan supported [ 2.558505] ipq806x-gmac-dwmac 37200000.ethernet: Enhanced/Alternate descriptors [ 2.565281] ipq806x-gmac-dwmac 37200000.ethernet: Enabled extended descriptors [ 2.572813] ipq806x-gmac-dwmac 37200000.ethernet: Ring mode enabled [ 2.579775] ipq806x-gmac-dwmac 37200000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 2.586944] ipq806x-gmac-dwmac 37400000.ethernet: IRQ eth_wake_irq not found [ 2.594728] ipq806x-gmac-dwmac 37400000.ethernet: IRQ eth_lpi not found [ 2.601908] ipq806x-gmac-dwmac 37400000.ethernet: PTP uses main clock [ 2.608323] ipq806x-gmac-dwmac 37400000.ethernet: User ID: 0x10, Synopsys ID: 0x37 [ 2.614703] ipq806x-gmac-dwmac 37400000.ethernet: DWMAC1000 [ 2.622110] ipq806x-gmac-dwmac 37400000.ethernet: DMA HW capability register supported [ 2.627868] ipq806x-gmac-dwmac 37400000.ethernet: RX Checksum Offload Engine supported [ 2.635666] ipq806x-gmac-dwmac 37400000.ethernet: COE Type 2 [ 2.643569] ipq806x-gmac-dwmac 37400000.ethernet: TX Checksum insertion supported [ 2.649308] ipq806x-gmac-dwmac 37400000.ethernet: Wake-Up On Lan supported [ 2.656753] ipq806x-gmac-dwmac 37400000.ethernet: Enhanced/Alternate descriptors [ 2.663532] ipq806x-gmac-dwmac 37400000.ethernet: Enabled extended descriptors [ 2.671009] ipq806x-gmac-dwmac 37400000.ethernet: Ring mode enabled [ 2.678121] ipq806x-gmac-dwmac 37400000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 2.685285] i2c /dev entries driver [ 2.695252] cpuidle: enable-method property 'qcom,kpss-acc-v1' found operations [ 2.696215] cpuidle: enable-method property 'qcom,kpss-acc-v1' found operations [ 2.704038] sdhci: Secure Digital Host Controller Interface driver [ 2.710674] sdhci: Copyright(c) Pierre Ossman [ 2.717014] sdhci-pltfm: SDHCI platform and OF driver helper [ 2.723713] NET: Registered protocol family 10 [ 2.728496] Segment Routing with IPv6 [ 2.731422] NET: Registered protocol family 17 [ 2.735465] 8021q: 802.1Q VLAN Support v1.8 [ 2.739440] Registering SWP/SWPB emulation handler [ 2.768449] qcom_rpm 108000.rpm: RPM firmware 3.0.16777364 [ 2.782363] s1a: supplied by regulator-dummy [ 2.782469] s1a: Bringing 0uV into 1050000-1050000uV [ 2.785998] s1b: supplied by regulator-dummy [ 2.790716] s1b: Bringing 0uV into 1050000-1050000uV [ 2.795250] s2a: supplied by regulator-dummy [ 2.799930] s2a: Bringing 0uV into 775000-775000uV [ 2.804444] s2b: supplied by regulator-dummy [ 2.808780] s2b: Bringing 0uV into 775000-775000uV [ 2.814948] Speed bin: 0 [ 2.817723] PVS bin: 4 [ 2.828767] UBI: auto-attach mtd6 [ 2.828788] ubi0: attaching mtd6 [ 2.892455] random: crng init done [ 3.527232] ubi0: scanning is finished [ 3.536748] ubi0: attached mtd6 (name "ubi", size 96 MiB) [ 3.536769] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes [ 3.541116] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 [ 3.547968] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096 [ 3.554800] ubi0: good PEBs: 772, bad PEBs: 0, corrupted PEBs: 0 [ 3.561513] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128 [ 3.567828] ubi0: max/mean erase counter: 11/5, WL threshold: 4096, image sequence number: 1587282572 [ 3.574862] ubi0: available PEBs: 0, total reserved PEBs: 772, PEBs reserved for bad PEB handling: 20 [ 3.584212] ubi0: background thread "ubi_bgt0d" started, PID 67 [ 3.584846] block ubiblock0_0: created from ubi0:0(rootfs) [ 3.599014] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem [ 3.604628] hctosys: unable to open rtc device (rtc0) [ 3.616625] VFS: Mounted root (squashfs filesystem) readonly on device 254:0. [ 3.617806] Freeing unused kernel memory: 1024K [ 3.652058] Run /sbin/init as init process [ 4.230053] init: Console is alive [ 4.230255] init: - watchdog - [ 5.209903] kmodloader: loading kernel modules from /etc/modules-boot.d/ [ 5.287063] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 5.289755] SCSI subsystem initialized [ 5.302106] libata version 3.00 loaded. [ 5.304967] ahci 29000000.sata: 29000000.sata supply ahci not found, using dummy regulator [ 5.305092] ahci 29000000.sata: 29000000.sata supply phy not found, using dummy regulator [ 5.312468] ahci 29000000.sata: 29000000.sata supply target not found, using dummy regulator [ 5.322016] ahci 29000000.sata: forcing port_map 0x0 -> 0x1 [ 5.328908] ahci 29000000.sata: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl platform mode [ 5.334238] ahci 29000000.sata: flags: ncq sntf pm led clo only pmp pio slum part ccc apst [ 5.343492] scsi host0: ahci [ 5.351203] ata1: SATA max UDMA/133 mmio [mem 0x29000000-0x2900017f] port 0x100 irq 26 [ 5.684503] ata1: SATA link down (SStatus 0 SControl 300) [ 5.689971] ehci-fsl: Freescale EHCI Host controller driver [ 5.691672] ehci-platform: EHCI generic platform driver [ 5.704167] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 5.704657] ohci-platform: OHCI generic platform driver [ 5.711364] dwc3-qcom 110f8800.usb3: IRQ hs_phy_irq not found [ 5.714435] dwc3-qcom 110f8800.usb3: IRQ dp_hs_phy_irq not found [ 5.720256] dwc3-qcom 110f8800.usb3: IRQ dm_hs_phy_irq not found [ 5.726415] dwc3-qcom 110f8800.usb3: IRQ ss_phy_irq not found [ 5.734068] dwc3-qcom 100f8800.usb3: IRQ hs_phy_irq not found [ 5.737967] dwc3-qcom 100f8800.usb3: IRQ dp_hs_phy_irq not found [ 5.743765] dwc3-qcom 100f8800.usb3: IRQ dm_hs_phy_irq not found [ 5.749770] dwc3-qcom 100f8800.usb3: IRQ ss_phy_irq not found [ 5.757102] dwc3 11000000.dwc3: Failed to get clk 'ref': -2 [ 5.814775] dwc3 10000000.dwc3: Failed to get clk 'ref': -2 [ 5.874648] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [ 5.874703] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1 [ 5.879218] xhci-hcd xhci-hcd.0.auto: hcc params 0x0228f065 hci version 0x100 quirks 0x0000000002010010 [ 5.886760] xhci-hcd xhci-hcd.0.auto: irq 43, io mem 0x11000000 [ 5.896964] hub 1-0:1.0: USB hub found [ 5.901977] hub 1-0:1.0: 1 port detected [ 5.905879] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [ 5.909768] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2 [ 5.915118] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed [ 5.922764] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 5.929532] hub 2-0:1.0: USB hub found [ 5.937535] hub 2-0:1.0: 1 port detected [ 5.941267] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller [ 5.945149] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3 [ 5.950512] xhci-hcd xhci-hcd.1.auto: hcc params 0x0228f065 hci version 0x100 quirks 0x0000000002010010 [ 5.958033] xhci-hcd xhci-hcd.1.auto: irq 44, io mem 0x10000000 [ 5.969274] hub 3-0:1.0: USB hub found [ 5.973310] hub 3-0:1.0: 1 port detected [ 5.977213] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller [ 5.981109] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 4 [ 5.986471] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed [ 5.994106] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. [ 6.000877] hub 4-0:1.0: USB hub found [ 6.008900] hub 4-0:1.0: 1 port detected [ 6.015820] usbcore: registered new interface driver usb-storage [ 6.016513] kmodloader: done loading kernel modules from /etc/modules-boot.d/ [ 6.028040] init: - preinit - [ 7.588238] dwmac1000: Master AXI performs any burst length [ 7.588276] ipq806x-gmac-dwmac 37400000.ethernet eth1: No Safety Features support found [ 7.592725] ipq806x-gmac-dwmac 37400000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported [ 7.600730] ipq806x-gmac-dwmac 37400000.ethernet eth1: registered PTP clock [ 7.609699] ipq806x-gmac-dwmac 37400000.ethernet eth1: configuring for fixed/sgmii link mode [ 7.617512] ipq806x-gmac-dwmac 37400000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off [ 7.625687] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 11.812811] mount_root: loading kmods from internal overlay [ 11.842331] kmodloader: loading kernel modules from //etc/modules-boot.d/ [ 11.843698] kmodloader: done loading kernel modules from //etc/modules-boot.d/ [ 11.874852] blk_update_request: I/O error, dev mtdblock0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0 [ 11.911947] blk_update_request: I/O error, dev mtdblock0, sector 8 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 [ 11.912846] blk_update_request: I/O error, dev mtdblock0, sector 16 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0 [ 11.922600] blk_update_request: I/O error, dev mtdblock0, sector 24 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 11.933169] blk_update_request: I/O error, dev mtdblock0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 11.943023] Buffer I/O error on dev mtdblock0, logical block 0, async page read [ 12.061928] blk_update_request: I/O error, dev mtdblock0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 12.061981] Buffer I/O error on dev mtdblock0, logical block 0, async page read [ 12.073081] blk_update_request: I/O error, dev mtdblock1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0 [ 12.079985] blk_update_request: I/O error, dev mtdblock1, sector 8 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 [ 12.091107] blk_update_request: I/O error, dev mtdblock1, sector 16 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0 [ 12.101864] blk_update_request: I/O error, dev mtdblock1, sector 24 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 12.112276] Buffer I/O error on dev mtdblock1, logical block 0, async page read [ 12.134608] Buffer I/O error on dev mtdblock1, logical block 0, async page read [ 12.301470] UBIFS (ubi0:1): Mounting in unauthenticated mode [ 12.301691] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 157 [ 12.350307] UBIFS (ubi0:1): recovery needed [ 12.466075] UBIFS (ubi0:1): recovery completed [ 12.466166] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data" [ 12.469404] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes [ 12.477386] UBIFS (ubi0:1): FS size: 88756224 bytes (84 MiB, 699 LEBs), journal size 4444160 bytes (4 MiB, 35 LEBs) [ 12.487260] UBIFS (ubi0:1): reserved for root: 4192175 bytes (4093 KiB) [ 12.497501] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID BD3E252E-6412-448F-B8FD-7E15706CE7A8, small LPT model [ 12.512261] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab [ 12.524560] block: extroot: not configured [ 12.524713] UBIFS (ubi0:1): un-mount UBI device 0 [ 12.527617] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" stops [ 12.535467] UBIFS (ubi0:1): Mounting in unauthenticated mode [ 12.538501] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 158 [ 12.643124] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data" [ 12.643148] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes [ 12.649928] UBIFS (ubi0:1): FS size: 88756224 bytes (84 MiB, 699 LEBs), journal size 4444160 bytes (4 MiB, 35 LEBs) [ 12.659896] UBIFS (ubi0:1): reserved for root: 4192175 bytes (4093 KiB) [ 12.670133] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID BD3E252E-6412-448F-B8FD-7E15706CE7A8, small LPT model [ 12.681938] mount_root: loading kmods from internal overlay [ 12.707235] kmodloader: loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/ [ 12.709608] kmodloader: done loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/ [ 12.735828] Buffer I/O error on dev mtdblock0, logical block 0, async page read [ 12.739352] Buffer I/O error on dev mtdblock0, logical block 0, async page read [ 12.747481] Buffer I/O error on dev mtdblock1, logical block 0, async page read [ 12.752351] Buffer I/O error on dev mtdblock1, logical block 0, async page read [ 12.936973] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab [ 12.940527] block: extroot: not configured [ 12.945676] mount_root: switching to ubifs overlay [ 12.960236] overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. [ 12.963618] urandom-seed: Seeding with /etc/urandom.seed [ 13.025718] ipq806x-gmac-dwmac 37400000.ethernet eth1: Link is Down [ 13.068857] procd: - early - [ 13.068976] procd: - watchdog - [ 13.634961] procd: - watchdog - [ 13.635589] procd: - ubus - [ 13.698492] procd: - init - [ 14.066414] urngd: v1.0.2 started. [ 14.073947] kmodloader: loading kernel modules from /etc/modules.d/ [ 14.083342] cryptodev: driver 1.10 loaded. [ 14.085456] Loading modules backported from Linux version v5.8-rc2-0-g48778464bb7d [ 14.086323] Backport generated by backports.git v5.8-rc2-1-0-g7a69429b [ 14.101184] xt_time: kernel timezone is -0000 [ 14.226528] ath10k_pci 0000:01:00.0: assign IRQ: got 35 [ 14.226548] ath10k 5.4 driver, optimized for CT firmware, probing pci device: 0x46. [ 14.226604] ath10k_mac_create, priv_size: 868 hw: b182c424 hw->priv: 2f91bb91 [ 14.233449] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142) [ 14.240351] ath10k_pci 0000:01:00.0: enabling bus mastering [ 14.240839] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [ 14.758037] ath10k_pci 0000:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe [ 14.758068] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0 [ 14.768352] ath10k_pci 0000:01:00.0: firmware ver 10.4b-ct-9984-tH-13-795874169 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,no-bmiss-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 7d16c2a5 [ 17.093362] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [ 22.808432] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536 [ 22.809532] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96 [ 22.813935] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32 [ 22.895596] 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' [ 22.896331] ath10k_pci 0000:01:00.0: wmi print 'free: 132768 iram: 9624 sram: 46068' [ 23.206272] 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 [ 23.296254] ath: EEPROM regdomain sanitized [ 23.296271] ath: EEPROM regdomain: 0x64 [ 23.296284] ath: EEPROM indicates we should expect a direct regpair map [ 23.296310] ath: Country alpha2 being used: 00 [ 23.296322] ath: Regpair used: 0x64 [ 23.301878] ath10k_pci 0001:01:00.0: assign IRQ: got 37 [ 23.301921] ath10k 5.4 driver, optimized for CT firmware, probing pci device: 0x46. [ 23.302059] ath10k_mac_create, priv_size: 868 hw: 3a331d42 hw->priv: 6f25e3c7 [ 23.309295] ath10k_pci 0001:01:00.0: enabling device (0140 -> 0142) [ 23.315858] ath10k_pci 0001:01:00.0: enabling bus mastering [ 23.316546] ath10k_pci 0001:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [ 23.886673] ath10k_pci 0001:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe [ 23.886716] ath10k_pci 0001:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0 [ 23.897906] ath10k_pci 0001:01:00.0: firmware ver 10.4b-ct-9984-tH-13-795874169 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,no-bmiss-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 7d16c2a5 [ 26.251608] ath10k_pci 0001:01:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [ 32.027651] ath10k_pci 0001:01:00.0: unsupported HTC service id: 1536 [ 32.028201] ath10k_pci 0001:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96 [ 32.033163] ath10k_pci 0001:01:00.0: msdu-desc: 2500 skid: 32 [ 32.117937] ath10k_pci 0001:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0' [ 32.118687] ath10k_pci 0001:01:00.0: wmi print 'free: 132768 iram: 9624 sram: 46068' [ 32.483756] ath10k_pci 0001:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 32 raw 0 hwcrypto 1 [ 32.566281] ath: EEPROM regdomain sanitized [ 32.566297] ath: EEPROM regdomain: 0x64 [ 32.566310] ath: EEPROM indicates we should expect a direct regpair map [ 32.566334] ath: Country alpha2 being used: 00 [ 32.566344] ath: Regpair used: 0x64 [ 32.574745] kmodloader: done loading kernel modules from /etc/modules.d/ [ 34.393010] print_req_error: 14 callbacks suppressed [ 34.393018] blk_update_request: I/O error, dev mtdblock0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0 [ 34.397955] blk_update_request: I/O error, dev mtdblock0, sector 8 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 [ 34.408562] blk_update_request: I/O error, dev mtdblock0, sector 16 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0 [ 34.419369] blk_update_request: I/O error, dev mtdblock0, sector 24 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 34.429918] blk_update_request: I/O error, dev mtdblock0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 34.439767] Buffer I/O error on dev mtdblock0, logical block 0, async page read [ 34.454352] blk_update_request: I/O error, dev mtdblock0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 34.457293] Buffer I/O error on dev mtdblock0, logical block 0, async page read [ 34.469035] blk_update_request: I/O error, dev mtdblock1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0 [ 34.476012] blk_update_request: I/O error, dev mtdblock1, sector 8 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 [ 34.486751] blk_update_request: I/O error, dev mtdblock1, sector 16 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0 [ 34.497444] blk_update_request: I/O error, dev mtdblock1, sector 24 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 34.508230] Buffer I/O error on dev mtdblock1, logical block 0, async page read [ 34.523729] Buffer I/O error on dev mtdblock1, logical block 0, async page read [ 35.075679] dwmac1000: Master AXI performs any burst length [ 35.075709] ipq806x-gmac-dwmac 37200000.ethernet eth0: No Safety Features support found [ 35.080056] ipq806x-gmac-dwmac 37200000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported [ 35.088219] ipq806x-gmac-dwmac 37200000.ethernet eth0: registered PTP clock [ 35.097162] ipq806x-gmac-dwmac 37200000.ethernet eth0: configuring for fixed/rgmii link mode [ 35.104579] ipq806x-gmac-dwmac 37200000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off [ 35.135763] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 35.137849] br-GUEST: port 1(eth0.9) entered blocking state [ 35.140848] br-GUEST: port 1(eth0.9) entered disabled state [ 35.146640] device eth0.9 entered promiscuous mode [ 35.151998] device eth0 entered promiscuous mode [ 35.171805] br-GUEST: port 1(eth0.9) entered blocking state [ 35.171836] br-GUEST: port 1(eth0.9) entered forwarding state [ 35.204716] br-IOT: port 1(eth0.99) entered blocking state [ 35.204741] br-IOT: port 1(eth0.99) entered disabled state [ 35.209213] device eth0.99 entered promiscuous mode [ 35.216207] br-IOT: port 1(eth0.99) entered blocking state [ 35.219336] br-IOT: port 1(eth0.99) entered forwarding state [ 35.250964] dwmac1000: Master AXI performs any burst length [ 35.250999] ipq806x-gmac-dwmac 37400000.ethernet eth1: No Safety Features support found [ 35.255494] ipq806x-gmac-dwmac 37400000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported [ 35.263590] ipq806x-gmac-dwmac 37400000.ethernet eth1: registered PTP clock [ 35.272463] ipq806x-gmac-dwmac 37400000.ethernet eth1: configuring for fixed/sgmii link mode [ 35.279360] ipq806x-gmac-dwmac 37400000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off [ 35.289390] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 35.299842] br-lan: port 1(eth1.1) entered blocking state [ 35.302845] br-lan: port 1(eth1.1) entered disabled state [ 35.309620] device eth1.1 entered promiscuous mode [ 35.313802] device eth1 entered promiscuous mode [ 35.320060] br-lan: port 1(eth1.1) entered blocking state [ 35.323235] br-lan: port 1(eth1.1) entered forwarding state [ 36.017976] ath: EEPROM regdomain: 0x8348 [ 36.018005] ath: EEPROM indicates we should expect a country code [ 36.020968] ath: doing EEPROM country->regdmn map search [ 36.027175] ath: country maps to regdmn code: 0x3a [ 36.032505] ath: Country alpha2 being used: US [ 36.037023] ath: Regpair used: 0x3a [ 36.041453] ath: regdomain 0x8348 dynamically updated by user [ 36.044965] ath: EEPROM regdomain: 0x8348 [ 36.050737] ath: EEPROM indicates we should expect a country code [ 36.054814] ath: doing EEPROM country->regdmn map search [ 36.060814] ath: country maps to regdmn code: 0x3a [ 36.066272] ath: Country alpha2 being used: US [ 36.070789] ath: Regpair used: 0x3a [ 36.075303] ath: regdomain 0x8348 dynamically updated by user [ 36.171890] IPv6: ADDRCONF(NETDEV_CHANGE): br-GUEST: link becomes ready [ 43.277097] ath10k_pci 0001:01:00.0: unsupported HTC service id: 1536 [ 43.277334] ath10k_pci 0001:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96 [ 43.282588] ath10k_pci 0001:01:00.0: msdu-desc: 2500 skid: 32 [ 43.367364] ath10k_pci 0001:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0' [ 43.368105] ath10k_pci 0001:01:00.0: wmi print 'free: 132768 iram: 9624 sram: 46068' [ 43.920264] ath10k_pci 0001:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4 [ 43.922402] br-lan: port 2(wlan1) entered blocking state [ 43.930188] br-lan: port 2(wlan1) entered disabled state [ 43.935868] device wlan1 entered promiscuous mode [ 44.260648] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready [ 44.260765] br-lan: port 2(wlan1) entered blocking state [ 44.266113] br-lan: port 2(wlan1) entered forwarding state [ 44.276252] ath10k_pci 0001:01:00.0: NOTE: Firmware DBGLOG output disabled in debug_mask: 0x10000000 [ 50.095713] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536 [ 50.095806] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96 [ 50.101156] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32 [ 50.182839] 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' [ 50.183563] ath10k_pci 0000:01:00.0: wmi print 'free: 132768 iram: 9624 sram: 46068' [ 50.562350] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4 [ 50.564407] br-lan: port 3(wlan0) entered blocking state [ 50.572349] br-lan: port 3(wlan0) entered disabled state [ 50.577905] device wlan0 entered promiscuous mode [ 50.585280] br-GUEST: port 2(wlan1-1) entered blocking state [ 50.587643] br-GUEST: port 2(wlan1-1) entered disabled state [ 50.593650] device wlan1-1 entered promiscuous mode [ 50.605820] br-GUEST: port 2(wlan1-1) entered blocking state [ 50.605847] br-GUEST: port 2(wlan1-1) entered forwarding state [ 50.643426] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1-1: link becomes ready [ 50.645308] br-IOT: port 2(wlan1-2) entered blocking state [ 50.648956] br-IOT: port 2(wlan1-2) entered disabled state [ 50.654575] device wlan1-2 entered promiscuous mode [ 50.662838] br-IOT: port 2(wlan1-2) entered blocking state [ 50.664557] br-IOT: port 2(wlan1-2) entered forwarding state [ 50.695457] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1-2: link becomes ready [ 51.197509] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 51.197638] br-lan: port 3(wlan0) entered blocking state [ 51.202995] br-lan: port 3(wlan0) entered forwarding state [ 51.210054] br-GUEST: port 3(wlan0-1) entered blocking state [ 51.213756] br-GUEST: port 3(wlan0-1) entered disabled state [ 51.219687] device wlan0-1 entered promiscuous mode [ 51.237783] br-GUEST: port 3(wlan0-1) entered blocking state [ 51.237808] br-GUEST: port 3(wlan0-1) entered forwarding state [ 51.282510] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready [ 51.284426] br-IOT: port 3(wlan0-2) entered blocking state [ 51.287929] br-IOT: port 3(wlan0-2) entered disabled state [ 51.293661] device wlan0-2 entered promiscuous mode [ 51.307239] br-IOT: port 3(wlan0-2) entered blocking state [ 51.307265] br-IOT: port 3(wlan0-2) entered forwarding state [ 51.353564] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-2: link becomes ready [ 53.705310] ath10k_pci 0001:01:00.0: Invalid peer id 0 or peer stats buffer, peer: 7968fa07 sta: 00000000

Fail-Safe commented 4 years ago

I initially believed this to be related to https://github.com/greearb/ath10k-ct/issues/139#issue-636233839. I posted additional information here: https://github.com/greearb/ath10k-ct/issues/139#issuecomment-672118572

With firmware ver 10.4b-ct-9984-tH-13-795874169, latency from the R7800 to one of the affected devices is improved in the cases where the MacBooks/iMac are engaged in a consistent data stream, whether audio/video, download, or simply a constant ping to another device on the network (from the affected device).

I loaded the 1158 firmware referenced by @graysky2 here https://github.com/greearb/ath10k-ct/issues/139#issuecomment-660458870 and found a marked improvement. Unfortunately at the present moment I do not have data captured to show this improvement, but will update this comment with that data ASAP.

Fail-Safe commented 4 years ago 
root@OpenWrt:~# dmesg | grep firmware
[    2.768381] qcom_rpm 108000.rpm: RPM firmware 3.0.16777364
[   14.093346] ath10k 5.4 driver, optimized for CT firmware, probing pci device: 0x46.
[   14.604608] ath10k_pci 0000:01:00.0: firmware ver 10.4b-ct-9984-tH-13-795874169 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,no-bmiss-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 7d16c2a5
[   23.105076] ath10k 5.4 driver, optimized for CT firmware, probing pci device: 0x46.
[   23.682505] ath10k_pci 0001:01:00.0: firmware ver 10.4b-ct-9984-tH-13-795874169 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,no-bmiss-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 7d16c2a5
root@OpenWrt:~# ping 192.168.9.83 -c60
PING 192.168.9.83 (192.168.9.83): 56 data bytes
64 bytes from 192.168.9.83: seq=3 ttl=64 time=3495.858 ms
64 bytes from 192.168.9.83: seq=4 ttl=64 time=2482.313 ms
64 bytes from 192.168.9.83: seq=5 ttl=64 time=1481.175 ms
64 bytes from 192.168.9.83: seq=6 ttl=64 time=476.783 ms
64 bytes from 192.168.9.83: seq=7 ttl=64 time=1074.036 ms
64 bytes from 192.168.9.83: seq=8 ttl=64 time=65.571 ms
64 bytes from 192.168.9.83: seq=9 ttl=64 time=605.466 ms
64 bytes from 192.168.9.83: seq=10 ttl=64 time=3017.754 ms
64 bytes from 192.168.9.83: seq=11 ttl=64 time=2015.649 ms
64 bytes from 192.168.9.83: seq=12 ttl=64 time=1008.733 ms
64 bytes from 192.168.9.83: seq=13 ttl=64 time=8.278 ms
64 bytes from 192.168.9.83: seq=14 ttl=64 time=254.260 ms
64 bytes from 192.168.9.83: seq=15 ttl=64 time=251.606 ms
64 bytes from 192.168.9.83: seq=16 ttl=64 time=507.151 ms
64 bytes from 192.168.9.83: seq=17 ttl=64 time=918.400 ms
64 bytes from 192.168.9.83: seq=18 ttl=64 time=3.019 ms
64 bytes from 192.168.9.83: seq=19 ttl=64 time=2.164 ms
64 bytes from 192.168.9.83: seq=20 ttl=64 time=3.814 ms
64 bytes from 192.168.9.83: seq=21 ttl=64 time=1263.659 ms
64 bytes from 192.168.9.83: seq=22 ttl=64 time=261.962 ms
64 bytes from 192.168.9.83: seq=23 ttl=64 time=2.991 ms
64 bytes from 192.168.9.83: seq=27 ttl=64 time=2265.876 ms
64 bytes from 192.168.9.83: seq=28 ttl=64 time=1265.576 ms
64 bytes from 192.168.9.83: seq=29 ttl=64 time=258.511 ms
64 bytes from 192.168.9.83: seq=33 ttl=64 time=2859.909 ms
64 bytes from 192.168.9.83: seq=34 ttl=64 time=1859.704 ms
64 bytes from 192.168.9.83: seq=35 ttl=64 time=848.043 ms
64 bytes from 192.168.9.83: seq=36 ttl=64 time=5.654 ms
64 bytes from 192.168.9.83: seq=37 ttl=64 time=2.373 ms
64 bytes from 192.168.9.83: seq=38 ttl=64 time=92.876 ms
64 bytes from 192.168.9.83: seq=39 ttl=64 time=1562.413 ms
64 bytes from 192.168.9.83: seq=40 ttl=64 time=561.023 ms
64 bytes from 192.168.9.83: seq=41 ttl=64 time=4.121 ms
64 bytes from 192.168.9.83: seq=42 ttl=64 time=834.278 ms
64 bytes from 192.168.9.83: seq=43 ttl=64 time=3.875 ms
64 bytes from 192.168.9.83: seq=44 ttl=64 time=2392.530 ms
64 bytes from 192.168.9.83: seq=45 ttl=64 time=1391.948 ms
64 bytes from 192.168.9.83: seq=46 ttl=64 time=389.467 ms
64 bytes from 192.168.9.83: seq=50 ttl=64 time=2315.519 ms
64 bytes from 192.168.9.83: seq=51 ttl=64 time=1312.532 ms
64 bytes from 192.168.9.83: seq=52 ttl=64 time=312.304 ms
64 bytes from 192.168.9.83: seq=53 ttl=64 time=3.531 ms
64 bytes from 192.168.9.83: seq=54 ttl=64 time=3.155 ms

--- 192.168.9.83 ping statistics ---
60 packets transmitted, 43 packets received, 28% packet loss
round-trip min/avg/max = 2.164/924.322/3495.858 ms
root@OpenWrt:~# ping 192.168.9.83 -c60
PING 192.168.9.83 (192.168.9.83): 56 data bytes
64 bytes from 192.168.9.83: seq=0 ttl=64 time=3281.805 ms
64 bytes from 192.168.9.83: seq=1 ttl=64 time=2281.926 ms
64 bytes from 192.168.9.83: seq=2 ttl=64 time=1280.053 ms
64 bytes from 192.168.9.83: seq=3 ttl=64 time=278.165 ms
64 bytes from 192.168.9.83: seq=4 ttl=64 time=2711.885 ms
64 bytes from 192.168.9.83: seq=5 ttl=64 time=1710.061 ms
64 bytes from 192.168.9.83: seq=6 ttl=64 time=708.203 ms
64 bytes from 192.168.9.83: seq=7 ttl=64 time=1.722 ms
64 bytes from 192.168.9.83: seq=9 ttl=64 time=4103.227 ms
64 bytes from 192.168.9.83: seq=10 ttl=64 time=3102.027 ms
64 bytes from 192.168.9.83: seq=11 ttl=64 time=2101.213 ms
64 bytes from 192.168.9.83: seq=12 ttl=64 time=1099.587 ms
64 bytes from 192.168.9.83: seq=13 ttl=64 time=98.136 ms
64 bytes from 192.168.9.83: seq=17 ttl=64 time=3863.746 ms
64 bytes from 192.168.9.83: seq=18 ttl=64 time=2863.071 ms
64 bytes from 192.168.9.83: seq=19 ttl=64 time=1863.290 ms
64 bytes from 192.168.9.83: seq=20 ttl=64 time=862.679 ms
64 bytes from 192.168.9.83: seq=21 ttl=64 time=3.778 ms
64 bytes from 192.168.9.83: seq=22 ttl=64 time=3121.166 ms
64 bytes from 192.168.9.83: seq=23 ttl=64 time=2120.753 ms
64 bytes from 192.168.9.83: seq=24 ttl=64 time=1120.574 ms
64 bytes from 192.168.9.83: seq=25 ttl=64 time=118.341 ms
64 bytes from 192.168.9.83: seq=26 ttl=64 time=1.775 ms
64 bytes from 192.168.9.83: seq=27 ttl=64 time=3.092 ms
64 bytes from 192.168.9.83: seq=28 ttl=64 time=3.069 ms
64 bytes from 192.168.9.83: seq=29 ttl=64 time=1.657 ms
64 bytes from 192.168.9.83: seq=30 ttl=64 time=1383.533 ms
64 bytes from 192.168.9.83: seq=31 ttl=64 time=383.057 ms
64 bytes from 192.168.9.83: seq=32 ttl=64 time=1.626 ms
64 bytes from 192.168.9.83: seq=33 ttl=64 time=573.255 ms
64 bytes from 192.168.9.83: seq=34 ttl=64 time=1449.175 ms
64 bytes from 192.168.9.83: seq=35 ttl=64 time=446.299 ms
64 bytes from 192.168.9.83: seq=36 ttl=64 time=3.173 ms
64 bytes from 192.168.9.83: seq=37 ttl=64 time=3.864 ms
64 bytes from 192.168.9.83: seq=38 ttl=64 time=681.381 ms
64 bytes from 192.168.9.83: seq=39 ttl=64 time=4.531 ms
64 bytes from 192.168.9.83: seq=43 ttl=64 time=4439.561 ms
64 bytes from 192.168.9.83: seq=44 ttl=64 time=3438.621 ms
64 bytes from 192.168.9.83: seq=45 ttl=64 time=2438.185 ms
64 bytes from 192.168.9.83: seq=46 ttl=64 time=1437.258 ms
64 bytes from 192.168.9.83: seq=47 ttl=64 time=425.822 ms
64 bytes from 192.168.9.83: seq=51 ttl=64 time=3559.122 ms
64 bytes from 192.168.9.83: seq=52 ttl=64 time=2553.035 ms
64 bytes from 192.168.9.83: seq=53 ttl=64 time=1551.441 ms
64 bytes from 192.168.9.83: seq=54 ttl=64 time=540.198 ms
64 bytes from 192.168.9.83: seq=55 ttl=64 time=3.755 ms
64 bytes from 192.168.9.83: seq=56 ttl=64 time=1590.468 ms
64 bytes from 192.168.9.83: seq=57 ttl=64 time=587.417 ms
64 bytes from 192.168.9.83: seq=58 ttl=64 time=475.636 ms
64 bytes from 192.168.9.83: seq=59 ttl=64 time=1802.190 ms

--- 192.168.9.83 ping statistics ---
60 packets transmitted, 50 packets received, 16% packet loss
round-trip min/avg/max = 1.626/1369.552/4439.561 ms
Fail-Safe commented 4 years ago

This is a difficult issue to fully scope because it affects multiple devices, but not consistently. Further, it seems to get better for some time after a reboot (or rmmod/modprobe), but the affected devices may differ even after the issue presents itself again.

graysky2 commented 4 years ago

@Fail-Safe - When you are experiencing the long pings with some packet loss, you mentioned the laptop is "idle."

  1. Do you experience any lag when you google something in a browser on an affected device? The lag to which I refer is the time between the time when you hit "Enter" on the keyboard, and when the search results comes up?
  2. When are you streaming video on the laptop, do the ping times tighten up?

Also, post your /etc/config/wireless here (be sure to redact your actual passwords to protect the privacy of your networks).

Fail-Safe commented 4 years ago

@graysky2

  1. Do you experience any lag when you google something in a browser on an affected device? The lag to which I refer is the time between the time when you hit "Enter" on the keyboard, and when the search results comes up?

I do occasionally, yes. I notice this on my iPhones, especially as distance increases from my R7800 (another complicating factor, I know). But I do see this on my MacBooks occasionally as well.

  1. When are you streaming video on the laptop, do the ping times tighten up?

Thanks for bringing this up--I actually meant to elaborate more on this in my OP. The answer is yes, absolutely. When this issue is presenting itself with one of my devices, once I get the wireless radio on the device busy with active data flow the ping times actually drop to a consistent <10ms on average. Typically 3-5ms.

Also, post your /etc/config/wireless here (be sure to redact your actual passwords to protect the privacy of your networks).

root@OpenWrt:~# cat /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 htmode 'VHT80'
    option legacy_rates '0'
    option channel '153'
    option txpower '30'
    option country 'US'
    option distance '450'
    option rts '980'

config wifi-iface 'default_radio0'
    option device 'radio0'
    option network 'lan'
    option mode 'ap'
    option key '...'
    option ieee80211w '1'
    option ssid 'LAN'
    option encryption 'psk2+ccmp'

config wifi-device 'radio1'
    option type 'mac80211'
    option hwmode '11g'
    option path 'soc/1b700000.pci/pci0001:00/0001:00:00.0/0001:01:00.0'
    option htmode 'HT20'
    option legacy_rates '0'
    option channel '11'
    option txpower '20'
    option country 'US'
    option distance '450'
    option rts '980'

config wifi-iface 'default_radio1'
    option device 'radio1'
    option network 'lan'
    option mode 'ap'
    option key '...'
    option ieee80211w '1'
    option macfilter 'allow'
    option encryption 'psk2+ccmp'
    list maclist '...'
    list maclist '...'
    list maclist '...'
    list maclist '...'
    list maclist '...'
    option ssid 'LAN'

config wifi-iface 'wifinet2'
    option network 'GUEST'
    option device 'radio1'
    option mode 'ap'
    option ieee80211w '1'
    option key '...'
    option ssid 'GUEST'
    option encryption 'psk2+ccmp'

config wifi-iface 'wifinet3'
    option network 'IOT'
    option device 'radio1'
    option mode 'ap'
    option ieee80211w '1'
    option key '...'
    option ssid 'IOT'
    option encryption 'psk2+ccmp'

config wifi-iface 'wifinet4'
    option network 'GUEST'
    option ssid 'GUEST'
    option device 'radio0'
    option mode 'ap'
    option ieee80211w '1'
    option key '...'
    option encryption 'psk2+ccmp'

config wifi-iface 'wifinet5'
    option network 'IOT'
    option ssid 'IOT'
    option device 'radio0'
    option mode 'ap'
    option ieee80211w '1'
    option key '...'
    option encryption 'psk2+ccmp'
Fail-Safe commented 4 years ago

FWIW, I created a new snapshot build last night with the following three patches added: https://git.openwrt.org/?p=openwrt/staging/nbd.git;a=commit;h=3b26a8b2563a416338c71fc36c1cf8c313457d7c

Updated OS/firmware info:

root@OpenWrt:~# dmesg | grep firmware
[    2.779054] qcom_rpm 108000.rpm: RPM firmware 3.0.16777364
[   13.566261] ath10k 5.4 driver, optimized for CT firmware, probing pci device: 0x46.
[   14.059286] ath10k_pci 0000:01:00.0: firmware ver 10.4b-ct-9984-tH-13-795874169 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,no-bmiss-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 7d16c2a5
[   22.582070] ath10k 5.4 driver, optimized for CT firmware, probing pci device: 0x46.
[   23.168275] ath10k_pci 0001:01:00.0: firmware ver 10.4b-ct-9984-tH-13-795874169 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,no-bmiss-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 7d16c2a5

root@OpenWrt:~# cat /etc/os-release
NAME="OpenWrt"
VERSION="SNAPSHOT"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt SNAPSHOT"
VERSION_ID="snapshot"
HOME_URL="https://openwrt.org/"
BUG_URL="https://bugs.openwrt.org/"
SUPPORT_URL="https://forum.openwrt.org/"
BUILD_ID="r14154-2d9db93397"
OPENWRT_BOARD="ipq806x/generic"
OPENWRT_ARCH="arm_cortex-a15_neon-vfpv4"
OPENWRT_TAINTS="no-all busybox"
OPENWRT_DEVICE_MANUFACTURER="OpenWrt"
OPENWRT_DEVICE_MANUFACTURER_URL="https://openwrt.org/"
OPENWRT_DEVICE_PRODUCT="Generic"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="OpenWrt SNAPSHOT r14154-2d9db93397"

root@OpenWrt:~# opkg list | grep kmod-ath10k
kmod-ath10k-ct-smallbuffers - 5.4.52+2020-06-30-edfbf916-1

root@OpenWrt:~# uname -a
Linux OpenWrt 5.4.52 #0 SMP Thu Aug 13 00:12:12 2020 armv7l GNU/Linux

Even after running all night on this new build and then two reboots this morning (trying to trigger the issue), I am not able to reproduce this same issue at the moment. Not suggesting the patches are the fix, but I did want to make you aware of this change in my config since my OP. Will report back on what I am seeing as time goes by today.

Fail-Safe commented 4 years ago

Here is what I am seeing on this latest patched build at "idle" on my primary trouble device (you will recognize this IP from my OP).

Same scenario--pinging my primary trouble device at "idle" (MBP 15") from my R7800:

--- 192.168.9.83 ping statistics ---
60 packets transmitted, 60 packets received, 0% packet loss
round-trip min/avg/max = 1.507/53.457/115.308 ms

Second scenario, when I start a ping from my MBP 15" to its gateway (ping -i.2 192.168.9.5), then simultaneously ping this MBP from my R7800:

--- 192.168.9.83 ping statistics ---
60 packets transmitted, 60 packets received, 0% packet loss
round-trip min/avg/max = 1.529/2.824/5.591 ms
graysky2 commented 4 years ago

I do occasionally, yes. I notice this on my iPhones, especially as distance increases from my R7800 (another complicating factor, I know). But I do see this on my MacBooks occasionally as well.

That is consistent with the bug I reported. When the bug hits, you see BOTH the high pings+packet loss AND shit response times on the google query.

Thanks for bringing this up--I actually meant to elaborate more on this in my OP. The answer is yes, absolutely. When this issue is presenting itself with one of my devices, once I get the wireless radio on the device busy with active data flow the ping times actually drop to a consistent <10ms on average. Typically 3-5ms.

This makes me think your issue is the same as mine. Why? Once the lag hits my iphones, it does not go away/screen on or screen off, downloading something or not. I am wondering if the idle nature of your problem is suggestive of some power savings option on the macbooks themselves? That is just speculation. Do you experience the ping lag when you use the ath10k driver and firmware? In my case, I do not see the bug.

Regarding your /etc/config/wireless... You config looks sane to me. As an aside (likely NOT causing your problem), may want to adjust your dtm_period to a value of 3 as this is what apple recommends. See this thread and the links therein.

Finally, I cannot speak to what your latest snapshot build with extra patches may do for you. Did you build include https://github.com/openwrt/openwrt/commit/91aab77bf1ce91b0e60e720eb147c94a02c1f2fd? Unless you're manually overwriting the firmware, this bumps the ath10k-ct version to the .019 versions as you may be aware.

Fail-Safe commented 4 years ago

@graysky2

I do occasionally, yes. I notice this on my iPhones, especially as distance increases from my R7800 (another complicating factor, I know). But I do see this on my MacBooks occasionally as well.

That is consistent with the bug I reported. When the bug hits, you see BOTH the high pings+packet loss AND shit response times on the google query.

Granted, I was not seeing the same level of packet loss as you for the most part. I think that was the primary driver for @greearb wanting me to open this separate issue.

Thanks for bringing this up--I actually meant to elaborate more on this in my OP. The answer is yes, absolutely. When this issue is presenting itself with one of my devices, once I get the wireless radio on the device busy with active data flow the ping times actually drop to a consistent <10ms on average. Typically 3-5ms.

This makes me think your issue is the same as mine. Why? Once the lag hits my iphones, it does not go away/screen on or screen off, downloading something or not. I am wondering if the idle nature of your problem is suggestive of some power savings option on the macbooks themselves? That is just speculation. Do you experience the ping lag when you use the ath10k driver and firmware? In my case, I do not see the bug.

While we do have a number of things in common, my main hold-up in drawing the correlation to your issue is my iPhones were not exhibiting the behavior with the same regularity as yours seem to. But it did happen at times and I wish I had saved some of the historic ping results during those moments.

I was thinking along the exact same lines regarding power saving. I could buy into that more easily in my case if my phones were the primary trouble devices, but at the moment it's more evident on my MacBooks. I guess it's conceivable that Apple might still be cycling radio power on/off on a MacBook that is plugged into a power supply, but why wouldn't my iPhones be showing this more often given they're 90% of the time running on battery. (Just thinking out loud here...)

I will say, even when my iPhones are not exhibiting the trouble behavior, they do still show consistently higher pings as compared to my kids' Nintendo Switch. It is <5ms (and usually closer to 2-3ms) ALL the time it is powered on.

Regarding your /etc/config/wireless... You config looks sane to me. As an aside (likely NOT causing your problem), may want to adjust your dtm_period to a value of 3 as this is what apple recommends. See this thread and the links therein.

Thanks for the second set of eyes on my config--always glad to have good feedback on things like that. I was not aware of the thread you linked, but checked it out and updated to dtim_period = 3. Many thanks for making me aware of that one!

Finally, I cannot speak to what your latest snapshot build with extra patches may do for you. Did you build include openwrt/openwrt@91aab77? Unless you're manually overwriting the firmware, this bumps the ath10k-ct version to the .019 versions as you may be aware.

As for trying the ath10k driver + firmware--I haven't used it for months, to be honest. I'm not against building and running that config for a bit, but I generally had tried to just commit to the ath10k-ct setup and grow with it. 👍

At the moment, though, I am just simply not seeing the issue with last night's build using the patches I mentioned. Any chance you would be willing to try a snapshot build with the same patches and see if your issue persists or not?

Fail-Safe commented 4 years ago

Well... isn't that just how IT stuff goes...

It's back:

--- 192.168.9.83 ping statistics ---
91 packets transmitted, 88 packets received, 3% packet loss
round-trip min/avg/max = 1.497/1115.832/4549.649 ms
greearb commented 4 years ago

fail-safe: Do you have a non-phone that exhibits this? I need to find a device that I can acquire that will reproduce the issue...this is too complicated to debug from afar I think.

Fail-Safe commented 4 years ago

fail-safe: Do you have a non-phone that exhibits this? I need to find a device that I can acquire that will reproduce the issue...this is too complicated to debug from afar I think.

Contrary to @graysky2's reports, my iPhones don't show it consistently. The device that I have the most consistent issue with is my MacBook Pro 15in (2019). After that, my next most troublesome device has been my MacBook Pro 16in (2019).

graysky2 commented 4 years ago

As for trying the ath10k driver + firmware--I haven't used it for months, to be honest. I'm not against building and running that config for a bit, but I generally had tried to just commit to the ath10k-ct setup and grow with it. +1

The point of the experiment is to see if it's the -ct's driver/firmware.

At the moment, though, I am just simply not seeing the issue with last night's build using the patches I mentioned. Any chance you would be willing to try a snapshot build with the same patches and see if your issue persists or not?

I am running a snapshot I build several days ago when the 5.4.58 kernel was released. I am running the the ath10k driver/firmware until @greearb has a new set of firmware for me test.

Fail-Safe commented 4 years ago

As for trying the ath10k driver + firmware--I haven't used it for months, to be honest. I'm not against building and running that config for a bit, but I generally had tried to just commit to the ath10k-ct setup and grow with it. +1

The point of the experiment is to see if it's the -ct's driver/firmware.

Yeah, I get it--sorry if it sounded like I wasn't tracking with the intent there. I am actually in the process of an ath10k build as I type this.

FYI, I just noticed the three AQL related patches I referred to previously have been committed to the current snapshot branch now.

At the moment, though, I am just simply not seeing the issue with last night's build using the patches I mentioned. Any chance you would be willing to try a snapshot build with the same patches and see if your issue persists or not?

I am running a snapshot I build several days ago when the 5.4.58 kernel was released. I am running the the ath10k driver/firmware until @greearb has a new set of firmware for me test.

Apart from the absence of this issue, are you noticing any other major differences between the ath10k and ath10k-ct drivers/fw at the moment? Decreased range? Increased latency? Anything like that?

Out of curiosity, too, where are you getting a 5.4.58 kernel from? The latest I am seeing in snapshot is 5.4.52.

graysky2 commented 4 years ago

Yeah, I get it--sorry if it sounded like I wasn't tracking with the intent there. I am actually in the process of an ath10k build as I type this.

OK, see what you get with it.

Apart from the absence of this issue, are you noticing any other major differences between the ath10k and ath10k-ct drivers/fw at the moment? Decreased range? Increased latency? Anything like that?

I did not compare range or latency. Just the ping test.

Out of curiosity, too, where are you getting a 5.4.58 kernel from? The latest I am seeing in snapshot is 5.4.52.

https://github.com/openwrt/openwrt/pull/3285

ghost commented 4 years ago

Well... isn't that just how IT stuff goes...

It's back:

Between the time when you were symptom free and the symptoms appears, did the client disassociate/re-associate to the AP? If so, you may want to see if you can trigger it by intentionally disconnecting/reconnecting after rebooting the client.

greearb commented 3 years ago

Any chance you can try some openwrt releases from earlier this year to see if they work any better for this particular problem?