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.

OpenedID  descCategoryTask TypePrioritySeveritySummaryReported InStatus
21.02.20192137Base systemBug ReportVery LowLowwifi isolate clients not working on several routersAllUnconfirmed Task Description

Routers and versions: wireless.isolate NOT working: TP Link WR841n v13
Version: OpenWrt SNAPSHOT, r9278-39273b8 (from roughly Feb 8)

wireless.isolate NOT working: TP Link TL-WDR3600 v1
Version: OpenWrt 18.06.02
Note: Only the 2GHz radio was enabled

Steps to reproduce: Reset router to default settings
Create wifi network
Restart the router
Connect two devices using wifi to the router
SSh from one device to the other =⇒ (This step incorrectly works!)

wireless.default_radio0=wifi-iface
wireless.default_radio0.device='radio0'
wireless.default_radio0.network='lan'
wireless.default_radio0.mode='ap'
wireless.default_radio0.isolate='1'
wireless.default_radio0.encryption='psk2+ccmp'
wireless.default_radio0.key='xxxxyyyyyyyy'
wireless.default_radio0.ssid='ssssssid'

Note that wireless.isolate DOES test as working on TP Link C7 v2. The ssh fails in the reproduction steps above.

19.02.20192135KernelBug ReportVery LowLowADB AV4202 (BCM43222) wifi gets broadcasted but clients...AllUnconfirmed Task Description

I’ve tried OpenWRT on an ADB AV4202N. Everything works fine except wifi. I know the used Broadcom chip (BCM43222) is problematic but there is a bit of hope.

After installation the wifi is disabled by default. When enabling it and setting the country code correct(AT in my case) the network actually gets found by other devices but they just don’t get accepted by the ap. If i set an encryption this is also correctly broadcasted and recognized by other devices but it’s impossible to connect. Also the following values are shown in OpenWRT’s webinterface which is a strong indicator that something isn’t working correct: “Signal: 0 dBm | Noise: 0 dBm Bitrate: 0.0 Mbit/s”.

device id:

root@OpenWrt:~# for i in /sys/bus/pci/devices/*; do [ -f $i/vendor ] && echo "$(cat $i/vendor):$(cat $i/device) $(cat $i/subsystem_vendor):$(cat $i/subsystem_device)"; done
0x14e4:0xa8d6 0x14e4:0xa8d6
0x14e4:0x6368 0x14e4:0x6368

dmesg:

root@OpenWrt:~# dmesg
[    0.000000] Linux version 4.14.101 (buildbot@6167ddb9a6c5) (gcc version 7.4.0 (OpenWrt GCC 7.4.0 r9393-d0b4596)) #0 SMP Sun Feb 17 18:30:34 2019
[    0.000000] Detected Broadcom 0x6368 CPU revision b2
[    0.000000] CPU frequency is 400 MHz
[    0.000000] 64MB of RAM installed
[    0.000000] board_bcm963xx: Boot address 0xb8000000
[    0.000000] board_bcm963xx: CFE version: 1.0.37-102.6
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0002a031 (Broadcom BMIPS4350)
[    0.000000] board: board name: 96368_Swiss_S1
[    0.000000] MIPS: machine is ADB P.DG AV4202N
[    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 64kB, VIPT, 4-way, linesize 16 bytes.
[    0.000000] Primary data cache 32kB, 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] On node 0 totalpages: 16384
[    0.000000] free_area_init_node: node 0, pgdat 80577690, node_mem_map 81007330
[    0.000000]   Normal zone: 128 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 16384 pages, LIFO batch:3
[    0.000000] random: get_random_bytes called from start_kernel+0x80/0x4b4 with crng_init=0
[    0.000000] percpu: Embedded 14 pages/cpu @8108a000 s25984 r8192 d23168 u57344
[    0.000000] pcpu-alloc: s25984 r8192 d23168 u57344 alloc=14*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 
[    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: 57676K/65536K available (4354K kernel code, 190K rwdata, 992K rodata, 1304K init, 211K bss, 7860K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=16, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 256
[    0.000000] genirq: irq_chip bcm6345-periph-intc did not update eff. affinity mask of irq 28
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000029] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.008242] Calibrating delay loop... 397.82 BogoMIPS (lpj=795648)
[    0.046765] pid_max: default: 32768 minimum: 301
[    0.052101] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.058995] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.072089] Hierarchical SRCU implementation.
[    0.079571] smp: Bringing up secondary CPUs ...
[    0.086729] SMP: Booting CPU1...
[    6.934360] Primary instruction cache 64kB, VIPT, 4-way, linesize 16 bytes.
[    6.934375] Primary data cache 32kB, 2-way, VIPT, cache aliases, linesize 16 bytes
[    6.934674] CPU1 revision is: 0002a031 (Broadcom BMIPS4350)
[    0.118454] Synchronize counters for CPU 1: 
[    0.139272] SMP: CPU1 is running
[    0.139326] done.
[    0.149437] smp: Brought up 1 node, 2 CPUs
[    0.171531] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.181656] futex hash table entries: 512 (order: 1, 8192 bytes)
[    0.188171] pinctrl core: initialized pinctrl subsystem
[    0.196658] NET: Registered protocol family 16
[    0.240012] registering PCI controller with io_map_base unset
[    0.246046] registering PCI controller with io_map_base unset
[    0.311758] PCI host bridge to bus 0000:00
[    0.316259] pci_bus 0000:00: root bus resource [mem 0x30000000-0x37ffffff]
[    0.323379] pci_bus 0000:00: root bus resource [io  0x8000000-0x8007fff]
[    0.330417] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
[    0.337680] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.346180] pci 0000:00:01.0: [14e4:a8d6] type 00 class 0x028000
[    0.348386] pci 0000:00:01.0: reg 0x10: [mem 0x00000000-0x00003fff]
[    0.355870] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
[    0.356046] pci 0000:00:01.0: BAR 0: assigned [mem 0x30000000-0x30003fff]
[    0.364098] PCI host bridge to bus 0000:01
[    0.368541] pci_bus 0000:01: root bus resource [mem 0x38000000-0x3fffffff]
[    0.375647] pci_bus 0000:01: root bus resource [io  0x8008000-0x800ffff]
[    0.382570] pci_bus 0000:01: root bus resource [??? 0x00000000 flags 0x0]
[    0.389579] pci_bus 0000:01: No busn resource found for root bus, will use [bus 01-ff]
[    0.397943] pci 0000:01:1e.0: [14e4:6368] type 02 class 0x060700
[    0.398768] pci 0000:01:1e.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.407692] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 05
[    0.407867] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 05
[    0.408066] pci 0000:01:1e.0: BAR 10: assigned [mem 0x38000000-0x3fffffff]
[    0.415246] pci 0000:01:1e.0: BAR 7: assigned [io  0x8008000-0x80080ff]
[    0.422091] pci 0000:01:1e.0: BAR 8: assigned [io  0x8008400-0x80084ff]
[    0.428924] pci 0000:01:1e.0: CardBus bridge to [bus 02-05]
[    0.434692] pci 0000:01:1e.0:   bridge window [io  0x8008000-0x80080ff]
[    0.441518] pci 0000:01:1e.0:   bridge window [io  0x8008400-0x80084ff]
[    0.448343] pci 0000:01:1e.0:   bridge window [mem 0x38000000-0x3fffffff]
[    0.462606] clocksource: Switched to clocksource MIPS
[    0.472337] PCI: Enabling device 0000:00:01.0 (0000 -> 0002)
[    0.507397] ssb: Found chip with id 0xA8D6, rev 0x00 and package 0x08
[    0.514624] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x1E, vendor 0x4243)
[    0.515162] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x10, vendor 0x4243)
[    0.515697] ssb: Core 2 found: PCI (cc 0x804, rev 0x0E, vendor 0x4243)
[    0.588530] ssb: Sonics Silicon Backplane found on PCI device 0000:00:01.0
[    0.596698] NET: Registered protocol family 2
[    0.604194] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.606157] random: fast init done
[    0.612165] TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
[    0.621583] TCP: Hash tables configured (established 1024 bind 1024)
[    0.628855] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.635018] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.642367] NET: Registered protocol family 1
[    0.647049] PCI: CLS 0 bytes, default 16
[    0.650334] Crashlog allocated RAM at address 0x3f00000
[    0.663506] workingset: timestamp_bits=30 max_order=14 bucket_order=0
[    0.692760] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.698841] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.753705] io scheduler noop registered
[    0.758168] io scheduler deadline registered (default)
[    0.768990] bcm6368-pinctrl 10000080.pin-controller: registered at mmio b0000080
[    0.780487] 10000100.serial: ttyS0 at MMIO 0x10000100 (irq = 10, base_baud = 1562500) is a bcm63xx_uart
[    0.790617] console [ttyS0] enabled
[    0.798066] bootconsole [early0] disabled
[    0.809201] bcm63xx-rng bcm63xx-rng: registered RNG driver
[    0.822290] 18000000.nor: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000001 Chip ID 0x002101
[    0.832762] 18000000.nor: Found an alias at 0x1000000 for the chip at 0x0
[    0.832810] Amd/Fujitsu Extended Query Table at 0x0040
[    0.838153]   Amd/Fujitsu Extended Query version 1.3.
[    0.843377] number of CFI chips: 1
[    0.848379] Searching for RedBoot partition table in 18000000.nor at offset 0xfe0000
[    0.892656] No RedBoot partition table detected in 18000000.nor
[    0.898992] 3 fixed-partitions partitions found on MTD device 18000000.nor
[    0.906114] Creating 3 MTD partitions on "18000000.nor":
[    0.911623] 0x000000000000-0x000000020000 : "CFE"
[    0.922427] 0x000000020000-0x000000fe0000 : "linux"
[    0.933452] parser_imagetag: rootfs: CFE image tag found at 0x0 with version 6, board type 96368_Swiss_S1
[    0.943525] parser_imagetag: Partition 0 is kernel offset 100 and length 1c0970
[    0.951149] parser_imagetag: Partition 1 is rootfs offset 1c0a70 and length dff590
[    0.958961] parser_imagetag: Spare partition is offset 3e0004 and length bdfffc
[    0.966556] 2 bcm963xx-imagetag partitions found on MTD device linux
[    0.973131] Creating 2 MTD partitions on "linux":
[    0.978080] 0x000000000100-0x0000001c0a70 : "kernel"
[    0.988840] 0x0000001c0a70-0x000000fc0000 : "rootfs"
[    0.999352] mtd: device 3 (rootfs) set to be root filesystem
[    1.005321] 1 squashfs-split partitions found on MTD device rootfs
[    1.011731] 0x0000003e0000-0x000000fc0000 : "rootfs_data"
[    1.022907] 0x000000fe0000-0x000001000000 : "nvram"
[    1.039611] bcm63xx-spi 10000800.spi: at [mem 0x10000800-0x10000f0b flags 0x200] (irq 9, FIFOs size 542)
[    1.056412] libphy: Fixed MDIO Bus: probed
[    1.110601] b53_common: found switch: BCM63xx, rev 0
[    1.117669] bcm63xx-wdt bcm63xx-wdt:  started, timer margin: 30 sec
[    1.141575] NET: Registered protocol family 10
[    1.151168] Segment Routing with IPv6
[    1.155277] NET: Registered protocol family 17
[    1.160044] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    1.173441] 8021q: 802.1Q VLAN Support v1.8
[    1.194502] VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
[    1.222721] Freeing unused kernel memory: 1304K
[    1.227401] This architecture does not have kernel memory protection.
[    2.816654] init: Console is alive
[    2.820845] init: - watchdog -
[    5.378462] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    5.629748] usbcore: registered new interface driver usbfs
[    5.635909] usbcore: registered new interface driver hub
[    5.641949] usbcore: registered new device driver usb
[    5.666304] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    5.676645] ehci-platform: EHCI generic platform driver
[    5.790160] ehci-platform ehci-platform: EHCI Host Controller
[    5.796258] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
[    5.805004] ehci-platform ehci-platform: irq 15, io mem 0xb0001500
[    5.826142] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00, overcurrent ignored
[    5.838275] hub 1-0:1.0: USB hub found
[    5.842423] hub 1-0:1.0: 2 ports detected
[    5.859914] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    5.869326] ohci-platform: OHCI generic platform driver
[    5.875339] ohci-platform ohci-platform: Generic Platform OHCI controller
[    5.882509] ohci-platform ohci-platform: new USB bus registered, assigned bus number 2
[    5.891178] ohci-platform ohci-platform: irq 13, io mem 0xb0001600
[    5.961590] hub 2-0:1.0: USB hub found
[    5.965787] hub 2-0:1.0: 2 ports detected
[    5.975380] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    5.988304] init: - preinit -
[    8.655702] random: jshn: uninitialized urandom read (4 bytes read)
[    9.040266] random: jshn: uninitialized urandom read (4 bytes read)
[    9.468482] random: jshn: uninitialized urandom read (4 bytes read)
[    9.864733] urandom_read: 1 callbacks suppressed
[    9.864759] random: jshn: uninitialized urandom read (4 bytes read)
[   10.598898] random: procd: uninitialized urandom read (4 bytes read)
[   10.625650] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   10.632236] bcm63xx_enetsw bcm63xx_enetsw.0: link UP on port3, 100Mbps, full-duplex
[   10.632481] bcm63xx_enetsw bcm63xx_enetsw.0: link UP on port4, 100Mbps, full-duplex
[   10.648613] IPv6: ADDRCONF(NETDEV_UP): eth0.1: link is not ready
[   10.655252] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready
[   11.602155] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   14.565445] jffs2: notice: (432) jffs2_build_xattr_subsystem: complete building xattr subsystem, 4 of xdatum (0 unchecked, 4 orphan) and 45 of xref (6 dead, 39 orphan) found.
[   14.586507] mount_root: overlay filesystem has not been fully initialized yet
[   14.955513] mount_root: switching to jffs2 overlay
[   15.045541] overlayfs: upper fs does not support tmpfile.
[   15.061837] urandom-seed: Seed file not found (/etc/urandom.seed)
[   15.392035] procd: - early -
[   15.395412] procd: - watchdog -
[   16.324654] procd: - watchdog -
[   16.328865] procd: - ubus -
[   16.424722] random: ubusd: uninitialized urandom read (4 bytes read)
[   16.608655] random: ubusd: uninitialized urandom read (4 bytes read)
[   16.616496] random: ubusd: uninitialized urandom read (4 bytes read)
[   16.625939] procd: - init -
[   17.831377] kmodloader: loading kernel modules from /etc/modules.d/*
[   18.031668] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   18.075416] Loading modules backported from Linux version v4.19.23-0-g67d52fae61c1
[   18.083356] Backport generated by backports.git v4.19.23-1-0-g480a925a
[   18.099683] ip_tables: (C) 2000-2006 Netfilter Core Team
[   18.141096] nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
[   18.328363] xt_time: kernel timezone is -0000
[   18.539141] PPP generic driver version 2.4.2
[   18.551564] NET: Registered protocol family 24
[   18.608971] b43-phy0: Broadcom 43222 WLAN found (core revision 16)
[   18.658122] b43-phy0: Found PHY: Analog 8, Type 4 (N), Revision 6
[   18.664442] b43-phy0: Found Radio: Manuf 0x17F, ID 0x2056, Revision 6, Version 0
[   18.688057] Broadcom 43xx driver loaded [ Features: PNL ]
[   18.709707] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   18.736997] kmodloader: done loading kernel modules from /etc/modules.d/*
[   22.095461] random: crng init done
[   22.098992] random: 1 urandom warning(s) missed due to ratelimiting
[   50.966616] bcm63xx_enetsw bcm63xx_enetsw.0: link UP on port3, 100Mbps, full-duplex
[   50.974838] bcm63xx_enetsw bcm63xx_enetsw.0: link UP on port4, 100Mbps, full-duplex
[   51.009263] br-lan: port 1(eth0.1) entered blocking state
[   51.015136] br-lan: port 1(eth0.1) entered disabled state
[   51.022906] device eth0.1 entered promiscuous mode
[   51.028018] device eth0 entered promiscuous mode
[   51.047687] br-lan: port 1(eth0.1) entered blocking state
[   51.053541] br-lan: port 1(eth0.1) entered forwarding state
[   51.060622] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[   51.955920] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 1005.490482] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 1005.676804] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1005.704384] br-lan: port 2(wlan0) entered blocking state
[ 1005.710061] br-lan: port 2(wlan0) entered disabled state
[ 1005.716666] device wlan0 entered promiscuous mode
[ 1005.750838] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1005.758685] br-lan: port 2(wlan0) entered blocking state
[ 1005.764276] br-lan: port 2(wlan0) entered forwarding state
[ 1194.941669] device wlan0 left promiscuous mode
[ 1194.947246] br-lan: port 2(wlan0) entered disabled state
[ 1195.732964] b43-phy0 ERROR: DMA RX reset timed out
[ 1196.013005] b43-phy0 ERROR: DMA TX reset timed out
[ 1196.042349] ssb: Timeout waiting for bitmask 01800000 on register 0F90 to clear.
[ 1198.385367] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
[ 1198.592303] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1198.698993] br-lan: port 2(wlan0) entered blocking state
[ 1198.704833] br-lan: port 2(wlan0) entered disabled state
[ 1198.712445] device wlan0 entered promiscuous mode
[ 1198.818777] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1198.826665] br-lan: port 2(wlan0) entered blocking state
[ 1198.832441] br-lan: port 2(wlan0) entered forwarding state

iwinfo:

root@OpenWrt:~# iwinfo 
wlan0     ESSID: "OpenWrt32"
          Access Point: 02:10:18:01:00:02
          Mode: Master  Channel: 11 (2.462 GHz)
          Tx-Power: 20 dBm  Link Quality: unknown/70
          Signal: unknown  Noise: unknown
          Bit Rate: unknown
          Encryption: none
          Type: nl80211  HW Mode(s): 802.11bg
          Hardware: unknown [Generic MAC80211]
          TX power offset: unknown
          Frequency offset: unknown
          Supports VAPs: no  PHY name: phy0

iw phy0 info

root@OpenWrt:~# iw phy0 info
Wiphy phy0
	max # scan SSIDs: 4
	max scan IEs length: 2285 bytes
	max # sched scan SSIDs: 0
	max # match sets: 0
	max # scan plans: 1
	max scan plan interval: -1
	max scan plan iterations: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Available Antennas: TX 0x3 RX 0x3
	Configured Antennas: TX 0x3 RX 0x3
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * mesh point
	Band 1:
		Frequencies:
			* 2412 MHz [1] (20.0 dBm)
			* 2417 MHz [2] (20.0 dBm)
			* 2422 MHz [3] (20.0 dBm)
			* 2427 MHz [4] (20.0 dBm)
			* 2432 MHz [5] (20.0 dBm)
			* 2437 MHz [6] (20.0 dBm)
			* 2442 MHz [7] (20.0 dBm)
			* 2447 MHz [8] (20.0 dBm)
			* 2452 MHz [9] (20.0 dBm)
			* 2457 MHz [10] (20.0 dBm)
			* 2462 MHz [11] (20.0 dBm)
			* 2467 MHz [12] (20.0 dBm)
			* 2472 MHz [13] (20.0 dBm)
			* 2484 MHz [14] (disabled)
	interface combinations are not supported
	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	Supported extended features:
		* [ RRM ]: RRM
		* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
		* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211

lsmod

root@OpenWrt:~# lsmod
b43                   363971  0 
cfg80211              233424  2 b43,mac80211
compat                  6567  3 b43,mac80211,cfg80211
crc_ccitt               1051  1 ppp_async
ehci_hcd               42167  1 ehci_platform
ehci_platform           4288  0 
gpio_button_hotplug     6464  0 
ip_tables              11245  4 iptable_nat,iptable_mangle,iptable_filter
ip6_tables             10945 24 ip6table_mangle,ip6table_filter
ip6t_REJECT             1040  2 
ip6table_filter          704  1 
ip6table_mangle         1216  0 
ipt_MASQUERADE           736  1 
ipt_REJECT              1008  2 
iptable_filter           704  1 
iptable_mangle           960  0 
iptable_nat              768  1 
ledtrig_usbport         2800  0 
mac80211              462241  1 b43
nf_conntrack           70989 13 nf_conntrack_ipv6,ipt_MASQUERADE,xt_state,xt_nat,xt_conntrack,xt_REDIRECT,xt_CT,nf_nat_masquerade_ipv4,nf_conntrack_ipv4,nf_nat_ipv4,nf_nat,nf_flow_table,nf_conntrack_rtcache
nf_conntrack_ipv4       5168 10 
nf_conntrack_ipv6       5584  4 
nf_conntrack_rtcache    2752  0 
nf_defrag_ipv4          1174  1 nf_conntrack_ipv4
nf_defrag_ipv6          5022  1 nf_conntrack_ipv6
nf_flow_table          14031  2 xt_FLOWOFFLOAD,nf_flow_table_hw
nf_flow_table_hw        2240  1 
nf_log_common           2879  2 nf_log_ipv4,nf_log_ipv6
nf_log_ipv4             3424  0 
nf_log_ipv6             4112  0 
nf_nat                 15164  4 xt_nat,nf_nat_redirect,nf_nat_masquerade_ipv4,nf_nat_ipv4
nf_nat_ipv4             4017  1 iptable_nat
nf_nat_masquerade_ipv4    1628  1 ipt_MASQUERADE
nf_nat_redirect         1515  1 xt_REDIRECT
nf_reject_ipv4          2275  1 ipt_REJECT
nf_reject_ipv6          2728  1 ip6t_REJECT
nls_base                5456  1 usbcore
ohci_hcd               30127  1 ohci_platform
ohci_platform           3808  0 
ppp_async               7120  0 
ppp_generic            23138  3 pppoe,ppp_async,pppox
pppoe                   8672  0 
pppox                   1402  1 pppoe
slhc                    5147  1 ppp_generic
usb_common              2551  1 usbcore
usbcore               138769  5 ledtrig_usbport,ohci_platform,ohci_hcd,ehci_platform,ehci_hcd
x_tables               14175 24 ipt_REJECT,ipt_MASQUERADE,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,iptable_mangle,iptable_filter,ip_tables,ip6t_REJECT,ip6table_mangle,ip6table_filter,ip6_tables
xt_CT                   2720  0 
xt_FLOWOFFLOAD          2896  0 
xt_LOG                   816  0 
xt_REDIRECT              752  0 
xt_TCPMSS               2800  0 
xt_comment               528107 
xt_conntrack            2400 12 
xt_limit                1344 20 
xt_mac                   672  0 
xt_mark                  720  0 
xt_multiport            1312  0 
xt_nat                  1584  0 
xt_state                 768  0 
xt_tcpudp               1808  8 
xt_time                 1824  0 

Although there is another wifi in reach “iw dev wlan0 scan” on the device returns nothing.

This problem applies to current release of OpenWRT (18.06.2) and also to current Snapshot (r9393-d0b4596). It most certainly also applies to lede-17.01 but i haven’t tested it there for now. I think i had lede installed on the device during 2018 and had the same problem but i’m not sure.

Please let me know in case you need more info. I’m also willing to test things in order to help improve the OpenWRT support for the AV4202N. As the network gets found maybe the problem can be solved just by of configuration or arguments to the module.

19.02.20192134Base systemBug ReportVery LowLowMake image wdr3600TrunkUnconfirmed Task Description

Error make image wdr3600
[mktplinkfw] rootfs offset aligned to 0×1617792 [mktplinkfw] *** error: images are too big by 49405 bytes
cp /home/user/openwrt/build_dir/target-mips_24kc_musl/linux-ath79_generic/tmp/openwrt-ath79-generic-tplink_tl-wdr3600-squashfs-factory.bin /home/user/openwrt/bin/targets/ath79/generic/openwrt-ath79-generic-tplink_tl-wdr3600-squashfs-factory.bin
cp: cannot stat ‘/home/user/openwrt/build_dir/target-mips_24kc_musl/linux-ath79_generic/tmp/openwrt-ath79-generic-tplink_tl-wdr3600-squashfs-factory.bin’: No such file or directory
Makefile:82: recipe for target ‘/home/user/openwrt/bin/targets/ath79/generic/openwrt-ath79-generic-tplink_tl-wdr3600-squashfs-factory.bin’ failed

 


19.02.20192133KernelBug ReportVery LowCriticallan rx performance on IPQ806X (R7800) AllUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on R7800
- Software versions of OpenWrt 18.06/Trunk

Firstly ,I found my ps4 download speed only 100mbps,so I’ve run iperf3
The lan rx work in problem ,tx works no problem.
One pair rx only 18mbps ten pair rx only 100mbps but tx can run in 1gbps.

So I change to offical 18.06.2 banch,rx is 400mbps ,tx is 1Gbps. Still in problem.
After I compile trunk banch ,it also WIP as 18.06 banch.

This problem also mentioned in FS#1598

18.02.20192132PackagesBug ReportVery LowMediumumdns: unicast response is always sent to udp port 5353openwrt-18.06Unconfirmed Task Description

According to RFC 6762 - Multicast DNS (https://tools.ietf.org/html/rfc6762), section 6. Responding tells:

The destination UDP port in all Multicast DNS responses MUST be 5353, and the destination address MUST be the mDNS IPv4 link-local multicast address 224.0.0.251 or its IPv6 equivalent FF02::FB, except when generating a reply to a query that explicitly requested a unicast response:
* via the unicast-response bit,
* by virtue of being a legacy query (Section 6.7), or
* by virtue of being a direct unicast query.

But current umdns implementation sets sender’s IP as dst IP for the response and always sets dst port 5353 ignoring actual sender’s port while sending the unicast response.

Also RFC 6762 tells that simple DNS resolver that uses One-Shot Multicast DNS Queries MUST NOT use source port 5353 (sections 5. Querying and 5.1. One-Shot Multicast DNS Queries):

These queries are typically done using a high-numbered ephemeral UDP source port, but regardless of whether they are sent from a dynamic port or from a fixed port, these queries MUST NOT be sent using UDP source port 5353, since using UDP source port 5353 signals the presence of a fully compliant Multicast DNS querier.

So simple DNS resolver can not receive the response from umdns if it requests the unicast response due to dst port 5353 that is always set by umdns for all responses.

17.02.20192131Base systemBug ReportVery LowLowObserva VH4032N: wired LAN clients unable to communicat...openwrt-18.06Unconfirmed Task Description

Device: Observa VH4032N (bcm63xx/smp)
Version: at least from 17.1 to 18.06.2
Steps to reproduce: under the default config connect two devices via wired LAN to the device, try to contact one device from the other one (a ping will suffice). Result: timeout/host unreachable. However, contact with the router works without any issues.
I have only tested this with wired LAN clients, not between WLAN clients or LAN to WLAN.

“Dirty fix”: separate each LAN port into a VLAN (create a VLAN for each port) and bridge these VLAN interfaces with the LAN interface.
The corresponding part of /etc/config/network would look as follows:

config interface 'lan'
	option type 'bridge'
	option proto 'static'
	option netmask '255.255.255.0'
	option ip6assign '60'
	option ifname 'eth0.1 eth0.2 eth0.3 eth0.4'
	option ipaddr '192.168.1.1'

config switch
	option name 'switch0'
	option reset '1'
	option enable_vlan '1'

config switch_vlan
	option device 'switch0'
	option vlan '1'
	option ports '3 8t'

config switch_vlan
	option device 'switch0'
	option vlan '2'
	option ports '2 8t'

config switch_vlan
	option device 'switch0'
	option vlan '3'
	option ports '1 8t'

config switch_vlan
	option device 'switch0'
	option vlan '4'
	option ports '0 8t'


17.02.20192130Base systemBug ReportVery LowMediumusbip fails to list USB devices due to libudev-fbsdTrunkUnconfirmed Task Description

The usbip package fails to list connected USB devices. “usbip list -l” simply gives an empty return.

This is not a kernel issue, it’s caused by libudev-fbsd. The dependencies for usbip are still pointing to libudev-fbsd. This lib contains just a stub for udev_device_get_sysattr_value, which leads to the errors mentioned by blasters and arrmo. Using libudev instead, everything’s working as expected.

This problem exists in 18.06 and trunk.

17.02.20192129PackagesBug ReportVery LowLowblock-mount shows incorrect UUID for NTFSopenwrt-18.06Unconfirmed Task Description

Issue description:
block-mount shows incorrect UUID for NTFS.

System version:
OpenWrt 18.06.1

Steps to reproduce:

# opkg update
...
 
# opkg install block-mount blkid losetup lsblk ntfs-3g-utils
...
 
# opkg list-installed block-mount
block-mount - 2018-04-16-e2436836-1
 
# dd if=/dev/zero of=ntfs.img bs=100M count=1
1+0 records in
1+0 records out
 
# mkfs.ntfs -F ntfs.img
...
 
# losetup /dev/loop1 /root/ntfs.img

# block info /dev/loop1
/dev/loop1: UUID="0000001800000030" TYPE="ntfs"
 
!># block detect | grep -C1 loop1
config 'mount'
	option	target	'/mnt/loop1'
	option	uuid	'0000001800000030'
 
# blkid /dev/loop1
/dev/loop1: UUID="4C40EAF864A1397B" TYPE="ntfs" PTTYPE="dos"
 
# lsblk -o name,uuid /dev/loop1
NAME  UUID
loop1 4C40EAF864A1397B
16.02.20192126Base systemBug ReportVery LowMediumDisable IPv6 link-local for VLAN-parent, bridge-slave, ...openwrt-18.06Unconfirmed Task Description

Disable IPv6 link-local for VLAN-parent, bridge-slave, L3-tunnel.

System version:
OpenWrt 18.06.1

Interfaces configured correctly:
lo, br-lan, eth0.1, eth0.2

Interfaces configured incorrectly:
* eth0 - VLAN-parent, should not have L3-address
* wlan0 - bridge-slave, should not have L3-address
* tun0 - L3-tunnel, IPv6 link-local breaks OpenVPN IPv6-connectivity for Windows-clients and is redundant for Linux-clients

16.02.20192125Base systemBug ReportVery LowMediumdropbear race condition with ipv6 networkingopenwrt-18.06Unconfirmed Task Description

I’m running OpenWRT on an x86 machine running OpenWRT 18.06.2.

Steps to reproduce:

Configure dropbear to only listen on an interface such as ‘lan’

 
  config dropbear
    option Interface 'lan'

After rebooting, often dropbear will be bound to 192.168.1.1, but not fd00:2233:4455:1::1 (router’s ipv6 address). Restarting dropbear fixes the problem and it binds correctly to the ipv4 and ipv6 lan address.

12.02.20192123KernelBug ReportVery LowCriticalmac80211: 802.11s TCP/IP Connectivity Fails After 2018-...TrunkUnconfirmed Task Description

802.11s mesh appears to not transport TCP/IP even though the mesh
appears up, for commits on master after late September, 2018.

(Steps to replicate at the end of this message)

The output of `iw dev mesh0 station dump` yields similar results for
working and non-working builds, though it has been confirmed after
the posting to the openwrt-devel list (archive link attached) that
“mesh peer PS mode” never seems to be “ACTIVE”
on builds after “first failing commit” (identified below).

    mesh plink:    ESTAB
    mesh local PS mode:    ACTIVE
    mesh peer PS mode:    UNKNOWN
    mesh non-peer PS mode:    ACTIVE
    authorized:    yes
    authenticated:    yes
    associated:    yes

ping to the peer(s) prior to the first failing commit is successful and
the peer is reflected in the arp table. Full connectivity can be
established over the mesh to peers with UDP or TCP transport.

Both ping and arp fail to behave as expected on or after the first
failing commit.

The routing is the same for both builds.

Behavior seen on both Archer C7 v2 (QCA9880-BR4A v2)
and a GL.iNet AR750S (QCA9887), both on ath79 target (AR750S is WIP)

Confirmed that the newer (newest?) firmware (ver 10.2.4-1.0-00041)
works on the “old” build.

Lack of TCP/IP transport over the mesh confirmed both with 802.11s
integral routing, as well with 802.11s routing disabled and replaced
with batman-adv. Configuration using both 802.11s routing and
batman-adv on distinct meshes on the same radios has been running
successfully with four or five Archer C7 v2 units for both backhaul
over the 5 GHz mesh, as well as client access on 5 GHz. (Not tested
on 2.4 GHz on either the Archer C7 or the AR750S.)

git bisect was used to identify the “first failing commit”:

commit db90c243a0b9bd72fc691cd09e58a96ac2a452cf
Author: Hauke Mehrtens <redacted>
Date:   Sun Sep 23 18:02:35 2018 +0200

    mac80211: update to version based on 4.19-rc4

Note that the Candela Technologies drivers do not appear to support
mesh on either chipset.

Additional notes at
https://forum.openwrt.org/t/mac80211-802-11s-tcp-ip-connectivity-on-master-failing-after-2018-09/30629

Thanks to @slh and Koen for hopping on thing there!

To Replicate:

=⇒ Pick your target of choice

$ ./scripts/diffconfig.sh
CONFIG_TARGET_ath79=y
CONFIG_TARGET_ath79_generic=y
CONFIG_TARGET_ath79_generic_DEVICE_glinet_gl-ar750s-nor=y
CONFIG_DEVEL=y
CONFIG_ATH10K_LEDS=y
CONFIG_BUILD_LOG=y
CONFIG_CCACHE=y
CONFIG_OPENSSL_WITH_DEPRECATED=y
CONFIG_OPENSSL_WITH_EC=y
CONFIG_OPENSSL_WITH_NPN=y
CONFIG_OPENSSL_WITH_PSK=y
CONFIG_OPENSSL_WITH_SRP=y
CONFIG_PACKAGE_ath10k-firmware-qca9887=y
# CONFIG_PACKAGE_ath10k-firmware-qca9887-ct is not set
CONFIG_PACKAGE_diffutils=y
CONFIG_PACKAGE_findutils-find=y
CONFIG_PACKAGE_kmod-ath10k=y
# CONFIG_PACKAGE_kmod-ath10k-ct is not set
# CONFIG_PACKAGE_kmod-hwmon-core is not set
CONFIG_PACKAGE_less=y
CONFIG_PACKAGE_libncurses=y
CONFIG_PACKAGE_libopenssl=y
CONFIG_PACKAGE_terminfo=y
# CONFIG_PACKAGE_wpad-basic is not set
CONFIG_PACKAGE_wpad-mesh-openssl=y

=⇒ Add to `/etc/config/network`

config interface 'nwi_mesh0'
    option ifname 'mesh0'
    option mtu '2304'
    option proto 'static'
    option ipaddr '172.16.0.NNN'
    option netmask '255.255.255.0'

=⇒ Add to / replace in `/etc/config/wireless`

  • Please confirm a valid channel for your location
  • Adjust the device path/reference as needed
  • ‘n’ used for support of older iPhones here
config wifi-device 'radio5'
    option type 'mac80211'
    option channel '149'
    option hwmode '11a'
    option path 'pci0000:00/0000:00:00.0'
    option htmode 'VHT80'
        option require_mode 'n'

config wifi-iface 'mesh0'
    option device 'radio5'
    option ifname 'mesh0'
    option network 'nwi_mesh0'
    option mode 'mesh'
    option mesh_id 'TestMesh'
    option mesh_fwding '1'
    option encryption 'psk2+ccmp'
    option key 'TestMeshPassPhrase'

=⇒ Flash and configure additional unit(s), changing the last octet
of the nwi_mesh0 interface address.

=⇒ Note that the mesh appears established from the output of
`iw dev mesh0 station dump`

=⇒ Note that the one unit can’t ping the other’s nwi_mesh0 address
when building on or after “first bad commit” but ping (arp and ip
neigh) will work as expected prior to that commit.


12.02.20192122Base systemBug ReportVery LowMediumNAT-Loopback not working with NCM protocolTrunkUnconfirmed Task Description

Hi,

today I updated my LEDE installation to OpenWRT 18.06.2 in hope, it fixes some problems:

One of them is, that the NAT loopback rules get not automatically created on interface up / firewall reload

I think, it is because of the virtually assigned _4 / _6 suffix of the interface name.

11.02.20192121Base systemBug ReportVery LowLowfirstboot -> "writing /dev/ubi0_2 failed: Operation not...openwrt-18.06Unconfirmed Task Description

bt home hub 5a running OpenWrt 18.06.2

Boot into failsafe mode then “firstboot” results in:
writing /dev/ubi0_2 failed: Operation not permitted

Extra info:

root@(none):~# mount
/dev/root on / type squashfs (ro,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
tmpfs on /dev type tmpfs (rw,nosuid,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,noatime,mode=600,ptmxmode=000)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)

root@(none):~# cat /proc/mtd
dev: size erasesize name
mtd0: 000a0000 00020000 “u-boot” mtd1: 00020000 00020000 “uboot-env” mtd2: 00040000 00020000 “unused” mtd3: 07e80000 00020000 “ubi”

root@(none):~# firstboot
This will erase all settings and remove any installed packages. Are you sure? [N/y]
y
/dev/ubi0_2 is not mounted
/dev/ubi0_2 will be erased on next mount
writing /dev/ubi0_2 failed: Operation not permitted

11.02.20192119PackagesBug ReportVery LowLowPython and Python3 pip and setuptools compilation step AllUnconfirmed Task Description

When compiling on new version of my OS (Gentoo) I encounter problem with Python and Python3 compilation. Originally there was no problem just weeks before but now I am not able to compile those two packages. It always fails on missing libffi.so.6.

Traceback (most recent call last):
  File "/home/build/run/turris-kittens-mox/8/openwrt/staging_dir/hostpkg/bin/pip3", line 7, in <module>
    from pip._internal import main
  File "/home/build/run/turris-kittens-mox/8/openwrt/staging_dir/hostpkg/lib/python3.6/site-packages/pip/_internal/__init__.py", line 42, in <module>
    from pip._internal import cmdoptions
  File "/home/build/run/turris-kittens-mox/8/openwrt/staging_dir/hostpkg/lib/python3.6/site-packages/pip/_internal/cmdoptions.py", line 16, in <module>
    from pip._internal.index import (
  File "/home/build/run/turris-kittens-mox/8/openwrt/staging_dir/hostpkg/lib/python3.6/site-packages/pip/_internal/index.py", line 25, in <module>
    from pip._internal.download import HAS_TLS, is_url, path_to_url, url_to_path
  File "/home/build/run/turris-kittens-mox/8/openwrt/staging_dir/hostpkg/lib/python3.6/site-packages/pip/_internal/download.py", line 39, in <module>
    from pip._internal.utils.glibc import libc_ver
  File "/home/build/run/turris-kittens-mox/8/openwrt/staging_dir/hostpkg/lib/python3.6/site-packages/pip/_internal/utils/glibc.py", line 3, in <module>
    import ctypes
  File "/home/build/run/turris-kittens-mox/8/openwrt/staging_dir/hostpkg/lib/python3.6/ctypes/__init__.py", line 7, in <module>
    from _ctypes import Union, Structure, Array
ImportError: libffi.so.6: cannot open shared object file: No such file or directory


The problem is in invalid environment used to run pip. In package python that is on line 170 and 179. In package python3 that is 174 and 183. They are missing something like HostPyRunTarget.

11.02.20192118OtherFeature RequestVery LowHighRenaming pre-configured firewall-zone names...AllUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on
This is a suggestion and is not a model-specific bug report.

- Software versions of OpenWrt/LEDE release, packages, etc.
OpenWrt 18.06.1, r7258-5eb055306f

- Steps to reproduce
Description below:

This is a decade-old suggestion I’ve held within and I really hope the words will gather enough attention and momentum of the dev team. Streight to the conclusion, two pre-configured firewall-zones IMHO should be renamed from “lan” to “internal” and “wan” to “external” respectively. There are a few reasons for which I confidently feel this should be done. I’d like to argue that this is important if not essential because;
a.)Those who prefer making changes to current configurations by editing /etc/config/*, using stuff like “sed -i ‘s/before/after/g’ ${file}” (and then proceeding to reboot) is powerful and is almost mistake-free. checking for config-mistakes using grep is also powerful (and this applies to folks using uci CUI tool as well). What I do now is rename these two zones from GUI and then proceed to these steps, and it works great but having to take this extra step is rather inconvenient if not annoying.
b.)Current presets for interfaces have IPv4-WAN named as “wan” and IPv6-WAN named as “wan6” where the IPv4-WAN‘s label “wan” is no different from the firewalled-zone labeled as “wan”. This is simply comfusing. In early days when I I had just heard about the OpenWrt and had started messing with releases like Kamikaze,I had hard times understanding which string corresponded to which (sure you may argue this is documented in details but things don’t work like that for newbies).
c.)If needs for either firewall-zones or the interface-labels to be renamed are understood, I’d then have to say I’m against renaming interface-labels because those who’d decide to use VLANs would most likely name the interfaces as “config interface ‘vlan_ID’” and the string lan would stay in there.

I hope the above proposal is powerful enough...

11.02.20192117Base systemBug ReportVery LowMediumFirewall - Custom Rules ingonred in some casesAllUnconfirmed Task Description

- Device problem occurs on
linkys WRT3500
- Software versions of OpenWrt/LEDE release, packages, etc.
all lede versions
- Steps to reproduce
Configure iptables custom rules in LUCI luci/admin/network/firewall/custom
the commands goes to /etc/firewall.user file

part of /etc/config/firewall:


config include

      option path '/etc/firewall.user'

———–

Note there is no “option reload ‘1’” added into config file, thus “fw3 reload” used in /etc/init.d/firewall and /etc/hotplug.d/iface/20-firewall (maybe somewhere else) does not reload user rules.

adding manually option “reaload 1” into /etc/config/firewall solve this issue.

11.02.20192116KernelBug ReportVery LowMediumNanopi NEO PLUS2 kernel: OTG USB not workingopenwrt-18.06Unconfirmed Task Description

Even with a recent devicetree fix, the OTG port does not seem to function in the desired host mode. Obviously because of the hardware design, it is intended to always operate in “host” mode, and this is confirmed by the devicetree. Plugging in a USB 2.0 device into this OTG port and then running lsusb shows notink!

dmesg shows notink.

If you look at the devicetree compatibility string for the “otg” node, and then grep the kernel source code for it, it takes you to a driver which is enabled by this line in the drivers/usb/musb/Makefile:

obj-$(CONFIG_USB_MUSB_SUNXI) += sunxi.o

There is no evidence that this “MUSB” party is happening in the kernel config file fragments. And since this kernel does not enable /proc/config.gz, there is a remnant of doubt about where one actually finds a complete kernel config file for this 4.14 kernel build, but I leave that for another day.

10.02.20192115KernelBug ReportVery LowCriticalkernel panic with Hardware flow offloading on ubnt-x (M...TrunkUnconfirmed Task Description

hardware ubnt-x (edgerouter-x)
openwrt: OpenWrt SNAPSHOT, r9293-e3311cb

I turn on hardware offload and system went south (hangup). Automatic hard
reset (by kernel itself or because of watchcat)
But syslogd logs to other machine and
this is what I found in logs:

Feb 10 21:04:59 thorgal kernel: [ 6300.830740]  (t=6003 jiffies g=60795 c=60794 q=1375)
Feb 10 21:04:59 thorgal kernel: [ 6300.860492] (detected by 1, t=6006 jiffies, g=60795, c=60794, q=1375)
Feb 10 21:04:59 thorgal kernel: [ 6300.863610] rcu_sched       I
Feb 10 21:04:59 thorgal kernel: [ 6300.884363] Sending NMI from CPU 1 to CPUs 3:
Feb 10 21:04:59 thorgal kernel: [ 6300.897157]     0     8      2 0x00100000
Feb 10 21:04:59 thorgal kernel: [ 6300.919637] Stack : 805b0000 8fc42bc0 8fc5fe30 8fc5fe30 81222380 8fc5fe30 805b0000 81222380
Feb 10 21:04:59 thorgal kernel: [ 6300.936268]         00000003 80086ddc 000912c6 81222380 81222380 8fc5fe30 805b0000 81222380
Feb 10 21:04:59 thorgal kernel: [ 6300.952899]         00000003 805ae1b8 805b6550 80491eec 00000001 8fc5fe30 805b0000 000912c6
Feb 10 21:04:59 thorgal kernel: [ 6300.969530]         81222380 80494e14 00000003 80082e28 805b0000 00000000 8fc5febc 00000001
Feb 10 21:04:59 thorgal kernel: [ 6300.986160]         00000000 812223f4 000912c6 8008732c 8fc42bc0 01c00001 00000001 805b6440
Feb 10 21:04:59 thorgal kernel: [ 6301.002793]         ...
Feb 10 21:04:59 thorgal kernel: [ 6301.007654] Call Trace:
Feb 10 21:04:59 thorgal kernel: [ 6301.012531] [<80491dcc>] __schedule+0x7ac/0x860
Feb 10 21:04:59 thorgal kernel: [ 6301.021543] [<80491eec>] schedule+0x6c/0x84
Feb 10 21:04:59 thorgal kernel: [ 6301.029863] [<80494e14>] schedule_timeout+0x17c/0x1b8
Feb 10 21:04:59 thorgal kernel: [ 6301.039912] [<80083444>] rcu_gp_kthread+0x560/0x950
Feb 10 21:04:59 thorgal kernel: [ 6301.049626] [<8004c1b8>] kthread+0x130/0x144
Feb 10 21:04:59 thorgal kernel: [ 6301.058120] [<8000b0d8>] ret_from_kernel_thread+0x14/0x1c
Feb 10 21:04:59 thorgal kernel: [ 6304.380977] NMI backtrace for cpu 3
Feb 10 21:04:59 thorgal kernel: [ 6304.387914] CPU: 3 PID: 2514 Comm: kworker/3:1 Not tainted 4.14.98 #0
Feb 10 21:04:59 thorgal kernel: [ 6304.400742] Workqueue: events rht_deferred_worker
Feb 10 21:04:59 thorgal kernel: [ 6304.410088] Stack : 8053ac44 8fc15d24 805b0000 8e9f3280 8053acd8 00000003 805b6440 805ae0ac
Feb 10 21:04:59 thorgal kernel: [ 6304.426716]         000000e0 800705fc 8ff0af3c 805b0947 805b0000 00000001 8fc15ce8 53261683
Feb 10 21:04:59 thorgal kernel: [ 6304.443343]         00000000 00000000 00000000 00003c40 00000000 000000dd 00000008 00000000
Feb 10 21:04:59 thorgal kernel: [ 6304.459969]         00000000 805b0000 00061d66 00000000 00000000 00000000 805d0000 00000003
Feb 10 21:04:59 thorgal kernel: [ 6304.476595]         805b6440 805ae0ac 000000e0 805b0000 00000000 802a4378 0000000c 8061000c
Feb 10 21:04:59 thorgal kernel: [ 6304.493222]         ...
Feb 10 21:04:59 thorgal kernel: [ 6304.498076] Call Trace:
Feb 10 21:04:59 thorgal kernel: [ 6304.502943] [<800106c0>] show_stack+0x58/0x100
Feb 10 21:04:59 thorgal kernel: [ 6304.511777] [<80478bfc>] dump_stack+0x9c/0xe0
Feb 10 21:04:59 thorgal kernel: [ 6304.520447] [<8047fa94>] nmi_cpu_backtrace+0xe4/0x108
Feb 10 21:04:59 thorgal kernel: [ 6304.530488] [<8047fb80>] nmi_trigger_cpumask_backtrace+0xc8/0x168
Feb 10 21:04:59 thorgal kernel: [ 6304.542606] [<80084dd8>] rcu_dump_cpu_stacks+0xc4/0x13c
Feb 10 21:04:59 thorgal kernel: [ 6304.552993] [<80084228>] rcu_check_callbacks+0x3b4/0x8b8
Feb 10 21:04:59 thorgal kernel: [ 6304.563560] [<800877a8>] update_process_times+0x34/0x7c
Feb 10 21:04:59 thorgal kernel: [ 6304.573963] [<8009838c>] tick_handle_periodic+0x34/0xd0
Feb 10 21:04:59 thorgal kernel: [ 6304.584364] [<803275e0>] gic_compare_interrupt+0x70/0x80
Feb 10 21:04:59 thorgal kernel: [ 6304.594930] [<80077ba0>] handle_percpu_devid_irq+0xbc/0x1a8
Feb 10 21:04:59 thorgal kernel: [ 6304.606024] [<80071ef0>] generic_handle_irq+0x40/0x58
Feb 10 21:04:59 thorgal kernel: [ 6304.616071] [<8025339c>] gic_handle_local_int+0x9c/0xe8
Feb 10 21:04:59 thorgal kernel: [ 6304.626458] [<8025355c>] gic_irq_dispatch+0x10/0x20
Feb 10 21:04:59 thorgal kernel: [ 6304.636153] [<80071ef0>] generic_handle_irq+0x40/0x58
Feb 10 21:04:59 thorgal kernel: [ 6304.646199] [<80495fcc>] do_IRQ+0x1c/0x2c
Feb 10 21:04:59 thorgal kernel: [ 6304.654166] [<8025252c>] plat_irq_dispatch+0xfc/0x138
Feb 10 21:04:59 thorgal kernel: [ 6304.664209] [<8000b5e8>] except_vec_vi_end+0xb8/0xc4
Feb 10 21:04:59 thorgal kernel: [ 6304.674076] [<8006a94c>] queued_spin_lock_slowpath+0x1dc/0x2e0
Feb 10 21:04:59 thorgal kernel: [ 6304.685677] [<802386ac>] rht_deferred_worker+0x20c/0x4f0
Feb 10 21:04:59 thorgal kernel: [ 6304.696236] [<80046230>] process_one_work+0x258/0x400
Feb 10 21:04:59 thorgal kernel: [ 6304.706276] [<80046728>] worker_thread+0x350/0x5b4
Feb 10 21:04:59 thorgal kernel: [ 6304.715806] [<8004c1b8>] kthread+0x130/0x144
Feb 10 21:04:59 thorgal kernel: [ 6304.724291] [<8000b0d8>] ret_from_kernel_thread+0x14/0x1c
10.02.20192114Base systemBug ReportVery LowHighWG302v1 (ixp4xx-generic) LAN (eth0) start and then stop...openwrt-18.06Unconfirmed Task Description

Hello

Device: Netgear WG302v1 ixp4xx
FW: 18.06.1 & 18.06.2

Device problem occurs at boot.
During boot LAN (eth0) become ready (LEDs are lit) and then stop after ~2 or ~3 seconds (LEDs are off).
WAN (radio) interface seems working but Ethernet (eth0) is down.
Impossible to get it up because ifconfig up have no effect.

No packages are installed only stock zImage and Shashfs.

With 18.06.1 (default config, IP after flashing) :
OpenWRT say that ethO is up and ready but eth0 and LEDs are off.
Impossible to reach LuCi or ping a computer with IP 192.168.1.10 (connected through serial console on device)
At boot eth0 stay up sometimes ~ 1 of 20.

With 18.06.2 (default config, IP after flashing) :
It seems there are more information during boot.
Kernel is reporting that br-lan: port 1(eth0) entered disabled stat
ifconfig up/down has no effect.

Step to reproduce:
Flash & boot.

You can find included as attached file 18.06.1 & 18.06.2 dmesg boot log.

Kind Regards

10.02.20192113Base systemBug ReportVery LowMediumLost connection to router after bridgingAllUnconfirmed Task Description

Supply the following if possible:
- Problem occurs on all (at least tp-link 842ndv3,841nd,741nd) devices with ar943x
- Software versions of OpenWrt/LEDE: openwrt 18.06, lede 17.04
- Steps to reproduce

 

1. create switch configuration:
config switch

      option name 'switch0'
      option reset '1'
      option enable_vlan '1'

config switch_vlan

      option device 'switch0'
      option vlan '1'
      option ports '0t 4'
      option vid '1'

config switch_vlan

      option device 'switch0'
      option vlan '2'
      option vid '2'
      option ports '0t 3'

config switch_vlan

      option device 'switch0'
      option vlan '3'
      option vid '3'
      option ports '0t 2t'

config switch_vlan

      option device 'switch0'
      option vlan '4'
      option vid '4'
      option ports '0t 1'


2. add interfaces eth0.2, eth0.3, eth0.4 into br-lan bridge

3. now we have unreachable device

10.02.20192112Base systemBug ReportVery LowLowRalink MT7620a + MT7610e evaluation boardTrunkUnconfirmed Task Description

I have a device that identifies as a MT7620A + MT7610e EVB:

cat /proc/cpuinfo
system type             : MediaTek MT7620A ver:2 eco:6
machine                 : Ralink MT7620a + MT7610e evaluation board
processor               : 0
cpu model               : MIPS 24KEc V5.0
BogoMIPS                : 385.84
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 32
extra interrupt vector  : yes
hardware watchpoint     : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa                     : mips1 mips2 mips32r1 mips32r2
ASEs implemented        : mips16 dsp
shadow register sets    : 1
kscratch registers      : 0
package                 : 0
core                    : 0
VCED exceptions         : not available
VCEI exceptions         : not available

I have been trying to load various openWrt releases onto it. None have been successful, and using the latest release that seems to match this hardware:

https://downloads.openwrt.org/releases/18.06.2/targets/ramips/mt7620/openwrt-18.06.2-ramips-mt7620-mt7620a_mt7610e-squashfs-sysupgrade.bin

I can see, from dmesg, that there is a problem with SPI:

Loading: Got ARP REPLY, set server/gtwy eth addr (1c:39:47:da:8f:4b)
Got it
#################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 ######################################################
done
Bytes transferred = 3932340 (3c00b4 hex)
NetBootFileXferSize= 003c00b4
Automatic boot of image at addr 0x80A00000 ...
## Booting image at 80a00000 ...
   Image Name:   MIPS OpenWrt Linux-4.14.95
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1437278 Bytes =  1.4 MB
   Load Address: 80000000
   Entry Point:  80000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
No initrd
## Transferring control to Linux (at address 80000000) ...
## Giving linux memsize in MB, 128

Starting kernel ...

[    0.000000] Linux version 4.14.95 (buildbot@builds-03.infra.lede-project.org) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r7627-753531d)) #0 Mon Jan 28 08:54:32 2019
[    0.000000] Board has DDR2
[    0.000000] Analog PMU set to hw control
[    0.000000] Digital PMU set to hw control
[    0.000000] SoC Type: MediaTek MT7620A ver:2 eco:6
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019650 (MIPS 24KEc)
[    0.000000] MIPS: machine is Ralink MT7620A evaluation board
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 08000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] random: get_random_bytes called from 0x8042472c with crng_init=0
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,57600 rootfstype=squashfs,jffs2
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Writing ErrCtl register=0003f200
[    0.000000] Readback ErrCtl register=0003f200
[    0.000000] Memory: 125216K/131072K available (3590K kernel code, 178K rwdata, 464K rodata, 176K init, 214K bss, 5856K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 256
[    0.000000] CPU Clock: 580MHz
[    0.000000] clocksource: systick: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 583261500 ns
[    0.000000] systick: enable autosleep mode
[    0.000000] systick: running - mult: 214748, shift: 32
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6590553264 ns
[    0.000012] sched_clock: 32 bits at 290MHz, resolution 3ns, wraps every 7405115902ns
[    0.015477] Calibrating delay loop... 385.84 BogoMIPS (lpj=1929216)
[    0.087712] pid_max: default: 32768 minimum: 301
[    0.097140] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.110157] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.129997] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.149480] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.161658] pinctrl core: initialized pinctrl subsystem
[    0.173277] NET: Registered protocol family 16
[    0.184832] rt2880-pinmux pinctrl: error claiming hogs: -22
[    0.195821] rt2880-pinmux pinctrl: could not claim hogs: -22
[    0.207099] rt2880-pinmux: probe of pinctrl failed with error -22
[    0.220550] Can't analyze schedule() prologue at 8037d498
[    0.231473] mt7620-pci 10140000.pcie: could not find pctldev for node /pinctrl/pcie, deferring probe
[    0.266577] rt2880_gpio 10000600.gpio: registering 24 gpios
[    0.277609] rt2880_gpio 10000600.gpio: registering 24 irq handlers
[    0.293963] clocksource: Switched to clocksource systick
[    0.305616] NET: Registered protocol family 2
[    0.315188] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.328966] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.341553] TCP: Hash tables configured (established 1024 bind 1024)
[    0.354324] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.365831] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.378529] NET: Registered protocol family 1
[    0.389802] rt-timer 10000100.timer: maximum frequency is 1220Hz
[    0.402541] Crashlog allocated RAM at address 0x3f00000
[    0.414676] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[    0.433435] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.444930] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.474961] io scheduler noop registered
[    0.482605] io scheduler deadline registered (default)
[    0.493790] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.508955] of_serial 10000c00.uartlite: could not find pctldev for node /pinctrl/uartlite, deferring probe
[    0.528624] cacheinfo: Failed to find cpu0 device node
[    0.538715] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    0.551498] spi-rt2880 10000b00.spi: could not find pctldev for node /pinctrl/spi, deferring probe
[    0.569831] libphy: Fixed MDIO Bus: probed
[    0.578410] mtk_soc_eth 10100000.ethernet: could not find pctldev for node /pinctrl/ephy, deferring probe
[    0.597719] rt2880_wdt 10000120.watchdog: Initialized
[    0.609110] NET: Registered protocol family 10
[    0.628789] Segment Routing with IPv6
[    0.636102] NET: Registered protocol family 17
[    0.644844] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    0.670578] 8021q: 802.1Q VLAN Support v1.8
[    0.679558] mt7620-pci 10140000.pcie: could not find pctldev for node /pinctrl/pcie, deferring probe
[    0.697775] of_serial 10000c00.uartlite: could not find pctldev for node /pinctrl/uartlite, deferring probe
[    0.717130] spi-rt2880 10000b00.spi: could not find pctldev for node /pinctrl/spi, deferring probe
[    0.734937] mtk_soc_eth 10100000.ethernet: could not find pctldev for node /pinctrl/ephy, deferring probe
[    0.755186] Warning: unable to open an initial console.
[    0.766222] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[    0.781014] Please append a correct "root=" boot option; here are the available partitions:
[    0.797592] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    0.814958] Rebooting in 1 seconds..

This seems very similar to the issue reported here:

https://bugs.openwrt.org/index.php?do=details&task_id=1515&opened=1266&status%5B0%5D=

Though that was for slightly different hardware.

Any ideas...?

10.02.20192111Base systemBug ReportVery LowLowLinksys EA3500 drops internet connectivity but doesn't ...openwrt-18.06Unconfirmed Task Description

On a Linksys EA3500, I’ve flashed 18.06.2 from the OEM firmware. I tried to setup two WPA2 networks (2.4 and 5.0) for my small apartment. I’m able to connect to both networks from laptops and phones, and the router maintains the connections, but internet connectivity gets dropped and picked up in rapid succession - choppy is apropos. But running successive speedtests shows a near constant 11.00-69 Mbit/s connection.

I’ve attached the System log, Kernel log, and a file with `uname -a` and `opkg list-installed`. There are several suspicious RF and TF antenna failures in the logs

I suspected at first it was an issue with the router having too high TX/RX, because I really do have a really small apartment. But that option is set to auto. FWIW, I am able to `ssh` to the router from all my devices OK, but trying to `ssh` to other connected devices on the network is not practical - i.e., it is possible after waiting for the connection for 10+ minutes, and when the connection is made, there is an unbelievable amount of lag.

On IRC, it was suggested that I go to 18.06.0 before trying to put the OEM firmware back. This issue is not unlike this one: https://dev.archive.openwrt.org/ticket/21284.

DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='18.06.2'
DISTRIB_REVISION='r7676-cddd7b4c77'
DISTRIB_TARGET='kirkwood/generic'
DISTRIB_ARCH='arm_xscale'
DISTRIB_DESCRIPTION='OpenWrt 18.06.2 r7676-cddd7b4c77'
DISTRIB_TAINTS=''
09.02.20192110Base systemBuild FailureVery LowMediumRamips rt305x A5 v11 break on 18.06.2, no ramips/rt305x...openwrt-18.06Unconfirmed Task Description

The builds have been failing since December 5th it seems, the External Linklatest buildbot log shows it’s choking on the A5 v11 images not being generated. As a result no rt305x images seem to be available at all on 18.06.2 - the rt305x folder is not listed among the .2 downloads while it’s still there on .1.

First reported here.


07.02.20192109Base systemBug ReportVery LowMediumAsus RT-AC51U - LEDs not working at all openwrt-18.06Unconfirmed Task Description

Device: ASUS RT-AC51U
Software: openwrt-18.06.2-ramips-mt7620-rt-ac51u-squashfs-sysupgrade.bin
Packages: default

LED configuration isn’t working at all, tried all possibilities available on the LuCi Interface (only power LED is working)
Tried also switching of LEDs on command line as described on OpenWRT website, but failed
Searched in forum, but only found another user with exactly the same problem

 


06.02.20192107Base systemBug ReportVery LowLowdnsmasq instances can read DHCP host files of all other...TrunkUnconfirmed Task Description

If multiple instances of dnsmasq are configured, then every instance has access to the DHCP host files of all other instances of dnsmasq.

For example, if two instances are configured in /etc/config/dhcp, “default” and “guest”, then when they are started (or if they receive SIGHUP), then each instance will log something like this to syslog:

Thu Feb  7 04:26:47 2019 daemon.info dnsmasq[3092]: read /tmp/hosts/odhcpd - 1 addresses
Thu Feb  7 04:26:47 2019 daemon.info dnsmasq[3092]: read /tmp/hosts/dhcp.default - 2 addresses
Thu Feb  7 04:26:47 2019 daemon.info dnsmasq[3092]: read /tmp/hosts/dhcp.guest - 2 addresses

From /etc/init.d/dnsmasq it doesn’t look like this is intentional, as procd_add_jail_mount() is called with the instance’s own host file ($HOSTFILE) only.

06.02.20192106KernelBug ReportVery LowMediumnew storage and match method required in firewall3/ipse...AllUnconfirmed Task Description

The new version of ipset now incoporates new set type: “hash:mac”.

But in openwrt project firewall3/ipset.c this new set type is not supported (line 68-87).

The result is that while refreshing firewall error message “Section @ipset has an invalid combination of storage method and matches” would appear, and no set type is created.

Please made some revision.

Thank you!

06.02.20192105KernelBug ReportVery LowHighnfs-kernel-server: exportfs always segfaultsTrunkUnconfirmed Task Description

This happens on the latest snapshot (2019-02-07) on TP-Link Archer C7. It did not happen on a snapshot from 2019-01-28.

To reproduce:

1. Create /etc/exports as follows:

/mnt/bigdisk	192.168.1.0/255.255.255.0(rw,mp,all_squash,no_subtree_check,insecure,sync)

2. install nfs-kernel-server

Or just run: exportfs -a

Result: exportfs segfaults.

I believe this is a kernel problem, because downgrading nfs-kernel-server to the version in OpenWRT 18.06.2 does not help.

06.02.20192104Base systemBug ReportVery LowLowwireguard: adds endpoint host to routing list. ( withou...TrunkUnconfirmed Task Description

Environment: ramips, OpenWrt 18.06.[1-2], MediaTek MT7621, Xiaomi Mi Router 3G

Description:
I tried to setup router as WG client for a while. But it doesn’t work on my setup.
After research, I realized that licu-wireguard application adds a static route somehow.
Also after terminating the wireguard connection, that static routing record does not removed. After removal of non needed record of endpoint from routing table (51.x.x.x in my setup) by hand, Wireguard starts working proper.

root@MainRouter:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.2.1     0.0.0.0         UG    0      0        0 eth0.2
10.0.2.0        *               255.255.255.0   U     0      0        0 wg0
51.x.x.x        MainRouter.lan  255.255.255.255 UGH   0      0        0 br-lan
192.168.1.0     *               255.255.255.0   U     0      0        0 br-lan
192.168.2.0     *               255.255.255.0   U     0      0        0 eth0.2

PS: MainRouter.lan is name of the router. (192.168.1.1)

06.02.20192103Base systemBug ReportVery LowMediumprocd: respawn parameters lost when using /etc/init.d/<...TrunkUnconfirmed Task Description

procd loses respawn parameters when using /etc/init.d/<program>/restart
This happens when the program takes too long time to stop.

Here is the reason why:
1. in instance.c, the respawn and restart bools are set to false.

//instance.c
void
instance_stop(struct service_instance *in, bool halt)
{
...
	in->restart = in->respawn = false; => restart and respawn bool set to false
	kill(in->proc.pid, SIGTERM);
...
}

2. in service_handle_set (called for starting the process anew), we have the following code:

	s = avl_find_element(&services, name, s, avl);
	if (s) {
		DEBUG(2, "Update service %s\n", name);
		return service_update(s, tb, add); => we are here, because the program didn't yet terminate ! avl_find_element doesn't return NULL
	}

	DEBUG(2, "Create service %s\n", name);
	s = service_alloc(name);
	if (!s)
		return UBUS_STATUS_UNKNOWN_ERROR;

	ret = service_update(s, tb, add);

In my case, avl_find_element returns the previous instance because the program didn’t close yet. service_update is called on the previous structure, without allocating a new one.

problem: in→restart and in→respawn are still false !
consequence: “respawn” parameters are lost. This is visible in the output of

ubus call service list '{"name":"program"}'

example:
before /etc/init.d/program/restart :

        "program": {
                "instances": {
                        "program": {
                                "running": true,
                                "pid": 4904,
                                "command": [
                                        "\/usr\/bin\/program",
                                ],
                                "term_timeout": 5,
                                "limits": {
                                        "core": "unlimited" 
                                },
                                "respawn": {
                                        "threshold": 3600,
                                        "timeout": 1,
                                        "retry": 0
                                },
                                "pidfile": "\/var\/run\/program.pid" 
                        }
                }
        },

after

        "program": {
                "instances": {
                        "program": {
                                "running": true,
                                "pid": 4904,
                                "command": [
                                        "\/usr\/bin\/program",
                                ],
                                "term_timeout": 5,
                                "limits": {
                                        "core": "unlimited" 
                                },
                                "pidfile": "\/var\/run\/program.pid" 
                        }
                }
        },
05.02.20192102Base systemBug ReportVery LowHighipq806x: ath10k-firmware-qca9984-ct crashes systemTrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

 tplink-c2600
 netgear-r7800

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

 18.06.2

- Steps to reproduce

 opkg remove ath10k-firmware-qca9984 && opkg install ath10k-firmware-qca9984-ct

On both systems using the -ct firmware caused a crash of the router resulting in a reboot. Replacement of the ct with the standard firmware makes the routers stable again.

No crashlogs haven been found (no persistent logging).


05.02.20192101Base systemBug ReportVery LowHighWDS bridge and PPPoE MTU problemAllUnconfirmed Task Description

Device: Netgear R7800
This issue is not present with original Netgear firmware and is not present with LEDE 17 (older kernel).

Preface:
I have very strange issue with interfaces MTU and it looks to be introduced with newer kernel (4.14).

My network is attached as a png:
1. my ISP uses VDSL, i just have a PPPoE (MTU=1492) on the ethernet interface through the ISP modem
2. all other internal clients and routers interfaces have MTU=1500

Ping from R7800 to 1.1.1.1 with 2000 packet size and fragmentation allowed = success
Ping from ArcherC7v2 to R7800 with 2000 packet size and fragmentation allowed = success
Ping from PC1 to R7800 with 2000 packet size and fragmentation allowed = success
Ping from PC2 to R7800 with 2000 packet size and fragmentation allowed = success
Ping from PC1 to 1.1.1.1 with 2000 packet size and fragmentation allowed = failure
Ping from PC2 to 1.1.1.1 with 2000 packet size and fragmentation allowed = success

Now the fun part:
Ping from PC1 to 1.1.1.1 with 1473 packet size and fragmentation allowed = failure
Ping from PC1 to 1.1.1.1 with 1472 packet size (1492-20) and fragmentation allowed = success

It seems a WDS (4addr) problem combined with PPPoE being at MTU=1492 at this point, but:
Ping from ArcherC7v2 to 1.1.1.1 with 2000 packet size and fragmentation allowed = success

I’ve messed up with MTU on all the interfaces, the only thing that fix the issue is setting the br-lan interface of the R7800 to MTU=1491, as soon as the bridge has MTU>1491 the pings fail.

R7800 network config

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '1 2 3 4 6t'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '5 0t'

config interface 'lan'
        option type 'bridge'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option stp '1'
        option mtu '1500'
        option ifname 'eth1.1'

config interface 'TIM_FTTC'
        option proto 'pppoe'
        option ifname 'eth0.2'
        option username '***'
        option password '***'
        option ipv6 'auto'
        option metric '1'
        option peerdns '0'
        option keepalive '5 6'

R7800 wireless config

config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11a'
        option path 'soc/1b500000.pci/pci0000:00/0000:00:00.0/0000:01:00.0'
        option htmode 'VHT80'
        option channel '136'
        option txpower '23'
        option country 'US'
        option legacy_rates '0'
        option noscan '1'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option mode 'ap'
        option ssid '***'
        option encryption 'psk2+ccmp'
        option key '***'
        option wps_pushbutton '0'
        option network 'lan'
        option wds '1'

ArcherC7v2 network config

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '1 2 3 4 6t'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '5 0t'

config interface 'lan'
        option type 'bridge'
        option proto 'static'
        option ipaddr '192.168.1.2'
        option netmask '255.255.255.0'
        option stp '1'
        option mtu '1500'
        option ifname 'eth1.1'

ArcherC7v2 wireless 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'
        option txpower '23'
        option country 'US'
        option legacy_rates '0'
        option noscan '1'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option mode 'sta'
        option wds '1'
        option ssid '***'
        option encryption 'psk2+ccmp'
        option key '***'
        option wps_pushbutton '0'
        option network 'lan'

WAN zone on firewall on R7800 has

option mtu_fix '1'
03.02.20192099Base systemFeature RequestVery LowLowPlease add an option to disable USB 3.0TrunkUnconfirmed Task Description

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

As you already know that USB 3.0 causes interference with WiFi 2.4ghz band.
A solution for that issue is to force driver to use USB2.0 only as mentioned here https://forum.openwrt.org/t/xiaomi-wifi-router-3g-18-06-x-wifi-issues-2-4ghz-5ghz/20169/33

Could you guys add an option to be enabled by the user without any compilation? Is it possible?

Thanks
Sinan


02.02.20192097KernelBug ReportVery LowLowmt7621 nand mtd slave fail to read same page twiceTrunkUnconfirmed Task Description

For my setup, only ‘firmware’ partition is specified in .dts (no ‘kernel’ or ‘rootfs’) so that mtdsplit can do its job of finding the correct offset for ubi parition.

mtdsplit found the ubi slave partition but attaching the ubi failed so kernel panicked due to lack of a root fs.

I narrowed down the issue to data all zero read when doing ubi_auto_attach().

Observe in below added printk in nand_do_read_ops() that 0×580000 was read once at 2.028127s and again at 3.682984s but the data are different:

[    1.166183] 7 fixed-partitions partitions found on MTD device MT7621-NAND
[    1.172957] Creating 7 MTD partitions on "MT7621-NAND": ***
[    1.178513] 0x000000000000-0x000000080000 : "uboot"
[    1.207245] 0x000000080000-0x0000000c0000 : "uboot_env"
[    1.237246] 0x0000000c0000-0x000000100000 : "factory"
[    1.266565] 0x000000100000-0x000000140000 : "s_env"
[    1.295219] 0x000000140000-0x000000180000 : "devinfo"
[    1.324541] 0x000000180000-0x000002980000 : "firmware"
[    1.902188] nand: read 4bytes 34f983(3471747): @8fc35b60=0 (retlen=4)
[    1.909212] nand: read 4bytes 360000(3538944): @8fc35b60=0 (retlen=4)
[    1.916224] nand: read 4bytes 380000(3670016): @8fc35b60=0 (retlen=4)
[    1.923224] nand: read 4bytes 3a0000(3801088): @8fc35b60=0 (retlen=4)
[    1.930201] nand: read 4bytes 3c0000(3932160): @8fc35b60=0 (retlen=4)
[    1.937204] nand: read 4bytes 3e0000(4063232): @8fc35b60=0 (retlen=4)
[    1.944203] nand: read 4bytes 400000(4194304): @8fc35b60=0 (retlen=4)
[    1.951180] nand: read 4bytes 420000(4325376): @8fc35b60=0 (retlen=4)
[    1.958183] nand: read 4bytes 440000(4456448): @8fc35b60=0 (retlen=4)
[    1.965183] nand: read 4bytes 460000(4587520): @8fc35b60=0 (retlen=4)
[    1.972160] nand: read 4bytes 480000(4718592): @8fc35b60=0 (retlen=4)
[    1.979163] nand: read 4bytes 4a0000(4849664): @8fc35b60=0 (retlen=4)
[    1.986162] nand: read 4bytes 4c0000(4980736): @8fc35b60=0 (retlen=4)
[    1.993172] nand: read 4bytes 4e0000(5111808): @8fc35b60=0 (retlen=4)
[    2.000150] nand: read 4bytes 500000(5242880): @8fc35b60=0 (retlen=4)
[    2.007147] nand: read 4bytes 520000(5373952): @8fc35b60=0 (retlen=4)
[    2.014152] nand: read 4bytes 540000(5505024): @8fc35b60=0 (retlen=4)
[    2.021130] nand: read 4bytes 560000(5636096): @8fc35b60=0 (retlen=4)
[    2.028127] nand: read 4bytes 580000(5767168): @8fc35b60=23494255 (retlen=4)
[    2.035166] mtdsplit: mtd_check_rootfs_magic(firmware, offset=4194304) got UBI_EC_MAGIC (magic=23494255)
[    2.044625] 2 uimage-fw partitions found on MTD device firmware
[    2.050514] run_parsers_by_type(firmware, MTD_PARSER_TYPE_FIRMWARE) found 2 parts
[    2.057997] 0x000000180000-0x000000580000 : "kernel"
[    2.087096] 0x000000580000-0x000002980000 : "ubi"
[    2.115345] 0x000002980000-0x000005180000 : "alt_firmware"
[    2.146730] [mtk_nand] probe successfully!
[    2.151499] Signature matched and data read!
[    2.155764] load_fact_bbt success 1023
[    2.160202] libphy: Fixed MDIO Bus: probed
[    2.234009] mtk_soc_eth 1e100000.ethernet: generated random MAC address 3e:90:49:dc:0e:f4
[    2.242383] libphy: mdio: probed
[    3.645190] mtk_soc_eth 1e100000.ethernet: loaded mt7530 driver
[    3.651851] mtk_soc_eth 1e100000.ethernet eth0: mediatek frame engine at 0xbe100000, irq 20
[    3.662579] NET: Registered protocol family 10
[    3.668281] Segment Routing with IPv6
[    3.672014] NET: Registered protocol family 17
[    3.676546] 8021q: 802.1Q VLAN Support v1.8
[    3.682984] nand: read 4bytes 580000(5767168): @8fc35e1c=0 (retlen=4)
[    3.689426] UBI mtd_read(ubi, offset=0, 4 bytes) got magic@8fc35e1c bytes: 0
[    3.696477] UBI error: no valid UBI magic found inside mtd7
[    3.702054] hctosys: unable to open rtc device (rtc0)
[    3.707847] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6

I added ops.oobbuf = 1 in nand_read() and the issue went away seemingly due to disabling of read from chip buffer (near line 1903 in nand_base.c). Observe below printk indicates now reading same address returns same data both times (3.188661s and 4.854364s):

[    3.153685] nand: read 4bytes 4e0000(5111808): @8fc35b60=0 (retlen=4)
[    3.160662] nand: read 4bytes 500000(5242880): @8fc35b60=0 (retlen=4)
[    3.167676] nand: read 4bytes 520000(5373952): @8fc35b60=0 (retlen=4)
[    3.174678] nand: read 4bytes 540000(5505024): @8fc35b60=0 (retlen=4)
[    3.181655] nand: read 4bytes 560000(5636096): @8fc35b60=0 (retlen=4)
[    3.188661] nand: read 4bytes 580000(5767168): @8fc35b60=23494255 (retlen=4)
[    3.195698] mtdsplit: mtd_check_rootfs_magic(firmware, offset=4194304) got UBI_EC_MAGIC (magic=23494255)
[    3.205161] 2 uimage-fw partitions found on MTD device firmware
[    3.211051] run_parsers_by_type(firmware, MTD_PARSER_TYPE_FIRMWARE) found 2 parts
[    3.218530] 0x000000180000-0x000000580000 : "kernel"
[    3.247625] 0x000000580000-0x000002980000 : "ubi"
[    3.275885] 0x000002980000-0x000005180000 : "alt_firmware"
[    3.307291] [mtk_nand] probe successfully!
[    3.312061] Signature matched and data read!
[    3.316326] load_fact_bbt success 1023
[    3.320776] libphy: Fixed MDIO Bus: probed
[    3.393926] mtk_soc_eth 1e100000.ethernet: generated random MAC address d6:1b:2e:2e:17:74
[    3.402252] libphy: mdio: probed
[    4.815958] mtk_soc_eth 1e100000.ethernet: loaded mt7530 driver
[    4.822595] mtk_soc_eth 1e100000.ethernet eth0: mediatek frame engine at 0xbe100000, irq 20
[    4.833311] NET: Registered protocol family 10
[    4.839073] Segment Routing with IPv6
[    4.842892] NET: Registered protocol family 17
[    4.847360] 8021q: 802.1Q VLAN Support v1.8
[    4.854364] nand: read 4bytes 580000(5767168): @8fc35e1c=23494255 (retlen=4)
[    4.861399] UBI mtd_read(ubi, offset=0, 4 bytes) got magic@8fc35e1c bytes: 23494255
[    4.869062] UBI: auto-attach mtd7
[    4.872414] ubi0: attaching mtd7
[    4.892381] UBI: EOF marker found, PEBs from 14 will be erased
[    4.898547] ubi0: scanning is finished
[    4.940681] ubi0: volume 1 ("rootfs_data") re-sized from 9 to 252 LEBs
[    4.948006] ubi0: attached mtd7 (name "ubi", size 36 MiB)
[    4.953428] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    4.960270] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    4.967044] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[    4.973995] ubi0: good PEBs: 287, bad PEBs: 1, corrupted PEBs: 0
[    4.979971] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[    4.987175] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1003525433
[    4.996288] ubi0: available PEBs: 0, total reserved PEBs: 287, PEBs reserved for bad PEB handling: 19
[    5.005507] ubi0: background thread "ubi_bgt0d" started, PID 354
[    5.006121] nand: read 4bytes 5c1000(6033408): @8fc35d8c=73717368 (retlen=4)
[    5.019595] block ubiblock0_0: created from ubi0:0(rootfs)
[    5.025122] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem
[    5.032069] hctosys: unable to open rtc device (rtc0)

I don’t know what oobbuf does and what’s the wider impact so what is the real problem and fix?

Thanks.

Let met know what other information is needed.

02.02.20192096Base systemBug ReportVery LowLowA second 'make' always rebuilds somethingTrunkUnconfirmed Task Description

After a full OpenWrt Git HEAD build finishes, running “make” repeatedly again always rebuilds something. Another user is reporting that a subsequent build takes 5 minutes on his Fedora 27 desktop, which I am also seeing on my oldish Ubuntu 16.04.5 laptop.

Some more information is in the original mailing list discussion. This is the first message in the relevant thread:

http://lists.infradead.org/pipermail/openwrt-devel/2019-January/015648.html

Please find attached a build script to reproduce this problem, and a full build log file from my laptop.

Look for “Running the second make...” in the log file. Afterwards, things like these are being rebuilt, which probably should not:

make[6]: Entering directory ‘/home/rdiez/rdiez/freifunk/openwrt/git-repo/build_dir/target-x86_64_musl/uci-2018-08-11-4c8b4d6e’ [ 5%] Building C object CMakeFiles/uci.dir/libuci.c.o
[ 10%] Building C object CMakeFiles/uci.dir/file.c.o

31.01.20192094ToolchainBug ReportVery LowMediumimage builder has incorrect board name for wr842n-v1 ca...AllUnconfirmed Task Description

Boardname mismatch in imagebuilder (and suspected release builds) for tplink wr842n-v1
Doesn't appear to be an issue if upgrading to another ar71xxx image but sysupgrade fails when upgrading to ath79 image for wr842n-v1 due to board mismatch.

from existing ar71xxx wr842n-v1 system

head -n5 /etc/board.json
{
"model": {
"id": "tl-mr3420",
"name": "TP-Link TL-WR842N/ND v1"
},

in file openwrt-imagebuilder-18.06.1-ar71xx-generic.Linux-x86_64/target/linux/ar71xx/image/generic-tp-link.mk

define Device/tl-wr842n-v1
$(Device/tplink-8m)
DEVICE_TITLE := TP-LINK TL-WR842N/ND v1
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
BOARDNAME := TL-MR3420 DEVICE_PROFILE := TLWR842
TPLINK_HWID := 0x08420001
endef
TARGET_DEVICES += tl-wr842n-v1
Supply the following if possible:
- Device problem occurs on
- Software versions of OpenWrt/LEDE release, packages, etc.
- Steps to reproduce

 

Discussed in form thread


30.01.20192093PackagesFeature RequestVery LowMediumThere is 'dslite' but not 'ipip6'?AllUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on
This is a suggestion and is not a model-specific bug report.

- Software versions of OpenWrt/LEDE release, packages, etc.
OpenWrt 18.06.1, r7258-5eb055306f

- Steps to reproduce
Description below:

I don't understand why people have not come across this, but I honestly think there should be a package providing users with a generic implementation of IPv4-over-IPv6 tunnel. There is 'dslite' which contains 'dslite.sh' but is too specifically optimized for DS-Lite since it has IPv4 addresses of hard-coded. Sure, I could alter these values locally for personal use, but that just doesn't feel right...I find it rather inflexible. I'm not saying 'dslite' should be renamed to 'ipip6' but I do think folks will be happier if there were a separate package named like 'ipip6' implemented with more flexibility. Or am

29.01.20192092Base systemBuild FailureVery LowLowCan't build current releaseopenwrt-18.06Unconfirmed Task Description

I can’t build stable release from sources

- Software versions of OpenWrt/LEDE release, packages, etc.
18.06.1
- Steps to reproduce
do everything like at wiki, but 18.06.1 failed to build, but 18.06 fresh sources snapshot building successfully.

error:
...
mv -f $depbase.Tpo $depbase.Po
lib/fseterr.c: In function ‘fseterr’:
lib/fseterr.c:77:3: error: #error “Please port gnulib fseterr.c to your platform! Look at the definitions of ferror and clearerr on your system, then report this to bug-gnulib.”

#error "Please port gnulib fseterr.c to your platform! Look at the definitions of ferror and clearerr on your system, then report this to bug-gnulib."
 ^~~~~

make[6]: * [Makefile:3461: lib/fseterr.o] Error 1
make[6]:
* Waiting for unfinished jobs....
....

aging_dir/toolchain-mipsel_24kc_gcc-7.3.0_musl/bin:/run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/staging_dir/host/bin:/run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/staging_dir/host/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/android-sdk/platform-tools:/opt/android-sdk/tools:/opt/android-sdk/tools/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/v/go/bin:~/.npm-global/bin:/sbin” ldconfig -n /run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/staging_dir/host/lib


Libraries have been installed in:

 /run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/staging_dir/host/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the ‘-LLIBDIR’ flag during linking and do at least one of the following:

  1. add LIBDIR to the ‘LD_LIBRARY_PATH’ environment variable

during execution

  1. add LIBDIR to the ‘LD_RUN_PATH’ environment variable

during linking

  1. use the ‘-Wl,-rpath -Wl,LIBDIR’ linker flag
  2. have your system administrator add LIBDIR to ‘/etc/ld.so.conf’

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.


.....

ake[6]: Entering directory ‘/run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/build_dir/host/mpc-1.1.0’ make[6]: Nothing to be done for ‘install-exec-am’.
/usr/bin/mkdir -p ‘/run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/staging_dir/host/include’ /usr/bin/install -c -m 644 src/mpc.h ‘/run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/staging_dir/host/include’ make[6]: Leaving directory ‘/run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/build_dir/host/mpc-1.1.0’ make[5]: Leaving directory ‘/run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/build_dir/host/mpc-1.1.0’ make[4]: Leaving directory ‘/run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/build_dir/host/mpc-1.1.0’ mkdir -p /run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/staging_dir/host/stamp
touch /run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/build_dir/host/mpc-1.1.0/.built
touch /run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/staging_dir/host/stamp/.mpc_installed
make[3]: Leaving directory ‘/run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/tools/mpc’ time: tools/mpc/compile#18.28#3.65#16.10
make[2]: Leaving directory ‘/run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt’ make[1]: * [tools/Makefile:150: /run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/staging_dir/target-mipsel_24kc_musl/stamp/.tools_compile_yynyyyyynyyyyynyynyyyyynyyyyyyyyyyyyyyynyynynnyyynnyy] Error 2
make[1]: Leaving directory ‘/run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt’ make:
* [/run/media/v/1390ab77-3888-441a-ac20-cb46d9511e27/openwrt/openwrt-stable/openwrt/include/toplevel.mk:218: world] Error 2

 


29.01.20192091Base systemBug ReportVery LowLowwrt1900 (v1 mamba) USB 3 port brokenTrunkUnconfirmed Task Description

Appears to be a regression on master with no power to USB 3 port on wrt1900, still works on 18.x
forum thread

29.01.20192090KernelBug ReportVery LowCritical[mt76] MCU message 31 timeout, clients losing connectio...openwrt-18.06Unconfirmed Task Description

This issue is occurring both with commit f34ad1a8f0d1ee4a3e4b966d58c8f3b8a523a417 and commit 6e16dd1234ea4814af2b46a22b4aea111baef3ab on a D-Link DIR-860L rev. B1 (mt7621 SoC) running 18.06 HEAD.

It also looks similar to issue 142 on the mt76 Github.

Scenario:
- Connect the client to the AP. Clients in use are an Intel 8260AC card and an Xperia XZ1 Compact (Qualcomm SoC so probably QCA wireless?).
- Connection is choppy. Pings will take multiple seconds (not milliseconds) sometimes, web pages won’t load at one point and then will, very unpredictable.
- Client loses connection to AP within minutes and is unable to reconnect; ‘wifi status’ on the device shows the AP is still up however.
- Behaviour was really bad with the 2019-01-10 and seemed to have improved with 2019-01-25, but I gave 2019-01-25 just one shot before rolling back to 2018-11-09.
- logread shows deauthentication and MCU message 31 timeout filling the logs:

Sun Jan 27 21:14:57 2019 daemon.notice hostapd: wlan0: AP-STA-POLL-OK a4:34:xx:xx:6e:0f
Sun Jan 27 21:15:05 2019 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 38:78:xx:xx:04:d3
Sun Jan 27 21:15:05 2019 daemon.info hostapd: wlan0: STA 38:78:xx:xx:04:d3 IEEE 802.11: disassociated due to inactivity
Sun Jan 27 21:15:06 2019 daemon.info hostapd: wlan0: STA 38:78:xx:xx:04:d3 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Jan 27 21:15:19 2019 kern.err kernel: [ 2675.025292] mt76x2e 0000:01:00.0: MCU message 31 (seq 8) timed out
Sun Jan 27 21:15:21 2019 kern.err kernel: [ 2677.105305] mt76x2e 0000:01:00.0: MCU message 31 (seq 9) timed out
Sun Jan 27 21:15:23 2019 kern.err kernel: [ 2679.185298] mt76x2e 0000:01:00.0: MCU message 31 (seq 10) timed out
Sun Jan 27 21:15:25 2019 kern.err kernel: [ 2681.265299] mt76x2e 0000:01:00.0: MCU message 31 (seq 11) timed out
Sun Jan 27 21:15:27 2019 kern.err kernel: [ 2683.345294] mt76x2e 0000:01:00.0: MCU message 31 (seq 12) timed out
Sun Jan 27 21:15:29 2019 kern.err kernel: [ 2685.425291] mt76x2e 0000:01:00.0: MCU message 31 (seq 13) timed out
Sun Jan 27 21:15:31 2019 kern.err kernel: [ 2687.505287] mt76x2e 0000:01:00.0: MCU message 31 (seq 14) timed out
Sun Jan 27 21:15:33 2019 kern.err kernel: [ 2689.585284] mt76x2e 0000:01:00.0: MCU message 31 (seq 15) timed out
Sun Jan 27 21:15:35 2019 kern.err kernel: [ 2691.665279] mt76x2e 0000:01:00.0: MCU message 31 (seq 1) timed out
Sun Jan 27 21:15:38 2019 kern.err kernel: [ 2693.745276] mt76x2e 0000:01:00.0: MCU message 31 (seq 2) timed out
Sun Jan 27 21:15:40 2019 kern.err kernel: [ 2695.825270] mt76x2e 0000:01:00.0: MCU message 31 (seq 3) timed out
Sun Jan 27 21:15:42 2019 kern.err kernel: [ 2697.905268] mt76x2e 0000:01:00.0: MCU message 31 (seq 4) timed out
Sun Jan 27 21:15:44 2019 kern.err kernel: [ 2699.985259] mt76x2e 0000:01:00.0: MCU message 31 (seq 5) timed out
Sun Jan 27 21:15:46 2019 kern.err kernel: [ 2702.065274] mt76x2e 0000:01:00.0: MCU message 31 (seq 6) timed out
Sun Jan 27 21:15:48 2019 kern.err kernel: [ 2704.145282] mt76x2e 0000:01:00.0: MCU message 31 (seq 7) timed out
Sun Jan 27 21:15:50 2019 kern.err kernel: [ 2706.225272] mt76x2e 0000:01:00.0: MCU message 31 (seq 8) timed out
Sun Jan 27 21:15:52 2019 kern.err kernel: [ 2708.305263] mt76x2e 0000:01:00.0: MCU message 31 (seq 9) timed out
Sun Jan 27 21:15:54 2019 kern.err kernel: [ 2710.385268] mt76x2e 0000:01:00.0: MCU message 31 (seq 10) timed out
Sun Jan 27 21:15:56 2019 kern.err kernel: [ 2712.465253] mt76x2e 0000:01:00.0: MCU message 31 (seq 11) timed out
Sun Jan 27 21:15:58 2019 kern.err kernel: [ 2714.545266] mt76x2e 0000:01:00.0: MCU message 31 (seq 12) timed out
Sun Jan 27 21:16:00 2019 kern.err kernel: [ 2716.625232] mt76x2e 0000:01:00.0: MCU message 31 (seq 13) timed out
Sun Jan 27 21:16:02 2019 kern.err kernel: [ 2718.705225] mt76x2e 0000:01:00.0: MCU message 31 (seq 14) timed out
Sun Jan 27 21:16:05 2019 kern.err kernel: [ 2720.785213] mt76x2e 0000:01:00.0: MCU message 31 (seq 15) timed out
Sun Jan 27 21:16:07 2019 kern.err kernel: [ 2722.865219] mt76x2e 0000:01:00.0: MCU message 31 (seq 1) timed out
Sun Jan 27 21:16:09 2019 kern.err kernel: [ 2724.945202] mt76x2e 0000:01:00.0: MCU message 31 (seq 2) timed out
Sun Jan 27 21:16:11 2019 kern.err kernel: [ 2727.025200] mt76x2e 0000:01:00.0: MCU message 31 (seq 3) timed out
Sun Jan 27 21:16:13 2019 kern.err kernel: [ 2729.105189] mt76x2e 0000:01:00.0: MCU message 31 (seq 4) timed out
Sun Jan 27 21:16:15 2019 kern.err kernel: [ 2731.185194] mt76x2e 0000:01:00.0: MCU message 31 (seq 5) timed out
Sun Jan 27 21:16:17 2019 kern.err kernel: [ 2733.265189] mt76x2e 0000:01:00.0: MCU message 31 (seq 6) timed out
Sun Jan 27 21:16:19 2019 kern.err kernel: [ 2735.345176] mt76x2e 0000:01:00.0: MCU message 31 (seq 7) timed out
Sun Jan 27 21:16:21 2019 kern.err kernel: [ 2737.425183] mt76x2e 0000:01:00.0: MCU message 31 (seq 8) timed out
Sun Jan 27 21:16:23 2019 kern.err kernel: [ 2739.505191] mt76x2e 0000:01:00.0: MCU message 31 (seq 9) timed out
Sun Jan 27 21:16:25 2019 kern.err kernel: [ 2741.585169] mt76x2e 0000:01:00.0: MCU message 31 (seq 10) timed out
Sun Jan 27 21:16:27 2019 kern.err kernel: [ 2743.665183] mt76x2e 0000:01:00.0: MCU message 31 (seq 11) timed out
Sun Jan 27 21:16:30 2019 kern.err kernel: [ 2745.745171] mt76x2e 0000:01:00.0: MCU message 31 (seq 12) timed out
Sun Jan 27 21:16:32 2019 kern.err kernel: [ 2747.825150] mt76x2e 0000:01:00.0: MCU message 31 (seq 13) timed out
Sun Jan 27 21:16:34 2019 kern.err kernel: [ 2749.905148] mt76x2e 0000:01:00.0: MCU message 31 (seq 14) timed out
Sun Jan 27 21:16:36 2019 kern.err kernel: [ 2751.985146] mt76x2e 0000:01:00.0: MCU message 31 (seq 15) timed out
Sun Jan 27 21:16:38 2019 kern.err kernel: [ 2754.065143] mt76x2e 0000:01:00.0: MCU message 31 (seq 1) timed out
Sun Jan 27 21:16:40 2019 kern.err kernel: [ 2756.145130] mt76x2e 0000:01:00.0: MCU message 31 (seq 2) timed out
Sun Jan 27 21:16:42 2019 kern.err kernel: [ 2758.225141] mt76x2e 0000:01:00.0: MCU message 31 (seq 3) timed out
Sun Jan 27 21:16:44 2019 kern.err kernel: [ 2760.305124] mt76x2e 0000:01:00.0: MCU message 31 (seq 4) timed out
Sun Jan 27 21:16:46 2019 kern.err kernel: [ 2762.385151] mt76x2e 0000:01:00.0: MCU message 31 (seq 5) timed out
Sun Jan 27 21:16:48 2019 kern.err kernel: [ 2764.465119] mt76x2e 0000:01:00.0: MCU message 31 (seq 6) timed out
Sun Jan 27 21:16:50 2019 kern.err kernel: [ 2766.545112] mt76x2e 0000:01:00.0: MCU message 31 (seq 7) timed out
Sun Jan 27 21:16:52 2019 kern.err kernel: [ 2768.625111] mt76x2e 0000:01:00.0: MCU message 31 (seq 8) timed out
Sun Jan 27 21:16:54 2019 kern.err kernel: [ 2770.705101] mt76x2e 0000:01:00.0: MCU message 31 (seq 9) timed out
Sun Jan 27 21:16:57 2019 kern.err kernel: [ 2772.785097] mt76x2e 0000:01:00.0: MCU message 31 (seq 10) timed out
Sun Jan 27 21:16:59 2019 kern.err kernel: [ 2774.865089] mt76x2e 0000:01:00.0: MCU message 31 (seq 11) timed out
Sun Jan 27 21:17:01 2019 kern.err kernel: [ 2776.945093] mt76x2e 0000:01:00.0: MCU message 31 (seq 12) timed out
Sun Jan 27 21:17:03 2019 kern.err kernel: [ 2779.025083] mt76x2e 0000:01:00.0: MCU message 31 (seq 13) timed out
Sun Jan 27 21:17:05 2019 kern.err kernel: [ 2781.105078] mt76x2e 0000:01:00.0: MCU message 31 (seq 14) timed out
Sun Jan 27 21:17:07 2019 kern.err kernel: [ 2783.185079] mt76x2e 0000:01:00.0: MCU message 31 (seq 15) timed out
Sun Jan 27 21:17:09 2019 kern.err kernel: [ 2785.265074] mt76x2e 0000:01:00.0: MCU message 31 (seq 1) timed out
Sun Jan 27 21:17:11 2019 kern.err kernel: [ 2787.345067] mt76x2e 0000:01:00.0: MCU message 31 (seq 2) timed out
Sun Jan 27 21:17:13 2019 kern.err kernel: [ 2789.425059] mt76x2e 0000:01:00.0: MCU message 31 (seq 3) timed out
Sun Jan 27 21:17:15 2019 kern.err kernel: [ 2791.505056] mt76x2e 0000:01:00.0: MCU message 31 (seq 4) timed out
Sun Jan 27 21:17:17 2019 kern.err kernel: [ 2793.585050] mt76x2e 0000:01:00.0: MCU message 31 (seq 5) timed out
Sun Jan 27 21:17:19 2019 kern.err kernel: [ 2795.665044] mt76x2e 0000:01:00.0: MCU message 31 (seq 6) timed out
Sun Jan 27 21:17:22 2019 kern.err kernel: [ 2797.745051] mt76x2e 0000:01:00.0: MCU message 31 (seq 7) timed out
Sun Jan 27 21:17:24 2019 kern.err kernel: [ 2799.825041] mt76x2e 0000:01:00.0: MCU message 31 (seq 8) timed out
Sun Jan 27 21:17:26 2019 kern.err kernel: [ 2801.905033] mt76x2e 0000:01:00.0: MCU message 31 (seq 9) timed out
Sun Jan 27 21:17:28 2019 kern.err kernel: [ 2803.985028] mt76x2e 0000:01:00.0: MCU message 31 (seq 10) timed out
Sun Jan 27 21:17:30 2019 kern.err kernel: [ 2806.065023] mt76x2e 0000:01:00.0: MCU message 31 (seq 11) timed out
Sun Jan 27 21:17:32 2019 kern.err kernel: [ 2808.145015] mt76x2e 0000:01:00.0: MCU message 31 (seq 12) timed out
Sun Jan 27 21:17:34 2019 kern.err kernel: [ 2810.225013] mt76x2e 0000:01:00.0: MCU message 31 (seq 13) timed out
Sun Jan 27 21:17:36 2019 kern.err kernel: [ 2812.305018] mt76x2e 0000:01:00.0: MCU message 31 (seq 14) timed out
Sun Jan 27 21:17:38 2019 kern.err kernel: [ 2814.385016] mt76x2e 0000:01:00.0: MCU message 31 (seq 15) timed out
 


29.01.20192089Base systemBug ReportVery LowLowsocksify: always fails, Failed to find "bindresvport"TrunkUnconfirmed Task Description
Device problem occurs on: TP-Link Archer C7 v2
Software versions of OpenWrt/LEDE release, packages, etc.: ar71xx, yesterday’s snapshot, socksify_1.4.1-3_mips_24kc.ipk

To reproduce, just run any network program under socksify, it always fails with an error message about “bindresvport”, i.e. the package is 100% useless as it is.

# SOCKS_SERVER=127.0.0.1:9999 socksify wget -qO- http://ipecho.net/plain
Jan 29 04:52:00 (1548737520.054513) wget[12531]: error: symbolfunction(): compile time configuration error?  Failed to find "bindresvport" using RTLD_NEXT: Symbol not found: bindresvport
28.01.20192088Base systemBug ReportVery LowLowBuild renice busybox appletTrunkUnconfirmed Task Description

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

It would be nice (NPI) if the busybox “renice” applet were built.


27.01.20192086Base systemBug ReportVery LowLowIS_TTY in the makefile is brokenTrunkUnconfirmed Task Description

File include/toplevel.mk tries to find out whether the build is running in an interactive console like this:

export IS_TTY=$(shell tty -s && echo 1 || echo 0)

That is the wrong way to do it. The code above is testing stdin, and not stdout. As a result, piping to a log file with a tool like ‘tee’ yields a log file that still contains the same \r codes etc. as when running on an interactive console.

Other tools like systemd’s systemctl do it right by checking stdout. On an interactive console, run these 2 commands to see the difference:

systemctl –help
systemctl –help | tee test.txt

It turns out that checking stdout is not so easy to do inside a makefile. In the shell, you would normally check with “-t 1”, but a $(shell ...) construct inside a makefile won’t work, because $(shell) always redirects stdout in order to capture the command’s output.

See here for the gory details:

https://stackoverflow.com/questions/44097324/timing-of-makefile-include-statements-for-auto-generated-files/44133082

While there are workarounds for makefiles, I wouldn’t go that far. I would just stop trying. and let the user decide with some variable. Maybe some day there will be a wrapper shell script, instead of using the makefile directly. In such a wrapper script it would be trivial to check for things like interactive terminal and/or terminal color support.

26.01.20192084PackagesBug ReportVery LowMediumltq-vdsl-vr9-vectoring-fw-installer: New version of fir...openwrt-18.06Unconfirmed Task Description

When running vdsl_fw_install.sh from the ltq-vdsl-vr9-vectoring-fw-installer package, it tries to download https://www.telekom.de/hilfe/downloads/firmware-speedport-w921v-1.44.000.bin which does not exist anymore on the server.

There is a new version (1.45) out though.

Also, I had to install this package (ltq-vdsl-vr9-vectoring-fw-installer) manually, as it is not available in the repos of 18.06.

Warm regards and thanks for the good work!

Tom

25.01.20192083Base systemBug ReportVery LowVery LowRemove last references to the lede-project.org URLTrunkUnconfirmed Task Description

git grep -i “lede-project\.org” | grep -vi Copyright
There are still some references to the old project.

Thanks.

23.01.20192081Base systemBug ReportVery LowHighSnapShot Install for TP-Link Archer C20 AC750 Hardly Wo...openwrt-18.06Unconfirmed Task Description

Dear Colleagues:

1) I have been testing basic networking functions of OpenWrt 18.06.1 “full Install” version on the above captioned device since 2018-10-16. This was done through BIN file download and install process. The operations tested appeared to be fine.

2) I was instructed to try a “snapshot Install” version to see if a recent Kernel update (2018-12-14, see link below.) is performing as intended. Upon powering on this version in the existing test-bed, however, the DHCP client PCs (with Xubuntu OS) appeared to see the LAN service by having their addresses assigned and were able to get response from the gateway when PINGing it with 192.168.1.1. However, attempting to use a web browser to access the router homepage at 192.168.1.1 failed. Also, the PCs could not get PINGing response from one another. Perhaps the earliest tell-tail sign is that as soon as the router is powered on with the “snapshot version”, the 2.4G WiFi status indicator LED is turned on, while the “full Install” version does not.

3) To verify, I downloaded and installed both full and snapshot versions of current BIN files from the OpenWrt website today and verified their integrity by checking the check-sums first. The above symptoms appeared to be repeatable after going through the processes a couple cycles alternating between the two versions.

Thanks for your attention,

Abe (2019-01-23 15:58)


23.01.20192080PackagesBug ReportVery LowCriticalWan IPV6 interface with 6rd protocol reports bad mac ad...openwrt-18.06Unconfirmed Task Description

Device used is BT Home Hub 5 v1.2.
Openwrt release is 18.06.1,
6rd package version is 9-4
ISP is Free (France)

“Wan” interface, IPV4, with Dchp client protocol is up and works fine on physical interface dsl0.836.
Mac address has to be overriden because ISP uses a fixed mac address, different for each Freebox, it’s own dsl modem/box.

“Wan6”, IPV6, interface with 6rd protocol is up but the mac reported in the not the same as those reported in “Wan” interface.

As you could see on the attached capture of the “Interfaces overview”, the mac address reported is the “Wan” IpV4 address !!!

Wan6 interface is up but frames are rejected by ISP because the mac address is not those one expected as for “Wan” interface. Mac address can’t be overriden on these interface.

network config is attached.



Cromagnon31

23.01.20192079Base systemBug ReportVery LowCriticalMT7621 - lost RX streamAllUnconfirmed Task Description

Device: TP-LINK RE350 v1
OpenWRT: 18.06-SNAPSHOOT 22.01.2019
Wireless setup:

  config wifi-device 'radio0'
      option type 'mac80211'
      option channel '1'
      option hwmode '11g'
      option path 'pci0000:00/0000:00:00.0/0000:01:00.0'
      option ldpc '1'
      option greenfield '0'
      option diversity '1'
      option htmode 'HT40'
      option country 'PL'
      option log_level '8'
      option disabled '0'
      option legacy_rates '0'
      option noscan '1'
  config wifi-iface
      option device 'radio0'
      option mode 'sta'
      option ssid 'XXX'
      option bssid 'xxx'
      option encryption 'psk2'
      option key 'xxx'
      option disassoc_low_ack '0'
      option network 'wan'
      option disabled '0'
      option wmm '1'
  config wifi-iface
      option device 'radio0'
      option mode 'ap'
      option ssid 'XXX'
      option encryption 'psk2'
      option key 'xxx'
      option disassoc_low_ack '0'
      option network 'lan'
      option disabled '0'
      option wds '1'
      option wmm '1'

Problem and solution:
AP and STA works on Channel 1. STA few seconds after connection to upstream AP losts RX stream.

  Station xx:xx:xx:xx:xx:xx (on wlan0)
      inactive time:  20570 ms
      rx bytes:       222792
      rx packets:     1657
      tx bytes:       1482
      tx packets:     20
      tx retries:     133
      tx failed:      12
      beacon loss:    10
      beacon rx:      756
      rx drop misc:   2
      signal:         -68 [-68, -69] dBm
      signal avg:     -68 [-68, -68] dBm
      beacon signal avg:      188 dBm
      tx bitrate:     43.3 MBit/s MCS 10 short GI
      **rx bitrate:     1.0 MBit/s**
      authorized:     yes
      authenticated:  yes
      associated:     yes
      preamble:       long
      WMM/WME:        yes
      MFP:            no
      TDLS peer:      no
      DTIM period:    2
      beacon interval:100
      short slot time:yes
      connected time: 83 seconds
 


23.01.20192078KernelBug ReportVery LowLowtty noisy from /etc/hotplug.d/net/10-ar922x-led-fix TrunkUnconfirmed Task Description

Hi,

I think it is just a coding style issue,
but makes tty output noisy when procd debug level selected (3 or 4 for me).

noise examples:


cat: can't open '/sys/devices/virtual/ieee80211/phy*/name': No such file or directory
sh: add: unknown operand

# or

cat: can't open '/sys/devices/virtual/ieee80211/phy*/name': No such file or directory
sh: remove: unknown operand

# times depends on how many hotplug event happened

demo patch below



https://github.com/openwrt/openwrt/blob/master/target/linux/ar71xx/base-files/etc/hotplug.d/net/10-ar922x-led-fix

- phyname=$(cat $phydir/phy*/name)
+ phyname=$(cat $phydir/phy*/name 2>/dev/null)

- [ -z $phyname -o $ACTION != "add" ] && exit 0
+ [ 0 != $? -o -z "$phyname" -o "$ACTION" != "add" ] && exit 0

- [ $phyname -a $ACTION = "add" ] && {
+ [ ! -z "$phyname" -a "$ACTION" == "add" ] && {


22.01.20192076KernelBug ReportVery LowHighath9k lots of RXORN interruptslede-17.01Unconfirmed Task Description

i.
I am using the the lastest compat-wireless driver in trunk on a ar9300 device as an ap.
Now there is a problem:
when a ap run a few days latter I noticed there is thousands of RXORN interrupts per seconds on the ap side, and no RXLP interrupts when all stations can ‘t connect
someone can give advice?

21.01.20192075KernelBug ReportVery LowMediumath10k_pci -- SWBA overrun on vdev 0, skipped old beac...TrunkUnconfirmed Task Description

Periodically (every 4-12 hours) the AP (Ubiquiti UniFi-AC-LITE) apparently resets it firmware and drops all clients. After recovery all clients migrate back to the failed AP. I receive the following in the system log:

Sun Jan 20 01:19:15 2019 kern.warn kernel: [626814.624640] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:15 2019 kern.warn kernel: [626814.727032] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:15 2019 kern.warn kernel: [626814.829453] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:15 2019 kern.warn kernel: [626814.931841] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:15 2019 kern.warn kernel: [626815.034240] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:15 2019 kern.warn kernel: [626815.136629] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:15 2019 kern.warn kernel: [626815.239040] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:15 2019 kern.warn kernel: [626815.341440] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:15 2019 kern.warn kernel: [626815.443835] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:16 2019 kern.warn kernel: [626815.546251] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:16 2019 kern.warn kernel: [626815.648637] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:16 2019 kern.warn kernel: [626815.751043] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:16 2019 kern.warn kernel: [626815.853446] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:16 2019 kern.warn kernel: [626815.955854] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:16 2019 kern.warn kernel: [626816.058259] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:16 2019 kern.warn kernel: [626816.160653] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:16 2019 kern.warn kernel: [626816.263056] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:16 2019 kern.warn kernel: [626816.365458] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:16 2019 kern.warn kernel: [626816.467864] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:17 2019 kern.warn kernel: [626816.570265] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:17 2019 kern.warn kernel: [626816.672667] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:17 2019 kern.warn kernel: [626816.775083] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:17 2019 kern.warn kernel: [626816.877475] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:17 2019 kern.warn kernel: [626816.979877] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:17 2019 kern.warn kernel: [626817.082279] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:17 2019 kern.warn kernel: [626817.184686] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:17 2019 kern.warn kernel: [626817.287098] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:17 2019 kern.warn kernel: [626817.389482] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:17 2019 kern.warn kernel: [626817.491885] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.543991] ath10k_pci 0000:00:00.0: wmi command 36893 timeout, restarting hardware
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.552229] ath10k_pci 0000:00:00.0: failed to delete peer 40:4e:36:7f:72:59 for vdev 0: -11
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.561304] ath10k_pci 0000:00:00.0: found sta peer 40:4e:36:7f:72:59 (ptr 85cf0200 id 86) entry on vdev 0 after it was supposedly removed
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.574561] ————[ cut here ]———— Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.579573] WARNING: CPU: 0 PID: 14402 at backports-4.19.7-1/net/mac80211/sta_info.c:1004 sta_set_sinfo+0xaec/0xb98 [mac80211]
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.591588] Modules linked in: ath9k ath9k_common pppoe ppp_async 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 iptable_mangle iptable_filter ip_tables crc_ccitt compat ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables gpio_button_hotplug
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.657187] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.665363] CPU: 0 PID: 14402 Comm: hostapd Not tainted 4.14.91 #0
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.671831] Stack : 80540000 804f1a8c 00000000 00000000 804cb014 865d3b04 87d0c85c 8051b9c7
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.680702] 804c73b8 00003842 80593800 000003ec 865d3cb4 00000001 865d3ab8 6a0710c0
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.689575] 00000000 00000000 80590000 000083f0 00000000 00000000 00000008 00000000
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.698350] 00000188 f8b6dd8c 00000187 6d6d3a20 80000000 00000000 87663a04 876079d4
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.707137] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.715075] 00000009 000003ec 865d3cb4 87c92000 00000010 80263864 00000000 80590000
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.723805] ...
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.726511] Call Trace:
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.729234] [<8006c44c>] show_stack+0×58/0×100 Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.734094] [<800824c0>] __warn+0xe4/0×118 Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.738594] [<80082584>] warn_slowpath_null+0x1c/0×28 Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.744162] [<876079d4>] sta_set_sinfo+0xaec/0xb98 [mac80211]
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.750389] [<87607b60>] sta_info_destroy_addr_bss+0×38/0×60 [mac80211]
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.757764] [<8750f15c>] cfg80211_check_station_change+0x1be0/0x2c54 [cfg80211]
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.765684] —[ end trace 4604677d3a14d96c ]— Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.799099] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.901488] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626818.003882] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626818.106295] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626818.208683] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626818.311083] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626818.413480] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626818.515885] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:19 2019 kern.warn kernel: [626818.618279] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:19 2019 kern.warn kernel: [626818.720682] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:19 2019 kern.warn kernel: [626818.823084] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:19 2019 kern.warn kernel: [626818.925504] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:19 2019 kern.warn kernel: [626819.027903] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:19 2019 kern.warn kernel: [626819.130290] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:19 2019 kern.warn kernel: [626819.232697] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:19 2019 kern.warn kernel: [626819.335107] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:19 2019 kern.warn kernel: [626819.437492] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:20 2019 kern.warn kernel: [626819.539900] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:20 2019 kern.warn kernel: [626819.642300] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:20 2019 kern.warn kernel: [626819.744707] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:20 2019 kern.warn kernel: [626819.847110] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:20 2019 kern.warn kernel: [626819.949512] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:20 2019 kern.warn kernel: [626820.051909] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:20 2019 kern.warn kernel: [626820.154304] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:20 2019 kern.warn kernel: [626820.256719] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:20 2019 kern.warn kernel: [626820.359112] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:20 2019 kern.warn kernel: [626820.461524] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:21 2019 kern.warn kernel: [626820.563921] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:21 2019 kern.warn kernel: [626820.666314] ath10k_pci 0000:00:00.0: SWBA overrun on vdev 0, skipped old beacon
Sun Jan 20 01:19:21 2019 kern.warn kernel: [626820.698954] ath10k_pci 0000:00:00.0: removing peer, cleanup-all, deleting: peer 8612e200 vdev: 0 addr: fc:ec:da:ae:a0:d1
Sun Jan 20 01:19:21 2019 kern.info kernel: [626820.838595] ieee80211 phy0: Hardware restart was requested
Sun Jan 20 01:19:21 2019 kern.warn kernel: [626820.844562] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 0: -143
Sun Jan 20 01:19:21 2019 kern.warn kernel: [626820.852243] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 0: -143
Sun Jan 20 01:19:22 2019 kern.warn kernel: [626821.884646] ath10k_pci 0000:00:00.0: 10.1 wmi init: vdevs: 16 peers: 127 tid: 256
Sun Jan 20 01:19:22 2019 kern.info kernel: [626821.902855] ath10k_pci 0000:00:00.0: wmi print ‘P 128 V 8 T 410’ Sun Jan 20 01:19:22 2019 kern.info kernel: [626821.909440] ath10k_pci 0000:00:00.0: wmi print ‘msdu-desc: 1424 sw-crypt: 0 ct-sta: 0’ Sun Jan 20 01:19:22 2019 kern.info kernel: [626821.917837] ath10k_pci 0000:00:00.0: wmi print ‘alloc rem: 24616 iram: 26584’ Sun Jan 20 01:19:22 2019 kern.warn kernel: [626821.990859] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
Sun Jan 20 01:19:22 2019 kern.warn kernel: [626822.006126] ath10k_pci 0000:00:00.0: set-coverage-class, phyclk: 88 value: 0
Sun Jan 20 01:19:22 2019 kern.info kernel: [626822.023489] ath10k_pci 0000:00:00.0: device successfully recovered

Supply the following if possible:
- Device problem occurs on

- Ubiquiti UniFi-AC-LITE
- OpenWrt SNAPSHOT r9019-0e8d5ff / LuCI Master (git-19.011.54860-47d9205)
- Qualcomm Atheros QCA956X ver 1 rev 0

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

@OpenWrt_LR:~# opkg list-installed
ath10k-firmware-qca988x-ct - 2018-10-10-d366b80d-1
base-files - 196-r9019-0e8d5ff
busybox - 1.30.0-2
dnsmasq - 2.80-5
dropbear - 2017.75-9
firewall - 2019-01-02-70f8785b-2
fstools - 2018-12-28-af93f4b8-3
fwtool - 1
hostapd - 2018-12-02-c2c6c01b-1
hostapd-common - 2018-12-02-c2c6c01b-1
ip6tables - 1.8.2-2
iptables - 1.8.2-2
iw - 4.14-1
iwinfo - 2018-12-25-dd508af4-1
jshn - 2018-07-25-c83a84af-2
jsonfilter - 2018-02-04-c7e938d6-1
kernel - 4.14.91-1-62c515ec7afd0a040b29be060097c14e
kmod-ath - 4.14.91+4.19.7-1-1
kmod-ath10k-ct - 4.14.91+2018-12-20-118e16da-1
kmod-ath9k - 4.14.91+4.19.7-1-1
kmod-ath9k-common - 4.14.91+4.19.7-1-1
kmod-cfg80211 - 4.14.91+4.19.7-1-1
kmod-gpio-button-hotplug - 4.14.91-2
kmod-hwmon-core - 4.14.91-1
kmod-ip6tables - 4.14.91-1
kmod-ipt-conntrack - 4.14.91-1
kmod-ipt-core - 4.14.91-1
kmod-ipt-nat - 4.14.91-1
kmod-ipt-offload - 4.14.91-1
kmod-lib-crc-ccitt - 4.14.91-1
kmod-mac80211 - 4.14.91+4.19.7-1-1
kmod-nf-conntrack - 4.14.91-1
kmod-nf-conntrack6 - 4.14.91-1
kmod-nf-flow - 4.14.91-1
kmod-nf-ipt - 4.14.91-1
kmod-nf-ipt6 - 4.14.91-1
kmod-nf-nat - 4.14.91-1
kmod-nf-reject - 4.14.91-1
kmod-nf-reject6 - 4.14.91-1
kmod-ppp - 4.14.91-1
kmod-pppoe - 4.14.91-1
kmod-pppox - 4.14.91-1
kmod-slhc - 4.14.91-1
libblobmsg-json - 2018-07-25-c83a84af-2
libc - 1.1.20-1
libgcc - 7.4.0-1
libip4tc - 1.8.2-2
libip6tc - 1.8.2-2
libiwinfo - 2018-12-25-dd508af4-1
libiwinfo-lua - 2018-12-25-dd508af4-1
libjson-c - 0.12.1-2
libjson-script - 2018-07-25-c83a84af-2
liblua - 5.1.5-1
liblucihttp - 2018-05-18-cb119ded-1
liblucihttp-lua - 2018-05-18-cb119ded-1
libmbedtls - 2.14.1-1
libnl-tiny - 0.1-5
libpthread - 1.1.20-1
libubox - 2018-07-25-c83a84af-2
libubus - 2018-10-06-221ce7e7-1
libubus-lua - 2018-10-06-221ce7e7-1
libuci - 2018-08-11-4c8b4d6e-1
libuclient - 2018-11-24-3ba74ebc-1
libustream-mbedtls - 2018-07-30-23a3f283-1
libxtables - 1.8.2-2
logd - 2018-12-18-876c7f5b-1
lua - 5.1.5-1
luci - git-19.011.54860-47d9205-1
luci-app-firewall - git-19.011.54860-47d9205-1
luci-app-opkg - git-19.011.54860-47d9205-1
luci-base - git-19.011.54860-47d9205-1
luci-lib-ip - git-19.011.54860-47d9205-1
luci-lib-jsonc - git-19.011.54860-47d9205-1
luci-lib-nixio - git-19.011.54860-47d9205-1
luci-mod-admin-full - git-19.011.54860-47d9205-1
luci-mod-network - git-19.011.54860-47d9205-1
luci-mod-status - git-19.011.54860-47d9205-1
luci-mod-system - git-19.011.54860-47d9205-1
luci-proto-ipv6 - git-19.011.54860-47d9205-1
luci-proto-ppp - git-19.011.54860-47d9205-1
luci-ssl - git-19.011.54860-47d9205-1
luci-theme-bootstrap - git-19.011.54860-47d9205-1
mtd - 23
netifd - 2018-12-16-2750ce2e-1
odhcp6c - 2019-01-11-d2e247d8-16
odhcpd-ipv6only - 2018-12-12-2d2a3b84-3
openwrt-keyring - 2018-05-18-103a32e9-1
opkg - 2017-12-07-3b417b9f-3
ppp - 2.4.7-14
ppp-mod-pppoe - 2.4.7-14
procd - 2018-11-23-d6673547-1
px5g-mbedtls - 8
rpcd - 2018-11-28-3aa81d0d-1
rpcd-mod-rrdns - 20170710
swconfig - 12
uboot-envtools - 2018.03-3
ubox - 2018-12-18-876c7f5b-1
ubus - 2018-10-06-221ce7e7-1
ubusd - 2018-10-06-221ce7e7-1
uci - 2018-08-11-4c8b4d6e-1
uclient-fetch - 2018-11-24-3ba74ebc-1
uhttpd - 2018-11-28-cdfc902a-1
usign - 2015-07-04-ef641914-1
wireless-regdb - 2017-10-20-4343d359

- Steps to reproduce

 

Occurs every 4-12 hours.

Showing tasks 51 - 100 of 797 Page 2 of 16 - 1 - 2 - 3 - 4 - 5 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing