OpenWrt/LEDE Project

Welcome to the OpenWrt/LEDE Project bug reporting and issue tracking system

Problems to be reported here are for the OpenWrt/LEDE Project targets, sources, toolchain, core packages, build procedures, distribution and infrastructure. Guidelines for submitting a good bug report can be found at the OpenWrt/LEDE Project website. Problems related to LuCI or OpenWrt packages need to be reported in their repositories:

Notifications of all submissions and task changes are sent to lede-bugs@infradead.org.

OpenedIDCategoryTask TypePrioritySeveritySummaryReported In  descStatus
14.11.20181951KernelBug ReportVery LowCriticalbrcm63xx: Livebox: 4.14 kernel boot stuck at "random: c...openwrt-19.07New Task Description

The kernel 4.14 is unable to boot on the Inventel Livebox 1 (BCM6348 board with a redboot bootloader).

Steps to reproduce:

  • Intall the latest trunk version (i.e. r8455-042d68a) kernel 4.14

Sympthoms:

  1. It won’t detect the BogoMips CPU speed
  2. It stucks at “random: fast init done”, and apparently no more kernel messages
  3. But after a minute it spits the last message random: crng init done

Boot log:

965543210120123456+678ESA: 30:78:30:30:3a:30
WEP KEY : FFFFFFFFFFFFFFFFFFFFFFFFFF
Auto-negotiation timed-out
10 MB Half-Duplex (assumed)
Ethernet eth0: MAC address 30:78:30:30:3a:30
IP: 10.7.58.112, Default server: 10.7.58.114
Hardware version 0x90, mask=0x7E
Hardware version 0x10 (masked) BLUE5G.9 DV4210
Factory Settings Recovery Switch OFF

RedBoot(tm) bootstrap and debug environment [ROM]
unlocked release, eCos 2.0b1 - built 23:01:33, Jan 11 2013

Platform: Blue_5g (MIPS32 4Kc) 
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x80000000-0x84000000, [0x80435e50-0x83fe2000] available
FLASH: 0xbe400000 - 0xbec00000, 128 blocks of 0x00010000 bytes each.
== Executing boot script in 20.000 seconds - enter ^C twice to abort
RedBoot> fis load -b 0x80a00000 -d kernel
 -- Redboot version without crypt_verify -- 
Image loaded from 0x80a00000-0x80f55b2e
RedBoot> exec -c "noinitrd" 0x80a00000
Now booting linux kernel:
 Base address 0x8000fc00 Entry 0x80a00000
 Cmdline : noinitrd
changing Kseg0 coherency algorithm to write back...
enabling icache and dcache...

[    0.000000] Linux version 4.14.80 (buildbot@buildslave) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r8455-042d68a195)) #0 Tue Nov 13 20:40:30 2018
[    0.000000] Detected Broadcom 0x6348 CPU revision b0
[    0.000000] CPU frequency is 300 MHz
[    0.000000] 64MB of RAM installed
[    0.000000] board_livebox: flash address is: 0x1fc00000, forcing to: 0x1e400000
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00029107 (Broadcom BMIPS3300)
[    0.000000] board: board name: Livebox-blue-5g
[    0.000000] MIPS: machine is Inventel Livebox 1
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 04000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Primary instruction cache 16kB, VIPT, 2-way, linesize 16 bytes.
[    0.000000] Primary data cache 8kB, 2-way, VIPT, no aliases, linesize 16 bytes
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] random: get_random_bytes called from start_kernel+0x80/0x488 with crng_init=0
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 16256
[    0.000000] Kernel command line: rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200
[    0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Memory: 58160K/65536K available (4003K kernel code, 193K rwdata, 956K rodata, 1304K init, 209K bss, 7376K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=16, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 256
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 12741736309 ns
[    0.000031] sched_clock: 32 bits at 150MHz, resolution 6ns, wraps every 14316557820ns
[    1.037346] random: fast init done
[   53.974911] random: crng init done
 


23.03.20192202KernelBug ReportVery LowCriticalbrcm63xx: Hg556a: 4.14 kernel boot stuck at "random: cr...openwrt-19.07New Task Description

The kernel 4.14.107 is unable to boot on the Hg556a (BCM6358).

Steps to reproduce:

  Intall the latest trunk version kernel 4.14.107

Sympthoms:

  No Boot
  It stucks at “random: fast init done”, and apparently no more kernel messages
  But after a minute it spits the last message random: crng init done

Boot Log:

*** Press any key to stop auto run (1 seconds) ***
Auto run second count down: 0
boot kernel from be020100
Code Address: 0x80A00000, Entry Address: 0x80a00000
Decompression OK!
Entry at 0x80a00000
Closing network.
Starting program at 0x80a00000
[    0.000000] Linux version 4.14.107 (hg556a@localhost.localdomain) (gcc version 7.4.0 (OpenWrt GCC 7.4.0 r9015-34696ce25e)) #0 Thu Mar 10 15:47:43 2019
[    0.000000] Detected Broadcom 0x6358 CPU revision a1
[    0.000000] CPU frequency is 300 MHz
[    0.000000] 64MB of RAM installed
[    0.000000] board_bcm963xx: Boot address 0xbe000000
[    0.000000] board_bcm963xx: CFE version: d081.5003
[    0.000000] bcm63xx_nvram: nvram checksum failed, contents may be invalid (expected 33313330, got 3c502ae7)
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0002a010 (Broadcom BMIPS4350)
[    0.000000] board: board name: HW556_B
[    0.000000] MIPS: machine is Huawei EchoLife HG556a (version B)
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 04000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Primary instruction cache 16kB, VIPT, 2-way, linesize 16 bytes.
[    0.000000] Primary data cache 16kB, 2-way, VIPT, cache aliases, linesize 16 bytes
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] random: get_random_bytes called from start_kernel+0x80/0x488 with crng_init=0
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 16256
[    0.000000] Kernel command line: rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200
[    0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Memory: 54392K/65536K available (6369K kernel code, 343K rwdata, 2132K rodata, 1324K init, 256K bss, 11144K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=16, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 256
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 12741736309 ns
[    0.000026] sched_clock: 32 bits at 150MHz, resolution 6ns, wraps every 14316557820ns
[    1.034043] random: fast init done
[   53.820705] random: crng init done


19.01.20202755Base systemBug ReportVery LowCriticalR3P Xiaomi Wireless don't workopenwrt-19.07Unconfirmed Task Description

19.07.0 installed with a sysupgrade on luci http.

device wifi radio 0 and radio 1 impossible to enabled it.


01.04.20192216KernelBug ReportVery LowHighath79 - eth0 Spasmodic Link Speed After Driver Changes?...openwrt-19.07New Task Description

I’ve built the latest version of OpenWRT with stock packages and configuration, however, after random amounts of time, all clients lose connectivity because the eth0 link speed drops from the regular 100 Mbps Full Duplex to 10 Mbps Half Duplex, only to reconnect again after a couple of minutes (seconds to mintes, it depends), and do it again at another random time.

[18580.106696] eth0: link up (100Mbps/Full duplex)
[19014.825937] eth0: link up (10Mbps/Half duplex)
[19055.384105] eth0: link up (100Mbps/Full duplex)
[21927.853366] eth0: link up (10Mbps/Half duplex)
[22003.771999] eth0: link up (100Mbps/Full duplex)
[23743.685216] eth0: link down
[23744.723679] eth0: link up (100Mbps/Full duplex)
[23756.242265] eth0: link down
[23757.283590] eth0: link up (100Mbps/Full duplex)
[24075.522397] eth0: link up (10Mbps/Half duplex)
[24090.081802] eth0: link up (100Mbps/Full duplex)
[24100.481809] eth0: link up (10Mbps/Half duplex)
[24166.001178] eth0: link up (100Mbps/Full duplex)
[24500.880989] eth0: link up (10Mbps/Half duplex)

The logs aren’t very useful, it seems. Both syslog and dmesg show the same.

I suspect this started happening after this series of commits (ending with this one) where there were driver changes to the switch, as it didn’t happen before I recompiled a new build with all those newer changes:
https://github.com/openwrt/openwrt/commit/3d93b35f039de86830565420968715b300066475

29.09.20192523KernelBug ReportVery LowHighRB750 randomly reboots after kernel warningsopenwrt-19.07Unconfirmed Task Description

Mikrotik RB750Gr3
LuCI openwrt-19.07 branch (git-19.267.59428-7b36dae) / OpenWrt 19.07-SNAPSHOT r10532-cf3b50377e

Router randomly reboots (it may be stable for hours or can reboot in a minute after power up). Seems like kernel problem.

Here are some logs I managed to fetch before the reboots:

Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.010562] ------------[ cut here ]------------
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.015202] WARNING: CPU: 2 PID: 0 at net/ipv4/tcp_output.c:2509 0x803cc8bc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.022158] invalid inflight: 1 state 1 cwnd 10 mss 1388
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.027441] Modules linked in: qcserial pppoe ppp_async option cdc_mbim usb_wwan sierra_net sierra rndis_host qmi_wwan pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cdc_ncm cdc_ether xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT wireguard usbserial usbnet usblp ts_fsm ts_bm slhc nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.097872]  nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda nf_conntrack iptable_raw iptable_mangle iptable_filter ip_tables crc_ccitt cdc_wdm cdc_acm fuse ledtrig_usbport gpio_beeper input_core xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ip6_udp_tunnel udp_tunnel tun vfat fat nls_utf8 nls_iso8859_1 nls_cp437 uas usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd ehci_platform
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.169233]  sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4 mbcache jbd2 usbcore nls_base usb_common mii crc32c_generic
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.180291] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.14.143 #0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.186357] Stack : 00000000 00000000 00000000 81230398 00000000 00000000 00000000 00000000
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.194691]         00000000 00000000 00000000 00000000 00000000 00000001 8fc0dd30 ac07f596
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.203026]         8fc0ddc8 00000000 00000000 00004ea0 00000038 8049db58 00000007 00000000
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.211359]         00000000 80550000 0002c043 00000000 8fc0dd10 00000000 80570000 8050c6a0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.219690]         803cc8bc 000009cd 812303d8 81230398 00000000 802af9e8 00000008 805b0008
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.228022]         ...
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.230459] Call Trace:
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.230475] [<8049db58>] 0x8049db58
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.236372] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.239840] [<802af9e8>] 0x802af9e8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.243312] [<800101a0>] 0x800101a0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.246782] [<800101a8>] 0x800101a8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.250250] [<80486a9c>] 0x80486a9c
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.253722] [<800758a0>] 0x800758a0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.257243] [<80032588>] 0x80032588
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.260714] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.264185] [<80032610>] 0x80032610
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.267654] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.271126] [<803cf3d0>] 0x803cf3d0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.274596] [<8009d750>] 0x8009d750
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.278064] [<803cf7a8>] 0x803cf7a8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.281537] [<8009dd80>] 0x8009dd80
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.285007] [<803cf770>] 0x803cf770
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.288474] [<8008c2cc>] 0x8008c2cc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.291945] [<8008c588>] 0x8008c588
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.295413] [<8007cee8>] 0x8007cee8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.298883] [<804a49b8>] 0x804a49b8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.302357] [<80036f14>] 0x80036f14
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.305827] [<8025d440>] 0x8025d440
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.309296] [<8000b488>] 0x8000b488
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.312764]
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.314310] ---[ end trace a36c893f27b6a6f3 ]---
Sun Sep 29 18:56:25 2019 kern.alert kernel: [ 2442.525228] CPU 1 Unable to handle kernel paging request at virtual address 00000010, epc == 803be4a0, ra == 803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.535821] Oops[#1]:
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.538087] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G        W       4.14.143 #0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.545363] task: 8fc3be80 task.stack: 8fc5c000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.549869] $ 0   : 00000000 00000001 0000004a 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.555080] $ 4   : 8ea76f3c 00000001 0000d706 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.560290] $ 8   : 00034501 00000321 811d7440 00000322
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.565501] $12   : 8ea22180 8ea22180 8e9a8e00 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.570712] $16   : 8ea76e40 00001204 6375f4c6 ffffffff
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.575923] $20   : 00001204 00000001 00000000 00000002
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.581133] $24   : 00000000 8034b220
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.586344] $28   : 8fc5c000 8fc0bbb8 00000000 803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.591555] Hi    : 0000caa1
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.594419] Lo    : 47aec5c8
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.597285] epc   : 803be4a0 0x803be4a0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.601098] ra    : 803c4104 0x803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.604912] Status: 11007c03      KERNEL EXL IE
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.609082] Cause : 40800008 (ExcCode 02)
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.613066] BadVA : 00000010
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.615931] PrId  : 0001992f (MIPS 1004Kc)
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.620003] Modules linked in: qcserial pppoe ppp_async option cdc_mbim usb_wwan sierra_net sierra rndis_host qmi_wwan pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cdc_ncm cdc_ether xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT wireguard usbserial usbnet usblp ts_fsm ts_bm slhc nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.690391]  nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda nf_conntrack iptable_raw iptable_mangle iptable_filter ip_tables crc_ccitt cdc_wdm cdc_acm fuse ledtrig_usbport gpio_beeper input_core xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ip6_udp_tunnel udp_tunnel tun vfat fat nls_utf8 nls_iso8859_1 nls_cp437 uas usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd ehci_platform
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.761710]  sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4 mbcache jbd2 usbcore nls_base usb_common mii crc32c_generic
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.772740] Process swapper/1 (pid: 0, threadinfo=8fc5c000, task=8fc3be80, tls=00000000)
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.780788] Stack : 00000204 8034def4 8ea76e40 00000000 8ea76e40 8ea76e40 00001204 803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.789123]         8f346480 8056ba00 00000000 8015000a 00018bc3 8fc0bc74 00000004 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.797457]         80550000 8ea76f3c 00000002 00000001 91946e37 00000000 00000018 91946e37
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.805791]         00000000 91946e37 00000000 00000001 80570000 8050c458 00000000 00000002
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.814125]         00018bc3 00000018 8ee92564 8e9a0600 00000000 00000000 00000001 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.822457]         ...
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.824891] Call Trace:
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.824903] [<8034def4>] 0x8034def4
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.830852] [<803c4104>] 0x803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.834335] [<8015000a>] 0x8015000a
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.837825] [<803c4efc>] 0x803c4efc
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.841318] [<803c6f34>] 0x803c6f34
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.844788] [<803a98a0>] 0x803a98a0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.848313] [<803d1bc0>] 0x803d1bc0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.851802] [<803d2f18>] 0x803d2f18
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.855307] [<8e86426c>] 0x8e86426c [nf_conntrack_ipv4@8e864000+0x1420]
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.861893] [<803a9da0>] 0x803a9da0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.865406] [<803aa078>] 0x803aa078
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.868887] [<803a9940>] 0x803a9940
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.872360] [<803a9c10>] 0x803a9c10
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.402270] ------------[ cut here ]------------
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.406908] WARNING: CPU: 1 PID: 0 at net/ipv4/tcp_output.c:2509 0x803cc8bc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.413864] invalid inflight: 1 state 1 cwnd 10 mss 1388
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.419148] Modules linked in: qcserial pppoe ppp_async option cdc_mbim usb_wwan sierra_net sierra rndis_host qmi_wwan pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cdc_ncm cdc_ether xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT wireguard usbserial usbnet usblp ts_fsm ts_bm slhc nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.489628]  nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda nf_conntrack iptable_raw iptable_mangle iptable_filter ip_tables crc_ccitt cdc_wdm cdc_acm fuse ledtrig_usbport gpio_beeper input_core xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ip6_udp_tunnel udp_tunnel tun vfat fat nls_utf8 nls_iso8859_1 nls_cp437 uas usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd ehci_platform
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.561103]  sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4 mbcache jbd2 usbcore nls_base usb_common mii crc32c_generic
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.572189] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.14.143 #0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.578264] Stack : 00000000 00000000 00000000 81222398 00000000 00000000 00000000 00000000
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.586600]         00000000 00000000 00000000 00000000 00000000 00000001 8fc0bd30 ac07f596
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.594938]         8fc0bdc8 00000000 00000000 00004f18 00000038 8049db58 00000007 00000000
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.603273]         00000000 80550000 0008bb1d 00000000 8fc0bd10 00000000 80570000 8050c6a0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.611605]         803cc8bc 000009cd 812223d8 81222398 00000000 802af9e8 00000004 805b0004
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.619937]         ...
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.622376] Call Trace:
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.622394] [<8049db58>] 0x8049db58
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.628288] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.631755] [<802af9e8>] 0x802af9e8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.635228] [<800101a0>] 0x800101a0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.638699] [<800101a8>] 0x800101a8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.642170] [<80486a9c>] 0x80486a9c
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.645638] [<800758a0>] 0x800758a0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.649107] [<80032588>] 0x80032588
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.652580] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.656052] [<80032610>] 0x80032610
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.659528] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.663008] [<803cf3d0>] 0x803cf3d0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.666478] [<8009d750>] 0x8009d750
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.669947] [<803cf7a8>] 0x803cf7a8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.673420] [<8009dd80>] 0x8009dd80
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.676890] [<803cf770>] 0x803cf770
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.680358] [<8008c2cc>] 0x8008c2cc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.683829] [<80063018>] 0x80063018
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.687300] [<8008c588>] 0x8008c588
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.690768] [<8007cee8>] 0x8007cee8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.694244] [<804a49b8>] 0x804a49b8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.697717] [<80036f14>] 0x80036f14
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.701185] [<8025d440>] 0x8025d440
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.704662] [<8000b488>] 0x8000b488
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.708131]
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.709665] ---[ end trace 0dde230055179878 ]---
12.11.20192593Base systemBug ReportVery LowHighno AC wifi with ath10k on 19.07-rc1openwrt-19.07Waiting on reporter Task Description

- Archer C7, Netgear R7800
- 19.07-RC1 default
- install image, configure wifi, try to connect, in my case i’m getting 300Mbps rate, others report as low as up to 54 (legacy only)

 

R7800 report: https://forum.openwrt.org/t/openwrt-19-07-0-first-release-candidate/48040/33

Archer C7 v2 report: https://forum.openwrt.org/t/openwrt-19-07-rc1-archer-c7-v2-5g-wifi-died-after-trying-to-change-channels/48182/7

the situation is the same with intree 4.9.200 driver or any of the latest backports installed on client PC

18.11.20192614KernelBug ReportVery LowHighath10k 5 GHz connectivity issues for some client device...openwrt-19.07Researching Task Description

* - Device problem occurs on TP-Link Archer C2600.

* - Software version of OpenWrt 19.07-rc1 and older 19.07.

* - From the first version, which I tested after the release of 19.07, I have a problem with 5GHz radio / Wi-Fi. On two devices: LG OLED B8 55 “OTT and Cyfrowy Polsat STB OTT does not work internet. Both devices connect to the network, but do not have access to the Internet. In the connection diagnostics on the TV, the message pops up that it is a DNS error. On 2.4 GHz Wi-Fi everything is fine.

* - I have reverted to the 18.06 to fix the problem for now.


01.12.20192647Base systemBug ReportVery LowHighEA6350v3 (IPQ4018) memory usage climbs until processes ...openwrt-19.07Unconfirmed Task Description

Device is Linksys EA6350v3

Issue occurs on 19.07 rc1, 19.07 rc2 and snapshot r11595 (snapshot version is by memory, but pretty sure that’s what I had on it).

Information for this bug report is based on 19.07 rc2 with the following packages installed for future potential use, but most not in use:
luci-app-sqm luci-proto-wireguard luci-app-wireguard ca-bundle curl https_dns_proxy luci-app-https_dns_proxy luci-app-statistics luci-app-samba kmod-usb-printer p910nd luci-app-p910nd diffutils minidlna luci-app-minidlna

Note: sqm, wireguard, https_dns_proxy, samba, usb printer, p910nd server, and minidlna are NOT in use. These are just the typical packages I add to my
router for future use.

Steps to reproduce:
Problem occurs after router runs for a few hours. EA6350v3 is set up as a wired access point for an EdgeRouter X (also on 19.07 rc2). The Edgerouter provides sqm and DNS and DHCP for LAN, guest and IOT VLANs. There are ~3 “Guest” 2.4 G wifi clients (a smart switch, an IP camera, a DEEBOT vacuum); the IOT VLAN is mapped to a physical port with an Ooma Telo plugged in (I know - I need to map the guest devices to IOT wifi someday...). The LAN is mapped to a physical port with a Roku 3 plugged in and to normal wifi. There are another ~4 or 5 5GHz wifi clients on the LAN wifi (a laptop, a couple Amazon Echo’s, a Google Home Mini, a Samsung Orbit Android phone) and a 2.4G LG Android phone on the 2.4 GHz wifi. CPU loading is quite low.

Memory usage starts out rather high (~100MB, climbs and climbs, eventually drops, climbs again, repeats. Eventually (a day or two) processes start getting killed to free up memory and things start dying. I have an EA8500 setup almost identically as a second AP in the house, and it’s memory usage sits around 50 MB versus 100MB to 200+MB for the EA6350v3. Something’s just not right...

The final message in the logs that repeats until processes begin to get killed is:

kern.warn kernel: [15897.905286] ath10k_ahb a000000.wifi: failed to increase tx pending count: -16, dropping

But the weird memory usage pattern precedes this message in the logs.

I’ve attached memory usage graphs and system and kernel logs from 19.07 rc2 to illustrate the problem. rc1 and snapshot behaved the same. This post also has logs showing processes getting killed if that helps diagnose: https://forum.openwrt.org/t/ipq4018-linksys-ea6350v3-wifi-dead-after-24-48-hrs/49080/3?u=eginnc

12.12.20192670KernelBug ReportVery LowHigh[ATH79] unstable USB on WR1043 v2openwrt-19.07Unconfirmed Task Description

Hi there!

I recently upgraded my TP-Link TL-WR1043 v2 device to the ath79 targeted 19.07-rc2 release using my custom build, which I have compiled with the image builder.

make image PROFILE=tplink_tl-wr1043nd-v2 PACKAGES="block-mount curl diffutils ethtool iperf3 iwinfo htop kmod-fs-ext4 kmod-usb-storage luci mailsend-nossl minidlna nfs-kernel-server ppp-mod-pppoe shadow-su transmission-daemon-mbedtls transmission-web vsftpd zram-swap -ip6tables -kmod-ip6tables -kmod-ipv6 -kmod-nf-conntrack6 -kmod-nf-ipt6 -libopenssl1.1 -odhcp6c -odhcpd-ipv6only -luci-proto-ipv6 -libip6tc2"

I just recently rolled back to an EXT4 partition, because of it's smaller memory footprint. (just mounting a ~50GB f2fs partition consumes around 10MBs of memory)
So in the very first attempt I wanted to copy back everything to my Transcend 790K. But after the first 500-1000 MBs(mix of archives, image, text and video files), the transaction speed has fallen down couple of times. I thought maybe the passive FTP connection was the problem, because after a few automatic reconnect attempts, the speed of the copy has been normalized again and in the end the device was connected. Later I found that the USB devices was reseted.
I had another try with a Sandisk Ultra Fit drive (SDCZ-43), but the result and the configuration was pretty sam. ~50GB EXT4 partition without journal and without barrier.
I force upgraded the machine to the ar71xx target and Filezilla so far copied back 16GBs without any problem.
Target ATH79 seem to be has so many problems with the USB subsystem, please see my other bugreport for the WDR4300 as well: FS#2567 - [ATH79] USB speed degradation on WDR4300.

Let me know if I can help the bughunting any way,
thanks and regards!

16.12.20192679KernelBug ReportHighHighBad 5 GHz Wi-Fi performance with some wireless NICs (ho...openwrt-19.07Researching Task Description

Supply the following if possible:

- Device problem occurs on
Zyxel NBG6617 and possibly others based on reports in https://forum.openwrt.org/t/openwrt-19-07-0-second-release-candidate/49593/24

- Software versions of OpenWrt/LEDE release, packages, etc.

19.07 release and snapshot

- Steps to reproduce
Flash 19.07rcX release image, connect to 5Ghz wifi and check throughput(preferably with a 802.11ac adapter) → the max throughput is very low (~10Mbps) and big spikes in lag which makes even a SSH connection unusable

I put my test details also in the forum post: https://forum.openwrt.org/t/zyxel-nbg6617-ipq4019-regression-in-wifi-5ghz/50544/3

I did some bisecting and found that the hostapd-2.9 upgrade was the reason. When I reverted the patch and rebuild the performance was good again.

09.01.20202719Base systemBug ReportVery LowHighBuffalo WBMR-HP-G300H: DSL does not connect at all with...openwrt-19.07Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on: Buffalo WBMR-HP-G300H
- Software versions of OpenWrt/LEDE release, packages, etc.: OpenWRT 19.07, kmod-ltq-adsl-ar9-fw-a 0.1-1, which shows up as 4.4.4.0.0.1 in dsl_control status.
- Steps to reproduce:

1. Get an ADSL line from Rostelecom.
2. Upgrade the router to OpenWRT 19.07.
3. Reboot.

Result: DSL does not connect. In /etc/init.d/dsl_control status, it goes through all phases, then briefly shows as “Up”, but then the “dsl0” interface is not created, and the following lines are logged in dmesg:

 [   56.597766] [DSL_BSP_Showtime 914]: Datarate US intl = 1024000, fast = 0
 [   56.603091] [DSL_BSP_Showtime 934]: no hookup from ATM driver to set cell rate

The error does not exist with the 4.5.4.9.1.1 firmware obtained from unofficial sources. The bug has been submitted through the affected ADSL line with the unofficial firmware.

Status:

# /etc/init.d/dsl_control status
ATU-C Vendor ID: Broadcom 161.149
ATU-C System Vendor ID: 00,00,00,00,00,00,00,00
Chipset: Ifx-AR9
Firmware Version: 4.5.4.9.1.1
API Version: 3.24.4.4
XTSE Capabilities: 0×4, 0×0, 0×0, 0×0, 0×0, 0×0, 0×0, 0×0 Annex: A
Line Mode: G.992.1 (ADSL)
Profile:
Line State: UP [0×801: showtime_tc_sync]
Forward Error Correction Seconds (FECS): Near: 413342 / Far: 0
Errored seconds (ES): Near: 0 / Far: 0
Severely Errored Seconds (SES): Near: 0 / Far: 0
Loss of Signal Seconds (LOSS): Near: 0 / Far: 0
Unavailable Seconds (UAS): Near: 253 / Far: 253
Header Error Code Errors (HEC): Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P): Near: / Far:
Pre-emtive CRC errors (CRCP_P): Near: / Far:
Power Management Mode: L0 - Synchronized
Latency [Interleave Delay]: 8.0 ms [Interleave] 8.0 ms [Interleave]
Data Rate: Down: 9.952 Mb/s / Up: 1.024 Mb/s
Line Attenuation (LATN): Down: 32.2 dB / Up: 19.5 dB
Signal Attenuation (SATN): Down: 32.6 dB / Up: 19.5 dB
Noise Margin (SNR): Down: 6.1 dB / Up: 13.0 dB
Aggregate Transmit Power (ACTATP): Down: 20.0 dB / Up: 12.3 dB
Max. Attainable Data Rate (ATTNDR): Down: 8.848 Mb/s / Up: 1.204 Mb/s
Line Uptime Seconds: 1164
Line Uptime: 19m 24s

(yes, very bad line)

Config:

config atm-bridge ‘atm’

option vpi '1'
option encaps 'llc'
option payload 'bridged'
option nameprefix 'dsl'
option vci '50'
option unit '0'
option atmdev '0'

config dsl ‘dsl’

option annex 'a'
option firmware '/lib/firmware/dsl_ar9_firmware_adsl_a-04.05.04.09.01.01.bin'

config interface ‘wan’

option ifname 'dsl0'
option proto 'pppoe'
option ipv6 '1'
option username 'censored'
list dns '8.8.8.8'
list dns '8.8.4.4'
option peerdns '0'
option keepalive '60 5'
option password 'censored'
10.01.20202723Base systemBug ReportVery LowHighAfter libubus/ubox: procd - failed to open/remove pidfi...openwrt-19.07Assigned Task Description

Device problem occurs on Turris Omnia (mvebu), Turris MOX (aarch64).
OpenWrt 19.07 and the latest OpenWrt master branch.

How to reproduce it?

Master:

# opkg list-installed | grep ubus
libubus - 2020-01-05-d35df8ad-1.0
libubus-lua - 2020-01-05-d35df8ad-1.0
python3-ubus - 0.1-3.8-1.7
ubus - 2020-01-05-d35df8ad-1.0
ubusd - 2020-01-05-d35df8ad-1.0

# opkg list-installed | grep libubox
libubox - 2019-12-28-cd75136b-1.0

Find any package which has in init script hard coded path for pid file

procd_set_param pidfile 

E.g. Install i2pd package and run:

/etc/init.d/i2pd start

Then stop it:

/etc/init.d/i2pd stop

And here you go, the router crashes:

[  587.264257] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
[  587.264257] 
[  587.273419] CPU1: stopping
[  587.276135] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.19.93 #0
[  587.282153] Hardware name: Marvell Armada 380/385 (Device Tree)
[  587.288098] [<c010f2e0>] (unwind_backtrace) from [<c010b208>] (show_stack+0x10/0x14)
[  587.295862] [<c010b208>] (show_stack) from [<c085f240>] (dump_stack+0x94/0xa8)
[  587.303103] [<c085f240>] (dump_stack) from [<c010dfe4>] (handle_IPI+0xf0/0x19c)
[  587.310435] [<c010dfe4>] (handle_IPI) from [<c052e648>] (gic_handle_irq+0x8c/0x90)
[  587.318024] [<c052e648>] (gic_handle_irq) from [<c0101a0c>] (__irq_svc+0x6c/0x90)
[  587.325523] Exception stack(0xef09bf60 to 0xef09bfa8)
[  587.330587] bf60: 00000000 001bda5c ef6e12c4 c0114fc0 ffffe000 c0d03c6c c0d03cac 00000002
[  587.338783] bf80: 00000000 c0d03c48 c0c4d628 00000000 2ea95000 ef09bfb0 c0108644 c0108648
[  587.346977] bfa0: 60000013 ffffffff
[  587.350478] [<c0101a0c>] (__irq_svc) from [<c0108648>] (arch_cpu_idle+0x34/0x38)
[  587.357898] [<c0108648>] (arch_cpu_idle) from [<c0150950>] (do_idle+0xf4/0x1f0)
[  587.365226] [<c0150950>] (do_idle) from [<c0150ccc>] (cpu_startup_entry+0x18/0x1c)
[  587.372814] [<c0150ccc>] (cpu_startup_entry) from [<001023ec>] (0x1023ec)
[  587.380295] Rebooting in 3 seconds..

With this issue, we have been able to reproduce another issue with the package fosquitto, which is not available in OpenWrt feeds. In the init script, we commented out procd_set_param pidfile and then restart the process, we see these rows in the system log.

Jan 10 17:32:51 turris procd: Failed to removed pidfile: ������t.d/fosquitto: No such file or directory
Jan 10 17:32:51 turris procd: failed to open pidfile for writing: ������t.d/fosquitto: No such file or directory

I'm sure that this can be reproduced with other packages from packages feed as well.

This happens after the latest changes in libubox and ubus. Anyway, it was not a good idea to include the latest changes in libubox and ubus 2 days before tagging the OpenWrt 19.07. Reverting to libubox to 2019-10-29 and ubus to 2018-10-06 helps for both issues.

12.01.20202730KernelBug ReportVery LowHighTL-WR841N v8 ath79 Link Unstableopenwrt-19.07New Task Description

Probably related to https://bugs.openwrt.org/index.php?do=details&task_id=2216 which was reported almost a year ago. The bug is still not fixed though.

Are there any plans to fix it or will 18.06 be the last stable version for this and probably other devices?

[8451.981464] eth1: link up (100Mbps/Full duplex)
[37071.909045] eth1: link down
[37072.988861] eth1: link up (100Mbps/Full duplex)
[48492.291332] eth1: link up (10Mbps/Half duplex)
[48632.691559] eth1: link up (100Mbps/Full duplex)
[55697.449886] eth1: link down
[55698.491082] eth1: link up (100Mbps/Full duplex)
[62395.095374] eth1: link up (10Mbps/Half duplex)
[62507.411488] eth1: link up (100Mbps/Full duplex)
[62726.853998] eth1: link up (10Mbps/Half duplex)
[62732.053093] eth1: link up (100Mbps/Full duplex)
[71071.460663] eth1: link down
[71072.618285] eth1: link up (100Mbps/Full duplex)
[73435.556373] eth1: link down
[73436.597169] eth1: link up (100Mbps/Full duplex)
[73547.879987] eth1: link up (10Mbps/Half duplex)
[73558.277169] eth1: link up (100Mbps/Full duplex)
[74438.121970] eth1: link down
[74439.162824] eth1: link up (100Mbps/Full duplex)
[75341.889076] eth1: link up (10Mbps/Half duplex)
[75352.290230] eth1: link up (100Mbps/Full duplex)
[76274.772404] eth1: link down
[76275.813134] eth1: link up (100Mbps/Full duplex)

13.01.20202733Base systemBug ReportVery LowHighAth79 firmware accident enter to failsafe mode when reb...openwrt-19.07Unconfirmed Task Description

Sometime when reboot/reflash router, I see serial console messages:

[    5.868712] init: - preinit -
[    5.960699] random: procd: uninitialized urandom read (4 bytes read)
[    6.909058] random: jshn: uninitialized urandom read (4 bytes read)
[    7.327749] random: jshn: uninitialized urandom read (4 bytes read)
[    7.567130] random: jshn: uninitialized urandom read (4 bytes read)
[    7.638687] random: jshn: uninitialized urandom read (4 bytes read)
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[    9.860896] eth0: link up (1000Mbps/Full duplex)
- failsafe button rfkill was pressed -
- failsafe -
[   12.309911] urandom_read: 3 callbacks suppressed
[   12.309921] random: dropbearkey: uninitialized urandom read (32 bytes read)
Generating 1024 [   12.323834] random: dropbearkey: uninitialized urandom read (32 bytes read)
bit rsa key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgQCKZVT/UJoTHz2CkNHrYmfzzBDfa/6Yd6+LJVcrURD15lbN3ch7AG/tc/ZolkeOrqkKD6dM2h4TsYv4+)
Fingerprint: sha1!! b9:a4:d3:94:71:b3:34:ae:a3:85:c8:e9:a7:c8:63:fd:74:52:5e:ad


BusyBox v1.30.1 () built-in shell (ash)

ash: can't access tty; job control turned off
  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 19.07-SNAPSHOT, r10868-08d9828b76
 -----------------------------------------------------
================= FAILSAFE MODE active ================

I noticed when wifi on/off switch on router is on, sometime it accident enter failsafe mode. If switch to off, it’s not happen.
Issue happens with 841n v8/v9/v10 & 841hp v3 (same hardware as v9/10) model.


09.02.2017488Base systemBug ReportVery LowMediumdynamic VLAN doesn't work on ath10kopenwrt-19.07Unconfirmed Task Description

Dynamic vlan config on ath10k seems not to work. Same config on ath9k works fine.

Config:

config wifi-device  radio0
        option type     mac80211
        option channel  36
        option hwmode   11a
        option path     'pci0000:01/0000:01:00.0'
        option htmode   VHT80
[...]

config wifi-iface
        option device   radio0
        option network  vlan1
        option mode     ap
[...]
        option dynamic_vlan     '1'
        option 'vlan_tagged_interface' 'eth1'
        option 'vlan_bridge' 'br-vlan'
        option 'vlan_naming' '0'

Log:

Thu Feb  9 15:54:37 2017 daemon.err hostapd: WPA initialization for VLAN 1 failed (-1)
Thu Feb  9 15:54:37 2017 daemon.err hostapd: WPA deinit of wlan0.1 failed
Thu Feb  9 15:54:37 2017 daemon.debug hostapd: wlan0: STA ac:22:0b:a1:c7:6b IEEE 802.11: could not add dynamic VLAN interface for vlan=1
25.10.20192567KernelBug ReportVery LowMedium[ATH79] USB speed degradation on WDR4300openwrt-19.07Assigned Task Description

Hello!

I experience huge speed loss on the lastest build (Thu Oct 24 21:58:18 2019) using the ath79 snapshot image builder. I had the same problem on the ~2 weeks earlier build as well, just wanted to have a try on the up to date version now.
Built configuration on both 18.04.6 and 19.07:
PROFILE=tplink_tl-wdr4300-v1 PACKAGES=”block-mount diffutils f2fs-tools kmod-fs-f2fs kmod-mtd-rw kmod-usb-storage luci mailsend-nossl minidlna nfs-kernel-server ppp-mod-pppoe shadow-su transmission-daemon-mbedtls transmission-remote-mbedtls vsftpd usbreset zram-swap -ip6tables -kmod-ip6tables -kmod-ipv6 -kmod-nf-conntrack6 -kmod-nf-ipt6 -libopenssl1.1 -odhcp6c -odhcpd-ipv6only -luci-proto-ipv6 -libip6tc2”

Drive: Kingston DT G3 32GB (old one, better quality with Intel MLC flash)
Firewall: w and w/o flow offload on 19.07
Model: TP-Link WDR4300 v1

File read speeds:
18.06.4 orig vstpd 542M 75s 7,2MB/s
18.06.4 pepe2k vstpd 542M 64s 7,2MB/s
19.07 pepe2k vstpd 542M 543s 1,0MB/s
19.07 pepe2k dd+nc 256M 321s 0,8MB/s

- During the measurement, no root overlay was in use, just a general filesystem was attached
- lower speeds are really close to USB 1.x standard
- measurements took on fresh installations
- the degradation exists if only one drive is attached
- the degradation exists on both filesystem and block level.

I’m using pepe2k’s uboot image (CPU clocked to 600MHz). However I didn’t revert the uboot partition now, I did for a few weeks, nothing has changed.

Let me know if I can help the troubleshooting anyway. Dmesg logs are attached for all mentioned configurations (18.06.4 orig, 18.06.4 pepe2k, 19.07 pepe2k).

Best regards

23.11.20192623Base systemBug ReportVery LowMediumJumbo Frames not possible on Archer C7 v5openwrt-19.07Unconfirmed Task Description

ip link set mtu 9000 dev eth0
RTNETLINK answers: Invalid argument

swconfig dev eth0 show

no sign of jumbo frames.

Only a payload of 1474 can be transmitted over a mtu 9000 core network, effectively.

Related issue:
https://dev.archive.openwrt.org/ticket/18296

25.11.20192628KernelBug ReportVery LowMediumKernel warning: eth0 (mtk_soc_eth): transmit queue 0 ti...openwrt-19.07Unconfirmed Task Description

Model ZBT-WG3526 (16M)
Architecture - MediaTek MT7621 ver:1 eco:3
Firmware version - OpenWrt 19.07-SNAPSHOT r10731-e68d589e7b / LuCI openwrt-19.07 branch git-19.326.61751-179c5e8
Kernel version- 4.14.155

 Mon Nov 25 10:11:25 2019 kern.info kernel: [  106.762093] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Mon Nov 25 10:11:25 2019 kern.info kernel: [  106.770348] br-VLAN8: port 2(wlan1) entered blocking state
Mon Nov 25 10:11:25 2019 kern.info kernel: [  106.775981] br-VLAN8: port 2(wlan1) entered forwarding state
Mon Nov 25 10:11:25 2019 kern.info kernel: [  106.784594] br-VLAN6: port 3(wlan1-1) entered blocking state
Mon Nov 25 10:11:25 2019 kern.info kernel: [  106.790393] br-VLAN6: port 3(wlan1-1) entered disabled state
Mon Nov 25 10:11:25 2019 kern.info kernel: [  106.796955] device wlan1-1 entered promiscuous mode
Mon Nov 25 10:11:25 2019 kern.info kernel: [  106.803794] IPv6: ADDRCONF(NETDEV_UP): wlan1-1: link is not ready
Mon Nov 25 10:11:25 2019 kern.info kernel: [  106.810026] br-VLAN6: port 3(wlan1-1) entered blocking state
Mon Nov 25 10:11:25 2019 kern.info kernel: [  106.815820] br-VLAN6: port 3(wlan1-1) entered forwarding state
Mon Nov 25 10:11:25 2019 kern.info kernel: [  107.343567] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1-1: link becomes ready
Mon Nov 25 11:10:20 2019 kern.info kernel: [ 3641.266434] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based  firewall rule not found. Use the iptables CT target to attach helpers instead.
Mon Nov 25 11:37:14 2019 kern.info kernel: [ 5255.651116] TCP: request_sock_TCP: Possible SYN flooding on port 88. Sending cookies.  Check SNMP counters.
Mon Nov 25 11:41:29 2019 kern.warn kernel: [ 5510.958004] ------------[ cut here ]------------
Mon Nov 25 11:41:29 2019 kern.warn kernel: [ 5510.962647] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:320 0x8038e1c0
Mon Nov 25 11:41:29 2019 kern.info kernel: [ 5510.969709] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 0 timed out
Mon Nov 25 11:41:29 2019 kern.warn kernel: [ 5510.976660] Modules linked in: qcserial pppoe ppp_async option cdc_mbim usb_wwan sierra_net sierra rndis_host qmi_wwan pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 mt76x2e mt76x2_common mt76x02_lib mt7603e mt76 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_ncm cdc_ether xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_FLOWOFFLOAD xt_DSCP xt_CT xt_CLASSIFY wireguard usbserial usbnet usblp ts_fsm ts_bm slhc nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4
Mon Nov 25 11:41:29 2019 kern.warn kernel: [ 5511.047339]  nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda nf_conntrack iptable_raw iptable_mangle iptable_filter ipt_ECN ip_tables crc_ccitt compat cdc_wdm cdc_acm fuse ledtrig_usbport xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT
Mon Nov 25 11:41:29 2019 kern.warn kernel: [ 5511.118581]  x_tables nf_reject_ipv6 ip6_udp_tunnel udp_tunnel tun vfat fat nls_utf8 nls_iso8859_1 nls_cp437 uas mmc_block usb_storage mtk_sd mmc_core leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd ahci libahci libata ehci_platform sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4 mbcache jbd2 usbcore nls_base usb_common mii crc32c_generic
Mon Nov 25 11:41:29 2019 kern.warn kernel: [ 5511.149081] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.14.155 #0
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.155177] Stack : 00000000 00000000 00000000 8fe6d540 00000000 00000000 00000000 00000000
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.163556]         00000000 00000000 00000000 00000000 00000000 00000001 8fc0bd60 ac07f582
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.171942]         8fc0bdf8 00000000 00000000 000093c8 00000038 8049e458 00000008 00000000
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.180305]         00000000 80550000 00024659 00000000 8fc0bd40 00000000 00000000 8050c830
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.188647]         8038e1c0 00000140 00000001 8fe6d540 00000000 802b02b8 00000004 805b0004
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.196980]         ...
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.199415] Call Trace:
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.199535] [<8049e458>] 0x8049e458
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.205440] [<8038e1c0>] 0x8038e1c0
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.208923] [<802b02b8>] 0x802b02b8
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.212412] [<800101a0>] 0x800101a0
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.215881] [<800101a8>] 0x800101a8
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.219354] [<804873a4>] 0x804873a4
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.222825] [<800759a0>] 0x800759a0
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.226315] [<800325b8>] 0x800325b8
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.229802] [<8038e1c0>] 0x8038e1c0
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.233316] [<80032640>] 0x80032640
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.236785] [<800d20e8>] 0x800d20e8
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.240287] [<8038e1c0>] 0x8038e1c0
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.243757] [<8009d860>] 0x8009d860
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.247237] [<8038e014>] 0x8038e014
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.250711] [<8008c3dc>] 0x8008c3dc
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.254181] [<80063108>] 0x80063108
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.257662] [<8008c698>] 0x8008c698
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.261136] [<8007cfe8>] 0x8007cfe8
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.264627] [<804a5240>] 0x804a5240
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.268102] [<80036f74>] 0x80036f74
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.271573] [<8025daf0>] 0x8025daf0
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.275054] [<8000b488>] 0x8000b488
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.278548]
Mon Nov 25 11:41:30 2019 kern.warn kernel: [ 5511.280144] ---[ end trace f0b0ca1dd55db7a7 ]---
Mon Nov 25 11:41:30 2019 kern.err kernel: [ 5511.284782] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out
Mon Nov 25 11:41:30 2019 kern.info kernel: [ 5511.291016] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000065
Mon Nov 25 11:41:30 2019 kern.info kernel: [ 5511.297053] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=0dc00000, max=0, ctx=1789, dtx=1789, fdx=1788, next=1789
Mon Nov 25 11:41:30 2019 kern.info kernel: [ 5511.307977] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=0db60000, max=0, calc=893, drx=894
Mon Nov 25 11:41:30 2019 kern.info kernel: [ 5511.321091] mtk_soc_eth 1e100000.ethernet: 0x100 = 0x6060000c, 0x10c = 0x80818
Mon Nov 25 11:41:30 2019 kern.info kernel: [ 5511.334877] mtk_soc_eth 1e100000.ethernet: PPE started

25.11.20192631Base systemBug ReportVery LowMediumsysntp often fails when using DHCP provided serveropenwrt-19.07Unconfirmed Task Description

I’m managing a network with 25 openwrt WLAN access points (mostly TL-WR1043ND v1, a few v2 and a few zbt-2626) and since updating to 19.07 some devices often have an incorrect time. All are configured to get their NTP server from DHCP and this happen on all models.

When this happen ntpd is simply not running and starting it restore the correct time right away. It is hard to says if ntpd crash or if it never started in the first place. Last time I checked all affected devices had been restarted recently so I would first suspect some race condition during boot.

29.11.20192641KernelBug ReportVery LowMediumDevice file for USB does not appear /dev/ttyUSB*openwrt-19.07Waiting on reporter Task Description

With new version 19.07.0rc I could not make my USB cellular (3g) modem dongle to work due to it simply no any serial device like /dev/ttyUSB* file appear with insertion.
In kernel log it appears report about new device insertion and nothing happenings after.
I made several attempts, with ‘modeswitch’ or without and several other ‘mods’ the result is the same no any /dev/ttyUSB*
With other version it was not such problem it appeared exactly three /dev/ttyUSB0 /dev/ttyUSB1 /dev/ttyUSB2 es well as on my Ubuntu 19.04 And Ubuntu 16.04 Ubuntu 18.04

Both router and dongle are USB-2
Actually router is Asus RT-N16
and modem dongle is Alcatel One Touch X090S

P.S. I need this one to be solved to report other bugs. :)

09.12.20192666Base systemBug ReportVery LowMediumprocd: reboot inside lxc container causes shutdownopenwrt-19.07Assigned Task Description

- Device problem occurs on
armvirt64
- Software versions of OpenWrt/LEDE release, packages, etc.
openwrt-19.07-rc2
- Steps to reproduce

Create a lxc package from the openwrt-19.07-rc2 rootfs package.
Start a lxc container using the openwrt lxc package.
Initiate a `reboot` command from inside the container.

Expected result: Container reboots.
Actual result: Container halts.

Current Version openwrt-19.07-rc2.
While running in a lxc container, initiating a reboot from openwrt results in a shutdown of the container instead of rebooting the container.

This appears to have been caused by commit <832369078d818d19ab64051fdc8da9e06c90ad88> state: fix shutdown when running in a container ( FS#2425 ).
Instead of triggering reboot(reboot_event);, it detects that it is inside a container and exits pid 1, resulting in the container halting.

There is a patch at [0] to resolve this, but would likely break the original intention of the fix above.

10.12.20192667Base systemBug ReportVery LowMediumLantiq specific, "dsl interfae" VDSL driver, unhelpful ...openwrt-19.07Unconfirmed Task Description

Probably, FAO "John Crispin" Lantiq maintainer, apparently!,

On OpenWRT 19.07.0rc2, both on TP-LINK TD-W8980 and also BT-Homehub-v5-type-A [lantiq xrx200 devices] ...

I am finding a consistent frustrating limitation, that the default config, and LuCI web interface, does not provide any way to expose the MTU capability of the built-in VDSL driver, which allows for full 1500 MTU to be carried on PPPoE on VDSL, as is commonplace in provided routers.

Specifically, the VDSL device "dsl0" (and, in my case, VLAN 101, "dsl0.101"), has an unhelpful default MTU restriction to 1500, such that PPPoE (as is common in UK!) does not work at the normally expected 1500MTU, requiring workarounds 1492MTU MSS-clamping hacks. Turns out this is fixable at the configuration-level, but not via anything exposed in web-interface (as underlying DSL MTU is wrong from the start...).

Example below, extra /etc/config/network lines to support the standard MTU:-

config interface 'wan'

      option ifname 'dsl0.101'
      option proto 'pppoe'
      option password 'PASSWORD'
      option ipv6 'auto'
      option username 'USERNAME'
      option mtu '1500'           #exposed via web, still needs setting, to try to negotiate that MTU 1500 inside PPPoE...

config device 'wan_dev'

      option name 'dsl0'
      option macaddr 'e8:11:22:33:44:4b'
      option mtu '1508'           #This line Had to be added manually

config device 'wan_dev2' # Extra section added, if not done,

      option name 'dsl0.101'             #  MTU wrong for the dsl 0.101 link!
      option macaddr 'e8:11:22:33:44:4b' #  As in this case having to use VLAN101
      option mtu '1508'                  #  As per UK Openreach VDSL configuration...

In my view, at the very least, the 'internal' DSL driver, should be allowing a larger mtu like 1508, 'by default'. Possibly, if this is done at driver level, the PPPoE MTU won't need to be specified at all.

The PPPoE over VDSL configuration, also needed to be told to attempt 1500 MTU, which I understand relies upon rfc4638 PPP extension, in order to have fully functional 1500MTU connection. Not having this has caused connectivity issues requiring MSS clamping etc. and is, in short, undesirable!.

It think, the PPPoE over PTM over VDSL should, additionally, attempt this 1500-MTU 'by default' unless the MTU is reduced manually in the configuration.

I understand this should be passed to Lantiq maintainer, "John Crispin" apparently!, according to IRC-discussions!.

With many thanks,

25.12.20192694Base systemBug ReportVery LowMediumClearfog Pro: Default LAN / WAN Interface assignment is...openwrt-19.07Unconfirmed Task Description

On my Clearfog Pro Rev 2.0 the interfaces map as follows:

eth0: switch
eth1: SFP
eth2: standalone ethernet

This does not match the current description in /etc/board.d/02_network:

# eth0 is standalone ethernet
# eth1 is switch (-pro) or standalone ethernet (-base)
# eth2 is SFP
ucidef_set_interfaces_lan_wan "eth1" "eth0 eth2"

While I don’t agree with the lan/wan decision made here, at least the comment should match reality.
So I suggest changing it to:

# eth2 is standalone ethernet
# eth0 is switch (-pro) or standalone ethernet (-base)
# eth1 is SFP
ucidef_set_interfaces_lan_wan "eth0 eth1" "eth2"

Please also see the attached patch file, which also changes the switch configuration accordingly.

28.12.20192702KernelBug ReportVery LowMediumPerformance degradation after kernel.warn ath10k_core@8...openwrt-19.07Unconfirmed Task Description

Supply the following if possible:

- Device problem occurs on
Archer C7v2

- Software versions of OpenWrt/LEDE release, packages, etc.
OpenWrt 19.07-rc.2

[---] PACKAGES INSTALLED
echo [INFO] Downloading package information ...
opkg update
#
echo [INFO] Removing packages ...
opkg remove wpad-basic
#
echo [INFO] Installing packages ...
opkg install bash
opkg install block-mount
opkg install curl
opkg install e2fsprogs
opkg install htop
# opkg install igmpproxy
opkg install kmod-br-netfilter
opkg install kmod-fs-ext4
opkg install kmod-fs-msdos
opkg install kmod-fs-ntfs
opkg install kmod-scsi-core
opkg install kmod-usb-storage
opkg install libncurses
opkg install libpcre
opkg install lua luafilesystem
opkg install luci-mod-rpc
opkg install luci-proto-relay
opkg install mailsend
opkg install nano
opkg install relayd
opkg install rpcd
opkg install terminfo
opkg install tcpdump
opkg install uhttpd-mod-ubus
opkg install vsftpd
opkg install wget
opkg install wpad
#
# batman-adv
opkg install kmod-batman-adv
opkg install batctl-full
[---]

- Steps to reproduce
Today worked on batman-adv via ad-hoc between two devices. Device A has LAN to bat0, batman-adv works over ad-hoc wifi, Device B has bat0 to LAN. (Device B has only one wired client behind)
Both devices (Archer C7v2 with OpenWrt 19.07-rc.2) had multiple crashes of the below printed type resulting in only 10 MBit/s download speed on the computer attached via LAN to Device B. Before the kernel.warn log line appeared on one of the APs, the speed was full 100 MBit/s. As soon I reboot the “kernel.warn”ing AP, the speed is 100 MBit again. bat0 is bridged to eth0.101 on both ends.

 
Sat Dec 28 14:50:04 2019 daemon.notice hostapd: wlan0-1: AP-ENABLED
Sat Dec 28 14:50:05 2019 kern.info kernel: [ 2416.392454] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sat Dec 28 14:50:05 2019 daemon.notice wpa_supplicant[16106]: Successfully initialized wpa_supplicant
Sat Dec 28 14:50:06 2019 kern.info kernel: [ 2417.755684] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sat Dec 28 14:50:06 2019 daemon.notice wpa_supplicant[16106]: Note: nl80211 driver interface is not designed to be used with ap_scan=2; this can result in connection failures
Sat Dec 28 14:50:06 2019 daemon.notice wpa_supplicant[16176]: wlan0: Trying to associate with SSID 'Permakultur'
Sat Dec 28 14:50:06 2019 kern.info kernel: [ 2417.950938] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2417.991646] ------------[ cut here ]------------
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2417.996394] WARNING: CPU: 0 PID: 16176 at /builder/shared-workdir/build/build_dir/target-mips_24kc_musl/linux-ath79_generic/ath10k-ct-2019-09-09-5e8cd86f/ath10k-4.19/mac.c:6598 0x8700bd24 [ath10k_core@87000000+0x5d210]
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.016231] Modules linked in: ath9k ath9k_common pppoe ppp_async batman_adv ath9k_hw ath10k_pci ath10k_core ath pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack libcrc32c iptable_mangle iptable_filter ip_tables crc_ccitt compat br_netfilter ledtrig_usbport nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 msdos vfat fat ntfs nls_utf8 nls_iso8859_1 nls_cp437
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.088204]  usb_storage sd_mod scsi_mod ext4 mbcache jbd2 crc16 crc32c_generic crypto_hash ehci_platform ehci_hcd gpio_button_hotplug usbcore nls_base usb_common
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.103218] CPU: 0 PID: 16176 Comm: wpa_supplicant Tainted: G        W       4.14.156 #0
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.111503] Stack : 000000f8 800b2a94 80500000 804af544 00000000 00000000 00000000 00000000
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.120128]         00000000 00000000 00000000 00000000 00000000 00000001 853c59d8 ebe9a33e
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.128783]         853c5a70 00000000 00000000 00009378 00000038 80447958 00000008 00000000
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.137442]         000001c9 6e8dd5be 000001c8 00000000 853c59b8 80000000 00000000 8704e480
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.146036]         8700bd24 000019c6 86310d28 87428800 00000003 8027f944 00000000 80630000
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.154570]         ...
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.157183] Call Trace:
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.157198] [<800b2a94>] 0x800b2a94
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.163293] [<80500000>] 0x80500000
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.166873] [<80447958>] 0x80447958
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.170485] [<8700bd24>] 0x8700bd24 [ath10k_core@87000000+0x5d210]
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.176813] [<8027f944>] 0x8027f944
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.180352] [<8006a56c>] 0x8006a56c
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.184017] [<8006a574>] 0x8006a574
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.187559] [<80084c20>] 0x80084c20
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.191102] [<8700bd24>] 0x8700bd24 [ath10k_core@87000000+0x5d210]
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.197583] [<80084d08>] 0x80084d08
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.201136] [<80318194>] 0x80318194
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.204714] [<8700bd24>] 0x8700bd24 [ath10k_core@87000000+0x5d210]
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.211078] [<87795f70>] 0x87795f70 [mac80211@87780000+0x6c280]
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.217204] [<8772d0d0>] 0x8772d0d0 [cfg80211@87700000+0x363f0]
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.223313] [<8772941c>] 0x8772941c [cfg80211@87700000+0x363f0]
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.229530] [<8771ddc0>] 0x8771ddc0 [cfg80211@87700000+0x363f0]
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.235711] [<80134f00>] 0x80134f00
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.239316] [<80350498>] 0x80350498
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.243000] [<803501ac>] 0x803501ac
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.246630] [<8034eb44>] 0x8034eb44
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.250375] [<8034f410>] 0x8034f410
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.253980] [<8034c9bc>] 0x8034c9bc
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.257540] [<8034e208>] 0x8034e208
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.261197] [<8034e6e4>] 0x8034e6e4
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.264845] [<802f7c1c>] 0x802f7c1c
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.268386] [<8034bcf8>] 0x8034bcf8
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.271988] [<8034e308>] 0x8034e308
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.275625] [<802f7e7c>] 0x802f7e7c
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.279170] [<800ac680>] 0x800ac680
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.282723] [<802f5f34>] 0x802f5f34
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.286301] [<802f6718>] 0x802f6718
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.289840] [<8034bdec>] 0x8034bdec
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.293390] [<802f681c>] 0x802f681c
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.297024] [<8013fd78>] 0x8013fd78
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.300656] [<802fd5c0>] 0x802fd5c0
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.304252] [<802f8704>] 0x802f8704
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.307808] [<802f6718>] 0x802f6718
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.311405] [<8006f72c>] 0x8006f72c
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.314981] [<802f84a4>] 0x802f84a4
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.318624]
Sat Dec 28 14:50:06 2019 kern.warn kernel: [ 2418.320140] ---[ end trace b03503722668fd71 ]---
Sat Dec 28 14:50:07 2019 kern.info kernel: [ 2418.329016] wlan0: Selected IBSS BSSID [MAC] based on configured SSID
Sat Dec 28 14:50:07 2019 daemon.notice netifd: Network device 'wlan0-1' link is up
Sat Dec 28 14:50:07 2019 daemon.notice netifd: Network device 'wlan0-2' link is up
Sat Dec 28 14:50:07 2019 daemon.notice netifd: Network device 'wlan0-3' link is up
Sat Dec 28 14:50:07 2019 daemon.notice netifd: Network device 'wlan0' link is up
Sat Dec 28 14:50:07 2019 daemon.notice netifd: Interface 'nwi_mesh0' is enabled
Sat Dec 28 14:50:07 2019 daemon.notice netifd: Interface 'nwi_mesh0' has link connectivity
Sat Dec 28 14:50:07 2019 daemon.notice netifd: Interface 'nwi_mesh0' is setting up now
Sat Dec 28 14:50:07 2019 kern.info kernel: [ 2418.899578] batman_adv: bat0: Adding interface: wlan0
Sat Dec 28 14:50:07 2019 kern.info kernel: [ 2418.904876] batman_adv: bat0: Interface activated: wlan0
Sat Dec 28 14:50:07 2019 daemon.notice netifd: Interface 'nwi_mesh0' is now up
Sat Dec 28 14:50:08 2019 daemon.notice wpa_supplicant[16176]: wlan0: Associated with [MAC]


29.12.20192709Base systemBug ReportVery LowMediumUnable to connect wifi on mvebu platform with esp8266openwrt-19.07Unconfirmed Task Description

- Device problem occurs on mvebu platform - Linksys wrt3200acm Marvell 88W8964 802.11bgn wifi while trying to connect by esp8266
- Software versions OpenWrt 19.07

esp8266 is not getting dhcp address and even when trying to communicate with static IP it is not possible to acquire connection. esp8266 is unable to get access to the router. Same problem exists in openwrt 18.06

 


14.01.20202734Base systemBug ReportVery LowMediumOpkg update fails although router has enough memoryopenwrt-19.07Unconfirmed Task Description

19.07.0 running on WNDR3700v2, 32MB of memory. The machine is certainly not short on memory:

                total        used        free      shared  buff/cache   available
  Mem:          59560       26912       24108         956        8540       16564
  Swap:             0           0           0

Running “opkg update” a first time works fine. However, if I run “opkg update” a second time, it reports:

  Collected errors:
   * pkg_hash_add_from_file: Failed to open /var/opkg-lists/openwrt_routing: Out of memory.

After doing “rm /var/opkg-lists/openwrt_*”, everything works fine again.

15.01.20202740Base systemBug ReportVery LowMedium19.07 ath79 uclient-fetch defaults fail in IPv4-only en...openwrt-19.07Unconfirmed Task Description

I have a TP-Link Archer C7 v2.0, that’s currently running the ath79 19.07. When trying to install other packages after the initial upgrade, ‘opkg update’ failed on each repository with a ‘wget’ error. I can work around this with the following commands:

mv /bin/uclient-fetch /bin/uclientfetch
echo '#!/bin/sh' > /bin/uclient-fetch
echo 'exec /bin/uclientfetch -4 !*' >> /bin/uclient-fetch
chmod 755 /bin/uclient-fetch

so I presume that it’s trying to operate in IPv6 mode first and failing. After running the commands above, subsequent ‘opkg update’ commands work without error.

Here’s a quick run to illustrate:

root@grdl:~# uclientfetch 'http://www.google.com/' 
Downloading 'http://www.google.com/'
Failed to establish connection
root@grdl:~# uclientfetch -4 'http://www.google.com/' 
Downloading 'http://www.google.com/'
Connecting to 172.217.3.100:80
Writing to 'index.html'

Download completed (11751 bytes)
root@grdl:~# uname -a
Linux grdl 4.14.162 #0 Mon Jan 6 16:47:09 2020 mips GNU/Linux
18.01.20202748Base systemBug ReportVery LowMediumPrinter no more receiving IP address since 19.07.0openwrt-19.07Unconfirmed Task Description

Dear community,
Previously I had OpenWRT 18.06.5 in use and my printer (HP LaserJet Pro 400 M475dw) was connecting fine over 2.4 GHz WiFi and obtained an IP address of defined DHCP static leases.
I went to 19.07.0 by starting from scratch on the same Netgear R7800 hardware. Everything works fine except for the mentioned printer.
It connects to WiFi and is shown in the list of associated stations, but it doesn’t receive an IP. The syslog prints following two lines about every minute:
Sat Jan 18 13:12:19 2020 daemon.info dnsmasq-dhcp[20788]: DHCPDISCOVER(wlan1) 34:23:87:xx:xx:xx
Sat Jan 18 13:12:19 2020 daemon.info dnsmasq-dhcp[20788]: DHCPOFFER(wlan1) 192.168.1.128 34:23:87:xx:xx:xx

What I’ve tried so far:
- enable/disable static leases: same behavior
- enable/disable KRACK countermeasures: same behavior
- require/optional/disable 802.11w Management Frame Protection: with require and even with optional the printer would not connect to WiFi at all
- factory reset printer and try again: no difference

Additional info:
- I have no WPA3 packets installed or activated - just default firmware image obtained from OpenWRT. Only additional packet is luci-ssl (+dependencies)
- all other devices that connect to 2.4 GHz or 5 GHz get their IP addresses. Those are mobile phones, laptops, tablets, TV’s, Chromecast, vacuum robot...
- As well no problem with physically connected devices like NAS, VoIP phone base, home automation system
- Printer display shows WiFi is connected but IP is set to 169.254.60.37
- It doesn’t look like a WiFi issue, more like something is different with the DHCP server between 18.06.5 and 19.07.0

18.01.20202750Base systemBug ReportVery LowMediumWireless on Netgear WNDR3700v2 not workingopenwrt-19.07Unconfirmed Task Description

After upgrading my Netgear WNDR3700 v2 to 19.07 (ath79 target), the WiFi cards aren’t detected.

Here are the outputs of dmesg, logread, lsmod | grep ath, ls /sys/bus/pci/*, lspci -vnn; at the recommendation of PaulFertser in #openwrt, I tried echo -n 168c ff1d > /sys/bus/pci/drivers/ath9k/new_id, which resulted in some error messages in dmesg, but the WiFi interfaces still aren’t detected (wifi config produces an empty file).

With ar71xx target, wifi works; the cards seem to have a different http://p.0au.de/3393221e/, too. dmesg, logread, ls /sys/bus/pci/*.

19.01.20202753Base systemBug ReportVery LowMediumUSB has no power on TP-Link TL-WR842ND v2.0 after upgra...openwrt-19.07Unconfirmed Task Description

After upgrading from 18.06 to 19.07 (ath97) the USB port of the device seems to provide no power at all. I have a simple device (TEMPer) I am using for this test. The device has a power LED which starts as soon as there is power on the USB port. The LED in on if I even only connect the device to an active USB hub not being connected to a computer.
I checked that the device has power just before the upgrade.
I made a factory reset of the device before the upgrade.
I tried with two identical devices and had the same effect.
When I run lsusb, I do see the USB hub, but no connected devices.
I applied 19.07 (ar71xx) on one of the devices and the USB port has power.
Can I provide any additional info to support working on this issue?

21.01.20202759PackagesBug ReportVery LowMediumodhcpd IPv6 NDP + macOS don't play togetheropenwrt-19.07Unconfirmed Task Description

My device: TP-Link Archer C7 v2.0 (JP)
My software stack: OpenWrt 19.07

My router uses odhcpd’s relay mode to relay IPv6 neighbor discovery protocol and router advertisements from the uplink router.

My linux-based system connected to the router is able to get IPv6 connectivity through the router without problems.

However, my macOS-based system doesn’t get IPv6 connectivity. It gets a global IPv6 prefix, which suggests that it’s able to receive RA packets, but my router is also unable to ping6 the macOS system by it’s globally unique address, and doing ip -6 neigh on the router makes it clear that the router doesn’t know the MAC address of the macOS system, and all of it’s probes to find it, end up failing.

Inspecting the ICMPv6 traffic in the LAN shows that my macOS system doesn’t respond to the neighbor solicitation packets send by the router. Here’s an example of such a packet:

02:28:50.006540 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 32) fd26:e9f1:e833::1 > ff02::1:ff65:88f8: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has 2404:7a80:9621:7100:404:978a:5765:88f8

  source link-address option (1), length 8 (1): 18:a6:f7:8d:c0:d3

Here, fd26:e9f1:e833::1 is the ULA of the LAN interface of the router.

According to Apple discussion board ( https://discussions.apple.com/thread/8620806 ) macOS seems to have a behaviour such that it ignores neighbor solicitation packets unless the source address of the packet is a link-local address.

Indeed, commenting out option ula_prefix in /etc/config/network makes odhcpd to use link-local addresses, and that makes macOS to respond to neighbor solicitation queries, and in my system, demonstrably restores IPv6 connectivity.

Since macOS is a very common operating system, it would be benefical if odhcpd’s default behaviour were to use LLA in NDP packets. The current situation of not being able to set ULA prefix without losing connectivity is unfortunate. (And I think that ULA prefix is set by default in OpenWRT, which makes macOS not play together with it by default.)

For reference, here’s a forum thread I documented my forays into inspecting this problem: https://forum.openwrt.org/t/how-to-send-icmp6-neighbor-solicitation-with-a-link-local-source-address/53220

Could the default source address of odhcpd’s NDP/RA packets be changed to LLA?

09.10.20192541KernelBug ReportMediumLowHardware offloading causes some flows to fail to be NAT...openwrt-19.07New Task Description

Just after a reboot, some flows are not NATed: packets from a machine in the LAN are sent to the WAN port with a private source IP address.

This is on a Linksys RE6500 (ramips mt7621) running openwrt 19.07-SNAPSHOT r10578-b3d70f628.
It is configured with flow_offloading and flow_offloading_hw.

Here is a tcpdump capture showing the problem on the WAN port (172.23.184.0/24 is my LAN address space):

root@openwrt:~# tcpdump -n -i eth0.20 net 172.23.184.0/24
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0.20, link-type EN10MB (Ethernet), capture size 262144 bytes
18:51:21.756552 IP 172.23.184.119.51001 > 91.224.XX.YY.52001: UDP, length 112
18:51:22.651556 IP 172.23.184.119.51001 > 91.224.XX.YY.52001: UDP, length 148
18:51:26.681032 IP 172.23.184.119.51001 > 91.224.XX.YY.52001: UDP, length 768
18:51:27.771654 IP 172.23.184.119.51001 > 91.224.XX.YY.52001: UDP, length 148

Here is what conntrack -L says:

udp      17 55 src=172.23.184.119 dst=91.224.XX.YY sport=51001 dport=52001 packets=93 bytes=20412 [UNREPLIED] src=91.224.XX.YY dst=172.23.184.119 sport=52001 dport=51001 packets=0 bytes=0 mark=0 use=1

Notice the second dst= that shows the private IP address of the LAN machine.

After restarting the firewall, the flow is correctly NAT-ed and conntrack -L shows the correct entry (193.33.ZZ.WW is my public IP address):

udp      17 175 src=172.23.184.119 dst=91.224.XX.YY sport=51001 dport=52001 packets=4 bytes=704 [UNREPLIED] src=91.224.XX.YY dst=193.33.ZZ.WW sport=52001 dport=51001 packets=0 bytes=0 mark=0 use=1

Note: when I only enable flow_offloading, the issue does not appear anymore, so this really seems to be an issue with the hw offloading integration in the firewall.

16.11.20192607PackagesBug ReportVery LowLowodhcpd: assigns IPv4 address outside of interface subne...openwrt-19.07Unconfirmed Task Description

When a static IPv4 lease is set up for a MAC address, odhcpd assigns that address even if it is outside the configured subnet of the relevant interface.

This is a problem if one wants to set a static lease for a host that may connect to one of multiple interfaces. It is also not possible to set separate static leases for each interface, as only the last one is used.

Software versions of OpenWrt/LEDE release, packages, etc:

Trunk and 19.07.
18.06 is unaffected.

It looks like this was introduced with https://git.openwrt.org/?p=project/odhcpd.git;a=commit;h=ca8ba91c757b1559bc6391707547d54477c8315a.

Steps to reproduce:

Steps based on fresh install of OpenWrt:

Replace odhcpd-ipv6only by odhcpd

Enable odhcpd for IPv4 and set static lease with IPv4 address outside the default lan subnet:

uci set dhcp.odhcp.maindhcp=1
uci set dhcp.lan.dhcpv4="server"

uci add dhcp host
uci set dhcp.@host[-1].mac="11:22:33:44:55:66"
uci set dhcp.@host[-1].ip="192.168.2.100"

uci commit dhcp

Expected result: IP address from 192.168.1.0/24 is assigned to host 11:22:33:44:55:66
Actual result: IP address 192.168.2.100 is assigned to host 11:22:33:44:55:66

17.11.20192608Base systemBug ReportVery LowLowsysntpd cannot acquire time on IPv6 only networkopenwrt-19.07Unconfirmed Task Description

I’ve encountered an issue with ntpd in OpenWrt where it cannot acquire the time on an IPv6 only network, it seems that the issue lies in dns resolution by ntpd as specifying an IPv6 address instead of a domain works as expected.

By the way, I believe only 2.pool.ntp.org returns IPv6 addresses in case anyone tries to reproduce my issue.

Possibly relevant: https://dev.archive.openwrt.org/attachment/ticket/12167/0001-busybox-make-ntpd-prefer-IPv6-addresses.patch

28.11.20192640Base systemBug ReportVery LowLowFailed to sync jffs2 overlayopenwrt-19.07Unconfirmed Task Description

GL-B1300
19.07-SNAPSHOT

Every time I run a sys upgrade I get “failed to sync jffs2 overlay” message in the log (log is configured during the setup by a custom script under /etc/uci-defaults). The error happens during execution of the command: “cp -a /tmp/root/upper/* / 2>/dev/null” in “libfstools/overlay.c”. By the time the copy command runs, the files under /etc/uci-defaults are already deleted and it looks like the “deletion marker” files cannot be copied in this case.

I re-run the command myself after a successful upgrade and got the following logs.

cp -a /tmp/root/upper/* /root/test/
cp: can’t create ‘/root/test/etc/uci-defaults/luci-sqm’: Operation not permitted
cp: can’t create ‘/root/test/etc/uci-defaults/ddns’: Operation not permitted
cp: can’t create ‘/root/test/etc/uci-defaults/bcp38’: Operation not permitted

ls -la /tmp/root/upper/etc/uci-defaults/
c——— 1 root root 0, 0 Nov 26 16:48 bcp38
c——— 1 root root 0, 0 Nov 26 16:48 ddns
c——— 1 root root 0, 0 Nov 26 16:48 luci-sqm

More details: https://forum.openwrt.org/t/getting-error-failed-to-sync-jffs2-overlay/47742


01.12.20192644Base systemBug ReportVery LowLowdnsmasq-full: Cannot satisfy dependenciesopenwrt-19.07Unconfirmed Task Description

Environment:
arch: mips
model: TP-link WDR4300
Openwrt: 19.07.0-rc1

Description:
I probably overlooked but hit the following issue where unable to install dnsmasq-full. Actually downloading only already gives the following warning and wonder if I can/should force-install:

# opkg install dnsmasq-full --download-only
Downloading http://downloads.openwrt.org/releases/19.07.0-rc1/packages/mips_24kc/base/dnsmasq-full_2.80-14_mips_24kc.ipk
Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for dnsmasq-full:
 * 	kernel (= 4.14.151-1-342af9e4f67b3447c53216ab8e3b12a1)
 * opkg_install_cmd: Cannot install package dnsmasq-full.
03.12.20192650Base systemBug ReportVery LowLowr7800 19.07-rc2 unable to change channel for ACopenwrt-19.07Waiting on reporter Task Description

- Device problem occurs on - Linux r7800 4.14.156 #0 SMP Sat Nov 30 15:52:33 2019 armv7l GNU/Linux
- Software versions of OpenWrt/LEDE release - 19.07-rc2

in Luci when change channel number change actually never gets committed, when do manually in /etc/config/wireless and then reboot router comes up with 5GHz network disabled, after changing back to default channel 36 5GHz network is usable again.

please provide steps to collect log

in dmesg only:

(wlan0) entered blocking state
(wlan0) entered disabled state
   
04.12.20192651KernelBug ReportVery LowLowOut of memory errors with 5 GHz Wi-Fi enabledopenwrt-19.07Waiting on reporter Task Description

- Device problem occurs on Archer C60 V2
- Software versions: Powered by LuCI Master (git-19.337.71995-796301a) / OpenWrt SNAPSHOT r11618-416d2cc71e

I’ve installed via TFTP “openwrt-19.07.0-rc2-ath79-generic-tplink_archer-c60-v2-squashfs-factory.bin” but because of some “out of memory” errors, i’ve upgraded to “openwrt-ath79-generic-tplink_archer-c60-v2-squashfs-sysupgrade.bin” in the hope of solving.
The problems continued, so i wrote to forum (https://forum.openwrt.org/t/tp-link-archer-c60-v2-19-07-0-rc2-ath79-snapshot-out-of-memory/49725) and i saw that other users had the same problem that they solved by disabling 5 Ghz.
Disabling the 5Ghz actually “out of memory” problems disappear. I was also able to install additional packages without problem.

 


15.12.20192676Base systemBug ReportVery LowLowUnexpected realpath behaviouropenwrt-19.07Unconfirmed Task Description

There is a problem with creating chrooted SFTP access using OpenSSH package. However, it seems that the problem isn’t with the package, rather with realpath function of OpenWRT. The whole description of the problem was already provided in forum, here I only copy the part of the log file:

Nov 29 10:06:27 OpenWrt internal-sftp[12557]: realpath "."
Nov 29 10:06:27 OpenWrt internal-sftp[12557]: debug3: request 46352: sent status 2
Nov 29 10:06:27 OpenWrt internal-sftp[12557]: sent status No such file

Tested on both 18.06.5 and 19.07.0-rc1 with the same result.

18.12.20192685Base systemBug ReportVery LowLowColdplug too soon; hotplug.d scripts not run for some e...openwrt-19.07Unconfirmed Task Description

OpenWrt 19.07.0-rc2, latest openwrt-packages.

Occurs on at least ath79 but looking at the code this is not device-specific.

1. Have USB devices for which you have hotplug scripts (e.g. from p910d and sane-backends)
2. Boot (or reboot) with usb devices already plugged in.
3. Observe that the actions in the hotplug script (e.g. setting permissions / group ownership that don’t belong in the base system (i.e. hotplug.json)) as it’d be bloat to detect product:vendor ip pairs and take appropriate action for all the various packages and devices hotplug handles – if hotplug.json could have hotplug.json.d or somesuch it would alleviate most of this pain.

Looking at the procd code coldplug (udevtrigger) is called during ‘early’ init, which means that hotplug.d scripts are not yet present. Because /etc/init.d/boot (or any other initscript) no longer does a later call to udevtrigger, the events get missed).

If udevtrigger were called during regular init this wouldn’t be an issue (but probably the coldplug is needed earlier *as well* for devices needed to boot the system.

See also #1903 and #996 (they are likely the same root cause).

15.01.20202737Base systemBug ReportVery LowLowRadio0 Device is not activeopenwrt-19.07Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on
TPLink TP-WRD3600 v1
- Software versions of OpenWrt/LEDE release, packages, etc.
Luci-Network-Wireless, Radio0 Generic 802.11bg device is not active
OpenWrt 19.03
- Steps to reproduce
Freshly installed. Reboot/Restart do not fix the issue

Radio0 is a Generic 802.11bg device, which is always not active even after restart of the device, or reboot of the router.
There is a Radio2, which is a Generic 802.11bgn device, which is working normally for 2.4Ghz band.

 


15.01.20202741Base systemBug ReportVery LowLowIPv6 traffic stops switch on Linksys EA6350openwrt-19.07Unconfirmed Task Description

I use a Linksys EA6350v3 running 19.07 (issue occurs in the latest snapshots) and IPv6 traffic is able stop the built in switch from working cutting off internet access (IPv4 traffic does not impact the switch). Through WiFi you are still able to access Luci and a reboot of the router is needed to fix the issue.

The topic is being discussed here and seems to impact other router models as well:
https://forum.openwrt.org/t/ethernet-cuts-out-on-linksys-ea6350v3/39111

The following are from “logread -f” after the switch stops working during an iperf3 IPv6 test:

Wed Jan 15 00:37:11 2020 kern.alert kernel: [ 1094.936813] BUG: Bad page state in process swapper/0  pfn:8d4d0
Wed Jan 15 00:37:11 2020 kern.emerg kernel: [ 1094.936855] page:cffa2a00 count:-1 mapcount:0 mapping:  (null) index:0x0
Wed Jan 15 00:37:11 2020 kern.emerg kernel: [ 1094.941546] flags: 0x0()
Wed Jan 15 00:37:11 2020 kern.alert kernel: [ 1094.948495] raw: 00000000 00000000 00000000 ffffffff ffffffff 00000100 00000200 00000000
Wed Jan 15 00:37:11 2020 kern.alert kernel: [ 1094.951008] page dumped because: nonzero _count
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1094.959074] Modules linked in: pppoe ppp_async ath10k_pci ath10k_core ath pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables hwmon crc_ccitt compat nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_of_simple gpio_button_hotplug
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.007768] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.14.162 #0
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.029997] Hardware name: Generic DT based system
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.036257] Function entered at [<c030e2a8>] from [<c030a7a8>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.040938] Function entered at [<c030a7a8>] from [<c073f994>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.046754] Function entered at [<c073f994>] from [<c03a2fb4>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.052570] Function entered at [<c03a2fb4>] from [<c03a5430>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.058386] Function entered at [<c03a5430>] from [<c03a5d08>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.064201] Function entered at [<c03a5d08>] from [<c03a69a4>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.070016] Function entered at [<c03a69a4>] from [<c0628114>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.075834] Function entered at [<c0628114>] from [<c0628190>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.081647] Function entered at [<c0628190>] from [<c05cda7c>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.087466] Function entered at [<c05cda7c>] from [<c05d0c24>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.093280] Function entered at [<c05d0c24>] from [<c063c41c>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.099097] Function entered at [<c063c41c>] from [<c0301520>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.104912] Function entered at [<c0301520>] from [<c0321e3c>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.110729] Function entered at [<c0321e3c>] from [<c035b308>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.116546] Function entered at [<c035b308>] from [<c030140c>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.122360] Function entered at [<c030140c>] from [<c030b30c>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.128176] Exception stack(0xc0a01f40 to 0xc0a01f88)
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.133997] 1f40: 00000001 00000000 00000000 c0313960 ffffe000 c0a03cb8 c0a03c6c 00000000
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.139124] 1f60: 00000000 00000001 cfffcd40 c092da28 c0a01f88 c0a01f90 c0307d88 c0307d8c
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.147276] 1f80: 60000013 ffffffff
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.155429] Function entered at [<c030b30c>] from [<c0307d8c>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.158733] Function entered at [<c0307d8c>] from [<c0352058>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.164635] Function entered at [<c0352058>] from [<c0352378>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.170451] Function entered at [<c0352378>] from [<c0900c04>]
Wed Jan 15 00:37:11 2020 kern.warn kernel: [ 1095.176267] Disabling lock debugging due to kernel taint
Wed Jan 15 00:51:36 2020 kern.alert kernel: [  443.412420] BUG: Bad page state in process swapper/0  pfn:8d8fa
Wed Jan 15 00:51:36 2020 kern.emerg kernel: [  443.412461] page:cffaaf40 count:-1 mapcount:0 mapping:  (null) index:0x0
Wed Jan 15 00:51:36 2020 kern.emerg kernel: [  443.417152] flags: 0x0()
Wed Jan 15 00:51:36 2020 kern.alert kernel: [  443.424100] raw: 00000000 00000000 00000000 ffffffff ffffffff 00000000 cffaaf54 00000000
Wed Jan 15 00:51:36 2020 kern.alert kernel: [  443.426615] page dumped because: nonzero _count
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.434680] Modules linked in: pppoe ppp_async ath10k_pci ath10k_core ath pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables hwmon crc_ccitt compat nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_of_simple gpio_button_hotplug
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.483374] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.14.162 #0
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.505602] Hardware name: Generic DT based system
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.511863] Function entered at [<c030e2a8>] from [<c030a7a8>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.516543] Function entered at [<c030a7a8>] from [<c073f994>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.522360] Function entered at [<c073f994>] from [<c03a2fb4>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.528175] Function entered at [<c03a2fb4>] from [<c03a5430>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.533992] Function entered at [<c03a5430>] from [<c03a5d08>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.539807] Function entered at [<c03a5d08>] from [<c03a69a4>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.545621] Function entered at [<c03a69a4>] from [<c0628114>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.551440] Function entered at [<c0628114>] from [<c0628190>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.557254] Function entered at [<c0628190>] from [<c05cda7c>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.563071] Function entered at [<c05cda7c>] from [<c05d0c24>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.568886] Function entered at [<c05d0c24>] from [<c063c41c>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.574704] Function entered at [<c063c41c>] from [<c0301520>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.580520] Function entered at [<c0301520>] from [<c0321e3c>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.586335] Function entered at [<c0321e3c>] from [<c035b308>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.592152] Function entered at [<c035b308>] from [<c030140c>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.597965] Function entered at [<c030140c>] from [<c030b30c>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.603783] Exception stack(0xc0a01f40 to 0xc0a01f88)
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.609604] 1f40: 00000001 00000000 00000000 c0313960 ffffe000 c0a03cb8 c0a03c6c 00000000
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.614729] 1f60: 00000000 00000001 cfffcd40 c092da28 c0a01f88 c0a01f90 c0307d88 c0307d8c
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.622883] 1f80: 60000013 ffffffff
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.631035] Function entered at [<c030b30c>] from [<c0307d8c>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.634337] Function entered at [<c0307d8c>] from [<c0352058>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.640241] Function entered at [<c0352058>] from [<c0352378>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.646056] Function entered at [<c0352378>] from [<c0900c04>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.651873] Disabling lock debugging due to kernel taint
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.663306] ------------[ cut here ]------------
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.663359] WARNING: CPU: 0 PID: 1767 at net/core/dev.c:4700 0xc063c104
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.667803] Modules linked in: pppoe ppp_async ath10k_pci ath10k_core ath pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables hwmon crc_ccitt compat nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_of_simple gpio_button_hotplug
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.718585] CPU: 0 PID: 1767 Comm: dropbear Tainted: G    B           4.14.162 #0
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.740761] Hardware name: Generic DT based system
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.748407] Function entered at [<c030e2a8>] from [<c030a7a8>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.753089] Function entered at [<c030a7a8>] from [<c073f994>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.758905] Function entered at [<c073f994>] from [<c031dd34>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.764721] Function entered at [<c031dd34>] from [<c031de00>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.770534] Function entered at [<c031de00>] from [<c063c104>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.776353] Function entered at [<c063c104>] from [<c063c184>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.782167] Function entered at [<c063c184>] from [<c063c48c>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.787983] Function entered at [<c063c48c>] from [<c0301520>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.793800] Function entered at [<c0301520>] from [<c0321e3c>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.799615] Function entered at [<c0321e3c>] from [<c035b308>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.805433] Function entered at [<c035b308>] from [<c030140c>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.811246] Function entered at [<c030140c>] from [<c030b6b0>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.817064] Exception stack(0xce95ffb0 to 0xce95fff8)
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.822881] ffa0:                                     00000001 bed43480 000001f0 0000002b
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.828011] ffc0: bed43480 b6f76230 0000005e 000001d0 bed434a4 00000020 b6f73010 00025a9c
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.836169] ffe0: 00000010 bed43468 0001f5d0 000123c4 60000010 ffffffff
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.844409] ---[ end trace 963ab92f22dbc474 ]---
Wed Jan 15 00:51:36 2020 kern.alert kernel: [  443.853363] BUG: Bad page state in process ksoftirqd/0  pfn:8d928
Wed Jan 15 00:51:36 2020 kern.emerg kernel: [  443.855616] page:cffab500 count:-1 mapcount:0 mapping:  (null) index:0x0
Wed Jan 15 00:51:36 2020 kern.emerg kernel: [  443.861595] flags: 0x0()
Wed Jan 15 00:51:36 2020 kern.alert kernel: [  443.868372] raw: 00000000 00000000 00000000 ffffffff ffffffff 00000100 00000200 00000000
Wed Jan 15 00:51:36 2020 kern.alert kernel: [  443.870884] page dumped because: nonzero _count
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.878951] Modules linked in: pppoe ppp_async ath10k_pci ath10k_core ath pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables hwmon crc_ccitt compat nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_of_simple gpio_button_hotplug
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.927646] CPU: 0 PID: 7 Comm: ksoftirqd/0 Tainted: G    B   W       4.14.162 #0
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.949876] Hardware name: Generic DT based system
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.957522] Function entered at [<c030e2a8>] from [<c030a7a8>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.962204] Function entered at [<c030a7a8>] from [<c073f994>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.968020] Function entered at [<c073f994>] from [<c03a2fb4>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.973835] Function entered at [<c03a2fb4>] from [<c03a5430>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.979650] Function entered at [<c03a5430>] from [<c03a5d08>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.985467] Function entered at [<c03a5d08>] from [<c03a69a4>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.991281] Function entered at [<c03a69a4>] from [<c0628114>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  443.997099] Function entered at [<c0628114>] from [<c0628190>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  444.002913] Function entered at [<c0628190>] from [<c05cda7c>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  444.008731] Function entered at [<c05cda7c>] from [<c05d0bac>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  444.014545] Function entered at [<c05d0bac>] from [<c063c41c>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  444.020363] Function entered at [<c063c41c>] from [<c0301520>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  444.026179] Function entered at [<c0301520>] from [<c0321b68>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  444.031995] Function entered at [<c0321b68>] from [<c033bea4>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  444.037811] Function entered at [<c033bea4>] from [<c0339060>]
Wed Jan 15 00:51:36 2020 kern.warn kernel: [  444.043626] Function entered at [<c0339060>] from [<c03074a8>]
Wed Jan 15 00:51:59 2020 kern.warn kernel: [  467.147594] ------------[ cut here ]------------
Wed Jan 15 00:51:59 2020 kern.warn kernel: [  467.147640] WARNING: CPU: 0 PID: 0 at net/core/dev.c:4700 0xc063c104
Wed Jan 15 00:51:59 2020 kern.warn kernel: [  467.151298] Modules linked in: pppoe ppp_async ath10k_pci ath10k_core ath pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables hwmon crc_ccitt compat nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_of_simple gpio_button_hotplug
Wed Jan 15 00:51:59 2020 kern.warn kernel: [  467.201852] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G    B   W       4.14.162 #0
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.224032] Hardware name: Generic DT based system
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.231328] Function entered at [<c030e2a8>] from [<c030a7a8>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.236184] Function entered at [<c030a7a8>] from [<c073f994>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.242001] Function entered at [<c073f994>] from [<c031dd34>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.247817] Function entered at [<c031dd34>] from [<c031de00>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.253630] Function entered at [<c031de00>] from [<c063c104>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.259447] Function entered at [<c063c104>] from [<c063c184>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.265262] Function entered at [<c063c184>] from [<c063c1d0>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.271078] Function entered at [<c063c1d0>] from [<c05d0cc0>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.276896] Function entered at [<c05d0cc0>] from [<c063c41c>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.282709] Function entered at [<c063c41c>] from [<c0301520>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.288527] Function entered at [<c0301520>] from [<c0321e3c>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.294344] Function entered at [<c0321e3c>] from [<c035b308>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.300159] Function entered at [<c035b308>] from [<c030140c>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.305974] Function entered at [<c030140c>] from [<c030b30c>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.311791] Exception stack(0xc0a01f40 to 0xc0a01f88)
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.317613] 1f40: 00000001 00000000 00000000 c0313960 ffffe000 c0a03cb8 c0a03c6c 00000000
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.322738] 1f60: 00000000 00000001 cfffcd40 c092da28 c0a01f88 c0a01f90 c0307d88 c0307d8c
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.330892] 1f80: 60000013 ffffffff
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.339045] Function entered at [<c030b30c>] from [<c0307d8c>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.342347] Function entered at [<c0307d8c>] from [<c0352058>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.348249] Function entered at [<c0352058>] from [<c0352378>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.354066] Function entered at [<c0352378>] from [<c0900c04>]
Wed Jan 15 00:52:00 2020 kern.warn kernel: [  467.359978] ---[ end trace 963ab92f22dbc475 ]---
Wed Jan 15 00:52:00 2020 kern.alert kernel: [  467.370760] Unable to handle kernel NULL pointer dereference at virtual address 00000000
Wed Jan 15 00:52:00 2020 kern.alert kernel: [  467.370804] pgd = c0204000
Wed Jan 15 00:56:36 2020 kern.err kernel: [  121.687088] ess_edma c080000.edma: Invalid RRD source port bit set
Wed Jan 15 00:56:36 2020 kern.err kernel: [  121.687195] ess_edma c080000.edma: Invalid RRD source port bit set
Wed Jan 15 00:56:36 2020 kern.err kernel: [  121.695201] ess_edma c080000.edma: Invalid RRD source port bit set
Wed Jan 15 00:56:36 2020 kern.alert kernel: [  121.703775] Unable to handle kernel NULL pointer dereference at virtual address 00000004
Wed Jan 15 00:56:36 2020 kern.alert kernel: [  121.704505] pgd = c0204000
Wed Jan 15 00:56:36 2020 kern.alert kernel: [  121.712797] [00000004] *pgd=00000000

I have reset the router to defaults and only changed the WAN IPv6 prefix length and during the failures many error lines are in logs like posts above.

Enabling the Wifi appears to generate less errors (but could be unrelated)
2.4GHz only:

Wed Jan 15 01:40:36 2020 kern.alert kernel: [ 103.230457] Unable to handle kernel NULL pointer dereference at virtual address 00000004
Wed Jan 15 01:40:36 2020 kern.alert kernel: [ 103.230497] pgd = c0204000
Wed Jan 15 01:40:36 2020 kern.alert kernel: [ 103.237612] [00000004] *pgd=00000000
Wed Jan 15 01:40:36 2020 kern.emerg kernel: [ 103.240191] Internal error: Oops: 817 [#1] SMP ARM

5GHz only:

Wed Jan 15 01:43:58 2020 kern.warn kernel: [ 184.317800] backlog: Budget exhausted after napi rescheduled
With both 2.4GHz and 5GHz enabled it seems to fail so you can still connect to Luci over WiFi but with no errors in logs (like I experienced at parents).
19.01.20202751Base systemBug ReportVery LowLowDevice tl-wr2543n not supported while upgrading from ar...openwrt-19.07Unconfirmed Task Description

Upgrade from ar71xx (18.06.6) to ath79 (19.07.0) failed on my TP-Link TL-WR2543ND-V1:

root@router:/tmp# sysupgrade openwrt-19.07.0-ath79-generic-tplink_tl-wr2543
-v1-squashfs-sysupgrade.bin 
Device tl-wr2543n not supported by this image
Supported devices: tplink,tl-wr2543-v1 tl-wr2543-v1
Image check 'fwtool_check_image' failed.

tl-wr2543-v1 is missing the last “n”. It was used in BOARD_NAME (https://github.com/openwrt/openwrt/blob/openwrt-18.06/target/linux/ar71xx/image/generic-tp-link.mk#L418) but not in the profile name.

Is it safe to do a force upgrade?

It flashed without warning to target ar71xx (https://downloads.openwrt.org/releases/19.07.0/targets/ar71xx/generic/openwrt-19.07.0-ar71xx-generic-tl-wr2543-v1-squashfs-sysupgrade.bin)

It also failed to flash between the same version 19.07.0 but from ar71xx to ath79:

root@router:~# sysupgrade -T /tmp/openwrt-19.07.0-ath79-generic-tplink_tl-w
r2543-v1-squashfs-sysupgrade.bin 
Device tl-wr2543n not supported by this image
Supported devices: tplink,tl-wr2543-v1 tl-wr2543-v1
Image check failed.
19.01.20202752Base systemBug ReportVery LowLowDevice tl-wr841n-v7 not supported by ath97 tplink_tl-wr...openwrt-19.07Unconfirmed Task Description

OpenWrt version: 19.07.0

Device: TP-Link TL-WR841ND v7

When attempting a sysupgrade from a 19.07.0 ar71xx image (profile tl-wr841-v7) to 19.07.0 ath79 image (profile tplink_tl-wr841-v7), LuCI says:

Device tl-wr841n-v7 not supported by this image Supported devices: tplink,tl-wr841-v7 tl-wr841-v7 cat: write error: Broken pipe cat: write error: Broken pipe cat: write error: Broken pipe Image check failed.

The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform.

Observe the extra “n” in “tl-wr841n-v7”. Note: both images are built with Image Builder and a custom package set.

Similar issue: FS#2751

18.12.20192687Base systemBug ReportVery LowVery LowWiFi LED does not dynamically track state of radio on Z...openwrt-19.07Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on
- Software versions of OpenWrt/LEDE release, packages, etc.
- Steps to reproduce

 

Occurs on ZBT-WE3526 (16M) an MT76 unit with 512MB Ram

Stock 19.07, but has been this way since 18.06.xx

Steps to reproduce:
Log into to LuCi and disable a wifi radio, LED remains on.

reboot, radiox LED is now off, so LED is only set at boot

Log back into luci, turn radio on, radio becomes operational (STAs can connect) but LED remains off.

Desired behavior: LED tracks state of radio without requiring a reboot.

31.07.20181719Base systemBug ReportVery LowCriticalNo wireless interfaces on the UniFi AP AC Lite on the f...openwrt-18.06Unconfirmed Task Description

The same issue as this, but on the final release: https://bugs.openwrt.org/index.php?do=details&task_id=1663&string=unifi&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=

03.08.20181726Base systemBug ReportVery LowCriticalNetifd lockup when USB LTE modem was restartedopenwrt-18.06Unconfirmed Task Description

OpenWrt 18.06.0, r7188-b0b5c64c22
Device: Xiaomi Mir3G
Modem: Huawei E3372

How to reproduce:
1. Bring up wwan interface
2. Reconnect modem (or echo ‘at^reset’ > /dev/ttyUSB0)
3. See in logs:

Fri Aug  3 16:59:02 2018 kern.info kernel: [  950.710901] usb 1-1: USB disconnect, device number 3
Fri Aug  3 16:59:02 2018 kern.info kernel: [  950.716646] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Fri Aug  3 16:59:02 2018 kern.info kernel: [  950.725206] option 1-1:1.0: device disconnected
Fri Aug  3 16:59:02 2018 kern.info kernel: [  950.730738] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Fri Aug  3 16:59:02 2018 kern.info kernel: [  950.739145] option 1-1:1.1: device disconnected
Fri Aug  3 16:59:02 2018 kern.info kernel: [  950.744808] huawei_cdc_ncm 1-1:1.2 wwan0: unregister 'huawei_cdc_ncm' usb-1e1c0000.xhci-1, Huawei CDC NCM device
Fri Aug  3 16:59:02 2018 daemon.notice netifd: Network device 'wwan0' link is down
Fri Aug  3 16:59:02 2018 daemon.notice netifd: Network alias 'wwan0' link is down
Fri Aug  3 16:59:02 2018 daemon.notice netifd: Interface 'wwan_4' has link connectivity loss
Fri Aug  3 16:59:02 2018 daemon.notice netifd: Interface 'wwan_4' is disabled
Fri Aug  3 16:59:02 2018 daemon.info chronyd[1303]: Source 94.247.111.10 offline
Fri Aug  3 16:59:02 2018 daemon.info chronyd[1303]: Source 195.91.239.8 offline
Fri Aug  3 16:59:02 2018 daemon.info chronyd[1303]: Source 91.207.136.50 offline
Fri Aug  3 16:59:02 2018 daemon.info chronyd[1303]: Source 195.210.189.106 offline
Fri Aug  3 16:59:02 2018 daemon.info chronyd[1303]: Can't synchronise: no selectable sources
Fri Aug  3 16:59:02 2018 daemon.notice netifd: wwan_4 (4421): udhcpc: SIOCGIFINDEX: No such device
Fri Aug  3 16:59:02 2018 daemon.notice netifd: wwan_4 (4421): udhcpc: received SIGTERM
Fri Aug  3 16:59:03 2018 daemon.notice netifd: wwan (4800): Stopping network wwan
Fri Aug  3 16:59:03 2018 daemon.notice netifd: wwan (4800): Can't open device /dev/ttyUSB1.
Fri Aug  3 16:59:03 2018 daemon.notice netifd: wwan (4800): Failed to disconnect
Fri Aug  3 16:59:03 2018 daemon.notice netifd: Interface 'wwan' is now down
Fri Aug  3 16:59:03 2018 daemon.warn dnsmasq[4567]: no servers found in /tmp/resolv.conf.auto, will retry
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.683961] usb 1-1: new high-speed USB device number 4 using xhci-mtk
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.867590] option 1-1:1.0: GSM modem (1-port) converter detected
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.874380] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.882334] option 1-1:1.1: GSM modem (1-port) converter detected
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.889115] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.915707] huawei_cdc_ncm 1-1:1.2: resetting NTB format to 16-bit
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.926799] huawei_cdc_ncm 1-1:1.2: MAC-Address: 00:1e:10:1f:00:00
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.933038] huawei_cdc_ncm 1-1:1.2: setting rx_max = 16384
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.938957] huawei_cdc_ncm 1-1:1.2: NDP will be placed at end of frame for this device.
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.947454] huawei_cdc_ncm 1-1:1.2: cdc-wdm0: USB WDM device
Fri Aug  3 16:59:09 2018 kern.info kernel: [  957.955970] huawei_cdc_ncm 1-1:1.2 wwan0: register 'huawei_cdc_ncm' at usb-1e1c0000.xhci-1, Huawei CDC NCM device, 00:1e:10:1f:00:00
Fri Aug  3 16:59:10 2018 daemon.notice netifd: Interface 'wwan' is setting up now
Fri Aug  3 16:59:10 2018 daemon.notice netifd: wwan (5197): Stopping network wwan
Fri Aug  3 16:59:11 2018 daemon.notice netifd: wwan (5197): sending ->
Fri Aug  3 16:59:15 2018 daemon.notice netifd: Interface 'wwan' is now down

Now ``ifup wwan`` or ``ifdown wwan`` doesn’t do anything until restart of netifd process.

10.08.20181759Base systemBug ReportVery LowCritical SQM fine in 17.01.4, can’t keep up with line speed in ...openwrt-18.06Unconfirmed Task Description

Netgear R7800 running 17.01.4 kept up with my ISP line speed (nominal 250Mbps/15Mbps) when configured to use SQM with cake/piece_of_cake.
In 18.06, it cannot keep up
Possibly the same root cause as issue 1598

DSLreports speed test with SQM enabled in 17.01.4 (223.1/14.71 Mbps):
http://www.dslreports.com/speedtest/29614883

and with 18.06 ( 95.8/14.16 Mbps):
http://www.dslreports.com/speedtest/36981183

root@LEDE:~# cat /etc/config/sqm

config queue 'eth1'
	option qdisc_advanced '0'
	option verbosity '5'
	option upload '15000'
	option linklayer 'ethernet'
	option overhead '18'
	option debug_logging '1'
	option download '232750'
	option interface 'eth0.2'
	option enabled '1'
	option qdisc 'cake'
	option script 'piece_of_cake.qos'

Sample tc output after running the DSLreports speed test

root@LEDE:~# tc -d qdisc
qdisc noqueue 0: dev lo root refcnt 2 
qdisc mq 0: dev eth0 root 
qdisc fq_codel 0: dev eth0 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
qdisc mq 0: dev eth1 root 
qdisc fq_codel 0: dev eth1 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
qdisc noqueue 0: dev br-lan root refcnt 2 
qdisc noqueue 0: dev eth1.1 root refcnt 2 
qdisc cake 8012: dev eth0.2 root refcnt 2 bandwidth 15Mbit besteffort triple-isolate split-gso rtt 100.0ms noatm overhead 18 
qdisc ingress ffff: dev eth0.2 parent ffff:fff1 ---------------- 
qdisc noqueue 0: dev br-guest root refcnt 2 
qdisc noqueue 0: dev br-iot root refcnt 2 
qdisc noqueue 0: dev wlan0 root refcnt 2 
qdisc noqueue 0: dev wlan1 root refcnt 2 
qdisc noqueue 0: dev wlan1-1 root refcnt 2 
qdisc noqueue 0: dev wlan1-2 root refcnt 2 
qdisc noqueue 0: dev wlan0-1 root refcnt 2 
qdisc fq_codel 0: dev ovpns0 root refcnt 2 limit 10240p flows 1024 quantum 1500 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
qdisc fq_codel 0: dev ovpns1 root refcnt 2 limit 10240p flows 1024 quantum 1500 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
qdisc cake 8013: dev ifb4eth0.2 root refcnt 2 bandwidth 232750Kbit besteffort triple-isolate wash split-gso rtt 100.0ms noatm overhead 18 

root@LEDE:~# tc -s qdisc
qdisc noqueue 0: dev lo root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc mq 0: dev eth0 root 
 Sent 351709498 bytes 2034499 pkt (dropped 0, overlimits 0 requeues 65185) 
 backlog 0b 0p requeues 65185
qdisc fq_codel 0: dev eth0 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
 Sent 351709498 bytes 2034499 pkt (dropped 0, overlimits 0 requeues 65185) 
 backlog 0b 0p requeues 65185
  maxpacket 1514 drop_overlimit 0 new_flow_count 60774 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc mq 0: dev eth1 root 
 Sent 4385184093 bytes 3164614 pkt (dropped 0, overlimits 0 requeues 109126) 
 backlog 0b 0p requeues 109126
qdisc fq_codel 0: dev eth1 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
 Sent 4385184093 bytes 3164614 pkt (dropped 0, overlimits 0 requeues 109126) 
 backlog 0b 0p requeues 109126
  maxpacket 1514 drop_overlimit 0 new_flow_count 137321 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc noqueue 0: dev br-lan root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev eth1.1 root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc cake 8012: dev eth0.2 root refcnt 2 bandwidth 15Mbit besteffort triple-isolate split-gso rtt 100.0ms noatm overhead 18 
 Sent 41321462 bytes 92960 pkt (dropped 919, overlimits 39456 requeues 0) 
 backlog 0b 0p requeues 0
 memory used: 194432b of 4Mb
 capacity estimate: 15Mbit
 min/max network layer size:           28 /    1500
 min/max overhead-adjusted size:       46 /    1518
 average network hdr offset:           14

                  Tin 0
  thresh         15Mbit
  target          5.0ms
  interval      100.0ms
  pk_delay        672us
  av_delay        211us
  sp_delay         11us
  backlog            0b
  pkts            93879
  bytes        42712828
  way_inds            6
  way_miss          392
  way_cols            0
  drops             919
  marks               0
  ack_drop            0
  sp_flows            0
  bk_flows            1
  un_flows            0
  max_len         12112
  quantum           457

qdisc ingress ffff: dev eth0.2 parent ffff:fff1 ---------------- 
 Sent 143870988 bytes 121001 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev br-guest root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev br-iot root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev wlan0 root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev wlan1 root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev wlan1-1 root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev wlan1-2 root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc noqueue 0: dev wlan0-1 root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc fq_codel 0: dev ovpns0 root refcnt 2 limit 10240p flows 1024 quantum 1500 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
 Sent 2015423 bytes 2972 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev ovpns1 root refcnt 2 limit 10240p flows 1024 quantum 1500 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
 Sent 228 bytes 3 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
  maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
  new_flows_len 0 old_flows_len 0
qdisc cake 8013: dev ifb4eth0.2 root refcnt 2 bandwidth 232750Kbit besteffort triple-isolate wash split-gso rtt 100.0ms noatm overhead 18 
 Sent 148570176 bytes 120706 pkt (dropped 297, overlimits 622 requeues 0) 
 backlog 0b 0p requeues 0
 memory used: 661056b of 11637500b
 capacity estimate: 232750Kbit
 min/max network layer size:           46 /    1500
 min/max overhead-adjusted size:       64 /    1518
 average network hdr offset:           14

                  Tin 0
  thresh     232750Kbit
  target          5.0ms
  interval      100.0ms
  pk_delay        245us
  av_delay         45us
  sp_delay          4us
  backlog            0b
  pkts           121003
  bytes       149019834
  way_inds            6
  way_miss          384
  way_cols            0
  drops             297
  marks               0
  ack_drop            0
  sp_flows            0
  bk_flows            1
  un_flows            0
  max_len         12112
  quantum          1514
30.08.20181824Base systemBug ReportVery LowCriticalCisco / Meraki MR24 locks up after a day or so using 18...openwrt-18.06Unconfirmed Task Description

Upgrade an MR24 from LEDE 17.01.5 to 18.06.1, and wait a day. Device locks up. WIFI is still advertised, but lan port is no longer pingable.

 


30.09.20181872Base systemBug ReportVery LowCriticalArcher C2600 v1.0 tftp recovery is brokenopenwrt-18.06Unconfirmed Task Description

After i have flashed Openwrt 18.06.1 on my Archer c2600 the tftp recovery dont work anymore. I updated the Openwrt factory image over the web interface. Now i have tried to flash back the original firmware over tftp but it dont work. Im able to start the recovery, and the image is transferred over tftp from my pc, but the router just reboots and load Openwrt again. If i try to flash the Openwrt factory image it also dont work this way anymore. This is a big problem, because somebody would have trouble with the system, he would not be able to recover the router. Also because its not very easy to connect the serial port from the router.


Showing tasks 1 - 50 of 945 Page 1 of 191 - 2 - 3 - 4 - 5 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing