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
01.11.20181924Base systemBug ReportVery LowLowArcher C7 V4, Archer C7 V5, TL-WR841n-V13: wan/ lan led...openwrt-18.06Unconfirmed Task Description

with these devices, the LEDs light up permanently but do not flash when network traffic

Software versions: OpenWrt 18.06 - 4b4a6308e711e6fb614d4886a9887fac040a1d56

01.11.20181923KernelBug ReportVery LowMediumigb driver fails to probe i210 interfaces on x86-64 sin...openwrt-18.06Unconfirmed Task Description

We use OpenWrt 18.06 on the Lex 3I380NX which has a four-port Intel I210IT Ethernet interface.

Since OpenWrt updates to kernel version 4.14.77, the kernel fails to probe all but the first port logging instead of

Thu Nov  1 11:44:25 2018 kern.info kernel: [    7.023605] igb 0000:01:00.0: added PHC on eth0
Thu Nov  1 11:44:25 2018 kern.info kernel: [    7.023605] igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection
Thu Nov  1 11:44:25 2018 kern.info kernel: [    7.030852] igb 0000:01:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 4c:02:89:10:f9:49
Thu Nov  1 11:44:25 2018 kern.info kernel: [    7.038137] igb 0000:01:00.0: eth0: PBA No: 000300-000
Thu Nov  1 11:44:25 2018 kern.info kernel: [    7.043390] igb 0000:01:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
Thu Nov  1 11:44:25 2018 kern.warn kernel: [    7.281959] igb: probe of 0000:02:00.0 failed with error -2
Thu Nov  1 11:44:25 2018 kern.warn kernel: [    7.534335] igb: probe of 0000:03:00.0 failed with error -2
Thu Nov  1 11:44:25 2018 kern.warn kernel: [    7.791954] igb: probe of 0000:04:00.0 failed with error -2

We have built a vanilla upstream kernel 4.14.77 using the same configuration as the OpenWrt build and it does enable all four interfaces, so our guess is that some of the patches applied for OpenWrt broke when updating from 4.14.76.

01.11.20181922Base systemBug ReportVery LowHighBuilding on mac os 10.13.6 fails due to perl issues wit...TrunkUnconfirmed Task Description

Attempting to build latest OpenWrt firmware for NETGEAR R7800 (arm-openwrt-linux-musl) fails with Perl errors about dynamic module loading:

/Volumes/OpenWrt/NETGEAR_R7800/staging_dir/hostpkg/usr/bin/perl5.28.0 files/perlconfig.pl -Dowrt:target_cc='arm-openwrt-linux-muslgnueabi-gcc' -Dowrt:gccversion="7.3.0" -Dowrt:target_cross='arm-openwrt-linux-muslgnueabi-' -Dowrt:cflags='-O2 -pipe -mcpu=cortex-a9 -mfpu=vfp3 -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -mfloat-abi=hard -I/Volumes/OpenWrt/NETGEAR_R7800/staging_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/usr/include -I/Volumes/OpenWrt/NETGEAR_R7800/staging_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/include -I/Volumes/OpenWrt/NETGEAR_R7800/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-7.3.0_musl_eabi/usr/include -I/Volumes/OpenWrt/NETGEAR_R7800/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-7.3.0_musl_eabi/include/fortify -I/Volumes/OpenWrt/NETGEAR_R7800/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-7.3.0_musl_eabi/include' -Dowrt:ldflags='-L/Volumes/OpenWrt/NETGEAR_R7800/staging_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/usr/lib -L/Volumes/OpenWrt/NETGEAR_R7800/staging_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/lib -L/Volumes/OpenWrt/NETGEAR_R7800/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-7.3.0_musl_eabi/usr/lib -L/Volumes/OpenWrt/NETGEAR_R7800/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-7.3.0_musl_eabi/lib -znow -zrelro' -Dowrt:libc="musl" -Dowrt:ipv6=undef -Dowrt:threads=no -Dowrt:staging_dir='/Volumes/OpenWrt/NETGEAR_R7800/staging_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi' -Dowrt:host_perl_prefix='/Volumes/OpenWrt/NETGEAR_R7800/staging_dir/hostpkg/usr' files/version.config files/base.config files/arm.config files/architecture.config files/signal.config files/threads.config files/libc.config files/misc.config > /Volumes/OpenWrt/NETGEAR_R7800/build_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/perl/perl-5.28.0/config.sh
Can't load module List::Util, dynamic loading not available in this perl.
  (You may need to build a new perl executable which either supports
  dynamic loading or has the List::Util module statically linked into it.)
 at files/perlconfig.pl line 229.
