OpenWrt/LEDE Project

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

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

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

OpenedIDCategoryTask TypePrioritySeveritySummaryReported InStatus
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.

21.01.20192074Base systemBug ReportVery LowMedium ath10k_pci -- SWBA overrun on vdev 0, skipped old bea...TrunkUnconfirmed Task Description

Periodically (every 4 to 12 hours) the AP (Ubiquiti UniFi-AC-LITE) resets its kernel firmware, dropping all clients and resetting. It then recovers and clients re-connect after about 5 to 10 minutes. I get 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+0x58/0x100
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.734094] [<800824c0>] __warn+0xe4/0x118
Sun Jan 20 01:19:18 2019 kern.warn kernel: [626817.738594] [<80082584>] warn_slowpath_null+0x1c/0x28
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+0x38/0x60 [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

  1. Ubiquiti UniFi-AC-LITE
  2. OpenWrt SNAPSHOT r9019-0e8d5ff / LuCI Master (git-19.011.54860-47d9205)

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

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 of normal use.

21.01.20192073Base systemBug ReportVery LowCriticalSha1 in firmware-utils/src/sha1.c has TLS or DTLS Vulne...AllUnconfirmed Task Description

Hi,
The sha1 file in openwrt/tools/firmware-utils/src/sha1.c is not fixed and is vulnerable to remote code execution or DoS. The CVE (CVE-2018-0487) and fixed in multiple other repos including ubuntu. (https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-0487.html)

21.01.20192072PackagesBug ReportVery LowCriticalbn_wexpand return value vulnerable to memory leakopenwrt-18.06Unconfirmed Task Description

Hi,
The code in the openwrt/package/network/services/ead/src/tinysrp/bn_div.c should be fixed to check the bn_wexpand return value. The problem exists in multiple other projects including openssl with CVE (CVE-2009-3245)(https://github.com/openssl/openssl/commit/2d9dcd4ff0923347fab727ac90e8526dd65e4e07).

21.01.20192071PackagesBug ReportVery LowCriticalbn_wexpand return value vulnerable to memory leakopenwrt-18.06Unconfirmed Task Description

Hi,
The code in the openwrt/package/network/services/ead/src/tinysrp/bn_div.c should be fixed to check the bn_wexpand return value. The problem exists in multiple other projects including openssl with CVE (CVE-2009-3245)(https://github.com/openssl/openssl/commit/2d9dcd4ff0923347fab727ac90e8526dd65e4e07).

21.01.20192070PackagesBug ReportVery LowCriticalbn_wexpand in bn_div.c are not checked for failure and ...openwrt-18.06Unconfirmed Task Description

Hi,
The code in the openwrt/package/network/services/ead/src/tinysrp/bn_div.c should be fixed to check the bn_wexpand return value. The problem exists in multiple other projects including openssl with CVE (CVE-2009-3245)(https://github.com/openssl/openssl/commit/2d9dcd4ff0923347fab727ac90e8526dd65e4e07).

21.01.20192069PackagesFeature RequestVery LowLowAdd HSTS support to uhttpdopenwrt-18.06Unconfirmed Task Description

I’d like to be able to use HTTP Strict Transport Security (HSTS) on my uhttpd server.

20.01.20192068KernelBug ReportVery LowMediumtar not working properly with OverlayFSopenwrt-18.06Unconfirmed Task Description

I’ve configured extroot as recommended on the wiki, and I’m trying to create a Debian LXC container on my Netgear R8000. I’ve installed lxc-create, tar, getopt, and gnupg-utils, and tried installing the container with ‘lxc-create -t download -n debian’. But it failed with the following errors:

Downloading the image index
Downloading the rootfs
Downloading the metadata
The image cache is now ready
Unpacking the rootfs
tar: ./usr/share/vim/addons/plugin: Directory renamed before its status could be extracted
tar: ./usr/share/vim/addons: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/Canada: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/Mexico: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/US: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/Etc: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/Indian: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/Chile: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/Pacific: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/Antarctica: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/Asia: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/Atlantic: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/Brazil: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/Canada: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/Europe: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/SystemV: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/Mexico: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/US: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/Indian: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/Australia: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/America/Indiana: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/America/North_Dakota: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/America/Kentucky: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/America/Argentina: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/America: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/Africa: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/Etc: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix/Arctic: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/posix: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/right/Brazil: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/right/America/Argentina: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/right/America/Kentucky: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/right/America/Indiana: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/right/Chile: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/right/SystemV: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/right/Antarctica: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/right/Etc: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/right/Indian: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/right/US: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/right/Canada: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/right/Mexico: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/Antarctica: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/Chile: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/SystemV: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/Brazil: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/America/Indiana: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/America/Kentucky: Directory renamed before its status could be extracted
tar: ./usr/share/zoneinfo/America/Argentina: Directory renamed before its status could be extracted
tar: ./usr/share/man/man1: Directory renamed before its status could be extracted
tar: ./usr/share/man/fr/man1: Directory renamed before its status could be extracted
tar: ./usr/share/man/fr: Directory renamed before its status could be extracted
tar: ./usr/share/man/man8: Directory renamed before its status could be extracted
tar: ./usr/share/man/pl/man1: Directory renamed before its status could be extracted
tar: ./usr/share/man/pl: Directory renamed before its status could be extracted
tar: ./usr/share/man/it/man1: Directory renamed before its status could be extracted
tar: ./usr/share/man/it: Directory renamed before its status could be extracted
tar: ./usr/share/man/man7: Directory renamed before its status could be extracted
tar: ./usr/share/man/ja/man1: Directory renamed before its status could be extracted
tar: ./usr/share/man/ja: Directory renamed before its status could be extracted
tar: ./usr/share/man/ru/man1: Directory renamed before its status could be extracted
tar: ./usr/share/man/ru: Directory renamed before its status could be extracted
tar: ./usr/share/man: Directory renamed before its status could be extracted
tar: ./usr/share/locale: Directory renamed before its status could be extracted
tar: ./usr/lib/apt/planners: Directory renamed before its status could be extracted
tar: ./usr/lib/apt: Directory renamed before its status could be extracted
tar: ./usr/lib/systemd/user/graphical-session-pre.target.wants: Directory renamed before its status could be extracted
tar: ./usr/lib/systemd/user: Directory renamed before its status could be extracted
tar: ./usr/lib/systemd: Directory renamed before its status could be extracted
tar: ./usr/lib: Directory renamed before its status could be extracted
tar: ./usr/sbin: Directory renamed before its status could be extracted
tar: ./bin: Directory renamed before its status could be extracted
tar: ./lib/systemd/system/getty.target.wants: Directory renamed before its status could be extracted
tar: ./lib/systemd/system/rescue.target.wants: Directory renamed before its status could be extracted
tar: ./lib/systemd/system/timers.target.wants: Directory renamed before its status could be extracted
tar: ./lib/systemd/system/sockets.target.wants: Directory renamed before its status could be extracted
tar: ./lib/systemd/system/multi-user.target.wants: Directory renamed before its status could be extracted
tar: ./lib/systemd/system/sysinit.target.wants: Directory renamed before its status could be extracted
tar: ./lib/systemd/system/local-fs.target.wants: Directory renamed before its status could be extracted
tar: ./lib/systemd/system/graphical.target.wants: Directory renamed before its status could be extracted
tar: ./lib/systemd/system: Directory renamed before its status could be extracted
tar: ./lib/systemd: Directory renamed before its status could be extracted
tar: ./lib: Directory renamed before its status could be extracted
tar: ./sbin: Directory renamed before its status could be extracted
tar: Exiting with failure status due to previous errors
lxc-create: debian: lxccontainer.c: create_run_template: 1473 container creation template for debian failed
lxc-create: debian: tools/lxc_create.c: main: 329 Error creating container debian

I’m pretty sure this is fixed in a more recent kernel (output of uname -a: Linux OpenWrt 4.14.63 #0 SMP Thu Aug 16 07:51:15 2018 armv7l GNU/Linux), and I believe it has to do with constant indoe numbers (https://github.com/amir73il/overlayfs/wiki/Overlayfs-non-standard-behavior#constant-inode-numbers). This issue appears to be related: https://github.com/docker/hub-feedback/issues/727.

20.01.20192066KernelBug ReportVery LowMediumUSB doesn't work on openwrt-18.06.1 & lede-17.01.4AllUnconfirmed Task Description

Hello, it’s my first issue here.
My hardware: ALFA Network W502U / R36
Problem: USB port doesn’t work.
It works on openwrt-15.05, but does not work on lede-17.01.4 & openwrt-18.06.1.
I tried all I could find on google, but no successes.

All bellow done using: OpenWrt 18.06.1, r7258-5eb055306f

I don’t know how to do diagnostics properly, but here is what I already did:


root@OpenWrt:~# lsusb -t
Segmentation fault
root@OpenWrt:~# lsusb
unable to initialize libusb: -99
root@OpenWrt:~# opkg list-installed | grep usb
kmod-usb-core - 4.14.63-1
kmod-usb-ehci - 4.14.63-1
kmod-usb-storage - 4.14.63-1
kmod-usb-uhci - 4.14.63-1
kmod-usb2 - 4.14.63-1
libusb-1.0 - 1.0.22-1
usbutils - 007-9
root@OpenWrt:~# lsusb
unable to initialize libusb: -99
root@OpenWrt:~# lsusb -t
Segmentation fault
root@OpenWrt:~#


Maybe this can help:
root@OpenWrt:~# dmesg
[ 0.000000] Linux version 4.14.63 (buildbot@builds-03.infra.lede-project.org) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r7102-3f3a2c9)) #0 Thu Aug 16 07:51:15 20 18
[ 0.000000] SoC Type: Ralink RT3350 id:1 rev:2
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU0 revision is: 0001964c (MIPS 24KEc)
[ 0.000000] MIPS: machine is ALFA Networks W502U
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 02000000 @ 00000000 (usable)
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[ 0.000000] Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 byt es
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0×0000000000000000-0x0000000001ffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0×0000000000000000-0x0000000001ffffff]
[ 0.000000] Initmem setup node 0 [mem 0×0000000000000000-0x0000000001ffffff]
[ 0.000000] On node 0 totalpages: 8192
[ 0.000000] free_area_init_node: node 0, pgdat 803eaeb0, node_mem_map 8100004 0
[ 0.000000] Normal zone: 64 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 8192 pages, LIFO batch:0
[ 0.000000] random: get_random_bytes called from 0x803ee72c with crng_init=0
[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 8128
[ 0.000000] Kernel command line: console=ttyS0,115200 rootfstype=squashfs,jff s2
[ 0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[ 0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Writing ErrCtl register=00065de0
[ 0.000000] Readback ErrCtl register=00065de0
[ 0.000000] Memory: 27964K/32768K available (3419K kernel code, 172K rwdata, 424K rodata, 200K init, 210K bss, 4804K 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: 320MHz
[ 0.000000] timer_probe: no matching timers found
[ 0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_i dle_ns: 11945377789 ns
[ 0.000019] sched_clock: 32 bits at 160MHz, resolution 6ns, wraps every 13421 772796ns
[ 0.007898] Calibrating delay loop... 212.58 BogoMIPS (lpj=1062912)
[ 0.094000] pid_max: default: 32768 minimum: 301
[ 0.099003] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.105607] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.122218] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, ma x_idle_ns: 19112604462750000 ns
[ 0.132051] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.138273] pinctrl core: initialized pinctrl subsystem
[ 0.146792] NET: Registered protocol family 16
[ 0.160804] Can’t analyze schedule() prologue at 80352ab0
[ 0.213659] rt2880_gpio 10000600.gpio: registering 24 gpios
[ 0.219347] rt2880_gpio 10000600.gpio: registering 24 irq handlers
[ 0.236791] clocksource: Switched to clocksource MIPS
[ 0.244339] NET: Registered protocol family 2
[ 0.250848] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.257890] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.264159] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.270926] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.276710] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.283640] NET: Registered protocol family 1
[ 0.295590] rt-timer 10000100.timer: maximum frequency is 3255Hz
[ 0.303509] Crashlog allocated RAM at address 0x1f00000
[ 0.313920] workingset: timestamp_bits=30 max_order=13 bucket_order=0
[ 0.332748] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.338615] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORIT Y) © 2001-2006 Red Hat, Inc.
[ 0.380470] io scheduler noop registered
[ 0.384301] io scheduler deadline registered (default)
[ 0.390769] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[ 0.403784] console [ttyS0] disabled
[ 0.407515] 10000c00.uartlite: ttyS0 at MMIO 0x10000c00 (irq = 20, base_baud = 6666666) is a Palmchip BK-3103
[ 0.417412] console [ttyS0] enabled
[ 0.424364] bootconsole [early0] disabled
[ 0.433566] cacheinfo: Failed to find cpu0 device node
[ 0.438911] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 0.446463] 1f000000.cfi: Found 1 x16 devices at 0×0 in 16-bit bank. Manufact urer ID 0x0000c2 Chip ID 0x0022cb
[ 0.456743] Amd/Fujitsu Extended Query Table at 0×0040 [ 0.462002] Amd/Fujitsu Extended Query version 1.1.
[ 0.467163] number of CFI chips: 1
[ 0.488329] 4 fixed-partitions partitions found on MTD device 1f000000.cfi
[ 0.495300] Creating 4 MTD partitions on “1f000000.cfi”:
[ 0.500855] 0×000000000000-0×000000030000 : “u-boot” [ 0.508096] 0×000000030000-0×000000040000 : “u-boot-env” [ 0.515425] 0×000000040000-0×000000050000 : “factory” [ 0.522776] 0×000000050000-0×000000800000 : “firmware” [ 0.542321] 2 uimage-fw partitions found on MTD device firmware
[ 0.548525] 0×000000050000-0x00000019e790 : “kernel” [ 0.555519] 0x00000019e790-0×000000800000 : “rootfs” [ 0.562562] mtd: device 5 (rootfs) set to be root filesystem
[ 0.568501] 1 squashfs-split partitions found on MTD device rootfs
[ 0.574802] 0x0000003c0000-0×000000800000 : “rootfs_data” [ 0.583610] libphy: Fixed MDIO Bus: probed
[ 0.591353] rt3050-esw 10110000.esw: link changed 0×01 [ 0.609880] mtk_soc_eth 10100000.ethernet eth0: mediatek frame engine at 0xb0 100000, irq 5
[ 0.619526] rt2880_wdt 10000120.watchdog: Initialized
[ 0.627610] NET: Registered protocol family 10
[ 0.642865] Segment Routing with IPv6
[ 0.646978] NET: Registered protocol family 17
[ 0.651634] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 0.664823] 8021q: 802.1Q VLAN Support v1.8
[ 0.681284] VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
[ 0.691413] Freeing unused kernel memory: 200K
[ 0.695918] This architecture does not have kernel memory protection.
[ 1.619412] init: Console is alive
[ 1.623555] init: - watchdog -
[ 2.396830] random: fast init done
[ 2.722565] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[ 2.890829] kmodloader: done loading kernel modules from /etc/modules-boot.d/ *
[ 2.910041] init: - preinit -
[ 4.382680] 8021q: adding VLAN 0 to HW filter on device eth0
[ 4.672961] random: procd: uninitialized urandom read (4 bytes read)
[ 8.115618] jffs2: notice: (324) jffs2_build_xattr_subsystem: complete buildi ng xattr subsystem, 4 of xdatum (3 unchecked, 1 orphan) and 32 of xref (1 dead, 0 orphan) found.
[ 8.134525] mount_root: switching to jffs2 overlay
[ 8.190331] overlayfs: upper fs does not support tmpfile.
[ 8.206092] urandom-seed: Seeding with /etc/urandom.seed
[ 8.442557] procd: - early -
[ 8.445811] procd: - watchdog -
[ 9.256926] procd: - watchdog -
[ 9.261065] procd: - ubus -
[ 9.415882] random: ubusd: uninitialized urandom read (4 bytes read)
[ 9.427196] random: ubusd: uninitialized urandom read (4 bytes read)
[ 9.434866] random: ubusd: uninitialized urandom read (4 bytes read)
[ 9.444910] procd: - init -
[ 10.363541] kmodloader: loading kernel modules from /etc/modules.d/*
[ 10.493682] usbcore: registered new interface driver usbfs
[ 10.499804] usbcore: registered new interface driver hub
[ 10.505524] usbcore: registered new device driver usb
[ 10.542139] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
[ 10.640628] SCSI subsystem initialized
[ 10.679912] ehci-platform: EHCI generic platform driver
[ 10.696730] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 10.732456] Loading modules backported from Linux version wt-2017-11-01-0-gfe 248fc2c180
[ 10.740697] Backport generated by backports.git v4.14-rc2-1-31-g86cf0e5d
[ 10.756445] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 10.782367] nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
[ 10.925284] usbcore: registered new interface driver usb-storage
[ 10.976219] xt_time: kernel timezone is -0000
[ 11.101389] PPP generic driver version 2.4.2
[ 11.112322] NET: Registered protocol family 24
[ 11.161352] usbcore: registered new interface driver rtl8187
[ 11.203176] rt2800_wmac 10180000.wmac: loaded eeprom from mtd device “factory "
[ 11.210710] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 2872, rev 0200 d etected
[ 11.218641] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0005 detected
[ 11.227089] ieee80211 phy0: Selected rate control algorithm ‘minstrel_ht’ [ 11.399574] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 13.487575] urandom_read: 5 callbacks suppressed
[ 13.487592] random: jshn: uninitialized urandom read (4 bytes read)
[ 31.034969] 8021q: adding VLAN 0 to HW filter on device eth0
[ 31.128839] br-lan: port 1(eth0.1) entered blocking state
[ 31.134327] br-lan: port 1(eth0.1) entered disabled state
[ 31.140711] device eth0.1 entered promiscuous mode
[ 31.145584] device eth0 entered promiscuous mode
[ 31.247802] br-lan: port 1(eth0.1) entered blocking state
[ 31.253292] br-lan: port 1(eth0.1) entered forwarding state
[ 31.259544] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[ 32.027373] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 39.584842] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 39.605642] br-lan: port 2(wlan0) entered blocking state
[ 39.611182] br-lan: port 2(wlan0) entered disabled state
[ 39.617552] device wlan0 entered promiscuous mode
[ 40.719820] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 40.726761] br-lan: port 2(wlan0) entered blocking state
[ 40.732315] br-lan: port 2(wlan0) entered forwarding state
[ 76.772365] random: crng init done
[ 83.214660] do_page_fault(): sending SIGSEGV to lsusb for invalid read access from 00000000
[ 83.223256] epc = 00406f3d in lsusb[400000+11000]
[ 83.228069] ra = 00406f19 in lsusb[400000+11000]
[ 1235.373340] do_page_fault(): sending SIGSEGV to lsusb for invalid read access from 00000000
[ 1235.381999] epc = 00406f3d in lsusb[400000+11000]
[ 1235.386822] ra = 00406f19 in lsusb[400000+11000]

 


19.01.20192064Base systemBug ReportVery LowLowAfter umount /overlay && firstboot && reboot, settings ...openwrt-18.06Unconfirmed Task Description

Archer C7 V2 (US)
OpenWrt 18.06.1

Basically what happened is that after resetting using the command below, subsequent saves to router settings (e.g. enable WiFi, set SSID etc) were not retained. I could see it as I am applying it, but when I turn the router off and back on, it’s with the default settings! I did that several times, so pressty sure it wasn’t a one time glitch.

umount /overlay && firstboot && reboot

Backkground of the issue: router was initially flashed using openwrt-18.06.1-ar71xx-generic-archer-c7-v2-squashfs-factory, then happened to do resetting from LuCI but faced some problem with firewall/interfaces settings, so thought it’s best to reset using umount and firstboot, and that’s when the not-retaining settings happened.

I now reflashed with openwrt-18.06.1-ar71xx-generic-archer-c7-v2-squashfs-sysupgrade and settings are saved. So issue is solved for me.

I am not able to do further checking since I reflashed the router already, but thought of mentionnig what happened in case it rings any bell.


18.01.20192062Base systemBug ReportVery LowHighMTU is not set to 1508/1500 when using PPPoEopenwrt-18.06Unconfirmed Task Description

TP-LINK Archer C7, OpenWrt 18.06.1 r7258-5eb055306f / LuCI openwrt-18.06 branch (git-18.228.31946-f64b152).

Use PPPoE for WAN. Set MTU to 1508.

Observe ifconfig result. MTU is set at 1492, it should be 1500.

Add

config interface ‘eth0’

option ifname 'eth0'
option mtu '1508'

to /etc/config/network, ensure PPPoE MTU (as above) is set to 1508 and restart the network/reboot the router.

Observe ifconfig result. MTU is set at 1500 as expected.

15.01.20192059Base systemBug ReportVery LowHighuclient-fetch not working at all on http (not https) co...TrunkUnconfirmed Task Description

I just tried today’s trunk snapshot on my Turris Omnia; everything’s working fine apart from uclient-fetch. I noticed the failure because the ddns updater stopped working. If I install wget, everything works, since wget replaces uclient-fetch. Sample output follows.

Bad:

root@heimdall:/tmp# uclient-fetch http://perdu.com/ Downloading ‘http://perdu.com/’ Failed to establish connection
root@heimdall:/tmp#

Good:

root@heimdall:/tmp# wget http://perdu.com/ –2019-01-15 14:31:09– http://perdu.com/ Resolving perdu.com... 208.97.177.124
Connecting to perdu.com|208.97.177.124|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 204 [text/html]
Saving to: ‘index.html’

index.html 100%[==================================================================================================================================================================>] 204 --.-KB/s in 0s 2019-01-15 14:31:10 (16.4 MB/s) - 'index.html' saved [204/204] root@heimdall:/tmp# Image builder command line: make image PROFILE=turris-omnia PACKAGES="-kmod-ath9k -dnsmasq -odhcpd -odhcpd-ipv6only -odhcp6c -ppp -ppp-mod-pppoe ddns-scripts dnsmasq-full ethtool haveged htop ipset kmod-ipt-raw kmod-ipt-raw6 kmod-nf-nathelper-extra kmod-wireguard nano sqm-scripts tcpdump tor wget wireguard-tools zram-swap"

13.01.20192058Base systemBug ReportVery LowLowath79: valgrind fails to build for mip32TrunkUnconfirmed Task Description

Building the core system (current master)

tip commit:

commit 0e8d5ff0fc1cd8eb5236e6e497c340ceb21340fe
Author: Felix Fietkau <nbd@nbd.name>
Date:   Fri Jan 11 17:23:29 2019 +0100

    mt76: fix typo in version number

    Signed-off-by: Felix Fietkau <nbd@nbd.name>

( only for mip32 (specifically ath79 for a variety of boards) with CONFIG_ALL=y fails on building valgrind with:

{standard input}:91723: Error: opcode not supported on this processor: mips32 (mips32) `floor.l.s $f24,$f24'                    
{standard input}:91740: Error: `fp=64' used with a 32-bit fpu
{standard input}:91744: Error: opcode not supported on this processor: mips32 (mips32) `floor.l.d $f24,$f24'                    
{standard input}:91761: Error: `fp=64' used with a 32-bit fpu
{standard input}:91765: Error: opcode not supported on this processor: mips32 (mips32) `round.l.s $f24,$f24'                    
{standard input}:91782: Error: `fp=64' used with a 32-bit fpu
{standard input}:91786: Error: opcode not supported on this processor: mips32 (mips32) `round.l.d $f24,$f24'                    
{standard input}:91803: Error: `fp=64' used with a 32-bit fpu
{standard input}:91807: Error: opcode not supported on this processor: mips32 (mips32) `trunc.l.s $f24,$f24'                    
{standard input}:91824: Error: `fp=64' used with a 32-bit fpu
{standard input}:91828: Error: opcode not supported on this processor: mips32 (mips32) `trunc.l.d $f24,$f24'                    
lto-wrapper: fatal error: mips-openwrt-linux-musl-gcc returned 1 exit status                                                    
compilation terminated.
/home/daniel/Build/openwrt-ath79/staging_dir/toolchain-mips_24kc_gcc-7.4.0_musl/lib/gcc/mips-openwrt-linux-musl/7.4.0/../../../../mips-openwrt-linux-musl/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
13.01.20192057Base systemBug ReportVery LowMedium/etc/init.d/umount runs after other block devices must ...TrunkUnconfirmed Task Description

Supply the following if possible:

- Device problem occurs on

All.

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

18.06.01 & snapshots

- Steps to reproduce

 

Setup another block device that should be stopped after umount, e.g. cryptsetup, lvm2, or mdadm

Performing umount as K99umount allows very few things to run afterwards. Ideally, it would be K96umount or K97umount, which would allow for running multiple levels of stops afterwards. There should be at least two levels after umount.

For example, setting K98umount would still cause problems for K99cryptsetup & K99lvm2 because lvm2 must stop before cryptsetup and both must stop after mount.

Changing S99umount may also affect these other packages:

STOP=98 boot
STOP=98 kdump.init
STOP=98 mdadm.init
STOP=99 conserver.init
STOP=99 kismet_drone.init
STOP=99 kismet_server.init
STOP=99 socat.init

12.01.20192056Base systemBug ReportVery LowMediumodhcp misbehaves with multiple MACs for single host on ...TrunkUnconfirmed Task Description

According to the Static Leases section on DHCP's User Guide it should be possible to list several MAC addresses for the same host. Indeed everything works as expected with dnsmasq, and my host gets the expected IPv4 when using any of the listed MAC addresses.

However odhcp misbehaves when I list more than one MAC. With a single MAC on ‘option mac’, my host gets the expected IPv6, with the suffix defined under hostid. If I place two or more MACs on that option, odhcp fails to honor my rules and attributes a dynamic IPv6 with a random suffix.

Here is an example config that produces the erroneous behavior of odhcp.

config host
        option name 'host4'
        option ip '192.168.1.4'
        option hostid '4'
        option duid '00112233445566778899'
        option mac '00:11:22:33:44:55, 66:77:88:99:aa:bb'

(Separating the MACs list with either commas and spaces yields the same result. The DHCP User’s Guide has contradictory info on how the list should be separated, but it seems that both work for dnsmasq.)

11.01.20192055Base systemBug ReportVery LowLowconntrack -f ipv6 -L dumps IPv4 table, not IPv6TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on
TP-LINK wdr4300

- Software versions of OpenWrt/LEDE release, packages, etc.
18.06.1 fully up-to-date as of writing

- Steps to reproduce

# conntrack -f ipv6 -L -nv

This produces the IPv4 table, as if

-f ipv6

was not even specified.

11.01.20192054Base systemBug ReportVery LowLowAth9k RXORN stormTrunkUnconfirmed Task Description

the ath9k don’t clear RXORN bit . I think The write maybe think

 RXEOL  and RXORN shuold come together

but I test found the RXORN come only , In this situation the driver not
clear the RXORN bit , so driver can not recevice any pakcet ,I just recevie
RXORN interrupt


10.01.20192053KernelBug ReportVery LowMediumRegular crashes of ath10k-ct driver on ZyXEL NBG6817TrunkUnconfirmed Task Description

Model ZyXEL NBG6817
Architecture ARMv7 Processor rev 0 (v7l)
Firmware Version OpenWrt SNAPSHOT r9010-adc8b374e3 / LuCI Master (git-19.007.66460-4edac36)
Kernel Version 4.14.91
Local Time Thu Jan 10 10:57:42 2019
Uptime 16h 32m 57s
Load Average 0.40, 0.34, 0.18

Sadly there isn’t any simple way to reproduce, but they seem to be happening somewhat regularly. Since I put the device to use, 1 yesterday, 2 today.

Jan 10 09:26:10 hs14 kernel: [54084.922093] ath10k_pci 0001:01:00.0: firmware crashed! (guid ec43bc35-1369-4765-b62f-6ccef1fb3d02)
Jan 10 09:26:10 hs14 kernel: [54084.922155] ath10k_pci 0001:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
Jan 10 09:26:10 hs14 kernel: [54084.929958] ath10k_pci 0001:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
Jan 10 09:26:10 hs14 kernel: [54084.942242] ath10k_pci 0001:01:00.0: firmware ver 10.4b-ct-9984-fW-012-81e1edd54 api 5 features mfp,peer-flow-ctrl,txstatus-noack,wmi-10.x-CT,ratemask-CT,reg
dump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT,tx-rc-CT,cust-stats-CT,txrate2-CT crc32 0391c067
Jan 10 09:26:10 hs14 kernel: [54084.951289] ath10k_pci 0001:01:00.0: board_file api 2 bmi_id 0:2 crc32 cf58c3bc
Jan 10 09:26:10 hs14 kernel: [54084.972926] ath10k_pci 0001:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 32 raw 0 hwcrypto 1
Jan 10 09:26:10 hs14 kernel: [54084.982076] ath10k_pci 0001:01:00.0: firmware register dump:
Jan 10 09:26:10 hs14 kernel: [54084.990109] ath10k_pci 0001:01:00.0: [00]: 0x0000000A 0x000015B3 0x009A582B 0x00975B31
Jan 10 09:26:10 hs14 kernel: [54084.996013] ath10k_pci 0001:01:00.0: [04]: 0x009A582B 0x00060B30 0x00000000 0x00000000
Jan 10 09:26:10 hs14 kernel: [54085.003740] ath10k_pci 0001:01:00.0: [08]: 0x00000000 0x004602A4 0x00406764 0x00000000
Jan 10 09:26:10 hs14 kernel: [54085.011640] ath10k_pci 0001:01:00.0: [12]: 0x00000009 0x00000000 0x00973ABC 0x00973AD2
Jan 10 09:26:10 hs14 kernel: [54085.019537] ath10k_pci 0001:01:00.0: [16]: 0x00973AB0 0x0096398A 0x009606CA 0x00000000
Jan 10 09:26:10 hs14 kernel: [54085.027437] ath10k_pci 0001:01:00.0: [20]: 0x409A582B 0x0040660C 0x00000005 0x000000FF
Jan 10 09:26:10 hs14 kernel: [54085.035336] ath10k_pci 0001:01:00.0: [24]: 0x809A698A 0x0040666C 0x00000005 0xC09A582B
Jan 10 09:26:10 hs14 kernel: [54085.043235] ath10k_pci 0001:01:00.0: [28]: 0x809A7EF9 0x0040669C 0x0045F0D0 0x0045FCA8
Jan 10 09:26:10 hs14 kernel: [54085.051135] ath10k_pci 0001:01:00.0: [32]: 0x809A8D32 0x0040672C 0x0045FCE4 0x00406850
Jan 10 09:26:10 hs14 kernel: [54085.059035] ath10k_pci 0001:01:00.0: [36]: 0x809A8D62 0x0040684C 0x0042D864 0x0042EF70
Jan 10 09:26:10 hs14 kernel: [54085.066934] ath10k_pci 0001:01:00.0: [40]: 0x80985E4B 0x0040689C 0x00000000 0x0045A9F4
Jan 10 09:26:10 hs14 kernel: [54085.074833] ath10k_pci 0001:01:00.0: [44]: 0x80994A73 0x004068BC 0x0042ED20 0x0045A9F4
Jan 10 09:26:10 hs14 kernel: [54085.082732] ath10k_pci 0001:01:00.0: [48]: 0x8098FC30 0x004068DC 0x0042ED20 0x00000000
Jan 10 09:26:10 hs14 kernel: [54085.090631] ath10k_pci 0001:01:00.0: [52]: 0x80963AD3 0x00406A7C 0x0042ED20 0x0098FC28
Jan 10 09:26:10 hs14 kernel: [54085.098530] ath10k_pci 0001:01:00.0: [56]: 0x80960E80 0x00406A9C 0x0000001F 0x00400000
Jan 10 09:26:10 hs14 kernel: [54085.106429] ath10k_pci 0001:01:00.0: Copy Engine register dump:
Jan 10 09:26:10 hs14 kernel: [54085.114333] ath10k_pci 0001:01:00.0: [00]: 0x0004a000  13  13   3   3
Jan 10 09:26:10 hs14 kernel: [54085.120150] ath10k_pci 0001:01:00.0: [01]: 0x0004a400  10  10 432 433
Jan 10 09:26:10 hs14 kernel: [54085.126747] ath10k_pci 0001:01:00.0: [02]: 0x0004a800  46  46 109 110
Jan 10 09:26:10 hs14 kernel: [54085.133170] ath10k_pci 0001:01:00.0: [03]: 0x0004ac00  21  21  23  21
Jan 10 09:26:10 hs14 kernel: [54085.139594] ath10k_pci 0001:01:00.0: [04]: 0x0004b000 2043 1937  30  30
Jan 10 09:26:10 hs14 kernel: [54085.146018] ath10k_pci 0001:01:00.0: [05]: 0x0004b400   1   1 128 129
Jan 10 09:26:10 hs14 kernel: [54085.152441] ath10k_pci 0001:01:00.0: [06]: 0x0004b800  10  10  10  10
Jan 10 09:26:10 hs14 kernel: [54085.159039] ath10k_pci 0001:01:00.0: [07]: 0x0004bc00   1   1   1   1
Jan 10 09:26:10 hs14 kernel: [54085.165462] ath10k_pci 0001:01:00.0: [08]: 0x0004c000   0   0 127   0
Jan 10 09:26:10 hs14 kernel: [54085.171886] ath10k_pci 0001:01:00.0: [09]: 0x0004c400   1   1   1   1
Jan 10 09:26:10 hs14 kernel: [54085.178310] ath10k_pci 0001:01:00.0: [10]: 0x0004c800   0   0   0   0
Jan 10 09:26:10 hs14 kernel: [54085.184733] ath10k_pci 0001:01:00.0: [11]: 0x0004cc00   0   0   0   0
Jan 10 09:26:10 hs14 kernel: [54085.193175] ath10k_pci 0001:01:00.0: debug log header, dbuf: 0x423818  dropped: 0
Jan 10 09:26:10 hs14 kernel: [54085.198590] ath10k_pci 0001:01:00.0: [0] next: 0x423800 buf: 0x419610 sz: 1500 len: 252 count: 9 free: 0
Jan 10 09:26:10 hs14 kernel: [54085.206060] ath10k_pci 0001:01:00.0: ath10k_pci ATH10K_DBG_BUFFER:
Jan 10 09:26:10 hs14 kernel: [54085.214587] ath10k: [0000]: 034C7883 14004C01 71104441 01050F98 00019003 00000000 0000FFFF 034C7884
Jan 10 09:26:10 hs14 kernel: [54085.220581] ath10k: [0008]: 14004C01 71108880 00000000 00D80000 00000000 00000FF0 034C7884 14004C01
Jan 10 09:26:10 hs14 kernel: [54085.229521] ath10k: [0016]: 71108880 00010000 00D80000 00000000 00000000 034C7884 14004C01 71108880
Jan 10 09:26:10 hs14 kernel: [54085.238548] ath10k: [0024]: 00020000 00D80000 00000000 00000000 034C7884 14004C01 71108880 00030000
Jan 10 09:26:10 hs14 kernel: [54085.247576] ath10k: [0032]: 00D80000 00000000 00000000 034C7884 14004C01 71108880 00040000 00D80000
Jan 10 09:26:10 hs14 kernel: [54085.256604] ath10k: [0040]: 00000000 00000000 034C7884 14004C01 71108880 00050000 00D80000 00000000
Jan 10 09:26:10 hs14 kernel: [54085.265642] ath10k: [0048]: 00000000 034C7884 14004C01 71108880 00060000 00D80000 00000000 00000000
Jan 10 09:26:10 hs14 kernel: [54085.274659] ath10k: [0056]: 034C7885 17FC0001 009A582B 000015B3 000015B3 004064FC 91104569
Jan 10 09:26:10 hs14 kernel: [54085.283686] ath10k_pci 0001:01:00.0: ATH10K_END
Jan 10 09:26:10 hs14 kernel: [54085.293030] ath10k_pci 0001:01:00.0: [1] next: 0x423818 buf: 0x419020 sz: 1500 len: 0 count: 0 free: 0
Jan 10 09:26:10 hs14 kernel: [54085.336026] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 1, skipped old beacon
Jan 10 09:26:10 hs14 kernel: [54085.361017] ath10k_pci 0001:01:00.0: removing peer, cleanup-all, deleting: peer da1bf400 vdev: 0 addr: 48:45:20:c2:27:84
Jan 10 09:26:10 hs14 kernel: [54085.361055] ath10k_pci 0001:01:00.0: removing peer, cleanup-all, deleting: peer da1be400 vdev: 0 addr: 64:a2:f9:31:0f:98
Jan 10 09:26:10 hs14 kernel: [54085.371034] ath10k_pci 0001:01:00.0: removing peer, cleanup-all, deleting: peer da1be200 vdev: 0 addr: 84:c7:ea:8f:41:c7
Jan 10 09:26:10 hs14 kernel: [54085.381962] ath10k_pci 0001:01:00.0: removing peer, cleanup-all, deleting: peer da1bf000 vdev: 0 addr: 6c:c7:ec:46:de:44
Jan 10 09:26:10 hs14 kernel: [54085.392896] ath10k_pci 0001:01:00.0: removing peer, cleanup-all, deleting: peer da1bfc00 vdev: 0 addr: 88:d7:f6:9f:51:10
Jan 10 09:26:10 hs14 kernel: [54085.403829] ath10k_pci 0001:01:00.0: removing peer, cleanup-all, deleting: peer dbd42e00 vdev: 1 addr: 5e:e2:8c:f2:fe:80
Jan 10 09:26:10 hs14 kernel: [54085.414796] ath10k_pci 0001:01:00.0: removing peer, cleanup-all, deleting: peer dbbdc200 vdev: 0 addr: 5c:e2:8c:f2:fe:80
Jan 10 09:26:10 hs14 kernel: [54085.516577] ieee80211 phy1: Hardware restart was requested
Jan 10 09:26:11 hs14 kernel: [54085.597874] ath10k_pci 0001:01:00.0: Invalid state: 3 in ath10k_htt_tx_32, warning will not be repeated.
Jan 10 09:26:11 hs14 kernel: [54085.597905] ------------[ cut here ]------------
Jan 10 09:26:11 hs14 kernel: [54085.606562] WARNING: CPU: 1 PID: 0 at /var/lib/buildbot/slaves/tictex-02/ipq806x_generic/build/build_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/linux-ipq806x/ath10k-ct-2018-12-20-118e16da/ath10k-4.19/htt_tx.c:1250 ath10k_htt_tx_32+0xf0/0x9e0 [ath10k_core]
Jan 10 09:26:11 hs14 kernel: [54085.611507] Modules linked in: pppoe ppp_async ath10k_pci ath10k_core ath pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables crc_ccitt compat act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_tbf sch_htb sch_hfsc sch_ingress ledtrig_usbport ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables leds_gpio
Jan 10 09:26:11 hs14 kernel: [54085.682720]  xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_of_simple ohci_platform ohci_hcd phy_qcom_dwc3 ahci ehci_platform sd_mod ahci_platform libahci_platform libahci libata scsi_mod ehci_hcd gpio_button_hotplug ext4 jbd2 mbcache crc32c_generic
Jan 10 09:26:11 hs14 kernel: [54085.704952] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.14.91 #0
Jan 10 09:26:11 hs14 kernel: [54085.726639] Hardware name: Generic DT based system
Jan 10 09:26:11 hs14 kernel: [54085.732654] [<c030f58c>] (unwind_backtrace) from [<c030b7a4>] (show_stack+0x14/0x20)
Jan 10 09:26:11 hs14 kernel: [54085.737240] [<c030b7a4>] (show_stack) from [<c07b26f8>] (dump_stack+0x88/0x9c)
Jan 10 09:26:11 hs14 kernel: [54085.745143] [<c07b26f8>] (dump_stack) from [<c0318ec4>] (__warn+0xf0/0x11c)
Jan 10 09:26:11 hs14 kernel: [54085.752167] [<c0318ec4>] (__warn) from [<c0318fb0>] (warn_slowpath_null+0x20/0x28)
Jan 10 09:26:11 hs14 kernel: [54085.759059] [<c0318fb0>] (warn_slowpath_null) from [<bf4a5c18>] (ath10k_htt_tx_32+0xf0/0x9e0 [ath10k_core])
Jan 10 09:26:11 hs14 kernel: [54085.766772] [<bf4a5c18>] (ath10k_htt_tx_32 [ath10k_core]) from [<bf48a0f8>] (ath10k_mac_op_set_bitrate_mask+0xc40/0xdac [ath10k_core])
Jan 10 09:26:11 hs14 kernel: [54085.776369] [<bf48a0f8>] (ath10k_mac_op_set_bitrate_mask [ath10k_core]) from [<bf48ff24>] (ath10k_mac_tx_push_txq+0x234/0x290 [ath10k_core])
Jan 10 09:26:11 hs14 kernel: [54085.788524] [<bf48ff24>] (ath10k_mac_tx_push_txq [ath10k_core]) from [<bf4901b4>] (ath10k_mac_op_wake_tx_queue+0x88/0x12c [ath10k_core])
Jan 10 09:26:11 hs14 kernel: [54085.801339] [<bf4901b4>] (ath10k_mac_op_wake_tx_queue [ath10k_core]) from [<bf3fefa4>] (ieee80211_unreserve_tid+0x658/0x718 [mac80211])
Jan 10 09:26:11 hs14 kernel: [54085.813569] [<bf3fefa4>] (ieee80211_unreserve_tid [mac80211]) from [<bf401c94>] (__ieee80211_subif_start_xmit+0x728/0x978 [mac80211])
Jan 10 09:26:11 hs14 kernel: [54085.825444] [<bf401c94>] (__ieee80211_subif_start_xmit [mac80211]) from [<bf4021d4>] (ieee80211_subif_start_xmit+0x2f0/0x310 [mac80211])
Jan 10 09:26:11 hs14 kernel: [54085.837553] [<bf4021d4>] (ieee80211_subif_start_xmit [mac80211]) from [<c069cd80>] (dev_hard_start_xmit+0xc8/0x154)
Jan 10 09:26:11 hs14 kernel: [54085.849828] [<c069cd80>] (dev_hard_start_xmit) from [<c069d54c>] (__dev_queue_xmit+0x630/0x7b0)
Jan 10 09:26:11 hs14 kernel: [54085.859983] [<c069d54c>] (__dev_queue_xmit) from [<c07917d4>] (br_dev_queue_push_xmit+0x144/0x168)
Jan 10 09:26:11 hs14 kernel: [54085.868662] [<c07917d4>] (br_dev_queue_push_xmit) from [<c0791830>] (br_forward_finish+0x38/0xa0)
Jan 10 09:26:11 hs14 kernel: [54085.877688] [<c0791830>] (br_forward_finish) from [<c0791980>] (__br_forward+0xe8/0x144)
Jan 10 09:26:11 hs14 kernel: [54085.886629] [<c0791980>] (__br_forward) from [<c0793624>] (br_handle_frame_finish+0x4fc/0x56c)
Jan 10 09:26:11 hs14 kernel: [54085.894788] [<c0793624>] (br_handle_frame_finish) from [<c0793a90>] (br_handle_frame+0x328/0x3c0)
Jan 10 09:26:11 hs14 kernel: [54085.903218] [<c0793a90>] (br_handle_frame) from [<c0698458>] (__netif_receive_skb_core+0x71c/0xbdc)
Jan 10 09:26:11 hs14 kernel: [54085.912154] [<c0698458>] (__netif_receive_skb_core) from [<c069a714>] (process_backlog+0xb0/0x164)
Jan 10 09:26:11 hs14 kernel: [54085.921008] [<c069a714>] (process_backlog) from [<c069e334>] (net_rx_action+0x144/0x31c)
Jan 10 09:26:11 hs14 kernel: [54085.930032] [<c069e334>] (net_rx_action) from [<c03015c8>] (__do_softirq+0xf0/0x264)
Jan 10 09:26:11 hs14 kernel: [54085.938285] [<c03015c8>] (__do_softirq) from [<c031d280>] (irq_exit+0xdc/0x148)
Jan 10 09:26:11 hs14 kernel: [54085.946006] [<c031d280>] (irq_exit) from [<c035a0d8>] (__handle_domain_irq+0xa8/0xc8)
Jan 10 09:26:11 hs14 kernel: [54085.953036] [<c035a0d8>] (__handle_domain_irq) from [<c0301488>] (gic_handle_irq+0x6c/0xb8)
Jan 10 09:26:11 hs14 kernel: [54085.961022] [<c0301488>] (gic_handle_irq) from [<c030c38c>] (__irq_svc+0x6c/0x90)
Jan 10 09:26:11 hs14 kernel: [54085.969176] Exception stack(0xdd45ff80 to 0xdd45ffc8)
Jan 10 09:26:11 hs14 kernel: [54085.976838] ff80: 00000001 00000000 00000000 c0315300 ffffe000 c0b03c74 c0b03c28 00000000
Jan 10 09:26:11 hs14 kernel: [54085.981876] ffa0: 00000000 512f04d0 00000000 00000000 dd45ffc8 dd45ffd0 c030884c c0308850
Jan 10 09:26:11 hs14 kernel: [54085.990018] ffc0: 60000013 ffffffff
Jan 10 09:26:11 hs14 kernel: [54085.998171] [<c030c38c>] (__irq_svc) from [<c0308850>] (arch_cpu_idle+0x38/0x44)
Jan 10 09:26:11 hs14 kernel: [54086.001477] [<c0308850>] (arch_cpu_idle) from [<c034ff08>] (do_idle+0xe8/0x1bc)
Jan 10 09:26:11 hs14 kernel: [54086.009111] [<c034ff08>] (do_idle) from [<c0350250>] (cpu_startup_entry+0x1c/0x20)
Jan 10 09:26:11 hs14 kernel: [54086.016142] [<c0350250>] (cpu_startup_entry) from [<423017cc>] (0x423017cc)
Jan 10 09:26:11 hs14 kernel: [54086.023843] ---[ end trace 452feb3a499a0195 ]---
Jan 10 09:26:11 hs14 kernel: [54086.030636] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:11 hs14 kernel: [54086.035568] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:11 hs14 kernel: [54086.042594] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:11 hs14 kernel: [54086.048636] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:11 hs14 kernel: [54086.054310] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:11 hs14 kernel: [54086.061524] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:11 hs14 kernel: [54086.081184] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
Jan 10 09:26:11 hs14 kernel: [54086.081230] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 1, skipped old beacon
Jan 10 09:26:11 hs14 kernel: [54086.087310] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
Jan 10 09:26:11 hs14 kernel: [54086.094688] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 1, skipped old beacon
Jan 10 09:26:11 hs14 kernel: [54086.101966] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
Jan 10 09:26:11 hs14 kernel: [54086.398043] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:11 hs14 kernel: [54086.398093] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:11 hs14 kernel: [54086.404163] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:11 hs14 kernel: [54086.410265] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:11 hs14 kernel: [54086.415885] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:11 hs14 kernel: [54086.423100] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:12 hs14 kernel: [54086.859493] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:12 hs14 kernel: [54086.859541] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:12 hs14 kernel: [54086.865611] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:12 hs14 kernel: [54087.668435] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:12 hs14 kernel: [54087.668484] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:12 hs14 kernel: [54087.674553] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:13 hs14 kernel: [54087.998516] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:13 hs14 kernel: [54087.998564] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:13 hs14 kernel: [54088.004648] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:13 hs14 kernel: [54088.010739] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:13 hs14 kernel: [54088.016359] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:13 hs14 kernel: [54088.023559] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:13 hs14 kernel: [54088.315168] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:13 hs14 kernel: [54088.315215] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:13 hs14 kernel: [54088.321286] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.199325] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:16 hs14 kernel: [54091.199378] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.205447] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.317048] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:16 hs14 kernel: [54091.317096] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.323165] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.399734] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:16 hs14 kernel: [54091.399767] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.405938] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.414260] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:16 hs14 kernel: [54091.417567] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.424841] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.442523] ath10k_pci 0001:01:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
Jan 10 09:26:16 hs14 kernel: [54091.442587] ath10k_pci 0001:01:00.0: msdu-desc: 2500  skid: 32
Jan 10 09:26:16 hs14 kernel: [54091.474435] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:16 hs14 kernel: [54091.474465] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.480544] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.492287] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:16 hs14 kernel: [54091.492316] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.499467] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.524925] ath10k_pci 0001:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
Jan 10 09:26:16 hs14 kernel: [54091.525752] ath10k_pci 0001:01:00.0: wmi print 'free: 87020 iram: 26788 sram: 18240'
Jan 10 09:26:16 hs14 kernel: [54091.578225] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:16 hs14 kernel: [54091.578254] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.584413] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54091.941028] ath10k_pci 0001:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Jan 10 09:26:17 hs14 kernel: [54092.060188] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:17 hs14 kernel: [54092.060235] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.066307] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.072884] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:17 hs14 kernel: [54092.078031] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.085315] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.092632] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:17 hs14 kernel: [54092.096943] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.104226] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.110805] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.115940] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.122235] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.127668] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.194155] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.194197] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.199984] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.204944] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.263526] ath10k_pci 0001:01:00.0: device successfully recovered
07.01.20192051Base systemBug ReportVery LowHighDHCP not working properly. openwrt-18.06Unconfirmed Task Description

I have WRT3200ACM and also EX6150v2 both using openwrt 18.06.01. With their stock firmware, my IOT devices like Mi LED and Wemo will connect just fine. With OpenWrt, some devices just not getting IP from the router/AP. Also, relayd is not working when the main router is using OpenWrt. If I use stock firmware as main AP then all problem solved. Seems like something wrong with OpenWrt’s DHCP system. I have also tried 18.06 version.

05.01.20192049Base systemBug ReportVery LowLowWN3000RP boot failed Checksum mismatch, Boot program ch...TrunkUnconfirmed Task Description

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

 

Device WN3000RP without any additional endings e.g. v1
Software versions of LEDE 17, 18

Steps to reproduce:
flash with lede-17.01.6-brcm47xx-mips74k-netgear-wn3000rp-squashfs.chk or openwrt-18.06.1-brcm47xx-mips74k-netgear-wn3000rp-squashfs.chk results
for LEDE 17
Checksum mismatch:
Image chksum: 0x8E7E8A20
Calc chksum: 0x5D868420
Boot program checksum is invalid
and for LEDE 18
Checksum mismatch:
Image chksum: 0x50DEE50C
Calc chksum: 0x990DE392
Boot program checksum is invalid

logs from UART console.

04.01.20192047KernelBug ReportVery LowMediumSwap kernel option doesn't work and /proc/swap endpoint...TrunkUnconfirmed Task Description

Device: TP-LINK TL-MR3420 v2 with replaced NAND flash chip (8MB ROM now) + USB hub with external power + 8Gb flash drive + 1Tb USB hdd
OpenWRT version: Trunk, OpenWrt GCC 7.4.0 r8982-a54129d
Steps to reproduce:
1) Install block-mount and swap-utils
2) Create swap partition and try to enable it

root@OpenWrt:~# mkswap /dev/sdb2
mkswap: /dev/sdb2: warning: wiping old swap signature.
Setting up swapspace version 1, size = 256 MiB (268431360 bytes)
no label, UUID=3068f953-a060-41cd-a09b-bcc2c531bf40
root@OpenWrt:~# swapon /dev/sdb2
block: failed to swapon /dev/sdb2 (-1)

3) Try to get /proc/swaps file

root@OpenWrt:~# cat /proc/swaps
cat: can’t open ‘/proc/swaps’: No such file or directory


“dmesg” output is attached.

03.01.20192045Base systemBug ReportVery LowLowlvm2: /etc/init.d/lvm2 does not define a STOP levelTrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

specifically tested & confirmed on x86-64 and ipq806x

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

18.06.1 and snapshot

- Steps to reproduce

opkg install lvm2

03.01.20192044Base systemBug ReportVery LowLow/etc/init.d/mdadm is set to STOP=98 before /etc/init.d/...TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

specifically tested & confirmed on x86-64 and ipq806x

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

18.06.1 and snapshot

- Steps to reproduce

opkg install mdadm

03.01.20192043Base systemBug ReportVery LowLowmdadm files/mdadm.config should ship with an empty conf...TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

specifically tested & confirmed on x86-64 and ipq806x

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

18.06.1 and snapshot

- Steps to reproduce

opkg install mdadm

 


03.01.20192042Base systemBug ReportVery LowMediumnat helpers do not work (e.g. ftp), CT rules do not mat...TrunkUnconfirmed Task Description

OpenWrt SNAPSHOT, r8978-eb1887be93

Automatically generated rule like the below does not match any connections originating from WAN:

Chain zone_wan_helper (1 references)
pkts bytes target prot opt in out source destination
0 0 CT tcp – * * 0.0.0.0/0 192.168.1.250 tcp dpt:21 ctstate DNAT /* !fw3: FTP (CT helper) */ CT helper ftp

To have working passive FTP I need to add the following line to /etc/firewall.user (based on rules generated by shorewall):

iptables -t raw -A zone_wan_helper -p tcp –dport 21 -j CT –helper ftp –tcp-flags SYN,ACK,FIN,RST SYN

Either ctstate or destination ip does not match in the original rule.

02.01.20192041ToolchainBug ReportVery LowMediumPre-compiled headers don't work at all when building on...lede-17.01Unconfirmed Task Description

To reproduce:
1) Make a file test.h:
#define test 1
2) Make a file test.c:
void main() { return; }
3) Try to create and use a precompiled header
mips-...g++ -c -x c++-header -o test.gch test.h
mips-...g++ -o prog -Winvalid-pch -include test test.c

I get:

cc1plus: warning: test.gch: had text segment at different address

So it appears that something Bionic/GCC7.3 is doing to gcc causes gcc 5.4.0 PCH to break completely. PCH works fine on GCC 7.3 on the host, so it’s likely something that was fixed upstream, but I’m having difficulty finding the fix in gcc’s git history.

01.01.20192040Base systemBug ReportVery LowCriticalgdb 8.2 fails to compile for Raspberry Pi 3B+TrunkUnconfirmed Task Description

- Device problem occurs on
Attempting build for Raspberry Pi 3B+ with gdbserver included

- Software versions of OpenWrt/LEDE release, packages, etc.
commit d3bf5ff9bc7b55b2a3dab93853b33a0cd2c4ca47 (HEAD → master, origin/master, origin/HEAD)
Author: Jonas Gorski jonas.gorski@gmail.com Date: Mon Sep 10 11:42:53 2018 +0200

- Steps to reproduce
(I successfully built and ran it without gdbserver.)
In menuconfig, selected the correct SoC, added Luci, then followed https://openwrt.org/docs/guide-developer/gdb:
“Compiling Tools” - exactly as described.
“Add debugging to a package” - option “Global build settings > Compile packages with debugging info” (whether this is activated or not has no effect on the problem)

gdb compilation for the target fails, see error below.

I reverted 2 last commits to the gdb package, to what it was at this commit:
commit 525b8f06501233414ad6e56fe1134ae82ab28fc2
Author: Rosen Penev rosenp@gmail.com
Date: Wed Jun 6 18:22:26 2018 -0700

using these commands:
cd package/devel
git checkout 525b8f06501 gdb

and the build succeeded. Looks like the updated gdb

.config is attached.


aarch64-openwrt-linux-musl-g++ -x c++ -Os -pipe -mcpu=cortex-a53 -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -iremap/mnt/1TB/ow/openwrt/build_dir/target-aarch64_cortex-a53_musl/gdb-8.2:gdb-8.2 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro -I. -I. -I./common -I./config -DLOCALEDIR=”“/usr/share/locale”” -DHAVE_CONFIG_H -I./../include/opcode -I./../opcodes/.. -I./../zlib -I../bfd -I./../bfd -I./../include -I../libdecnumber -I./../libdecnumber -I./gnulib/import -Ibuild-gnulib/import -DTUI=1 -Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-body -Wunused-but-set-parameter -Wunused-but-set-variable -Wno-sign-compare -Wno-narrowing -Wno-error=maybe-uninitialized -Wsuggest-override -Wimplicit-fallthrough=3 -Wduplicated-cond -Wformat-nonliteral -c -o aarch64-linux-nat.o -MT aarch64-linux-nat.o -MMD -MP -MF ./.deps/aarch64-linux-nat.Tpo aarch64-linux-nat.c
In file included from nat/aarch64-sve-linux-ptrace.h:23:0,
from aarch64-linux-nat.c:35:
/mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/asm/sigcontext.h:26:8: error: redefinition of ‘struct sigcontext’ struct sigcontext {

In file included from /mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/signal.h:48:0,
from build-gnulib/import/signal.h:52,
from linux-nat.h:23,
from aarch64-linux-nat.c:26:
/mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/bits/signal.h:18:16: note: previous definition of ‘struct sigcontext’ typedef struct sigcontext {

In file included from nat/aarch64-sve-linux-ptrace.h:23:0,
from aarch64-linux-nat.c:35:
/mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/asm/sigcontext.h:63:8: error: redefinition of ‘struct _aarch64_ctx’ struct _aarch64_ctx {

In file included from /mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/signal.h:48:0,
from build-gnulib/import/signal.h:52,
from linux-nat.h:23,
from aarch64-linux-nat.c:26:
/mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/bits/signal.h:29:8: note: previous definition of ‘struct _aarch64_ctx’ struct _aarch64_ctx {

In file included from nat/aarch64-sve-linux-ptrace.h:23:0,
from aarch64-linux-nat.c:35:
/mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/asm/sigcontext.h:70:8: error: redefinition of ‘struct fpsimd_context’ struct fpsimd_context {

In file included from /mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/signal.h:48:0,
from build-gnulib/import/signal.h:52,
from linux-nat.h:23,
from aarch64-linux-nat.c:26:
/mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/bits/signal.h:33:8: note: previous definition of ‘struct fpsimd_context’ struct fpsimd_context {

In file included from nat/aarch64-sve-linux-ptrace.h:23:0,
from aarch64-linux-nat.c:35:
/mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/asm/sigcontext.h:80:8: error: redefinition of ‘struct esr_context’ struct esr_context {

In file included from /mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/signal.h:48:0,
from build-gnulib/import/signal.h:52,
from linux-nat.h:23,
from aarch64-linux-nat.c:26:
/mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/bits/signal.h:39:8: note: previous definition of ‘struct esr_context’ struct esr_context {

In file included from nat/aarch64-sve-linux-ptrace.h:23:0,
from aarch64-linux-nat.c:35:
/mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/asm/sigcontext.h:113:8: error: redefinition of ‘struct extra_context’ struct extra_context {

In file included from /mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/signal.h:48:0,
from build-gnulib/import/signal.h:52,
from linux-nat.h:23,
from aarch64-linux-nat.c:26:
/mnt/1TB/ow/openwrt/staging_dir/toolchain-aarch64_cortex-a53_gcc-7.4.0_musl/include/bits/signal.h:43:8: note: previous definition of ‘struct extra_context’ struct extra_context {

aarch64-linux-nat.c: In function ‘void store_sveregs_to_thread(regcache*)’:
aarch64-linux-nat.c:419:59: error: invalid use of incomplete type ‘struct store_sveregs_to_thread(regcache*)::user_sve_header’ iovec.iov_len = 1)→size;

aarch64-linux-nat.c:419:28: note: forward declaration of ‘struct store_sveregs_to_thread(regcache)::user_sve_header’ iovec.iov_len = 2)→size;

Makefile:1622: recipe for target ‘aarch64-linux-nat.o’ failed

1) struct user_sve_header ) base.get (
2) struct user_sve_header *) base.get (
01.01.20192039Base systemBug ReportVery LowMediumSierra Wireless EM7565 not working with Linksys WRT3200...openwrt-18.06Unconfirmed Task Description

I have problems with Sierra Wireless EM7565 wireless module and USB 3.0 M.2 adapter. Device is detected correctly and works with TP-Link Archer C7 v2 which have older kernel version. I am using 18.06-SNAPSHOT r7405 version and kernel 4.14.82. I am connecting with QMI mode. I have tested also MBIM mode without success. 

I have verified connection using following command:

uqmi -d /dev/cdc-wdm0 –get-data-status –get-current-settings –get-capabilities –get-signal-info –get-serving-system “connected”

I have also tried changing RAW IP-mode. I have read following article:

https://techship.com/faq/how-to-step-by-step-set-up-a-data-connection-over-qmi-interface-using-qmicli-and-in-kernel-driver-qmi-wwan-in-linux/


01.01.20192038Base systemBug ReportVery LowLow[18.06.1] Installing package grep breaks /etc/preinitTrunkUnconfirmed Task Description

I receive this error during start-up:

/etc/preinit: line 1: grep: not found

After I have installed the ‘grep - 2.26-1’ package.

BusyBox has it’s grep applet installed in /bin/grep, and the grep package removes this and installs the full version in /usr/bin/grep. For whatever reason /etc/preinit cannot find /usr/bin/grep despite the path being set and including /usr/bin.

Removing the ‘grep - 2.26-1’ package allows the system to revert back to BusyBox grep and /etc/preinit no longer reports an error.

30.12.20182036Base systemBug ReportVery LowLowSeems there is noticeable memleak in trunk - brcm47xx -...TrunkUnconfirmed Task Description

I’ve gave a try to “trunk” build from ~25 DEC on WL500GPv1 (brcm47xx - legacy). It generally worked (except for swap). But it seems to have memleak. Haven’t happened in early versions.

To reproduce:
1) Install trunk on WL500GP V1. As non-standard difference I have ath9k card installed in minipci, therefore kmod-ath9k package is installed.
2) Login by ssh and look on “free” output (ofc line including buff/cache).

  1. I had about 16 MB of free RAM total with freshly booted firmware at this point (no luci, etc, just stock trunk package set + ath9k).

3) Let it run for a while without reboots. I ran it about 5 days.
4) Repeat step 2 and look free RAM again.

  1. At this point I had just 10 MB free RAM without obvious users of rather large 6MB chunk. Let’s remind, it inlcudes buffers/cache.

Result:
In 5 days about 6MB RAM gone to unknown use I failed to identify. It does not seems to be attributed to processes, ps gives nothing useful. I would surely spot 6MB-sized process but there was none.

Showing tasks 101 - 150 of 797 Page 3 of 16 - 1 - 2 - 3 - 4 - 5 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing