WiFi connection dropped - Dropping frame due to full tx queue

Hi,

I am experiencing WiFi drops. rebooting the router does the trick, until next time.
Below is the kernel log:

[    0.000000] Linux version 4.4.92 (buildbot@debian8) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3560-79f57e422d) ) #0 Tue Oct 17 17:46:20 2017
[    0.000000] SoC: xRX200 rev 1.1
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019555 (MIPS 34Kc)
[    0.000000] MIPS: machine is P2812HNUF1 - ZyXEL P-2812HNU-F1
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 08000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] On node 0 totalpages: 32768
[    0.000000] free_area_init_node: node 0, pgdat 804bc4b0, node_mem_map 8100a780
[    0.000000]   Normal zone: 256 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 32768 pages, LIFO batch:7
[    0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyLTQ0,115200
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Writing ErrCtl register=00000001
[    0.000000] Readback ErrCtl register=00000001
[    0.000000] Memory: 123404K/131072K available (3923K kernel code, 161K rwdata, 884K rodata, 1224K init, 213K bss, 7668K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:256
[    0.000000] Setting up vectored interrupts
[    0.000000] CPU Clock: 500MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041786 ns
[    0.000010] sched_clock: 32 bits at 250MHz, resolution 4ns, wraps every 8589934590ns
[    0.007857] Calibrating delay loop... 332.54 BogoMIPS (lpj=665088)
[    0.042316] pid_max: default: 32768 minimum: 301
[    0.047159] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.053722] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.067054] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.076697] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.082910] pinctrl core: initialized pinctrl subsystem
[    0.089433] NET: Registered protocol family 16
[    0.098437] pinctrl-xway 1e100b10.pinmux: Init done
[    0.103958] dma-xway 1e104100.dma: Init done - hw rev: 7, ports: 7, channels: 28
[    0.214008] dcdc-xrx200 1f106a00.dcdc: Core Voltage : 1016 mV
[    0.219757] Can't analyze schedule() prologue at 80009078
[    0.233842] PCI host bridge /fpi@10000000/pci@E105400 ranges:
[    0.239454]  MEM 0x0000000018000000..0x0000000019ffffff
[    0.244738]   IO 0x000000001ae00000..0x000000001affffff
[    0.263549] gpio-stp-xway 1e100bb0.stp: Init done
[    0.268752] usbcore: registered new interface driver usbfs
[    0.274243] usbcore: registered new interface driver hub
[    0.279603] usbcore: registered new device driver usb
[    0.285005] PCI host bridge to bus 0000:00
[    0.288998] pci_bus 0000:00: root bus resource [mem 0x18000000-0x19ffffff]
[    0.295908] pci_bus 0000:00: root bus resource [io  0x1ae00000-0x1affffff]
[    0.302849] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
[    0.309704] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.317757] pci 0000:00:0e.0: [1814:3062] type 00 class 0x028000
[    0.317814] pci 0000:00:0e.0: reg 0x10: [mem 0xffff0000-0xffffffff]
[    0.318205] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
[    0.318249] pci 0000:00:0e.0: BAR 0: assigned [mem 0x18000000-0x1800ffff]
[    0.325838] clocksource: Switched to clocksource MIPS
[    0.332034] NET: Registered protocol family 2
[    0.337314] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.344200] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.350577] TCP: Hash tables configured (established 1024 bind 1024)
[    0.357082] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.362934] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.369495] NET: Registered protocol family 1
[    0.373825] PCI: CLS 0 bytes, default 32
[    0.380392] gptu: totally 6 16-bit timers/counters
[    0.385222] gptu: misc_register on minor 63
[    0.389325] gptu: succeeded to request irq 126
[    0.393812] gptu: succeeded to request irq 127
[    0.398327] gptu: succeeded to request irq 128
[    0.402839] gptu: succeeded to request irq 129
[    0.407353] gptu: succeeded to request irq 130
[    0.411866] gptu: succeeded to request irq 131
[    0.416699] phy-xrx200 gphy-xrx200: requesting lantiq/vr9_phy11g_a1x.bin
[    0.423952] phy-xrx200 gphy-xrx200: booting GPHY0 firmware at 7DA0000
[    0.430286] phy-xrx200 gphy-xrx200: booting GPHY1 firmware at 7DA0000
[    0.536932] No VPEs reserved for AP/SP, not initialize VPE loader
[    0.536932] Pass maxvpes=<n> argument as kernel argument
[    0.548292] No TCs reserved for AP/SP, not initializing RTLX.
[    0.548292] Pass maxtcs=<n> argument as kernel argument
[    0.560101] Crashlog allocated RAM at address 0x3f00000
[    0.585444] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.591168] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.604869] io scheduler noop registered
[    0.608680] io scheduler deadline registered (default)
[    0.614521] 1e100c00.serial: ttyLTQ0 at MMIO 0x1e100c00 (irq = 112, base_baud = 0) is a lantiq,asc
[    0.623419] console [ttyLTQ0] enabled
[    0.630745] bootconsole [early0] disabled
[    0.642021] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[    0.646918] nand: Samsung NAND 128MiB 3,3V 8-bit
[    0.651532] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    0.659171] Scanning device for bad blocks
[    0.686692] Bad eraseblock 281 at 0x000002320000
[    0.708969] Bad eraseblock 511 at 0x000003fe0000
[    0.716189] Bad eraseblock 560 at 0x000004600000
[    0.745896] Bad eraseblock 879 at 0x000006de0000
[    0.761084] 4 ofpart partitions found on MTD device 10000000.nand-parts
[    0.766263] Creating 4 MTD partitions on "10000000.nand-parts":
[    0.772180] 0x000000000000-0x000000040000 : "uboot"
[    0.778904] 0x000000040000-0x000000060000 : "uboot-env"
[    0.784754] 0x000000060000-0x000000260000 : "kernel"
[    0.790400] 0x000000260000-0x000008000000 : "ubi"
[    0.898847] libphy: lantiq,xrx200-mdio: probed
[    0.974572] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.3] (phy_addr=0:00, irq=-1)
[    1.042545] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.3] (phy_addr=0:01, irq=-1)
[    1.110530] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.4] (phy_addr=0:11, irq=-1)
[    1.178528] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.4] (phy_addr=0:13, irq=-1)
[    1.246546] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.3] (phy_addr=0:05, irq=-1)
[    1.254672] wdt 1f8803f0.watchdog: Init done
[    1.261463] NET: Registered protocol family 10
[    1.271119] NET: Registered protocol family 17
[    1.274259] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    1.286773] 8021q: 802.1Q VLAN Support v1.8
[    1.294987] UBI: auto-attach mtd3
[    1.296669] ubi0: attaching mtd3
[    1.481542] ubi0: scanning is finished
[    1.495941] ubi0: attached mtd3 (name "ubi", size 125 MiB)
[    1.500021] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[    1.506861] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[    1.513562] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[    1.520351] ubi0: good PEBs: 1001, bad PEBs: 4, corrupted PEBs: 0
[    1.526444] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[    1.533671] ubi0: max/mean erase counter: 5/2, WL threshold: 4096, image sequence number: 1508439421
[    1.542811] ubi0: available PEBs: 0, total reserved PEBs: 1001, PEBs reserved for bad PEB handling: 16
[    1.552179] ubi0: background thread "ubi_bgt0d" started, PID 317
[    1.559771] block ubiblock0_0: created from ubi0:0(rootfs)
[    1.563862] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem
[    1.577946] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    1.587373] Freeing unused kernel memory: 1224K
[    2.455282] init: Console is alive
[    2.457501] init: - watchdog -
[    3.406306] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    3.511639] dwc2 1e101000.ifxhcd: requested GPIO 495
[    3.982001] eth0: port 0 got link
[    4.370040] dwc2 1e101000.ifxhcd: DWC OTG Controller
[    4.373632] dwc2 1e101000.ifxhcd: new USB bus registered, assigned bus number 1
[    4.380946] dwc2 1e101000.ifxhcd: irq 62, io mem 0x00000000
[    4.386472] dwc2 1e101000.ifxhcd: Hardware does not support descriptor DMA mode -
[    4.393914] dwc2 1e101000.ifxhcd: falling back to buffer DMA mode.
[    4.401388] hub 1-0:1.0: USB hub found
[    4.404320] hub 1-0:1.0: 1 port detected
[    5.266023] dwc2 1e106000.ifxhcd: DWC OTG Controller
[    5.269632] dwc2 1e106000.ifxhcd: new USB bus registered, assigned bus number 2
[    5.276935] dwc2 1e106000.ifxhcd: irq 91, io mem 0x00000000
[    5.282462] dwc2 1e106000.ifxhcd: Hardware does not support descriptor DMA mode -
[    5.289904] dwc2 1e106000.ifxhcd: falling back to buffer DMA mode.
[    5.297361] hub 2-0:1.0: USB hub found
[    5.300338] hub 2-0:1.0: 1 port detected
[    5.305049] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    5.321464] init: - preinit -
[    6.027050] random: procd: uninitialized urandom read (4 bytes read, 25 bits of entropy available)
[    9.277678] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 395
[    9.305925] UBIFS (ubi0:1): recovery needed
[    9.420170] UBIFS (ubi0:1): recovery completed
[    9.423298] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[    9.431035] UBIFS (ubi0:1): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    9.440941] UBIFS (ubi0:1): FS size: 121927680 bytes (116 MiB, 945 LEBs), journal size 6064128 bytes (5 MiB, 47 LEBs)
[    9.451569] UBIFS (ubi0:1): reserved for root: 4952683 bytes (4836 KiB)
[    9.458183] UBIFS (ubi0:1): media format: w4/r0 (latest is w4/r0), UUID 7F084747-362D-4D3A-9D76-6458F3861680, small LPT model
[    9.473358] mount_root: switching to ubifs overlay
[    9.484365] urandom-seed: Seeding with /etc/urandom.seed
[    9.662726] procd: - early -
[    9.664321] procd: - watchdog -
[    9.981871] eth0: port 0 lost link
[   10.315061] procd: - watchdog -
[   10.317195] procd: - ubus -
[   10.396664] random: ubusd: uninitialized urandom read (4 bytes read, 43 bits of entropy available)
[   10.405817] random: ubusd: uninitialized urandom read (4 bytes read, 43 bits of entropy available)
[   10.414001] random: ubusd: uninitialized urandom read (4 bytes read, 43 bits of entropy available)
[   10.422499] random: ubusd: uninitialized urandom read (4 bytes read, 43 bits of entropy available)
[   10.431933] random: ubusd: uninitialized urandom read (4 bytes read, 43 bits of entropy available)
[   10.440432] random: ubusd: uninitialized urandom read (4 bytes read, 43 bits of entropy available)
[   10.449599] random: ubusd: uninitialized urandom read (4 bytes read, 43 bits of entropy available)
[   10.458577] random: ubusd: uninitialized urandom read (4 bytes read, 43 bits of entropy available)
[   10.467787] procd: - init -
[   10.940749] kmodloader: loading kernel modules from /etc/modules.d/*
[   10.949450] IFXOS, Version 1.5.19 (c) Copyright 2009, Lantiq Deutschland GmbH
[   10.960506] NET: Registered protocol family 8
[   10.963484] NET: Registered protocol family 20
[   10.974339] PPP generic driver version 2.4.2
[   10.984462] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   11.008060] Lantiq (VRX) DSL CPE MEI driver, version 1.5.17.6, (c) 2007-2015 Lantiq Beteiligungs-GmbH & Co. KG
[   11.008060] 
[   11.008060] Lantiq CPE API Driver version: DSL CPE API V4.17.18.6
[   11.031139] 
[   11.031139] Predefined debug level: 3
[   11.043402] Loading modules backported from Linux version wt-2017-01-31-0-ge882dff19e7f
[   11.050029] Backport generated by backports.git backports-20160324-13-g24da7d3c
[   11.061931] ip_tables: (C) 2000-2006 Netfilter Core Team
[   11.071124] Infineon Technologies DEU driver version 2.0.0 
[   11.077217] IFX DEU DES initialized (multiblock).
[   11.081492] IFX DEU AES initialized (multiblock).
[   11.085626] IFX DEU ARC4 initialized (multiblock).
[   11.090257] IFX DEU SHA1 initialized.
[   11.093786] IFX DEU MD5 initialized.
[   11.097480] IFX DEU SHA1_HMAC initialized.
[   11.101513] IFX DEU MD5_HMAC initialized.
[   11.112441] nf_conntrack version 0.5.0 (1947 buckets, 7788 max)
[   11.137125] NET: Registered protocol family 24
[   11.159714] xt_time: kernel timezone is -0000
[   11.246680] PCI: Enabling device 0000:00:0e.0 (0000 -> 0002)
[   11.251124] ieee80211 phy0: rt2x00lib_request_eeprom_file: Info - Loading EEPROM data from 'RT3062.eeprom'.
[   11.262515] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected
[   11.268903] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0008 detected
[   11.276466] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   11.375461] kmodloader: done loading kernel modules from /etc/modules.d/*
[   12.686394] random: jshn: uninitialized urandom read (4 bytes read, 53 bits of entropy available)
[   17.370282] PTM 1.0.27    PTM (E1) firmware version 0.30
[   17.374201] ifxmips_ptm: PTM init succeed
[   22.556495] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   22.578000] device eth0 entered promiscuous mode
[   22.587588] device eth0.1 entered promiscuous mode
[   22.596020] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[   22.651192] IPv6: ADDRCONF(NETDEV_UP): ptm0: link is not ready
[   23.266123] eth0: port 0 got link
[   23.268237] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   23.292358] br-lan: port 1(eth0.1) entered forwarding state
[   23.296623] br-lan: port 1(eth0.1) entered forwarding state
[   23.430758] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[   25.297869] br-lan: port 1(eth0.1) entered forwarding state
[   26.296384] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
[   26.621975] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.40
[   26.792364] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   26.818054] device wlan0 entered promiscuous mode
[   30.537889] random: nonblocking pool is initialized
[   35.082973] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   35.088187] br-lan: port 2(wlan0) entered forwarding state
[   35.093497] br-lan: port 2(wlan0) entered forwarding state
[   37.093902] br-lan: port 2(wlan0) entered forwarding state
[   61.091928] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.099817] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.109040] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.118260] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.127484] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.136711] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.145937] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.155163] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.164388] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.173616] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.182841] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.192079] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.201297] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.210529] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.219748] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.228973] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.238207] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.247433] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.256652] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.265886] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.275104] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   61.284328] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.094476] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.102376] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.111599] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.120810] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.130039] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.139267] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.148488] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.157719] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.166922] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.176170] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.185397] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.298326] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.306237] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.315450] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.324668] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.333900] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.343124] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[   91.352343] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2

How to fix this?
Regards Robert

Seems to be a known issue...

Hi!

This is a very dirty workaround but as even 18.06.0-rc2 has this problem, I have started to restart network only, which doesn't kill the uptime.

http:///cgi-bin/luci/admin/system/crontab

Textfield: 0 5,17 * * * /etc/init.d/network restart

At 0500 it's still time for the backup of my phone to GoogleDrive
At 1700 it's about an hour or two before I return home :wink:

Seems like this repo include fixed driver, discussion is here.

check if this patch make things any better https://lore.kernel.org/patchwork/patch/1005952/

any news guys?

@psyborg I want to test the patch that you suggest, I have 2 Xiaomi Miwifi Mini devices with this problem too.

How is the correct way to implement the patch in my trunk build environment?
Should it work if I put the patch in the package/kernel/mac80211/patches/subsys folder?

Thanks

it should work

if the above patch doesn't help this one does for sure:https://patchwork.kernel.org/patch/10739037/

additionaly, remove patches:
701-rt2800-move-usb-specific-txdone-txstatus-routines-to.patch
702-rt2800mmio-use-txdone-txstatus-routines-from-lib.patch
703-rt2x00-do-not-check-for-txstatus-timeout-every-time-.patch
704-rt2x00-use-different-txstatus-timeouts-when-flushing.patch
705-rt2800-flush-and-txstatus-rework-for-rt2800mmio.patch
980-rt2x00-reduce-power-consumption-on-mt7620.patch

and add patch: https://patchwork.kernel.org/patch/10743705/

to have both stable and fast wifi within normal range. mark thread solved

I an Asus RT-N56U wireless router (ramips target, rt3883 subtarget). When it had 18.06, the bug occurred very frequently. With the latest OpenWrt 18.06.2 r7676-cddd7b4c77 / LuCI openwrt-18.06 branch (git-19.020.41695-6f6641d) the bug almost went away - it is harder to trigger, but definitely not fixed. I'm not sure the issue only effects only the rt3883 subtarget, or the bug is still lurking in the rt2x00 driver affecting all ramips targets.

How could I help to fix the bug? I am able to trigger the bug quite regularly.

I am a bit confused regarding the info to remove patches (as proposed by @psyborg).

I cannot find them in the master or openwrt-18.06 branches. Are these referrring to a different openwrt source tree?

renamed for some reason to 002* - 006* in https://git.openwrt.org/?p=openwrt/openwrt.git;a=tree;f=package/kernel/mac80211/patches/rt2x00

Update: I flashed my Asus RT-N56U to the latest OpenWrt 18.06.4 r7808-ef686b7292 / LuCI openwrt-18.06 branch (git-19.170.32094-4d6d8bc) and to my disappointment, the problem is still there. When that happens, the same error is logged: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2

Please check master snapshots instead, that's where development (and potential improvement) happens, the openwrt-18.06 branch only gets (targetted) bugfixes (if identified and requested for backporting/ cherry-picking). The rt2x00 suite of drivers has seen some work on this particular issue in recent months, but given that these problems are longstanding, I wouldn't expect the world either - but it is worth testing.

2 Likes

First time user here. Same problem on my D-Link DIR-615 D4.
I just switched to openwrt because the stock firmware kept stopping passing traffic after a few hours.
OpenWrt is marginally better but still doesn't last more than 2 days before this problem shows up.
Even if it was fixed, I'm stuck with version 17.0.7 due to RAM/flash size.
I guess I'll put the D-Link in the bin now and go get a Cisco WAP 125 or something.

And old Honda advert comes to mind. It said something like "Isn't it great when things just ... work?!"

Just wanted to express my frustration :slight_smile:
Thanks for listening!

Update: OpenWRT 19.07.3 onwards do not have the problem.

1 Like

no. this bug still present on 19.07.4. I have dwr-118 and we1626. both have the same chipset. both appear the same wifi problem