Compilation failed in require at files/perlconfig.pl line 229.
BEGIN failed--compilation aborted at files/perlconfig.pl line 229.
make[3]: *** [/Volumes/OpenWrt/NETGEAR_R7800/build_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/perl/perl-5.28.0/.configured_68b329da9893e34099c7d8ad5cb9c940] Error 255
make[3]: Leaving directory `/Volumes/OpenWrt/NETGEAR_R7800/feeds/packages/lang/perl'
time: package/feeds/packages/perl/compile#0.25#0.13#0.66
make[2]: *** [package/feeds/packages/perl/compile] Error 2
make[2]: Leaving directory `/Volumes/OpenWrt/NETGEAR_R7800'
make[1]: *** [/Volumes/OpenWrt/NETGEAR_R7800/staging_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/stamp/.package_compile] Error 2
make[1]: Leaving directory `/Volumes/OpenWrt/NETGEAR_R7800'
make: *** [world] Error 2
31.10.20181920Base systemBug ReportVery LowLowath10k: pdev param 0 not supported by firmwareTrunkUnconfirmed Task Description

device: Archer C7 v2.0
OpenWrt revision: OpenWrt SNAPSHOT r8385-374e646

1 compile and flash
2 bring up the 5 GHz wifi interface
3 check the dmesg output
4 the wifi may or may not start when enabled

The CPU usage is pretty high (close to 80-90% used by sirq) when transferring 50-80 Mbps of data from the Internet. Packets are lost sometimes over the wifi and the wifi appears unstable overall. This packet loss doesn’t occur when pinging directly from the router.

The router is on a 5 GHz channel which is free.

I had to push the wifi on/off switch to get the wifi to work.

29.10.20181917Base systemBug ReportVery LowHighMT7621 hw offloading crashingTrunkUnconfirmed Task Description

I’m using the latest build OpenWrt 18.06.1 r7258-5eb055306f / LuCI openwrt-18.06 branch (git-18.284.42397-55ebe88)

With ZBT-WG3526 (16M), MediaTek MT7621 ver:1 eco:3.

Using HW offloading makes systems unstable after less than 24 hours.

I’ve tested it during several days. Now using SW offloading seems to be working ok.

I’ve posted traces here:

https://forum.openwrt.org/t/mt7621-offloading-reboots/24043

29.10.20181916Base systemBug ReportVery LowHighRouting/NAT Offloading not working with IPv6TrunkUnconfirmed Task Description

I’m using the latest build OpenWrt 18.06.1 r7258-5eb055306f / LuCI openwrt-18.06 branch (git-18.284.42397-55ebe88)

With ZBT-WG3526 (16M), MediaTek MT7621 ver:1 eco:3.

Trying hardware offloading, works well with IPv4, but in IPv6 it doesn’t work.

Tested with other MT7621 devices, such as Ubiquiti ER-X, with their own OS and it works, so clearly the SoC is allowing it, but OpenWRT is failing to properly enable it.

Same with CLAT/464XLAT, lw4o6 and other transition mechanism, the offloading is not working and it looks to me it should work the same.

29.10.20181915Base systemBug ReportVery LowLow/usr/lib/lua/luci/model/network.lua:203: attempt to ind...TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on
TP-Link Archer C7 v2

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

- Steps to reproduce
N/A

In the log I noticed:

12:04:01 uhttpd Failed to execute call dispatcher target for entry '/admin/network/wireless_status/radio0.network1,radio0.network2,radio1.network1,radio1.network2'.
12:04:01 uhttpd The called action terminated with an exception:
12:04:01 uhttpd /usr/lib/lua/luci/model/network.lua:203: attempt to index a nil value
12:04:01 uhttpd stack traceback:
12:04:01 uhttpd #011/usr/lib/lua/luci/model/network.lua:203: in function '_wifi_iwinfo_by_ifname'
12:04:01 uhttpd #011/usr/lib/lua/luci/model/network.lua:1649: in function '__init__'
12:04:01 uhttpd #011/usr/lib/lua/luci/util.lua:65: in function </usr/lib/lua/luci/util.lua:61>
12:04:01 uhttpd #011(tail call): ?
12:04:01 uhttpd #011/usr/lib/lua/luci/tools/status.lua:185: in function 'wifi_network'
12:04:01 uhttpd #011/usr/lib/lua/luci/controller/admin/network.lua:288: in function </usr/lib/lua/luci/controller/admin/network.lua:281>
12:04:01 uhttpd #011(tail call): ?


29.10.20181914Base systemBug ReportVery LowLowlua tonumber get wrong valueTrunkUnconfirmed Task Description

on x86_64
build base openwrt current master HEAD

problem:

lua -e ‘print(”42949672961111”+1)’ 1112
lua -e ‘print(”42949672951111”+1)’ 42949672951112

lua tonumber get wrong.

problem not happens on arm/mips but only x86_64
x86_generic not tested

28.10.20181912Base systemBug ReportVery LowLowRaspberry pi's cannot connect via WiFi to OpenWrt route...TrunkUnconfirmed Task Description

- Device problem occurs on: DLINK860L

- Software versions of OpenWrt/LEDE release, packages, etc.:
OpenWrt 18.06.1 r7258-5eb055306f / LuCI openwrt-18.06 branch (git-18.228.31946-f64b152)
dnsmasq 2.80test3-1
Rpi3: Linux raspberrypi 4.14.78-v7+ #1156 SMP 2018 armv7l GNU/Linux

- Steps to reproduce:
Both the rpi zero-w and the raspberry pi 3 cannot properly connect to wlan1 (2.4GHz).
The DHCP negotiation seems to fail. This looks similar issue as reported in FS#1418.

Logs:
Openwrt syslog, try to connect RPI3 via wlan: Sun Oct 21:07:25 2018 daemon.info hostapd: wlan1: STA b8:ff:ff:ff:ff:01 IEEE 802.11: authenticated
Sun Oct 21:07:25 2018 daemon.info hostapd: wlan1: STA b8:ff:ff:ff:ff:01 IEEE 802.11: associated (aid 1)
Sun Oct 21:07:25 2018 daemon.notice hostapd: wlan1: AP-STA-CONNECTED b8:ff:ff:ff:ff:01
Sun Oct 21:07:25 2018 daemon.info hostapd: wlan1: STA b8:ff:ff:ff:ff:01 WPA: pairwise key handshake completed (RSN) Sun Oct 21:07:28 2018 daemon.info dnsmasq-dhcp[9555]: DHCPDISCOVER(br-lan) b8:ff:ff:ff:ff:01
Sun Oct 21:07:28 2018 daemon.info dnsmasq-dhcp[9555]: DHCPOFFER(br-lan) 192.168.1.200 b8:ff:ff:ff:ff:01
Sun Oct 21:07:29 2018 daemon.info dnsmasq-dhcp[9555]: DHCPDISCOVER(br-lan) b8:ff:ff:ff:ff:01
Sun Oct 21:07:29 2018 daemon.info dnsmasq-dhcp[9555]: DHCPOFFER(br-lan) 192.168.1.200 b8:ff:ff:ff:ff:01
Sun Oct 21:07:37 2018 daemon.info dnsmasq-dhcp[9555]: DHCPDISCOVER(br-lan) b8:ff:ff:ff:ff:01
Sun Oct 21:07:37 2018 daemon.info dnsmasq-dhcp[9555]: DHCPOFFER(br-lan) 192.168.1.200 b8:ff:ff:ff:ff:01
Sun Oct 21:07:53 2018 daemon.info dnsmasq-dhcp[9555]: DHCPDISCOVER(br-lan) b8:ff:ff:ff:ff:01
Sun Oct 21:07:53 2018 daemon.info dnsmasq-dhcp[9555]: DHCPOFFER(br-lan) 192.168.1.200 b8:ff:ff:ff:ff:01
Sun Oct 21:08:28 2018 daemon.info dnsmasq-dhcp[9555]: DHCPDISCOVER(br-lan) b8:ff:ff:ff:ff:01
Sun Oct 21:08:28 2018 daemon.info dnsmasq-dhcp[9555]: DHCPOFFER(br-lan) 192.168.1.200 b8:ff:ff:ff:ff:01
Sun Oct 21:09:32 2018 daemon.info dnsmasq-dhcp[9555]: DHCPDISCOVER(br-lan) b8:ff:ff:ff:ff:01
Sun Oct 21:09:32 2018 daemon.info dnsmasq-dhcp[9555]: DHCPOFFER(br-lan) 192.168.1.200 b8:ff:ff:ff:ff:01
Sun Oct 21:10:36 2018 daemon.info dnsmasq-dhcp[9555]: DHCPDISCOVER(br-lan) b8:ff:ff:ff:ff:01
Sun Oct 21:10:36 2018 daemon.info dnsmasq-dhcp[9555]: DHCPOFFER(br-lan) 192.168.1.200 b8:ff:ff:ff:ff:01
But never an DHCPACK

All fine if I connect the ethernet cable:
Openwrt syslog, try to connect RPI3 via eth cable:
Sun Oct 21:11:38 2018 daemon.info dnsmasq-dhcp[9555]: DHCPDISCOVER(br-lan) b8:ff:ff:ff:ff:02
Sun Oct 21:11:38 2018 daemon.info dnsmasq-dhcp[9555]: DHCPOFFER(br-lan) 192.168.1.122 b8:ff:ff:ff:ff:02
Sun Oct 21:11:41 2018 daemon.info dnsmasq-dhcp[9555]: DHCPDISCOVER(br-lan) b8:ff:ff:ff:ff:02
Sun Oct 21:11:41 2018 daemon.info dnsmasq-dhcp[9555]: DHCPOFFER(br-lan) 192.168.1.122 b8:ff:ff:ff:ff:02
Sun Oct 21:11:41 2018 daemon.info dnsmasq-dhcp[9555]: DHCPREQUEST(br-lan) 192.168.1.122 b8:ff:ff:ff:ff:02
Sun Oct 21:11:41 2018 daemon.info dnsmasq-dhcp[9555]: DHCPACK(br-lan) 192.168.1.122 b8:ff:ff:ff:ff:02 raspberrypi

Here the Rpi side, trying to connect via WiFi (syslog):
Oct 16:41:00 raspberrypi dhcpcd[330]: wlan0: carrier acquired
Oct 16:41:00 raspberrypi dhcpcd[330]: DUID 00:01:00:01:....................
Oct 16:41:00 raspberrypi dhcpcd[330]: wlan0: IAID eb:...............
Oct 16:41:00 raspberrypi dhcpcd[330]: wlan0: adding address fe80::............
Oct 16:41:00 raspberrypi dhcpcd[330]: wlan0: soliciting a DHCP lease
Oct 16:41:00 raspberrypi dhcpcd[330]: wlan0: soliciting an IPv6 router
Oct 16:41:05 raspberrypi dhcpcd[330]: wlan0: probing for an IPv4LL address
Oct 16:41:11 raspberrypi dhcpcd[330]: wlan0: using IPv4LL address 169.254.141.76 Oct 16:41:11 raspberrypi dhcpcd[330]: wlan0: adding route to 169.254.0.0/16
Oct 16:41:11 raspberrypi dhcpcd[330]: wlan0: adding default route
Oct 16:41:13 raspberrypi dhcpcd[330]: wlan0: no IPv6 Routers available

Log from RPI3:

27.10.20181911Base systemBug ReportVery LowMediumXrx200/lantiq: if connected w/ USB hub reading from ftd...openwrt-18.06Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on
lantiq, xrx200
- Software versions of OpenWrt/LEDE release, packages, etc.
18.01
- Steps to reproduce
see
https://forum.openwrt.org/t/xrx200-lantiq-if-connected-w-usb-hub-reading-from-ftdi-arduino-nano-hangs-system/23858

 


27.10.20181910Base systemFeature RequestVery LowLowAdd Xiaomi Mi Router R3 support to base systemTrunkUnconfirmed Task Description

Please add this device. Files are implemented from Shibajee Roy.
ramips: add Xiaomi Mi Router R3 support


27.10.20181909Base systemBug ReportVery LowLowfailsafe packet sent to udp/4919 on WAN port does not m...TrunkUnconfirmed Task Description

- Device problem occurs on

Device tested: Archer C7 v2

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

Tested on Chaos Calmer 15.06, and on 18.06

- Steps to reproduce

 

packet sniff WAN port during power on
src MAC address of failsafe broadcast notification packet (sent to udp/4919) has a different MAC address than the final configured default MAC address for the WAN port after boot.

This causes issues with some ARRIS cable modem devices with a configured max client count of 1.

- Observed values

src MAC address of broadcast failsafe packet on the WAN port matches the LAN switch MAC.

- Suggested possible next actions:

1. Use the WAN switch MAC address for the broadcast packet, on all interfaces, which should be safe.
2. If 1. is infeasible, provide a /etc/config/... setting that disables the sending of the udp/4919 packet – which is not critical to experienced operators.

26.10.20181908FlysprayFeature RequestVery LowMediumEditing an Existing Task, At Least the Tags and Title, ...TrunkUnconfirmed Task Description

When posting a feature request for the NETGEAR DM200 on OpenWRT, I have tagged it incorrectly (adding commas in between tags, since I am used to doing this on other systems similar to Flyspray), and then I saw that I cannot edit my own post.
Also, I wanted to fix the title (capitalizing letters where necessary, and likewise, the opposite).

Can editing existing tasks one had authored be possible in the future, or at least improving the tagging system, to enable fixing such mistakes?

26.10.20181907Base systemFeature RequestVery LowLowPossibility of unlocking Gigabit speeds on the Netgear ...TrunkUnconfirmed Task Description

I was wondering if it would be possible to add Gigabit networking to the NETGEAR DM200 by modding the physical connectors, since from what I have seen, the chipset (Lantiq VRX220) supports Gigabit speeds, and there is a firmware which supports such speeds, however the DM200 officially supports only up to 100Mbts speeds.

When taking a look at my DM200’s board, I have noticed that the Ethernet connector only utilizes 4 out of the 8 pins, while the modem connector only utilizes 2 out of the pins, so I was thinking that it may be possible to solder the other pins (as required, of course), we may be able to “upgrade” the DM200 to Gigabit.

If the DM200 can boot properly with the Gigabit-enabled firmware, and this mod is undertaken, does anyone think that anything may come out of this?

25.10.20181906PackagesBug ReportVery LowLowStatic lease doesn't work sometimesTrunkUnconfirmed Task Description

Device: Xiaomi mi wifi mini
OpenWRT: SNAPSHOT r8377-70315fe144

If i reboot router or turn on it at the same time with PC static lease doesn’t work.

cat /etc/config/dhcp

config dnsmasq
        option domainneeded '1'
        option boguspriv '1'
        option filterwin2k '1'
        option localise_queries '1'
        option rebind_protection '1'
        option local '/[REDACTED]/'
        option domain '[REDACTED]'
        option expandhosts '1'
        option authoritative '1'
        option leasefile '/tmp/dhcp.leases'
        option nonwildcard '1'
        option localservice '0'
        option noresolv '1'
        list server '::1#5453'
        list server '127.0.0.1#5453'
        list rebind_domain '/[REDACTED]/'
        list server '[REDACTED]'
        option cachesize '1024'

config dhcp 'lan'
        option interface 'lan'
        option start '100'
        option limit '150'
        option leasetime '24h'
        option dhcpv6 'server'
        option ra 'server'

config dhcp 'wan'
        option interface 'wan'
        option ignore '1'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'
        option loglevel '4'

config srvhost
[REDACTED]

config host
        option name 'wks1'
        option mac '60:a4:4c:ce:65:ac'
        option ip '172.16.9.10'

config domain
[REDACTED]

logread -e dnsmasq-dhcp

Thu Oct 25 07:43:05 2018 daemon.info dnsmasq-dhcp[1780]: DHCP, IP range 172.16.9.100 -- 172.16.9.249, lease time 1d
Thu Oct 25 07:43:19 2018 daemon.info dnsmasq-dhcp[1780]: DHCPDISCOVER(br-lan) 172.16.9.10 60:a4:4c:ce:65:ac
Thu Oct 25 07:43:19 2018 daemon.info dnsmasq-dhcp[1780]: DHCPOFFER(br-lan) 172.16.9.211 60:a4:4c:ce:65:ac
Thu Oct 25 07:43:19 2018 daemon.info dnsmasq-dhcp[1780]: DHCPREQUEST(br-lan) 172.16.9.211 60:a4:4c:ce:65:ac
Thu Oct 25 07:43:19 2018 daemon.info dnsmasq-dhcp[1780]: DHCPACK(br-lan) 172.16.9.211 60:a4:4c:ce:65:ac wks1

config.seed

CONFIG_TARGET_ramips=y
CONFIG_TARGET_ramips_mt7620=y
CONFIG_TARGET_ramips_mt7620_DEVICE_miwifi-mini=y
CONFIG_GETDNS_ENABLE_STUB_ONLY=y
CONFIG_LIBCURL_COOKIES=y
CONFIG_LIBCURL_FILE=y
CONFIG_LIBCURL_FTP=y
CONFIG_LIBCURL_HTTP=y
CONFIG_LIBCURL_NO_SMB="!"
CONFIG_LIBCURL_OPENSSL=y
CONFIG_LIBCURL_PROXY=y
CONFIG_OPENSSL_WITH_DEPRECATED=y
CONFIG_OPENSSL_WITH_EC=y
CONFIG_OPENSSL_WITH_NPN=y
CONFIG_OPENSSL_WITH_PSK=y
CONFIG_OPENSSL_WITH_SRP=y
CONFIG_PACKAGE_bind-dig=y
CONFIG_PACKAGE_bind-libs=y
CONFIG_PACKAGE_ca-bundle=y
CONFIG_PACKAGE_ca-certificates=y
CONFIG_PACKAGE_curl=y
CONFIG_PACKAGE_ddns-scripts=y
CONFIG_PACKAGE_ddns-scripts_cloudflare.com-v4=y
# CONFIG_PACKAGE_dnsmasq is not set
CONFIG_PACKAGE_dnsmasq-full=y
CONFIG_PACKAGE_dnsmasq_full_auth=y
CONFIG_PACKAGE_dnsmasq_full_conntrack=y
CONFIG_PACKAGE_dnsmasq_full_dhcp=y
CONFIG_PACKAGE_dnsmasq_full_dhcpv6=y
CONFIG_PACKAGE_dnsmasq_full_dnssec=y
CONFIG_PACKAGE_dnsmasq_full_ipset=y
CONFIG_PACKAGE_dnsmasq_full_noid=y
CONFIG_PACKAGE_getdns=y
CONFIG_PACKAGE_gre=y
CONFIG_PACKAGE_ip-full=y
CONFIG_PACKAGE_ipset=y
CONFIG_PACKAGE_kmod-gre=y
CONFIG_PACKAGE_kmod-gre6=y
CONFIG_PACKAGE_kmod-ip6-tunnel=y
CONFIG_PACKAGE_kmod-ipt-ipset=y
CONFIG_PACKAGE_kmod-iptunnel=y
CONFIG_PACKAGE_kmod-iptunnel6=y
CONFIG_PACKAGE_kmod-nf-conntrack-netlink=y
CONFIG_PACKAGE_kmod-nfnetlink=y
CONFIG_PACKAGE_kmod-udptunnel4=y
CONFIG_PACKAGE_kmod-udptunnel6=y
CONFIG_PACKAGE_kmod-wireguard=y
CONFIG_PACKAGE_libcurl=y
CONFIG_PACKAGE_libgmp=y
CONFIG_PACKAGE_libipset=y
CONFIG_PACKAGE_libmnl=y
CONFIG_PACKAGE_libnetfilter-conntrack=y
CONFIG_PACKAGE_libnettle=y
CONFIG_PACKAGE_libnfnetlink=y
CONFIG_PACKAGE_libopenssl=y
CONFIG_PACKAGE_libyaml=y
CONFIG_PACKAGE_resolveip=y
CONFIG_PACKAGE_stubby=y
CONFIG_PACKAGE_wireguard=y
CONFIG_PACKAGE_wireguard-tools=y
CONFIG_PACKAGE_zlib=y
22.10.20181905KernelBug ReportVery LowMediumKernel bug: brcm47xx/mips74k reboots after: bgmac_bcma ...openwrt-18.06Unconfirmed Task Description

Device

OpenWrt version

Stable Release OpenWrt 18.06.1

# cat /etc/openwrt_release 
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='18.06.1'
DISTRIB_REVISION='r7258-5eb055306f'
DISTRIB_TARGET='brcm47xx/mips74k'
DISTRIB_ARCH='mipsel_74kc'
DISTRIB_DESCRIPTION='OpenWrt 18.06.1 r7258-5eb055306f'
DISTRIB_TAINTS=''
Linux OpenWrt 4.14.63 #0 Wed Aug 15 20:42:39 2018 mips GNU/Linux

What does it do that it should not do

Sometimes the router hangup and reboots.
This can happen several times a day.
The log contains entries:

Oct 22 12:50:50 OpenWrt kernel: [249137.210802] bgmac_bcma bcma0:1 eth0: Found oversized packet at slot 56, DMA issue!
Oct 22 12:50:50 OpenWrt kernel: [249137.254221] bgmac_bcma bcma0:1 eth0: Found oversized packet at slot 121, DMA issue!
Oct 22 12:50:50 OpenWrt kernel: [249137.295788] bgmac_bcma bcma0:1 eth0: Found oversized packet at slot 314, DMA issue!
Oct 22 12:50:50 OpenWrt kernel: [249137.320500] bgmac_bcma bcma0:1 eth0: Found oversized packet at slot 509, DMA issue!

Few entries from crashlog:

<3>[249137.254221] bgmac_bcma bcma0:1 eth0: Found oversized packet at slot 121, DMA issue!
<3>[249137.295788] bgmac_bcma bcma0:1 eth0: Found oversized packet at slot 314, DMA issue!
<3>[249137.320500] bgmac_bcma bcma0:1 eth0: Found oversized packet at slot 509, DMA issue!
<0>[249137.334933] skbuff: skb_over_panic: text:80238000 len:1753 put:1753 head:86862a80 data:86862a80 tail:0x86863159 end:0x868630e0 dev:<NULL>
<4>[249137.347856] Kernel bug detected[#1]:
<4>[249137.351653] CPU: 0 PID: 7 Comm: ksoftirqd/0 Tainted: G        W       4.14.63 #0

Full crashlog attached.

Steps to reproduce

To reproduce the bug I try to fill the nf_conntrack table with thousands of connections.

Several seconds it was kept filled:

net.netfilter.nf_conntrack_max = 16384
net.netfilter.nf_conntrack_count = 16383

log:

nf_conntrack: nf_conntrack: table full, dropping packet
nf_conntrack: nf_conntrack: table full, dropping packet
...

then several messages:

bgmac_bcma bcma0:1 eth0: Found oversized packet at slot 262, DMA issue!
...

and the router rebooted.

Another way to reproduce...

...same error messages in the log - run bandwidth test http://www.speedtest.net

...
Oct 22 14:46:08 OpenWrt kernel: [ 6908.757065] bgmac_bcma bcma0:1 eth0: Found oversized packet at slot 118, DMA issue!
Oct 22 14:46:08 OpenWrt kernel: [ 6908.770969] bgmac_bcma bcma0:1 eth0: Found oversized packet at slot 183, DMA issue!
Oct 22 14:46:08 OpenWrt kernel: [ 6908.800488] bgmac_bcma bcma0:1 eth0: Found oversized packet at slot 442, DMA issue!

What I have already done to workaround/fix the problem

I try to decrease value of the nf_conntrack_tcp_timeout_established
from

net.netfilter.nf_conntrack_tcp_timeout_established = 7440

to

net.netfilter.nf_conntrack_tcp_timeout_established = 900

typical value:

net.netfilter.nf_conntrack_count = 5130 (...7000)

but it still reboots sometimes.

Additional info

  • Wireless disabled
  • IPv6 disabled
  • VLANs used
22.10.20181904Base systemBug ReportVery LowMediumSD-reader doesn't work on GL.iNet GL-AR750openwrt-18.06Unconfirmed Task Description

Hello,

I’m using GL.iNet GL-AR750 and OpenWrt 18.06.1 installed using official sysupgrade file:

```
openwrt-18.06.1-ar71xx-generic-gl-ar750-squashfs-sysupgrade.bin
```

The device has a build-in SD-reader which as I understand is based on GL857L chip. The OS doesn’t seem to see the SD-reader. When I insert a SD-card nothing is printed to dmesg, device doesn’t appear in /dev.

The following packages are installed:

```
opkg update
opkg install kmod-scsi-core kmod-scsi-generic \

kmod-usb-core kmod-usb-ohci kmod-usb-uhci kmod-usb2 kmod-usb3 \
kmod-fs-msdos kmod-fs-vfat kmod-fs-ext4 usbutils \
kmod-usb-storage kmod-usb-storage-extras block-mount

```

The device has a USB port as well and it works with USB flash drives as expected.

It could be a bug (from user’s perspective, SD-reader supposed to work) or lack of the documentation (I couldn’t figure out how to make it work, maybe I just need some extra dependencies, community forum didn’t help either).

20.10.20181903Base systemBug ReportVery LowMediumHotplug event triggered too earlyopenwrt-18.06Unconfirmed Task Description

DEVICE: TP-Link Archer C7 v2
SYSTEM: OpenWRT 18.06.1
PACKAGES: base + luci, ca-certificates, ddns-scripts_no-ip_com, luci-app-ddns, wget, ip, ppp, ppp-mod-pppoe, vim, nano, usbutils, usb-modeswitch, kmod-usb-core,

        kmod-usb-serial, kmod-usb-serial-option, kmod-usb-net-cdc-ncm, kmod-usb-net-huawei-cdc-ncm, picocom, sqm-scripts, luci-app-sqm, kmod-ledtrig-heartbeat, htop

If the USB Device (HUAWEI E3372 LTE Stick) is left connected to the router during a reboot/boot, the hotplug event is triggered too early and the device has not yet all interfaces mapped in the /dev directory.
More specifically, my hotplug script wants to find the name of the interface (which is “ttyUSB0” in my case) by looking at the $DEVPATH directory, but during the hotplug script execution the link does not yet exist. Adding a “sleep” inside the script does not help, but executing a subscript via “exec script &” shows that after 3 seconds the link is created.
Attached is a file showing the directory listing of $DEVPATH during the hotplug event, and 3 seconds after the hotplug event.

Note that the hotplug script works as intended during actual hotplugging. This bug only presents itself during boot/reboot.
Also note that this was working on OpenWRT 15.05.1 (same Router, Stick and hotplug script)

19.10.20181900Base systemBug ReportVery LowLowsysupgrade cause trouble by package removalopenwrt-18.06Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on: TP-Link Archer C7 V2
- Software versions: Start with 18.06, upgrade to 18.06.1

- Steps to reproduce

1. Secure luci access with luci-ssl module and disable plain http access. While uograding the luci-ssl module will be removed, so after upgrade there is no login possible. Method here under Web-UI: https://wiki.openwrt.org/doc/howto/secure.access

2. Use an dsl-lite link for this, run the sysupgrade. While sysupgrade the ds-lite module is removed, so after reboot you only have IPv6 access. Thanks god openwrt is able to upgrade and install the ds-lite package over IPv6.

For me this is not the idea og "keep settings", require base modules should be kept or upgraded in the same procedure to keep base functionality.

 


19.10.20181899KernelBug ReportVery LowMediumKernel warning with Lantiq XRX200 TD-W8970 (cfg80211)openwrt-18.06Unconfirmed Task Description

[ 13.106643] ————[ cut here ]———— [ 13.109875] WARNING: CPU: 0 PID: 174 at backports-2017-11-01/net/wireless/reg.c:894 0x82c4848c [cfg80211@82c40000+0x31a40]
[ 13.120969] Modules linked in: ath9k ath9k_common ath9k_hw ath pppoe 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_CT wireguard pppox ppp_async nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack ltq_deu_vr9 iptable_mangle iptable_filter ip_tables crc_ccitt compat drv_dsl_cpe_api ledtrig_usbport drv_mei_cpe ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables pppoatm ppp_generic slhc ip6_udp_tunnel udp_tunnel br2684 atm drv_ifxos dwc2 gpio_button_hotplug
[ 13.189220] CPU: 0 PID: 174 Comm: kworker/0:1 Not tainted 4.9.120 #0
[ 13.195578] Workqueue: events 0x80277b54
[ 13.199463] Stack : 839b3a80 80520000 804bab98 82c6f6c4 00000000 00000000 00000000 00000000
[ 13.207816] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 13.216172] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 13.224528] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 13.232884] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 13.241239] ...
[ 13.243677] Call Trace:
[ 13.245975] [<8000fdd0>] 0x8000fdd0
[ 13.249438] [<8000fdd0>] 0x8000fdd0
[ 13.252918] [<801f8ec8>] 0x801f8ec8
[ 13.256445] [<82c4848c>] 0x82c4848c [cfg80211@82c40000+0x31a40]
[ 13.262319] [<8002ec6c>] 0x8002ec6c
[ 13.265817] [<82c4848c>] 0x82c4848c [cfg80211@82c40000+0x31a40]
[ 13.271735] [<8002ed08>] 0x8002ed08
[ 13.275217] [<82c4848c>] 0x82c4848c [cfg80211@82c40000+0x31a40]
[ 13.281123] [<80277b94>] 0x80277b94
[ 13.284616] [<80044c70>] 0x80044c70
[ 13.288088] [<80045b00>] 0x80045b00
[ 13.291565] [<800457c4>] 0x800457c4
[ 13.295048] [<800457c4>] 0x800457c4
[ 13.298529] [<80050000>] 0×80050000 [ 13.302002] [<8004aa60>] 0x8004aa60
[ 13.305489] [<8004ab78>] 0x8004ab78
[ 13.308978] [<8004aa60>] 0x8004aa60
[ 13.312455] [<8000a4d8>] 0x8000a4d8
[ 13.315943]
[ 13.317487] —[ end trace 918bdca9a01843a6 ]—

16.10.20181898Base systemBug ReportVery LowHighArcher C7 V2- AR71XX - Could not find PHY for device '...TrunkWaiting on reporter Task Description

Supply the following if possible:
- Archer C7 V2- AR71XX
- OpenWrt SNAPSHOT r8328-39e5e17045
- Clean Build and Boot

 

Get the following messages at bootup and the 5Ghz Radio will not come up.

Tue Oct 16 06:32:32 2018 daemon.notice netifd: radio0 (3767): Could not find PHY for device ‘radio0’ Tue Oct 16 06:32:32 2018 daemon.notice netifd: radio0 (3798): WARNING: Variable ‘data’ does not exist or is not an array/object

The 2.4Ghz Radio starts just fine.

I tried deleting the config file and doing

wifi config

But that had no effect only finding the the 2.4Ghz Radio. This was working before upgrading to the latest snapshot from base 18.06.


16.10.20181897Base systemBug ReportVery LowLowMikrotik SXT Lite 2: installation fails using sysupgrad...openwrt-18.06Unconfirmed Task Description

Tested using OpenWRT 18.06.1 on Mikrotik SXT Lite 2. This device is listed as supported on the wiki.

OpenWRT boots fine over netboot (DHCP/TFTP).
But when trying to install permanently (to flash memory) using sysupgrade, there is the following error message:

Device unknown not supported by this image
Supported devices: rb-750-r2 rb-750up-r2 rb-750p-pbr2 rb-911-2hn rb-911-5hn rb-941-2nd rb-951ui-2nd rb-952ui-5ac2nd rb-962uigs-5hact2hnt rb-lhg-5nd rb-map-2nd rb-mapl-2nd rb-wap-2nd
Image check ‘fwtool_check_image’ failed.

I am using the following files:

network boot: http://downloads.openwrt.org/releases/18.06.1/targets/ar71xx/mikrotik/openwrt-18.06.1-ar71xx-mikrotik-vmlinux-initramfs.elf sysupgrade: http://downloads.openwrt.org/releases/18.06.1/targets/ar71xx/mikrotik/openwrt-18.06.1-ar71xx-mikrotik-rb-nor-flash-16M-squashfs-sysupgrade.bin

This device has a 16 MiB NOR flash. By looking at the code (target/linux/ar71xx/files/arch/mips/ath79/mach-rbsxtlite.c), it seems we expect NAND flash instead.

15.10.20181896Base systemBug ReportVery LowLowmwifiex crashes when binding to an instance TrunkUnconfirmed Task Description

ACM3200 radio2 crashes when performing a client binding to an existing AP.

First seeing this:
[ 16.871856] mwifiex_sdio mmc0:0001:1: WLAN FW already running! Skip FW dnld
[ 16.878853] mwifiex_sdio mmc0:0001:1: WLAN FW is active
[ 16.908052] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0×242 error, result=0×2 [ 16.915055] mwifiex_sdio mmc0:0001:1: mwifiex_process_cmdresp: cmd 0×242 failed during initialization
[ 16.933559] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (15.68.7.p71)
[ 16.941621] mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (15.68.7.p71)

Then seeing this when binding via luci:
[ 1372.420128] mwifiex_sdio mmc0:0001:1: mwifiex_cmd_timeout_func: Timeout cmd id = 0×20, act = 0xc
[ 1372.428963] mwifiex_sdio mmc0:0001:1: num_data_h2c_failure = 0
[ 1372.434829] mwifiex_sdio mmc0:0001:1: num_cmd_h2c_failure = 0
[ 1372.440609] mwifiex_sdio mmc0:0001:1: is_cmd_timedout = 1
[ 1372.446034] mwifiex_sdio mmc0:0001:1: num_tx_timeout = 0
[ 1372.451381] mwifiex_sdio mmc0:0001:1: last_cmd_index = 2
[ 1372.456718] mwifiex_sdio mmc0:0001:1: last_cmd_id: 20 00 20 00 20 00 20 00 20 00
[ 1372.464154] mwifiex_sdio mmc0:0001:1: last_cmd_act: 0c 00 0c 00 0c 00 0c 00 0c 00
[ 1372.471682] mwifiex_sdio mmc0:0001:1: last_cmd_resp_index = 1
[ 1372.477455] mwifiex_sdio mmc0:0001:1: last_cmd_resp_id: 20 80 20 80 20 80 20 80 20 80
[ 1372.485323] mwifiex_sdio mmc0:0001:1: last_event_index = 1
[ 1372.490838] mwifiex_sdio mmc0:0001:1: last_event: 0a 00 65 00 0b 00 0a 00 0b 00
[ 1372.498182] mwifiex_sdio mmc0:0001:1: data_sent=0 cmd_sent=1
[ 1372.503872] mwifiex_sdio mmc0:0001:1: ps_mode=0 ps_state=0
[ 1372.511519] mwifiex_sdio mmc0:0001:1:

mwifiex driverinfo dump start

[ 1372.519822] mwifiex_sdio mmc0:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (15.68.7.p71)
[ 1372.527929] mwifiex_sdio mmc0:0001:1: SDIO register dump start
[ 1372.534101] mwifiex_sdio mmc0:0001:1: SDIO Func0 (0×0-0×9): 43 03 06 06 07 00 00 02 03 00
[ 1372.543252] mwifiex_sdio mmc0:0001:1: SDIO Func1 (0×10-0×17): 00 00 00 00 ff ff 00 00
[ 1372.551865] mwifiex_sdio mmc0:0001:1: SDIO Func1: (0×8) c3 (0×58) 00 (0x5c) 08 (0x5d) 00 (0×60) 07 (0×61) 0c (0×62) 00 (0×64) 10 (0×65) 00 (0×66) 00 (0×68) 00 (0×69) 00 (0x6a) 00
[ 1372.568108] mwifiex_sdio mmc0:0001:1: SDIO Func1 (0×90-0x9a): dc fe 77 00 9b 00 00 a6 a6 02 00
[ 1372.637288] mwifiex_sdio mmc0:0001:1: PREP_CMD: FW is in bad state
[ 1372.677051] mwifiex_sdio mmc0:0001:1: SDIO Func1 (0×90-0x9a): dc fe 83 00 a7 00 00 a6 a6 02 00
[ 1372.685860] mwifiex_sdio mmc0:0001:1: SDIO register dump end
[ 1372.691588] mwifiex_sdio mmc0:0001:1:

mwifiex driverinfo dump end

[ 1372.698315] mwifiex_sdio mmc0:0001:1: == mwifiex dump information to /sys/class/devcoredump start
[ 1372.707364] mwifiex_sdio mmc0:0001:1: == mwifiex dump information to /sys/class/devcoredump end
[ 1372.716312] mwifiex_sdio mmc0:0001:1: info: shutdown mwifiex...
[ 1372.782493] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
[ 1372.788543] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
[ 1372.830702] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
[ 1373.024962] mwifiex_sdio mmc0:0001:1: WLAN FW already running! Skip FW dnld
[ 1373.031994] mwifiex_sdio mmc0:0001:1: WLAN FW is active
[ 1377.910961] ieee80211 phy1: staid 1 deleted
[ 1381.911761] ieee80211 phy1: staid 1 deleted
[ 1383.304056] mwifiex_sdio mmc0:0001:1: mwifiex_cmd_timeout_func: Timeout cmd id = 0xa9, act = 0×0 [ 1383.312892] mwifiex_sdio mmc0:0001:1: num_data_h2c_failure = 0
[ 1383.318759] mwifiex_sdio mmc0:0001:1: num_cmd_h2c_failure = 0
[ 1383.324548] mwifiex_sdio mmc0:0001:1: is_cmd_timedout = 1
[ 1383.329975] mwifiex_sdio mmc0:0001:1: num_tx_timeout = 0
[ 1383.335322] mwifiex_sdio mmc0:0001:1: last_cmd_index = 3
[ 1383.340666] mwifiex_sdio mmc0:0001:1: last_cmd_id: 20 00 20 00 20 00 a9 00 20 00
[ 1383.348103] mwifiex_sdio mmc0:0001:1: last_cmd_act: 0c 00 0c 00 0c 00 00 00 0c 00
[ 1383.355625] mwifiex_sdio mmc0:0001:1: last_cmd_resp_index = 1
[ 1383.361402] mwifiex_sdio mmc0:0001:1: last_cmd_resp_id: 20 80 20 80 20 80 20 80 20 80
[ 1383.369279] mwifiex_sdio mmc0:0001:1: last_event_index = 2
[ 1383.374800] mwifiex_sdio mmc0:0001:1: last_event: 0a 00 65 00 0b 00 0a 00 0b 00
[ 1383.382151] mwifiex_sdio mmc0:0001:1: data_sent=1 cmd_sent=1
[ 1383.387845] mwifiex_sdio mmc0:0001:1: ps_mode=0 ps_state=0
[ 1383.393731] mwifiex_sdio mmc0:0001:1: info: _mwifiex_fw_dpc: unregister device

Once in this state .. radio2 goes complete offline.

 


13.10.20181893Base systemBug ReportVery LowHighRouting/NAT Offloading now working with VoIP/IPTV VLANsTrunkUnconfirmed Task Description

I’m using the latest build OpenWrt 18.06.1 r7258-5eb055306f / LuCI openwrt-18.06 branch (git-18.284.42397-55ebe88)

With ZBT-WG3526 (16M), MediaTek MT7621 ver:1 eco:3.

I’ve VLANs for VoIP and IPTV.

If I enable Routing/NAT Offloading (tried both options (software and hardware), it looks that this feature doesn’t allows the VoIP and IPTV traffic to work as it was doing previously.+

I know this is experimental and may be still needs some more testing, etc., but I just wanted to let the developers know about this issue, in case, they haven’t realized it.

11.10.20181890Base systemBug ReportVery LowLowath10k wifi sometimes failingTrunkUnconfirmed Task Description

I thought I had this tackeled with a previous build, but problems still exist. With this bug I have some more log info.

Device problem occurs on: TP-Link Archer C7 v2
Software versions of OpenWrt/LEDE release, packages, etc.: OpenWrt SNAPSHOT, r8284-212aa33226
Steps to reproduce:
- Create a build with ath10k driver and firmware, not ath10k-ct
- Setup an AP
- Connect and disconnect some stations
- Wait a few days
- Ath10k wifi fails with the log below:

Thu Oct 11 09:40:31 2018 daemon.info hostapd: wlan0: STA e0:ac:cb:f2:c6:ab WPA: group key handshake completed (RSN)
Thu Oct 11 09:40:31 2018 daemon.info hostapd: wlan0: STA c8:1e:e7:0f:44:8e WPA: group key handshake completed (RSN)
Thu Oct 11 09:40:35 2018 daemon.info hostapd: wlan0: STA d4:a3:3d:22:0d:f4 WPA: group key handshake failed (RSN) after 4 tries
Thu Oct 11 09:40:35 2018 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED d4:a3:3d:22:0d:f4
Thu Oct 11 09:40:39 2018 kern.warn kernel: [136848.995633] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:40:48 2018 kern.warn kernel: [136858.115571] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 0: -11
Thu Oct 11 09:40:51 2018 kern.warn kernel: [136861.155566] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 0: -11
Thu Oct 11 09:40:57 2018 daemon.info dnsmasq-dhcp[2076]: DHCPDISCOVER(br-lan) e0:ac:cb:f2:c6:ab
Thu Oct 11 09:40:57 2018 daemon.info dnsmasq-dhcp[2076]: DHCPOFFER(br-lan) 192.168.196.11 e0:ac:cb:f2:c6:ab
Thu Oct 11 09:40:57 2018 daemon.info dnsmasq-dhcp[2076]: DHCPDISCOVER(br-lan) e0:ac:cb:f2:c6:ab
Thu Oct 11 09:40:57 2018 daemon.info dnsmasq-dhcp[2076]: DHCPOFFER(br-lan) 192.168.196.11 e0:ac:cb:f2:c6:ab
Thu Oct 11 09:41:00 2018 kern.warn kernel: [136870.275464] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 0: -11
Thu Oct 11 09:41:03 2018 kern.warn kernel: [136873.315463] ath10k_pci 0000:00:00.0: failed to set cts protection for vdev 0: -11
Thu Oct 11 09:41:06 2018 daemon.info dnsmasq-dhcp[2076]: DHCPDISCOVER(br-lan) e0:ac:cb:f2:c6:ab
Thu Oct 11 09:41:06 2018 daemon.info dnsmasq-dhcp[2076]: DHCPOFFER(br-lan) 192.168.196.11 e0:ac:cb:f2:c6:ab
Thu Oct 11 09:41:06 2018 daemon.info dnsmasq-dhcp[2076]: DHCPREQUEST(br-lan) 192.168.196.11 e0:ac:cb:f2:c6:ab
Thu Oct 11 09:41:06 2018 daemon.info dnsmasq-dhcp[2076]: DHCPACK(br-lan) 192.168.196.11 e0:ac:cb:f2:c6:ab viola-iphone
Thu Oct 11 09:41:06 2018 kern.warn kernel: [136876.355620] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 0: -11
Thu Oct 11 09:41:06 2018 daemon.info dnsmasq-dhcp[2076]: DHCPREQUEST(br-lan) 192.168.196.11 e0:ac:cb:f2:c6:ab
Thu Oct 11 09:41:06 2018 daemon.info dnsmasq-dhcp[2076]: DHCPACK(br-lan) 192.168.196.11 e0:ac:cb:f2:c6:ab viola-iphone
Thu Oct 11 09:41:15 2018 kern.warn kernel: [136885.475296] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:41:24 2018 kern.warn kernel: [136894.595228] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:41:30 2018 daemon.info dnsmasq-dhcp[2076]: DHCPREQUEST(br-lan) 192.168.196.11 e0:ac:cb:f2:c6:ab
Thu Oct 11 09:41:30 2018 daemon.info dnsmasq-dhcp[2076]: DHCPACK(br-lan) 192.168.196.11 e0:ac:cb:f2:c6:ab viola-iphone
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136903.715153] ath10k_pci 0000:00:00.0: failed to delete peer d4:a3:3d:22:0d:f4 for vdev 0: -11
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136903.723823] ath10k_pci 0000:00:00.0: found sta peer d4:a3:3d:22:0d:f4 (ptr 8538cc00 id 243) entry on vdev 0 after it was supposedly removed
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136903.738468] ------------[ cut here ]------------
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136903.743378] WARNING: CPU: 0 PID: 2177 at backports-4.19-rc5-1/net/mac80211/sta_info.c:1004 sta_set_sinfo+0xaec/0xb98 [mac80211]
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136903.755406] Modules linked in: ath9k ath9k_common pppoe ppp_async option ath9k_hw ath10k_pci ath10k_core ath usb_wwan pppox ppp_generic nf_nat_pptp nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet nf_conntrack_pptp nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_ncm xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_policy xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_FLOWOFFLOAD xt_DSCP xt_CT xt_CLASSIFY usbserial usbnet usblp ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda ts_fsm ts_bm slhc nft_set_rbtree nft_set_hash nft_reject_ipv6
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136903.828489]  nft_reject_ipv4 nft_reject_inet nft_reject nft_redir_ipv4 nft_redir nft_quota nft_numgen nft_nat nft_meta nft_masq_ipv4 nft_masq nft_log nft_limit nft_flow_offload nft_exthdr nft_ct nft_counter nft_chain_route_ipv6 nft_chain_route_ipv4 nft_chain_nat_ipv4 nf_tables_ipv6 nf_tables_ipv4 nf_tables_inet nf_tables nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast ts_kmp nf_conntrack_amanda
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136903.901022]  iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables crc_ccitt compat cdc_wdm fuse sch_cake em_cmp em_nbyte sch_pie sch_gred sch_teql cls_basic act_ipt sch_red sch_multiq sch_prio sch_codel em_meta act_police em_text sch_sfq sch_fq sch_dsmark act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_tbf sch_htb sch_hfsc sch_ingress sg ledtrig_usbport ledtrig_gpio xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136903.973999]  ip6table_filter ip6_tables x_tables ifb sit ipcomp6 xfrm6_tunnel xfrm6_mode_tunnel xfrm6_mode_transport xfrm6_mode_beet esp6 ah6 ipcomp xfrm4_tunnel xfrm4_mode_tunnel xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 tunnel6 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo vfat fat ntfs nls_utf8 nls_iso8859_15 nls_iso8859_1 nls_cp850 nls_cp437 sha512_generic sha256_generic sha1_generic jitterentropy_rng drbg md5 hmac echainiv des_generic deflate zlib_inflate zlib_deflate cbc authenc crypto_acompress mmc_block usb_storage mmc_core ohci_platform ohci_hcd ehci_platform sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4 jbd2 mbcache exfat usbcore nls_base usb_common crc16 mii aead crypto_null cryptomgr crc32c_generic crypto_hash
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.041503] CPU: 0 PID: 2177 Comm: hostapd Not tainted 4.14.74 #0
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.047813] Stack : 80530000 804e0ff8 00000000 00000000 804b7948 860d7b04 8609345c 8050b967
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.056533]         804b3d50 00000881 80663670 000003ec 860d7cb4 00000001 860d7ab8 3d0e73f9
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.065255]         00000000 00000000 80660000 00006898 00000000 00000000 00000008 00000000
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.073834]         00000132 cba0de1a 00000131 6d3a2068 80000000 00000000 86f63978 86f07974
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.082428]         00000009 000003ec 860d7cb4 86dc8000 00000008 80266234 00000000 80660000
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.091008]         ...
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.093578] Call Trace:
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.096185] [<8006a89c>] show_stack+0x58/0x100
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.100798] [<800808a0>] __warn+0xe4/0x118
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.105044] [<80080964>] warn_slowpath_null+0x1c/0x28
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.110402] [<86f07974>] sta_set_sinfo+0xaec/0xb98 [mac80211]
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.116406] [<86f07b00>] sta_info_destroy_addr_bss+0x38/0x60 [mac80211]
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.123301] [<86e4f0e0>] cfg80211_check_station_change+0x1be4/0x2c58 [cfg80211]
Thu Oct 11 09:41:34 2018 kern.warn kernel: [136904.131279] ---[ end trace ad33bc905622a631 ]---
Thu Oct 11 09:41:34 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
Thu Oct 11 09:41:40 2018 daemon.info dnsmasq-dhcp[2076]: DHCPREQUEST(br-lan) 192.168.196.11 e0:ac:cb:f2:c6:ab
Thu Oct 11 09:41:40 2018 daemon.info dnsmasq-dhcp[2076]: DHCPACK(br-lan) 192.168.196.11 e0:ac:cb:f2:c6:ab viola-iphone
Thu Oct 11 09:41:40 2018 daemon.info hostapd: wlan0: STA d4:a3:3d:22:0d:f4 IEEE 802.11: deauthenticated due to local deauth request
Thu Oct 11 09:41:43 2018 kern.warn kernel: [136913.235034] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:41:58 2018 kern.warn kernel: [136928.434934] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 0: -11
Thu Oct 11 09:42:01 2018 kern.warn kernel: [136931.480915] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 0: -11
Thu Oct 11 09:42:07 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
Thu Oct 11 09:42:10 2018 kern.warn kernel: [136940.594784] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 0: -11
Thu Oct 11 09:42:13 2018 kern.warn kernel: [136943.634800] ath10k_pci 0000:00:00.0: failed to set cts protection for vdev 0: -11
Thu Oct 11 09:42:16 2018 kern.warn kernel: [136946.674731] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 0: -11
Thu Oct 11 09:42:25 2018 kern.warn kernel: [136955.794659] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:42:32 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
Thu Oct 11 09:42:41 2018 kern.warn kernel: [136970.999880] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:42:50 2018 kern.warn kernel: [136980.114416] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:43:05 2018 kern.warn kernel: [136995.314280] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 0: -11
Thu Oct 11 09:43:08 2018 kern.warn kernel: [136998.354280] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 0: -11
Thu Oct 11 09:43:17 2018 kern.warn kernel: [137007.474188] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 0: -11
Thu Oct 11 09:43:20 2018 kern.warn kernel: [137010.520160] ath10k_pci 0000:00:00.0: failed to set cts protection for vdev 0: -11
Thu Oct 11 09:43:23 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
Thu Oct 11 09:43:23 2018 kern.warn kernel: [137013.554131] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 0: -11
Thu Oct 11 09:43:32 2018 kern.warn kernel: [137022.674062] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:43:41 2018 kern.warn kernel: [137031.793972] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:43:57 2018 kern.warn kernel: [137046.993820] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:44:06 2018 kern.warn kernel: [137056.113734] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 0: -11
Thu Oct 11 09:44:09 2018 kern.warn kernel: [137059.153707] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 0: -11
Thu Oct 11 09:44:18 2018 kern.warn kernel: [137068.273603] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 0: -11
Thu Oct 11 09:44:21 2018 kern.warn kernel: [137071.313593] ath10k_pci 0000:00:00.0: failed to set cts protection for vdev 0: -11
Thu Oct 11 09:44:24 2018 kern.warn kernel: [137074.353565] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 0: -11
Thu Oct 11 09:44:30 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
Thu Oct 11 09:44:39 2018 kern.warn kernel: [137089.559456] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:44:48 2018 kern.warn kernel: [137098.673375] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:44:57 2018 kern.warn kernel: [137107.793270] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 0: -11
Thu Oct 11 09:45:01 2018 kern.warn kernel: [137110.833228] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 0: -11
Thu Oct 11 09:45:10 2018 kern.warn kernel: [137119.953146] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:45:16 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
Thu Oct 11 09:45:19 2018 kern.warn kernel: [137129.079104] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 0: -11
Thu Oct 11 09:45:22 2018 kern.warn kernel: [137132.113014] ath10k_pci 0000:00:00.0: failed to set cts protection for vdev 0: -11
Thu Oct 11 09:45:25 2018 kern.warn kernel: [137135.153007] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 0: -11
Thu Oct 11 09:45:40 2018 kern.warn kernel: [137150.352857] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:45:49 2018 kern.warn kernel: [137159.472775] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 0: -11
Thu Oct 11 09:45:52 2018 kern.warn kernel: [137162.512728] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 0: -11
Thu Oct 11 09:46:01 2018 kern.warn kernel: [137171.632640] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:46:07 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
Thu Oct 11 09:46:10 2018 kern.warn kernel: [137180.752604] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 0: -11
Thu Oct 11 09:46:13 2018 kern.warn kernel: [137183.792545] ath10k_pci 0000:00:00.0: failed to set cts protection for vdev 0: -11
Thu Oct 11 09:46:17 2018 kern.warn kernel: [137186.832517] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 0: -11
Thu Oct 11 09:46:32 2018 kern.warn kernel: [137202.032376] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:46:38 2018 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED e0:ac:cb:f2:c6:ab
Thu Oct 11 09:46:38 2018 daemon.info hostapd: wlan0: STA e0:ac:cb:f2:c6:ab IEEE 802.11: disassociated due to inactivity
Thu Oct 11 09:46:41 2018 kern.warn kernel: [137211.152300] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer e0:ac:cb:f2:c6:ab: -11
Thu Oct 11 09:46:41 2018 kern.err kernel: [137211.161484] wlan0: failed to remove key (0, e0:ac:cb:f2:c6:ab) from hardware (-11)
Thu Oct 11 09:46:41 2018 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED c8:1e:e7:0f:44:8e
Thu Oct 11 09:46:41 2018 daemon.info hostapd: wlan0: STA c8:1e:e7:0f:44:8e IEEE 802.11: disassociated due to inactivity
Thu Oct 11 09:46:50 2018 kern.warn kernel: [137220.272238] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer c8:1e:e7:0f:44:8e: -11
Thu Oct 11 09:46:50 2018 kern.err kernel: [137220.281489] wlan0: failed to remove key (0, c8:1e:e7:0f:44:8e) from hardware (-11)
Thu Oct 11 09:46:59 2018 kern.warn kernel: [137229.392124] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:47:08 2018 kern.warn kernel: [137238.512048] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:47:17 2018 kern.warn kernel: [137247.637994] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:47:23 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
Thu Oct 11 09:47:33 2018 kern.warn kernel: [137262.831833] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 0: -11
Thu Oct 11 09:47:36 2018 kern.warn kernel: [137265.871790] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 0: -11
Thu Oct 11 09:47:45 2018 kern.warn kernel: [137274.991682] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 0: -11
Thu Oct 11 09:47:48 2018 kern.warn kernel: [137278.031684] ath10k_pci 0000:00:00.0: failed to set cts protection for vdev 0: -11
Thu Oct 11 09:47:51 2018 kern.warn kernel: [137281.071627] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 0: -11
Thu Oct 11 09:47:57 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
Thu Oct 11 09:47:57 2018 daemon.info hostapd: wlan0: STA e0:ac:cb:f2:c6:ab IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.162330] ath10k_pci 0000:00:00.0: cipher 790772512 is not supported
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.169132] ath10k_pci 0000:00:00.0: failed to remove peer wep key 0: -122
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.176237] ath10k_pci 0000:00:00.0: failed to clear all peer wep keys for vdev 0: -122
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.184462] ath10k_pci 0000:00:00.0: failed to disassociate station: e0:ac:cb:f2:c6:ab vdev 0: -122
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.193728] ------------[ cut here ]------------
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.198629] WARNING: CPU: 0 PID: 2177 at backports-4.19-rc5-1/net/mac80211/sta_info.c:996 sta_set_sinfo+0xa80/0xb98 [mac80211]
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.210358] Modules linked in: ath9k ath9k_common pppoe ppp_async option ath9k_hw ath10k_pci ath10k_core ath usb_wwan pppox ppp_generic nf_nat_pptp nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet nf_conntrack_pptp nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_ncm xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_policy xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_FLOWOFFLOAD xt_DSCP xt_CT xt_CLASSIFY usbserial usbnet usblp ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda ts_fsm ts_bm slhc nft_set_rbtree nft_set_hash nft_reject_ipv6
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.283178]  nft_reject_ipv4 nft_reject_inet nft_reject nft_redir_ipv4 nft_redir nft_quota nft_numgen nft_nat nft_meta nft_masq_ipv4 nft_masq nft_log nft_limit nft_flow_offload nft_exthdr nft_ct nft_counter nft_chain_route_ipv6 nft_chain_route_ipv4 nft_chain_nat_ipv4 nf_tables_ipv6 nf_tables_ipv4 nf_tables_inet nf_tables nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast ts_kmp nf_conntrack_amanda
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.355530]  iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables crc_ccitt compat cdc_wdm fuse sch_cake em_cmp em_nbyte sch_pie sch_gred sch_teql cls_basic act_ipt sch_red sch_multiq sch_prio sch_codel em_meta act_police em_text sch_sfq sch_fq sch_dsmark act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_tbf sch_htb sch_hfsc sch_ingress sg ledtrig_usbport ledtrig_gpio xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.428278]  ip6table_filter ip6_tables x_tables ifb sit ipcomp6 xfrm6_tunnel xfrm6_mode_tunnel xfrm6_mode_transport xfrm6_mode_beet esp6 ah6 ipcomp xfrm4_tunnel xfrm4_mode_tunnel xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 tunnel6 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo vfat fat ntfs nls_utf8 nls_iso8859_15 nls_iso8859_1 nls_cp850 nls_cp437 sha512_generic sha256_generic sha1_generic jitterentropy_rng drbg md5 hmac echainiv des_generic deflate zlib_inflate zlib_deflate cbc authenc crypto_acompress mmc_block usb_storage mmc_core ohci_platform ohci_hcd ehci_platform sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4 jbd2 mbcache exfat usbcore nls_base usb_common crc16 mii aead crypto_null cryptomgr crc32c_generic crypto_hash
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.495621] CPU: 0 PID: 2177 Comm: hostapd Tainted: G        W       4.14.74 #0
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.503156] Stack : 80530000 804e0ff8 00000000 00000000 804b7948 860d7b04 8609345c 8050b967
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.511739]         804b3d50 00000881 80663670 000003e4 860d7cb4 00000001 860d7ab8 3d0e73f9
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.520367]         00000000 00000000 80660000 00009428 00000000 00000000 00000008 00000000
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.529010]         0000017d 5501c510 0000017c 20202020 80000000 00000000 86f63978 86f07908
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.537614]         00000009 000003e4 860d7cb4 86dc8000 00000003 80266234 00000000 80660000
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.546199]         ...
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.548767] Call Trace:
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.551352] [<8006a89c>] show_stack+0x58/0x100
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.556100] [<800808a0>] __warn+0xe4/0x118
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.560355] [<80080964>] warn_slowpath_null+0x1c/0x28
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.565721] [<86f07908>] sta_set_sinfo+0xa80/0xb98 [mac80211]
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.571720] [<86f07b00>] sta_info_destroy_addr_bss+0x38/0x60 [mac80211]
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.578612] [<86e4f0e0>] cfg80211_check_station_change+0x1be4/0x2c58 [cfg80211]
Thu Oct 11 09:47:57 2018 kern.warn kernel: [137287.586154] ---[ end trace ad33bc905622a632 ]---
Thu Oct 11 09:48:00 2018 kern.warn kernel: [137290.591579] ath10k_pci 0000:00:00.0: failed to delete peer e0:ac:cb:f2:c6:ab for vdev 0: -11
Thu Oct 11 09:48:00 2018 kern.warn kernel: [137290.600322] ath10k_pci 0000:00:00.0: found sta peer e0:ac:cb:f2:c6:ab (ptr 86b38400 id 218) entry on vdev 0 after it was supposedly removed
Thu Oct 11 09:48:09 2018 kern.warn kernel: [137299.711471] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:48:16 2018 daemon.info hostapd: wlan0: STA c8:1e:e7:0f:44:8e IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Oct 11 09:48:16 2018 kern.warn kernel: [137305.792092] ath10k_pci 0000:00:00.0: cipher 172183374 is not supported
Thu Oct 11 09:48:16 2018 kern.warn kernel: [137305.798839] ath10k_pci 0000:00:00.0: failed to remove peer wep key 0: -122
Thu Oct 11 09:48:16 2018 kern.warn kernel: [137305.805940] ath10k_pci 0000:00:00.0: failed to clear all peer wep keys for vdev 0: -122
Thu Oct 11 09:48:16 2018 kern.warn kernel: [137305.814163] ath10k_pci 0000:00:00.0: failed to disassociate station: c8:1e:e7:0f:44:8e vdev 0: -122
Thu Oct 11 09:48:19 2018 kern.warn kernel: [137308.831411] ath10k_pci 0000:00:00.0: failed to delete peer c8:1e:e7:0f:44:8e for vdev 0: -11
Thu Oct 11 09:48:19 2018 kern.warn kernel: [137308.840308] ath10k_pci 0000:00:00.0: found sta peer c8:1e:e7:0f:44:8e (ptr 86027000 id 149) entry on vdev 0 after it was supposedly removed
Thu Oct 11 09:48:28 2018 kern.warn kernel: [137317.951303] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:48:37 2018 kern.warn kernel: [137327.077130] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 0: -11
Thu Oct 11 09:48:40 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
Thu Oct 11 09:48:40 2018 kern.warn kernel: [137330.111193] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 0: -11
Thu Oct 11 09:48:49 2018 kern.warn kernel: [137339.231088] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 0: -11
Thu Oct 11 09:48:52 2018 kern.warn kernel: [137342.271058] ath10k_pci 0000:00:00.0: failed to set cts protection for vdev 0: -11
Thu Oct 11 09:48:55 2018 kern.warn kernel: [137345.311055] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 0: -11
Thu Oct 11 09:49:04 2018 kern.warn kernel: [137354.430986] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:49:13 2018 kern.warn kernel: [137363.551096] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 0: -11
Thu Oct 11 09:49:16 2018 kern.warn kernel: [137366.590838] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 0: -11
Thu Oct 11 09:49:25 2018 kern.warn kernel: [137375.710757] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 0: -11
Thu Oct 11 09:49:28 2018 kern.warn kernel: [137378.750743] ath10k_pci 0000:00:00.0: failed to set cts protection for vdev 0: -11
Thu Oct 11 09:49:31 2018 kern.warn kernel: [137381.790709] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 0: -11
Thu Oct 11 09:49:41 2018 kern.warn kernel: [137390.910625] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
Thu Oct 11 09:49:47 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
Thu Oct 11 09:49:56 2018 kern.warn kernel: [137406.116356] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
09.10.20181889Base systemBug ReportVery LowLowsysupgrade should try and preserve running states of th...TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

everything

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

- Steps to reproduce

do a sysupgrade on a remote box somewhere. The firewall and web server
are started by default. In some cases (like in an interior router) these
have been disabled explicitly so you can manage them from the outside. So preserving
the running state somehow of the essential services across an upgrade would help.

(bug report filed after I had to climb a building to re-re-re-flash a router after
foolishly thinking all I had to do was a sysupgrade)

 


08.10.20181886ToolchainBug ReportVery LowLowbuiltin_memcmp(a,b,c) != 0 not used on mips with -Os or...TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

mips, probably everything except x86_64.

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

18.06.1

- Steps to reproduce

Well, the simple way is to cross compile anything that uses a pattern like
memcmp(a,b,c) != 0 // (or ==) and count up the memcmps via objdump.

The != or == pattern gets substituted for a string of xors and a final or, which
is way faster than memcmp can ever be. It was added to gcc 7.

I was building the babel daemon and wondering why my x86_64 compiler was doing
the right thing but not the mips compiler of the same era.

memcmp is pretty expensive for 16 byte (ipv6 prefixes) compares especially when
you only care about equal or not equal. Code’s usually smaller too. Nothing faster than xor exists.

08.10.20181885Base systemBug ReportVery LowLowath79 / WDR3600: disappeared WLAN5G LED control in kern...TrunkUnconfirmed Task Description

device: TPLink WDR3600
platfrom: ath79

I do not know when it happened, in 4.14.63 it’s OK, in 4.14.74 it is missing.

I have WLAN5G LED control under kernel 4.14.63

root@OpenWRT:~# uname -a
Linux OpenWRT 4.14.63 #0 Thu Aug 16 20:29:28 2018 mips GNU/Linux

root@OpenWRT:~# ls -al /sys/class/leds/
drwxr-xr-x    2 root     root             0 Jan  1  1970 .
drwxr-xr-x   26 root     root             0 Jan  1  1970 ..
lrwxrwxrwx    1 root     root             0 Oct  8 18:03 ath9k-phy0 -> ../../devices/platform/ahb/ahb:apb/18100000.wmac/leds/ath9k-phy0
lrwxrwxrwx    1 root     root             0 Jan  1  1970 tp-link:green:qss -> ../../devices/platform/leds/leds/tp-link:green:qss
lrwxrwxrwx    1 root     root             0 Jan  1  1970 tp-link:green:system -> ../../devices/platform/leds/leds/tp-link:green:system
lrwxrwxrwx    1 root     root             0 Jan  1  1970 tp-link:green:usb1 -> ../../devices/platform/leds/leds/tp-link:green:usb1
lrwxrwxrwx    1 root     root             0 Jan  1  1970 tp-link:green:usb2 -> ../../devices/platform/leds/leds/tp-link:green:usb2
lrwxrwxrwx    1 root     root             0 Jan  1  1970 tp-link:green:wlan2g -> ../../devices/platform/leds/leds/tp-link:green:wlan2g
**lrwxrwxrwx    1 root     root             0 Oct  8 18:03 tp-link:green:wlan5g -> ../../devices/platform/ath9k-leds/leds/tp-link:green:wlan5g**

root@OpenWRT:~# ls -al /sys/devices/platform/leds/leds/
drwxr-xr-x    7 root     root             0 Jan  1  1970 .
drwxr-xr-x    3 root     root             0 Jan  1  1970 ..
drwxr-xr-x    2 root     root             0 Jan  1  1970 tp-link:green:qss
drwxr-xr-x    2 root     root             0 Jan  1  1970 tp-link:green:system
drwxr-xr-x    3 root     root             0 Jan  1  1970 tp-link:green:usb1
drwxr-xr-x    3 root     root             0 Jan  1  1970 tp-link:green:usb2
drwxr-xr-x    2 root     root             0 Jan  1  1970 tp-link:green:wlan2g

root@OpenWRT:~# ls -al /sys/devices/platform/ath9k-leds/leds/
drwxr-xr-x    3 root     root             0 Oct  8 18:03 .
drwxr-xr-x    3 root     root             0 Jan  1  1970 ..
**drwxr-xr-x    2 root     root             0 Oct  8 18:03 tp-link:green:wlan5g**

But with kernel 4.14.74 it is missing

root@OpenWRT:~# uname -a
Linux OpenWRT 4.14.74 #0 Mon Oct 8 08:03:23 2018 mips GNU/Linux

root@OpenWRT:~# ls -al /sys/class/leds/
drwxr-xr-x    2 root     root             0 Jan  1  1970 .
drwxr-xr-x   26 root     root             0 Jan  1  1970 ..
lrwxrwxrwx    1 root     root             0 Oct  8 18:07 ath9k-phy0 -> ../../devices/platform/ahb/ahb:apb/18100000.wmac/leds/ath9k-phy0
lrwxrwxrwx    1 root     root             0 Jan  1  1970 tp-link:green:qss -> ../../devices/platform/leds/leds/tp-link:green:qss
lrwxrwxrwx    1 root     root             0 Jan  1  1970 tp-link:green:system -> ../../devices/platform/leds/leds/tp-link:green:system
lrwxrwxrwx    1 root     root             0 Jan  1  1970 tp-link:green:usb1 -> ../../devices/platform/leds/leds/tp-link:green:usb1
lrwxrwxrwx    1 root     root             0 Jan  1  1970 tp-link:green:usb2 -> ../../devices/platform/leds/leds/tp-link:green:usb2
lrwxrwxrwx    1 root     root             0 Jan  1  1970 tp-link:green:wlan2g -> ../../devices/platform/leds/leds/tp-link:green:wlan2g

root@OpenWRT:~# ls -al /sys/devices/platform/leds/leds/
drwxr-xr-x    7 root     root             0 Jan  1  1970 .
drwxr-xr-x    3 root     root             0 Jan  1  1970 ..
drwxr-xr-x    2 root     root             0 Jan  1  1970 tp-link:green:qss
drwxr-xr-x    2 root     root             0 Jan  1  1970 tp-link:green:system
drwxr-xr-x    2 root     root             0 Jan  1  1970 tp-link:green:usb1
drwxr-xr-x    2 root     root             0 Jan  1  1970 tp-link:green:usb2
drwxr-xr-x    2 root     root             0 Jan  1  1970 tp-link:green:wlan2g

root@OpenWRT:~# ls -al /sys/devices/platform/ath9k-leds/leds
**ls: /sys/devices/platform/ath9k-leds/leds: No such file or directory**

root@OpenWRT:~# ls -al /sys/devices/platform/ath9k-leds/
drwxr-xr-x    2 root     root             0 Jan  1  1970 .
drwxr-xr-x   13 root     root             0 Jan  1  1970 ..
-rw-r--r--    1 root     root          4096 Oct  8 16:38 driver_override
-r--r--r--    1 root     root          4096 Oct  8 16:38 modalias
lrwxrwxrwx    1 root     root             0 Oct  8 16:38 of_node -> ../../../firmware/devicetree/base/ath9k-leds
lrwxrwxrwx    1 root     root             0 Oct  8 16:38 subsystem -> ../../../bus/platform
-rw-r--r--    1 root     root          4096 Oct  8 16:38 uevent
08.10.20181884Base systemBug ReportVery LowMediumFailed to disable DHCPv4openwrt-18.06Unconfirmed Task Description

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

 

I run a openwrt 18.06.1 on Lenovo Y1 with both IPv4 and IPv6, and I tried to disable the DHCPv6 on LAN to get a IPv6-Only network for testing, but it’s failed. And it’s successed to disable the DHCPv6 on lede 17.0.1.6

Steps to produce:
1、Navigate to Network –> Interfaces, choose LAN –> DHCP Server tab page, check the “ignore interface” 2、Connect to WIFI to obtain the IP addresses using a iPhone, you’ll see only IPv6 address is obtained.
3、Access a IPv4 site using browser, it’s successed, check the IP addresses again, you’ll see the device obtians a IPv4 address again.
4、Try to disalbe “Dynamic DHCP” on the Advanced Settings tab page, and then repeat the steps #1 ~ #3, it doesn’t work too.

07.10.20181883Base systemBug ReportVery LowHighWAN interface VLAN not working on AVM FRITZ!Box 4040TrunkUnconfirmed Task Description

WAN interface of AVM FRITZ!Box 4040 is on eth1. To gain internet connectivity the ISP requires VLAN tagging with ID 7. But while I can send packets through interface eth1, I cannot through eth1.7.

Affected device: https://openwrt.org/toh/hwdata/avm/avm_fritz_box_4040 Affected versions: All I have tested, that is: 18.06.1 and the snapshot available today.

I haven’t seen any disturbing firewall rules and it still doesn’t work after flushing iptables completely.

Steps to reproduce:

- flash OpenWrt 18.06.1 to FRITZ!Box 4040
- change WAN ifname to eth1.7
- connect WAN port to laptop or monitoring device with Wireshark or similar
- send something via eth1.7, e.g. ping, but dhcp or pppd are sending stuff anyway

What happens:

Monitoring device does not see pings, dhcp, pppoe or other packets that go through eth1.7. It received when sending via eth1 directly (untagged). When sniffing via tcpdump on the router, it looks like the packets are send, but they are actually not going over the wire.

What should happen:

VLAN tagged packets are send properly (so PPPoE discovery succeeds in the end).

It was advised to open this bug report in the following forum thread. There is also some more information including configuration dumps. https://forum.openwrt.org/t/vlan-configuration-for-telekom/21841

04.10.20181879KernelBug ReportVery LowMediumOpenWRT fails to initialize a SECOND USB-to-Ethernet ad...TrunkUnconfirmed Task Description

When using TWO USB-to-Ethernet adapters on Raspberry Pi3 Model B+, only the first one connected will work.
There’s a similar thread for openmptcprouter, so I assume it could be a Kernel bug? https://github.com/Ysurac/openmptcprouter/issues/142

* Device problem occurs on: Raspberry Pi 3 Model B+
* Software versions of OpenWrt/LEDE release, packages, etc.

  • OpenWrt: rpi-3-ext4-factory.img.gz 58beb23298e5c31ba2a61ed73a58af77ea26973904ef77e3cab21071a03f8a8b 9440.1 KB Wed Oct 3 08:47:27 2018
  • Kernel/Architecture: Linux OpenWrt 4.9.130 #0 SMP Wed Oct 3 03:54:01 2018 aarch64 GNU/Linux
  • Packages:
    • base-files - 196-r8217-2cc821e
    • brcm2708-gpu-fw - 2018-05-16-0f5f899ccec1c2ef8bba02aa49700b4ec19b4199
    • brcmfmac-board-rpi2 - 2018-03-12-86e88fbf0345da49555d0ec34c80b4fbae7d0cd3
    • brcmfmac-board-rpi3 - 2018-03-12-86e88fbf0345da49555d0ec34c80b4fbae7d0cd3
    • brcmfmac-firmware-43430-sdio - 2018-08-03-7b5835fd-1
    • brcmfmac-firmware-43455-sdio - 2018-08-03-7b5835fd-1
    • brcmfmac-firmware-usb - 2018-08-03-7b5835fd-1
    • busybox - 1.29.3-2
    • dnsmasq - 2.80test7-1
    • dropbear - 2017.75-8
    • e2fsprogs - 1.44.3-1
    • firewall - 2018-08-13-1c4d5bcd-1
    • fstools - 2018-05-23-dd02dad3-2
    • fwtool - 1
    • hostapd-common - 2018-05-21-62566bc2-4
    • ip-tiny - 4.18.0-4
    • ip6tables - 1.6.2-3
    • ipset - 6.34-1
    • iptables - 1.6.2-3
    • iptables-mod-conntrack-extra - 1.6.2-3
    • iptables-mod-ipopt - 1.6.2-3
    • iw - 4.14-1
    • iwinfo - 2018-07-31-65b8333f-1
    • joe - 4.6-1
    • jshn - 2018-07-25-c83a84af-2
    • jsonfilter - 2018-02-04-c7e938d6-1
    • kernel - 4.9.130-1-2adb9ed1c261fb0a5ff2564c10301966
    • kmod-brcmutil - 4.9.130+4.19-rc5-1-1
    • kmod-fs-vfat - 4.9.130-1
    • kmod-hid - 4.9.130-1
    • kmod-hid-generic - 4.9.130-1
    • kmod-input-core - 4.9.130-1
    • kmod-input-evdev - 4.9.130-1
    • kmod-ip6tables - 4.9.130-1
    • kmod-ipt-conntrack - 4.9.130-1
    • kmod-ipt-conntrack-extra - 4.9.130-1
    • kmod-ipt-core - 4.9.130-1
    • kmod-ipt-ipopt - 4.9.130-1
    • kmod-ipt-ipset - 4.9.130-1
    • kmod-ipt-nat - 4.9.130-1
    • kmod-ipt-raw - 4.9.130-1
    • kmod-lib-crc-ccitt - 4.9.130-1
    • kmod-libphy - 4.9.130-1
    • kmod-mii - 4.9.130-1
    • kmod-mmc - 4.9.130-1
    • kmod-nf-conntrack - 4.9.130-1
    • kmod-nf-conntrack6 - 4.9.130-1
    • kmod-nf-ipt - 4.9.130-1
    • kmod-nf-ipt6 - 4.9.130-1
    • kmod-nf-nat - 4.9.130-1
    • kmod-nf-reject - 4.9.130-1
    • kmod-nf-reject6 - 4.9.130-1
    • kmod-nfnetlink - 4.9.130-1
    • kmod-nls-base - 4.9.130-1
    • kmod-nls-cp437 - 4.9.130-1
    • kmod-nls-iso8859-1 - 4.9.130-1
    • kmod-nls-utf8 - 4.9.130-1
    • kmod-ppp - 4.9.130-1
    • kmod-pppoe - 4.9.130-1
    • kmod-pppox - 4.9.130-1
    • kmod-slhc - 4.9.130-1
    • kmod-sound-arm-bcm2835 - 4.9.130-1
    • kmod-sound-core - 4.9.130-1
    • kmod-usb-core - 4.9.130-1
    • kmod-usb-hid - 4.9.130-1
    • kmod-usb-net - 4.9.130-1
    • kmod-usb-net-asix - 4.9.130-1
    • kmod-usb-net-asix-ax88179 - 4.9.130-1
    • kmod-usb-net-cdc-ether - 4.9.130-1
    • libblkid - 2.32.1-2
    • libblobmsg-json - 2018-07-25-c83a84af-2
    • libc - 1.1.20-1
    • libcomerr - 1.44.3-1
    • libext2fs - 1.44.3-1
    • libf2fs - 1.11.0-1
    • libgcc - 7.3.0-1
    • libip4tc - 1.6.2-3
    • libip6tc - 1.6.2-3
    • libipset - 6.34-1
    • libiwinfo - 2018-07-31-65b8333f-1
    • libiwinfo-lua - 2018-07-31-65b8333f-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
    • libmnl - 1.0.4-1
    • libncurses - 6.1-1
    • libnl-tiny - 0.1-5
    • libpthread - 1.1.20-1
    • librt - 1.1.20-1
    • libsmartcols - 2.32.1-2
    • libss - 1.44.3-1
    • libubox - 2018-07-25-c83a84af-2
    • libubus - 2018-07-26-40e0931e-1
    • libubus-lua - 2018-07-26-40e0931e-1
    • libuci - 2018-08-11-4c8b4d6e-1
    • libuclient - 2018-08-03-ae1c656f-1
    • libuuid - 2.32.1-2
    • libxtables - 1.6.2-3
    • logd - 2018-02-14-128bc35f-2
    • lua - 5.1.5-1
    • luci - git-18.276.41146-280dd33-1
    • luci-app-firewall - git-18.276.41146-280dd33-1
    • luci-base - git-18.276.41146-280dd33-1
    • luci-lib-ip - git-18.276.41146-280dd33-1
    • luci-lib-jsonc - git-18.276.41146-280dd33-1
    • luci-lib-nixio - git-18.276.41146-280dd33-1
    • luci-mod-admin-full - git-18.276.41146-280dd33-1
    • luci-mod-network - git-18.276.41146-280dd33-1
    • luci-mod-status - git-18.276.41146-280dd33-1
    • luci-mod-system - git-18.276.41146-280dd33-1
    • luci-proto-ipv6 - git-18.276.41146-280dd33-1
    • luci-proto-ppp - git-18.276.41146-280dd33-1
    • luci-theme-bootstrap - git-18.276.41146-280dd33-1
    • mkf2fs - 1.11.0-1
    • mtd - 23
    • mwan3 - 2.7.2-1
    • netifd - 2018-10-02-83428fac-2
    • odhcp6c - 2018-07-14-67ae6a71-16
    • odhcpd-ipv6only - 1.11-3
    • openwrt-keyring - 2018-05-18-103a32e9-1
    • opkg - 2017-12-07-3b417b9f-2
    • partx-utils - 2.32.1-2
    • ppp - 2.4.7-13
    • ppp-mod-pppoe - 2.4.7-13
    • procd - 2018-08-06-e29966f0-1
    • rpcd - 2018-08-16-41333abe-1
    • rpcd-mod-rrdns - 20170710
    • terminfo - 6.1-1
    • ubox - 2018-02-14-128bc35f-2
    • ubus - 2018-07-26-40e0931e-1
    • ubusd - 2018-07-26-40e0931e-1
    • uci - 2018-08-11-4c8b4d6e-1
    • uclient-fetch - 2018-08-03-ae1c656f-1
    • uhttpd - 2018-08-23-b741dec3-1
    • usign - 2015-07-04-ef641914-1
    • wpad-mini - 2018-05-21-62566bc2-4

* Steps to reproduce

  • Connect two USB-to-Ethernet adapters
  • Connect Ethernet cables to both
  • See error message: ERROR::assign_and_init_hc:1397: assign_and_init_hc: Failed to allocate memory handle non-dword aligned buffer case
  • Observer second adapter not receiving an IP address via DHCP, not sending/receiving any packets according to Luci interfaces overview


03.10.20181878KernelBug ReportVery LowCriticalFsck privately repaired the file system ext4 on my hdd...openwrt-18.06Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on x86-64
- Software versions of OpenWrt/LEDE release, packages, etc.openwrt18.06 55bbd8
- Steps to reproduce.booting and the log showed:

[ 21.237803] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 21.272692] EXT4-fs (sda9): Errors on filesystem, clearing orphan list.
[ 21.272692]
[ 21.281161] EXT4-fs (sda9): recovery complete
[ 21.317228] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 22.061620] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 22.069917] br-lan: port 1(eth0) entered blocking state
[ 22.075803] br-lan: port 1(eth0) entered forwarding state
[ 22.081750] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 23.607322] EXT4-fs (sda10): 3 orphan inodes deleted
[ 23.612459] EXT4-fs (sda10): recovery complete
[ 23.708324] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 26.560650] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 27.547143] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 27.567936] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 27.674344] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 30.029453] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 30.949532] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 30.969532] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 31.076454] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 33.381486] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 34.252398] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 34.272320] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 34.386849] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 36.883663] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 37.787051] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 37.808077] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 37.914149] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 40.179819] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 41.121988] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 41.143438] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 41.249342] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 45.605695] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 46.626671] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 46.646619] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 46.761479] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 49.141156] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 50.029110] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 50.057517] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 50.171446] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 52.634916] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 53.630485] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 53.651385] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 53.765666] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 56.181064] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 57.106498] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 57.127788] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 57.226070] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 59.531087] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 60.476052] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 60.496576] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 60.602792] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 62.968986] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 63.853172] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 63.873463] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 63.980377] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 66.434813] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 67.379340] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 67.425858] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 67.541354] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 69.678280] F2FS-fs (sdb3): Magic Mismatch, valid(0xf2f52010) - read(0×0)
[ 69.685327] F2FS-fs (sdb3): Can’t find valid F2FS filesystem in 1th superblock
[ 69.693925] F2FS-fs (sdb3): Magic Mismatch, valid(0xf2f52010) - read(0×0)
[ 69.700936] F2FS-fs (sdb3): Can’t find valid F2FS filesystem in 2th superblock
[ 69.708463] F2FS-fs (sdb3): Magic Mismatch, valid(0xf2f52010) - read(0×0)
[ 69.715499] F2FS-fs (sdb3): Can’t find valid F2FS filesystem in 1th superblock
[ 69.723034] F2FS-fs (sdb3): Magic Mismatch, valid(0xf2f52010) - read(0×0)
[ 69.730039] F2FS-fs (sdb3): Can’t find valid F2FS filesystem in 2th superblock
[ 69.978884] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 71.390695] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 71.410966] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 71.517413] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 73.339283] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 74.259796] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 74.279939] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 74.377566] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 76.068444] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 76.960511] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 76.981847] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 77.079687] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 78.675960] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 79.687038] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 79.708336] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 79.806743] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 81.486004] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 82.438683] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 82.460115] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 82.574661] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 84.356267] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 85.274004] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 85.295104] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 85.409756] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 87.105830] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 88.151523] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 88.173126] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 88.269852] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 90.191325] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 91.112146] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 91.132150] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 91.238595] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 93.101835] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 94.013109] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 94.033603] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 94.131548] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 95.877771] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 96.848488] EXT4-fs (sda9): warning: mounting fs with errors, running e2fsck is recommended
[ 96.869262] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 96.975183] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)

then i booted my linuxmint,displayed file system error needs to be fixed


01.10.20181877KernelBug ReportVery LowHighSD Card corruption on reboot after power failureTrunkUnconfirmed Task Description

- problem occurs on zbt-we1326 with mt7621 cpu with mtk_sd kernel module loaded.
- openwrt latest snapshot(30-08-2017) firmware downloaded from openwrt.
- Steps to reproduce
1. setup extroot on the sdcard with a partition of 1gb(ext4)(boot) mounted as /overlay and 31gb(f2fs)(data) mounted at /media/
2. works fine on normal reboot(through ui).
3. turn off router power and start the router by plugging back in. notice corruption of extroot or data folder or both . it doesn’t happen rarely but it definitely happens on subsequent power off/on cycle.

 


01.10.20181876PackagesBug ReportVery LowMediumar71xx: btrfs (RAID1) broken on the TL-WDR3600 TrunkUnconfirmed Task Description

Hi,

I updated my TP-LINK TL-WDR3600 to OpenWrt 18.06.1 to attach 2 Harddisks in RAID1. The disks were attached to a Linux PC before and they work there without any problems. They are also working with gexxbox (cubibox hardware).

uname -a
Linux Grisu-AP 4.9.120 #0 Thu Aug 16 07:51:15 2018 mips GNU/Linux

root@Grisu-AP:/mnt# block info
label buffer too small 256 > 63
label buffer too small 256 > 63
/dev/mtdblock2: UUID=”d74faf39-3bf99749-7ff34679-ea820947” VERSION=”4.0” MOUNT=”/rom” TYPE=”squashfs” /dev/mtdblock3: MOUNT=”/overlay” TYPE=”jffs2” /dev/sda: UUID=”72a8abd2-1880-47d5-a91b-836c2bd0e6ae” TYPE=”btrfs” /dev/sdb: UUID=”72a8abd2-1880-47d5-a91b-836c2bd0e6ae” TYPE=”btrfs”

If I try to mount the RAID as sda I get the following:
mount /dev/sda /mnt/share
mount: mounting /dev/sda on /mnt/share failed: Invalid argument

If I try to mount the RAID as sdb it seems to work. I can browse through the directories for some seconds. Then nothing is listed anymore and I found the following in the log.

[ 206.334816] BTRFS: device label BTRFS_RAID1 devid 1 transid 21115 /dev/sda
[ 206.344960] BTRFS info (device sda): disk space caching is enabled
[ 206.353718] BTRFS error (device sda): failed to read the system array: -5
[ 206.362914] BTRFS error (device sda): open_ctree failed
[ 227.727463] BTRFS info (device sda): disk space caching is enabled
[ 227.735960] BTRFS error (device sda): failed to read the system array: -5
[ 227.745478] BTRFS error (device sda): open_ctree failed
[ 237.303189] BTRFS: device label BTRFS_RAID1 devid 2 transid 21115 /dev/sdb
[ 237.313585] BTRFS info (device sdb): disk space caching is enabled
[ 292.959623] ————[ cut here ]———— [ 292.964449] WARNING: CPU: 0 PID: 2010 at fs/btrfs/extent-tree.c:2967 0x8771f3e8 [btrfs@87700000+0xd74a0]
[ 292.974243] BTRFS: Transaction aborted (error -17)
[ 292.979183] Modules linked in: ath9k ath9k_common pppoe ppp_async ath9k_hw 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_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack lzo libcrc32c iptable_mangle iptable_filter ip_tables crc_ccitt compat ledtrig_usbport ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables nfsd nfs lockd sunrpc grace dns_resolver uas usb_storage sd_mod scsi_mod btrfs zlib_inflate zlib_deflate xor raid6_pq lzo_decompress lzo_compress
[ 293.051845] exportfs crc32c_generic crypto_hash ehci_platform ehci_hcd gpio_button_hotplug usbcore nls_base usb_common
[ 293.061554] CPU: 0 PID: 2010 Comm: btrfs-transacti Not tainted 4.9.120 #0
[ 293.068477] Stack : 80497672 0000003d 00000000 00000001 00000000 00000000 00000000 00000000
[ 293.077154] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 293.085741] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 293.094322] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 293.102919] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 293.111499] ...
[ 293.114007] Call Trace:
[ 293.116327] [<8006ad5c>] 0x8006ad5c
[ 293.119889] [<8006ad5c>] 0x8006ad5c
[ 293.123427] [<8007fd44>] 0x8007fd44
[ 293.127028] [<8771f3e8>] 0x8771f3e8 [btrfs@87700000+0xd74a0]
[ 293.132814] [<8007fd7c>] 0x8007fd7c
[ 293.136393] [<8771f3e8>] 0x8771f3e8 [btrfs@87700000+0xd74a0]
[ 293.142249] [<87737e5c>] 0x87737e5c [btrfs@87700000+0xd74a0]
[ 293.148041] [<877385ec>] 0x877385ec [btrfs@87700000+0xd74a0]
[ 293.153811] [<803a79d8>] 0x803a79d8
[ 293.157380] [<87732d94>] 0x87732d94 [btrfs@87700000+0xd74a0]
[ 293.163158] [<87732c10>] 0x87732c10 [btrfs@87700000+0xd74a0]
[ 293.168960] [<87732c10>] 0x87732c10 [btrfs@87700000+0xd74a0]
[ 293.174786] [<80098150>] 0×80098150 [ 293.178399] [<80098074>] 0×80098074 [ 293.181992] [<80065ef8>] 0x80065ef8
[ 293.185533]
[ 293.187041] —[ end trace 467c7995bdeef333 ]— [ 293.191792] BTRFS: error (device sdb) in btrfs_run_delayed_refs:2967: errno=-17 Object already exists
[ 293.201178] BTRFS info (device sdb): forced readonly
[ 293.206265] BTRFS warning (device sdb): Skipping commit of aborted transaction.
[ 293.213736] BTRFS: error (device sdb) in cleanup_transaction:1850: errno=-17 Object already exists

If you need more information please let me know.
Best regards, grisu

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

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


29.09.20181871KernelBug ReportVery LowCriticalKernel :Ipq806x MTD ECC ERRORopenwrt-18.06Unconfirmed Task Description

Kernel Version :4.14.72
Device :R7800 R7500v2
Problem Desrciption : low performance and unable to access later on

Partial Kernel log as below:
[ 13.139004] mount_root: loading kmods from internal overlay
[ 13.160507] kmodloader: loading kernel modules from etc/modules-boot.d/*
[ 13.162142] kmodloader: done loading kernel modules from
etc/modules-boot.d/*
[ 13.645897] print_req_error: I/O error, dev mtdblock0, sector 0
[ 13.646480] print_req_error: I/O error, dev mtdblock0, sector 8
[ 13.651170] print_req_error: I/O error, dev mtdblock0, sector 16
[ 13.657141] print_req_error: I/O error, dev mtdblock0, sector 24
[ 13.663652] print_req_error: I/O error, dev mtdblock0, sector 0
[ 13.668768] Buffer I/O error on dev mtdblock0, logical block 0, async page read
[ 13.675464] print_req_error: I/O error, dev mtdblock1, sector 0
[ 13.682197] print_req_error: I/O error, dev mtdblock1, sector 8
[ 13.688189] print_req_error: I/O error, dev mtdblock1, sector 16
[ 13.694064] print_req_error: I/O error, dev mtdblock1, sector 24
[ 13.700333] print_req_error: I/O error, dev mtdblock1, sector 0
[ 13.705746] Buffer I/O error on dev mtdblock1, logical block 0, async page read
[ 14.652468] UBIFS (ubi0:1): default file-system created
[ 14.863310] UBIFS (ubi0:1): background thread “ubifs_bgt0_1” started, PID 145
[ 15.992981] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name “rootfs_data” [ 15.993012] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 15.999790] UBIFS (ubi0:1): FS size: 86851584 bytes (82 MiB, 684 LEBs), journal size 4317184 bytes (4 MiB, 34 LEBs)
[ 16.009776] UBIFS (ubi0:1): reserved for root: 4102214 bytes (4006 KiB)
[ 16.020007] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID F5E27DA8-5132-4007-B493-3B43B43C9591, small LPT model
[ 16.027856] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[ 16.038233] block: unable to load configuration (fstab: Entry not found)
[ 16.044908] block: attempting to load /tmp/ubifs_cfg/etc/config/fstab
[ 16.051793] block: unable to load configuration (fstab: Entry not found)
[ 16.058205] block: attempting to load /etc/config/fstab
[ 16.065988] block: unable to load configuration (fstab: Entry not found)
[ 16.069806] block: no usable configuration
[ 16.119510] UBIFS (ubi0:1): un-mount UBI device 0
[ 16.119592] UBIFS (ubi0:1): background thread “ubifs_bgt0_1” stops
[ 16.128471] UBIFS (ubi0:1): background thread “ubifs_bgt0_1” started, PID 146
[ 16.705716] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name “rootfs_data” [ 16.705748] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 16.712618] UBIFS (ubi0:1): FS size: 86851584 bytes (82 MiB, 684 LEBs), journal size 4317184 bytes (4 MiB, 34 LEBs)
[ 16.722502] UBIFS (ubi0:1): reserved for root: 4102214 bytes (4006 KiB)
[ 16.732746] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID F5E27DA8-5132-4007-B493-3B43B43C9591, small LPT model
[ 16.754840] Buffer I/O error on dev mtdblock0, logical block 0, async page read
[ 16.757717] Buffer I/O error on dev mtdblock1, logical block 0, async page read
[ 17.872520] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[ 17.872644] block: unable to load configuration (fstab: Entry not found)
[ 17.878349] block: attempting to load /tmp/ubifs_cfg/etc/config/fstab
[ 17.885464] block: unable to load configuration (fstab: Entry not found)
[ 17.891622] block: attempting to load /etc/config/fstab
[ 17.898506] block: unable to load configuration (fstab: Entry not found)
[ 17.903495] block: no usable configuration

28.09.20181870Base systemBug ReportVery LowMediumOpenWrt bridge poor speed as HVM domU guest under XenSe...openwrt-18.06Unconfirmed Task Description

Hardware:
Wireless Adapter QCA9880 (PCI passthrough to OpenWrt guest)
Paravirtualized Adapter Network Adapter of XenServer (Netfront PCI driver)

XenServer 7.2 (all updates installed)
Virtualized OpenWRT 18.06.1 (stable build, x86_64, as guest — HVM with PV drivers domU)

All configuration is simply done, and Wi-Fi works on OpenWRT, have add Paravirtualized Adapter (vswitch bridged with LAN interface of Xenserver), then add it in Wireless configuration in web interface to bridge it, and do some speed tests over WiFi connection (from other VM → Virtual Ethernet bridget with WiFi → WiFi client) - download is great (maximum as possible), but upload (from WiFi → WiFi bridget with Virtual Ethernet → other VM) is terrible - it’s all time about 0.1-0.2 mbit (and TX packets is dropping on Paravirtualized Adapter Ethernet interface)!

Then i do some tests:

1. Install samba on guest OpenWRT to test download/upload speeds - all is great, speeds about maximum of WiFi speed. So - WiFi works normal. Try to test download/upload from OpenWRT to Xen (over Virtualized Ethernet bridge) - and all is great, speeds about maximum about OpenWRT storage speed!

2. Try routed network (NAT) on OpenWRT and speeds is better, but not good - download is about maximum of WiFi, upload about 4-10 mbit and very high unusual CPU usage.

3. Use both - internal (Single-Server Private Network) and External Network (based on NIC) each of them works identical with low speed OpenWrt bridge bug.
But when i make PCI Passthrought of Physical Ethernet NIC - it works without issues.

4. I have installed in same environment CentOS 7.5 with hostapd (same bridget Virtual Ethernet with PCI Passthrought WiFi) and it works good without any issues of speeds and CPU usage is not noticeable at all.

5. Then i compile kernel with full Xen guest support in kernel_menuconfig, but nothing changed.

So, it’s looks like problems in OpenWRT bridge with Wireless and Xen virtual Ethernet (before, i have successfully get it to work with same hardware in Hyper-V without any problems). Maybe i need to configure OpenWRT bridge to work properly with Xen virtual Ethernet, but i did not found any information on the web about it.

25.09.20181869Base systemBug ReportVery LowLowWRT610N V2 is not detected by the initial network confi...openwrt-18.06Unconfirmed Task Description

My WRT610N V2 is not detected by the initial network configuration script. The switch remains unconfigured and wlan/lan vlans are not created. The issue seems to be in:

openwrt/target/linux/brcm47xx/base-files/etc/board.d/01_network

as it does not have a case for this router. Here’s the model string from the live system:

root@OpenWrt:~# cat /tmp/sysinfo/model
Linksys WRT610N V2

The actual configuration is identical to the Linksys E3000 V1 and the switch and interfaces are correctly configured if the above string is added to the same case.

My firmware version:

OpenWrt 18.06.1 r7258-5eb055306f / LuCI openwrt-18.06 branch (git-18.228.31946-f64b152)

Board name if needed:

root@OpenWrt:~# cat /tmp/sysinfo/board_name
0x04cf:42

Thanks,
radicale

25.09.20181868KernelBug ReportVery LowHighkmod-netem: Unable to handle kernel NULL pointer derefe...TrunkUnconfirmed Task Description

Device is WRT1900ACv2, kernel version is 4.14.71
It is simple to reproduce, just invoke netem such as `tc qdisc add dev eth1 root netem delay 100ms`, it will crash immediately

24.09.20181867Base systemBug ReportVery LowLowCan't connect to WiFi network when using MAC filtering ...TrunkUnconfirmed Task Description

The AP/router is a TP-Link TD-W8970.It was just fine with previous LEDE versions (17.01.2 and 17.01.4 )

The wireless network is configured to hide the ESSID and allow only whitelisted MAC addresses.

A particular android tablet (Huawei Mediapad M3 10 lite running Android 7.0, with July 2018 patches) can't connect to the network while an Android phone is able to (LineageOS 14.1, Android 7.1.2).

If I disable either mac filtering or the hide essid option, the tablet is able to connect to the network. When both options are active, it can't. There's nothing in the syslog, not even a message like these that I get very often.

Mon Sep 24 08:45:45 2018 daemon.notice hostapd: Station da:a1:19:b6:76:18 not allowed to authenticate

Here's how /etc/config/wireless looks like:

config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11g'
        option path 'pci0000:00/0000:00:00.0/0000:01:00.0'
        option country 'ES'
        option legacy_rates '1'
        option channel '13'
        option distance '12'
        option htmode 'HT20'

config wifi-iface
        option device 'radio0'
        option mode 'ap'
        option ssid 'OpenWrt'
        option network 'lan'
        option encryption 'psk2+ccmp'
        option key '[edited]'
        option macfilter 'allow'
        list maclist '[edited]'
        option hidden '1'
 

I've tried to set the channel to auto, but that won't work either. Even though I only get this behaviour in a single client, it was working flawlessly with the previous LEDE version and that's why I consider this to be a bug.

24.09.20181866Base systemBug ReportVery LowMediumAn android client can't connect to the WiFi network whe...openwrt-18.06Unconfirmed Task Description

The AP/router is a TP-Link TD-W8970.It was just fine with previous LEDE versions (17.01.2 and 17.01.4 )

The wireless network is configured to hide the ESSID and allow only whitelisted MAC addresses.

A particular android tablet (Huawei Mediapad M3 10 lite running Android 7.0, with July 2018 patches) can't connect to the network while an Android phone is able to (LineageOS 14.1, Android 7.1.2).

If I disable either mac filtering or the hide essid option, the tablet is able to connect to the network. When both options are active, it can't. There's nothing in the syslog, not even a message like these that I get very often.

Mon Sep 24 08:45:45 2018 daemon.notice hostapd: Station da:a1:19:b6:76:18 not allowed to authenticate

Here's how /etc/config/wireless looks like:

config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11g'
        option path 'pci0000:00/0000:00:00.0/0000:01:00.0'
        option country 'ES'
        option legacy_rates '1'
        option channel '13'
        option distance '12'
        option htmode 'HT20'

config wifi-iface
        option device 'radio0'
        option mode 'ap'
        option ssid 'OpenWrt'
        option network 'lan'
        option encryption 'psk2+ccmp'
        option key '[edited]'
        option macfilter 'allow'
        list maclist '[edited]'
        option hidden '1'
 

I've tried to set the channel to auto, but that won't work either. Even though I only get this behaviour in a particular client, it was working flawlessly before upgrading to Openwrt-18.06 and so I think this could be a bug in OpenWrt.

24.09.20181865Base systemBug ReportVery LowLowsysupgrade -v firmware.img Can't open device for writi...openwrt-18.06Unconfirmed Task Description

HI!
My router Tp-Link TD-W8970 v1.2 with flash 16M
u-boot is compiled from https://github.com/GreenTeaDev/u-boot/tree/tdw8970-16m and flashed in flash by the programmer
My modifications are in mypatch_18.06.1.patch
I downloaded the firmware of my own modification through UART

setenv ipaddr 192.168.1.1
setenv serverip 192.168.1.2
setenv bootargs 'board=WD8970'
tftpboot 0x80800000 openwrt-lantiq-xrx200-tplink_tdw8970-16m-squashfs-sysupgrade-end.bin
sf erase 0x20000 0xfa0000
sf write 0x80800000 0x20000 $(filesize)
reset

When I try to burn the same file, I get an error:

root@OpenWrt:/tmp# sysupgrade  -v firmware.img
Saving config files...
etc/config/ddns
etc/config/dhcp
etc/config/dropbear
etc/config/firewall
etc/config/fstab
etc/config/luci
etc/config/network
etc/config/openvpn_recipes
etc/config/polipo
etc/config/rpcd
etc/config/samba4
etc/config/system
etc/config/ucitrack
etc/config/uhttpd
etc/config/upnpd
etc/config/wireless
etc/dropbear/authorized_keys
etc/dropbear/dropbear_rsa_host_key
etc/group
etc/hosts
etc/inittab
etc/luci-uploads/.placeholder
etc/opkg/keys/1035ac73cc4e59e3
etc/opkg/keys/5151f69420c3f508
etc/opkg/keys/72a57f2191b211e0
etc/opkg/keys/792d9d9b39f180dc
etc/opkg/keys/9a01db7703afac2b
etc/opkg/keys/9ef4694208102c43
etc/opkg/keys/b26f36ae0f4106d
etc/opkg/keys/b5043e70f9a75cde
etc/opkg/keys/c10b9afab19ee428
etc/opkg/keys/dace9d4df16896bf
etc/opkg/keys/dd6de0d06bbd3d85
etc/passwd
etc/profile
etc/rc.local
etc/samba/secrets.tdb
etc/samba/smb.conf
etc/samba/smbpasswd
etc/shadow
etc/shells
etc/sysctl.conf
etc/xattr.conf
Commencing upgrade. Closing all shell sessions.
Watchdog handover: fd=3
- watchdog -
killall: telnetd: no process killed
Sending TERM to remaining processes ... netifd odhcpd uhttpd dbus-daemon avahi-daemon ntpd dnsmasq polipo smbd wsdd2 smbd-notifyd cleanupd br2684ctl vdsl_cpe_contro ubusd logd rpcd
Sending KILL to remaining processes ... smbd
Switching to ramdisk...
Performing system upgrade...
Could not open mtd device: firmware
Could not open mtd device: firmware
Could not open mtd device: firmware
Can't open device for writing!
cat: write error: Broken pipe
sysupgrade aborte[ 1075.782393] reboot: Res▒
ROM VER: 1.1.4
CFG 05

What am I doing wrong?
Please, help Me.

23.09.20181864Base systemBug ReportVery LowLowImpossible to install/update any packages on WZR-HP-G30...TrunkUnconfirmed Task Description

I’ve installed 18.06.1 on Buffalo WZR-HP-G300NH (more times with sysupgrade and tftp), and I’m not able to install/upgrade any package. The same problem happens also with SNAPSHOT r8087-38a88ad, but it works with 17.01.6

I get errors like

Collected errors:
 * pkg_write_filelist: Failed to open //usr/lib/opkg/info/luci-lib-ip.list: I/O error.
 * opkg_install_pkg: Failed to extract data files for luci-lib-ip. Package debris may remain!
 * opkg_install_cmd: Cannot install package luci-ssl.
 * opkg_conf_write_status_files: Can't open status file //usr/lib/opkg/status: I/O error.

The problem seems related to jffs2 errors:

[    0.780920] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    8.406396] jffs2: notice: (415) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[    8.423476] mount_root: switching to jffs2 overlay
[  270.902671] jffs2: Write of 1989 bytes at 0x005ce6f8 failed. returned -5, retlen 962
[  270.931965] jffs2: Write of 1989 bytes at 0x005ceec0 failed. returned -5, retlen 0
[  270.939631] jffs2: Not marking the space at 0x005ceec0 as dirty because the flash driver returned retlen zero
[  270.950397] jffs2: Write of 68 bytes at 0x005ceec0 failed. returned -5, retlen 0
[  270.957838] jffs2: Not marking the space at 0x005ceec0 as dirty because the flash driver returned retlen zero
[  270.968584] jffs2: Write of 68 bytes at 0x005ceec0 failed. returned -5, retlen 0

Some more information is reported in:
https://forum.openwrt.org/t/impossible-to-install-update-any-packages-on-wzr-hp-g300nh-18-06-1/21666

21.09.20181862KernelBug ReportVery LowMediumnot working xhci-mtk USB 3.0openwrt-18.06Unconfirmed Task Description
 

- Xiaomi Mi WiFi Router 3G
- OpenWrt 18.06.1 r7258-5eb055306f
- After connecting the docking station(USB3.0 HDD docking station)- an error occurs, as indicated in the logs below.
• kernel log
[ 6.723777] usbcore: registered new interface driver usbfs
[ 6.729399] usbcore: registered new interface driver hub
[ 6.734904] usbcore: registered new device driver usb
[ 6.748554] xhci-mtk 1e1c0000.xhci: xHCI Host Controller
[ 6.753899] xhci-mtk 1e1c0000.xhci: new USB bus registered, assigned bus number 1
[ 6.765068] xhci-mtk 1e1c0000.xhci: hcc params 0×01401198 hci version 0×96 quirks 0×00210010 [ 6.773554] xhci-mtk 1e1c0000.xhci: irq 19, io mem 0x1e1c0000
[ 6.780252] hub 1-0:1.0: USB hub found
[ 6.784063] hub 1-0:1.0: 2 ports detected
[ 6.788660] xhci-mtk 1e1c0000.xhci: xHCI Host Controller
[ 6.793968] xhci-mtk 1e1c0000.xhci: new USB bus registered, assigned bus number 2
[ 6.801458] xhci-mtk 1e1c0000.xhci: Host supports USB 3.0 SuperSpeed
[ 6.808059] usb usb2: We don’t know the algorithms for LPM for this host, disabling LPM.
[ 6.816957] hub 2-0:1.0: USB hub found
[ 6.820769] hub 2-0:1.0: 1 port detected
[ 6.827692] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[ 6.845190] init: - preinit -
[ 7.235077] usb 2-1: new SuperSpeed USB device number 2 using xhci-mtk
[ 7.319396] random: procd: uninitialized urandom read (4 bytes read)
[ 7.550284] mtk_soc_eth 1e100000.ethernet: PPE started
[ 10.771163] UBIFS (ubi0:1): background thread “ubifs_bgt0_1” started, PID 485
[ 10.845628] UBIFS (ubi0:1): recovery needed
[ 11.031450] UBIFS (ubi0:1): recovery completed
[ 11.036066] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name “rootfs_data” [ 11.043862] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 11.053756] UBIFS (ubi0:1): FS size: 112373760 bytes (107 MiB, 885 LEBs), journal size 5586944 bytes (5 MiB, 44 LEBs)
[ 11.064327] UBIFS (ubi0:1): reserved for root: 4952683 bytes (4836 KiB)
[ 11.070963] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID 2748C915-40E4-4121-B2E0-E1B496DE7D66, small LPT model
[ 11.095502] mount_root: loading kmods from internal overlay
[ 11.222556] kmodloader: loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/*
[ 11.463453] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
[ 11.508096] SCSI subsystem initialized
[ 11.524655] ehci-platform: EHCI generic platform driver
[ 11.544381] usbcore: registered new interface driver usb-storage
[ 11.556203] scsi host0: uas
[ 11.559794] xhci-mtk 1e1c0000.xhci: ERROR Transfer event for unknown stream ring slot 1 ep 4
[ 11.568217] xhci-mtk 1e1c0000.xhci: @000000000f79b170 0ea7e000 00000000 05000000 01058001
[ 11.576364] xhci-mtk 1e1c0000.xhci: ERROR Transfer event for unknown stream ring slot 1 ep 6
[ 11.584771] xhci-mtk 1e1c0000.xhci: @000000000f79b180 0ea7e100 00000000 05000000 01078001
[ 32.574874] scsi 0:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[ 32.582434] scsi 0:0:0:0: tag#0 CDB: opcode=0×12 12 00 00 00 24 00
[ 32.588688] xhci-mtk 1e1c0000.xhci: Mismatch between completed Set TR Deq Ptr command & xHCI internal state.
[ 32.598474] xhci-mtk 1e1c0000.xhci: ep deq seg = 8e9ce700, deq ptr = ae9fb010
[ 33.684839] scsi host0: uas_eh_device_reset_handler FAILED to get lock err -16
[ 33.692042] scsi 0:0:0:0: Device offlined - not ready after error recovery
[ 33.699312] usbcore: registered new interface driver uas
[ 33.705028] kmodloader: done loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/*
[ 33.937005] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[ 33.950739] block: extroot: not configured
[ 33.998265] mount_root: switching to ubifs overlay
• system log
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.723777] usbcore: registered new interface driver usbfs
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.729399] usbcore: registered new interface driver hub
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.734904] usbcore: registered new device driver usb
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.748554] xhci-mtk 1e1c0000.xhci: xHCI Host Controller
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.753899] xhci-mtk 1e1c0000.xhci: new USB bus registered, assigned bus number 1
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.765068] xhci-mtk 1e1c0000.xhci: hcc params 0×01401198 hci version 0×96 quirks 0×00210010 Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.773554] xhci-mtk 1e1c0000.xhci: irq 19, io mem 0x1e1c0000
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.780252] hub 1-0:1.0: USB hub found
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.784063] hub 1-0:1.0: 2 ports detected
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.788660] xhci-mtk 1e1c0000.xhci: xHCI Host Controller
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.793968] xhci-mtk 1e1c0000.xhci: new USB bus registered, assigned bus number 2
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.801458] xhci-mtk 1e1c0000.xhci: Host supports USB 3.0 SuperSpeed
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.808059] usb usb2: We don’t know the algorithms for LPM for this host, disabling LPM.
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.816957] hub 2-0:1.0: USB hub found
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 6.820769] hub 2-0:1.0: 1 port detected
Thu Sep 20 12:22:42 2018 user.info kernel: [ 6.827692] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
Thu Sep 20 12:22:42 2018 user.info kernel: [ 6.845190] init: - preinit -
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 7.235077] usb 2-1: new SuperSpeed USB device number 2 using xhci-mtk
Thu Sep 20 12:22:42 2018 kern.notice kernel: [ 7.319396] random: procd: uninitialized urandom read (4 bytes read)
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 7.550284] mtk_soc_eth 1e100000.ethernet: PPE started
Thu Sep 20 12:22:42 2018 kern.notice kernel: [ 10.771163] UBIFS (ubi0:1): background thread “ubifs_bgt0_1” started, PID 485
Thu Sep 20 12:22:42 2018 kern.notice kernel: [ 10.845628] UBIFS (ubi0:1): recovery needed
Thu Sep 20 12:22:42 2018 kern.notice kernel: [ 11.031450] UBIFS (ubi0:1): recovery completed
Thu Sep 20 12:22:42 2018 kern.notice kernel: [ 11.036066] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name “rootfs_data” Thu Sep 20 12:22:42 2018 kern.notice kernel: [ 11.043862] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Thu Sep 20 12:22:42 2018 kern.notice kernel: [ 11.053756] UBIFS (ubi0:1): FS size: 112373760 bytes (107 MiB, 885 LEBs), journal size 5586944 bytes (5 MiB, 44 LEBs)
Thu Sep 20 12:22:42 2018 kern.notice kernel: [ 11.064327] UBIFS (ubi0:1): reserved for root: 4952683 bytes (4836 KiB)
Thu Sep 20 12:22:42 2018 kern.notice kernel: [ 11.070963] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID 2748C915-40E4-4121-B2E0-E1B496DE7D66, small LPT model
Thu Sep 20 12:22:42 2018 user.info kernel: [ 11.095502] mount_root: loading kmods from internal overlay
Thu Sep 20 12:22:42 2018 user.info kernel: [ 11.222556] kmodloader: loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/*
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 11.463453] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
Thu Sep 20 12:22:42 2018 kern.notice kernel: [ 11.508096] SCSI subsystem initialized
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 11.524655] ehci-platform: EHCI generic platform driver
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 11.544381] usbcore: registered new interface driver usb-storage
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 11.556203] scsi host0: uas
Thu Sep 20 12:22:42 2018 kern.err kernel: [ 11.559794] xhci-mtk 1e1c0000.xhci: ERROR Transfer event for unknown stream ring slot 1 ep 4
Thu Sep 20 12:22:42 2018 kern.err kernel: [ 11.568217] xhci-mtk 1e1c0000.xhci: @000000000f79b170 0ea7e000 00000000 05000000 01058001
Thu Sep 20 12:22:42 2018 kern.err kernel: [ 11.576364] xhci-mtk 1e1c0000.xhci: ERROR Transfer event for unknown stream ring slot 1 ep 6
Thu Sep 20 12:22:42 2018 kern.err kernel: [ 11.584771] xhci-mtk 1e1c0000.xhci: @000000000f79b180 0ea7e100 00000000 05000000 01078001
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 32.574874] scsi 0:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 32.582434] scsi 0:0:0:0: tag#0 CDB: opcode=0×12 12 00 00 00 24 00
Thu Sep 20 12:22:42 2018 kern.warn kernel: [ 32.588688] xhci-mtk 1e1c0000.xhci: Mismatch between completed Set TR Deq Ptr command & xHCI internal state.
Thu Sep 20 12:22:42 2018 kern.warn kernel: [ 32.598474] xhci-mtk 1e1c0000.xhci: ep deq seg = 8e9ce700, deq ptr = ae9fb010
Thu Sep 20 12:22:42 2018 kern.err kernel: [ 33.684839] scsi host0: uas_eh_device_reset_handler FAILED to get lock err -16
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 33.692042] scsi 0:0:0:0: Device offlined - not ready after error recovery
Thu Sep 20 12:22:42 2018 kern.info kernel: [ 33.699312] usbcore: registered new interface driver uas
• dmesg | grep usb
[ 6.723777] usbcore: registered new interface driver usbfs
[ 6.729399] usbcore: registered new interface driver hub
[ 6.734904] usbcore: registered new device driver usb
[ 6.808059] usb usb2: We don’t know the algorithms for LPM for this host, dis abling LPM.
[ 7.235077] usb 2-1: new SuperSpeed USB device number 2 using xhci-mtk
[ 11.544381] usbcore: registered new interface driver usb-storage
[ 33.699312] usbcore: registered new interface driver uas
• lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-mtk/1p, 5000M

|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M

/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-mtk/2p, 480M
• list-installed | grep usb
kmod-usb-core - 4.14.63-1
kmod-usb-ehci - 4.14.63-1
kmod-usb-ledtrig-usbport - 4.14.63-1
kmod-usb-storage - 4.14.63-1
kmod-usb-storage-uas - 4.14.63-1
kmod-usb2 - 4.14.63-1
kmod-usb3 - 4.14.63-1
libusb-1.0 - 1.0.22-1
usbutils - 007-7
• lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

20.09.20181861Base systemBug ReportVery LowMediumWIFI TX power cannot be set to maximum on TP-Link TL-WR...openwrt-18.06Unconfirmed Task Description

OpenWrt 18.06.1 r7258-5eb055306f / LuCI openwrt-18.06 branch (git-18.228.31946-f64b152)

In the /etc/config/wireless, when I set the country to ‘BR’, channel to ‘13’ and txpower to 20. After wifi down/wifi or reboot, the iwinfo reports Tx-Power: 16 dbm.
If I set the country to ‘US’, channel to whatever and txpower to 21, the iwinfo reports Tx-Power: 21 dbm.
Below is the configuration details for country = ‘BR’:

wireless.radio0=wifi-device
wireless.radio0.type=’mac80211’ wireless.radio0.path=’platform/ar934x_wmac’ wireless.radio0.hwmode=’11g’ wireless.radio0.htmode=’HT20’ wireless.radio0.beacon_int=’100’ wireless.radio0.disabled=’0’ wireless.radio0.txpower=’20’ wireless.radio0.country=’BR’ wireless.radio0.channel=’13’ wireless.radio0.legacy_rates=’1’ wireless.radio0.antenna_gain=’0’

Below is the iwinfo output:
wlan0 ESSID: “WIFI xxxxxxxx”

        Access Point: xx:xx:xx:xx:xx:xx
        Mode: Master  Channel: 13 (2.472 GHz)
        Tx-Power: 16 dBm  Link Quality: 38/70
        Signal: -72 dBm  Noise: -95 dBm
        Bit Rate: 16.3 MBit/s
        Encryption: WPA2 PSK (CCMP)
        Type: nl80211  HW Mode(s): 802.11bgn
        Hardware: unknown [Generic MAC80211]
        TX power offset: unknown
        Frequency offset: unknown
        Supports VAPs: yes  PHY name: phy0


20.09.20181860KernelBug ReportVery LowMediumBroken WLAN5G LED on TP-Link WDR-4300TrunkUnconfirmed Task Description

WLAN5G led becomes inactive after the following commit
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=ccab68f2d399d2395a18d1fb3495fe7e048fe054

though WLAN2G is unaffected.
Build with this commit reverted fixes WLAN5G led.


20.09.20181859Base systemBug ReportVery LowLowuclibc++ crashes when trying to splice to empty listTrunkUnconfirmed Task Description

Right now, each program seems to crash which uses splice to move an item to another list (which is empty):

  #include <list>
  
  int main()
  {
  	std::list<int> empty_list;
  	std::list<int> two_item_list;
  
  	two_item_list.push_back(1);
  	two_item_list.push_back(2);
  
  	empty_list.splice(empty_list.end(), two_item_list, two_item_list.begin());
  
  	return 0;
  }

It crashes with:

  4         {
  1: two_item_list = {list_start = 0x1, list_end = 0x77f0d57f <blobmsg_add_field+42>, elements = 2012192832, a = {<No data fields>}}
  2: empty_list = {list_start = 0x0, list_end = 0x77ec51ec <operator new(unsigned int)+44>, elements = 32, a = {<No data fields>}}
  (gdb) n
  151             std::list<int> empty_list;
  1: two_item_list = {list_start = 0x1, list_end = 0x77f0d57f <blobmsg_add_field+42>, elements = 2012192832, a = {<No data fields>}}
  2: empty_list = {list_start = 0x0, list_end = 0x77ec51ec <operator new(unsigned int)+44>, elements = 32, a = {<No data fields>}}
  (gdb) n
  5             std::list<int> two_item_list;
  1: two_item_list = {list_start = 0x1, list_end = 0x77f0d57f <blobmsg_add_field+42>, elements = 2012192832, a = {<No data fields>}}
  2: empty_list = {list_start = 0x77eb0910, list_end = 0x77eb0910, elements = 0, a = {<No data fields>}}
  (gdb) n
  6             two_item_list.push_back(1);
  1: two_item_list = {list_start = 0x77eb0930, list_end = 0x77eb0930, elements = 0, a = {<No data fields>}}
  2: empty_list = {list_start = 0x77eb0910, list_end = 0x77eb0910, elements = 0, a = {<No data fields>}}
  (gdb) n
  7             two_item_list.push_back(2);
  1: two_item_list = {list_start = 0x77eb0950, list_end = 0x77eb0930, elements = 1, a = {<No data fields>}}
  2: empty_list = {list_start = 0x77eb0910, list_end = 0x77eb0910, elements = 0, a = {<No data fields>}}
  (gdb) n
  8             empty_list.splice(empty_list.end(), two_item_list, two_item_list.begin());
  1: two_item_list = {list_start = 0x77eb0950, list_end = 0x77eb0930, elements = 2, a = {<No data fields>}}
  2: empty_list = {list_start = 0x77eb0910, list_end = 0x77eb0910, elements = 0, a = {<No data fields>}}
  (gdb) n
  
  Program received signal SIGSEGV, Segmentation fault.
  std::list<int, std::allocator<int> >::splice (i=..., x=..., position=..., this=0x7ffffb98) at /usr/src/openwrt/staging_dir/target-mips_24kc_musl-1.1.16/usr/include/uClibc++/list:608
  608                             i.link_struct()->previous->next = i.link_struct()->next;

The reported line is

  605                 //Insert at begining special case
  606                 if(position == begin()){
  607 
  608                         i.link_struct()->previous->next = i.link_struct()->next;
  609                         i.link_struct()->next->previous = i.link_struct()->previous;
  610 
  611                         i.link_struct()->previous = 0;
  612                         i.link_struct()->next = position.link_struct();
  613                         position.link_struct()->previous = i.link_struct();
  614 
  615                         list_start = i.link_struct();
  616 
  617                         --x.elements;
  618                         ++elements;
  619                         return;
  620                 }
19.09.20181857Base systemBug ReportVery LowLowpppd 14 failed attempts to set up wan (+ system log spa...TrunkUnconfirmed Task Description

Device: TD-W8970 v1
OpenWRT version affected:

  • LEDE 17.0x NOT AFFECTED
  • 18.06.00 NOT TESTED
  • 18.06.01 YES
  • 18.06 SNAPSHOT (r7313-4f6ad3c13a) YES
  • master YES

Protocol: PPPoA (other not tested).

What happen:

Too many early attempts to bring up the wan interface. The system logs is filled with:

daemon.notice netifd: Interface 'wan' is setting up now
daemon.info pppd[<pid>]: Plugin pppoatm.so loaded.
daemon.info pppd[<pid>]: PPPoATM plugin_init
daemon.info pppd[<pid>]: PPPoATM setdevname_pppoatm - SUCCESS:0.8.35
daemon.notice pppd[<pid>]: pppd 2.4.7 started by root, uid 0
daemon.err pppd[<pid>]: connect(0.8.35): No such device
daemon.info pppd[<pid>]: Exit.
daemon.notice netifd: Interface 'wan' is now down

14 attempts before successful one. This wasn’t the case on LEDE where only 1 failed attempt was made.
After all the failed connection, this shows up:

daemon.notice dsl-notify: Switching to TC-Layer ATM
kern.info kernel: [<time>] ATM1.0.26    ATM (A1) firmware version 0.24
kern.warn kernel: [<time>] ifxmips_atm: ATM init succeed

... and after that, finally:

daemon.info pppd[2218]: Plugin pppoatm.so loaded.
daemon.info pppd[<pid>]: PPPoATM plugin_init
daemon.info pppd[<pid>]: PPPoATM setdevname_pppoatm - SUCCESS:0.8.35
daemon.notice pppd[<pid>]: pppd 2.4.7 started by root, uid 0
kern.info kernel: [<time>] pppoa-wan: renamed from ppp0
daemon.info pppd[<pid>]: Using interface pppoa-wan
daemon.notice pppd[<pid>]: Connect: pppoa-wan <--> 0.8.35
daemon.info pppd[<pid>]: CHAP authentication succeeded
daemon.notice pppd[<pid>]: CHAP authentication succeeded
daemon.notice pppd[<pid>]: local  IP address 151.95.61.61
daemon.notice pppd[<pid>]: remote IP address 151.6.141.72
daemon.notice netifd: Network device 'pppoa-wan' link is up
daemon.notice netifd: Interface 'wan' is now up

Regarding the whole “Switching to TC-Layer ATM” block of messages:
* I do not know if is 100% needed to properly setup wan ..
* ... but for sure I’ve always seen failed attempts before it and the successful one after it ...
* Sometimes there is 1 more failed attempt after the “Switching to TC-Layer ATM” stuffs (and before the successful one).
* I do not know if is triggered by the failures or if is simple placed “too late” in the boot order

Also:
* After the first failure all the other after it will also trigger warnings (more spam inside logs) form insmod since each needed module (slhc, ppp_generic and pppoatm) is already loaded.
* On LEDE the whole process required only one “failure”

19.09.20181856Base systemBug ReportVery LowMediumConfig problems after hard power downopenwrt-18.06Unconfirmed Task Description

Netgear WNDR3700V2, OpenWrt 18.06.1

Installed approx. 1 month ago with minimal configuration changes (wifi setup, 2 port forwards), all worked well. Yesterday after power outage now multiple clients on my vlan are getting assigned the external wlan IP address, and naturally reporting conflicts.
Not sure why the firewall stopped working, and I apologize for not having more details about the problem. Please let me know if there is additional data I should collect and share (and soon, as I plan to reflash this evening.)


19.09.20181855Base systemBug ReportVery LowHighUSB works ONLY with WiFi disabledopenwrt-18.06Unconfirmed Task Description

The problem occurs on Netgear WNDR3700v3 USING latest 18.06.

After setting up the router and installing required USB packages then rebooting the router, USB can’t be accessed. USB LED indicator light flickers few times during booting of the router, then shuts off. Using DMESG later I see that USB connects, then suddenly disconnects. The ONLY way to use USB functionality is to DISABLE WIFI.

To simply reproduce the issue, flash openwrt to your wndr3700v3, install required base USB packages.

1.) Disable wifi and find USB devices working normally.
2.) Enable Wifi and find USB devices not working and not being powered. (no led indicator on USB).

Use DMESG to see USB being recognized during boot and then simply later disconnected for no reason whatsoever.

The same issue did occur on 17.01. with the same behavior.

Showing tasks 51 - 100 of 660 Page 2 of 14 - 1 - 2 - 3 - 4 - 5 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing