OpenWrt/LEDE Project

Welcome to the OpenWrt Project bug reporting and issue tracking system

Problems to be reported here are for the current OpenWrt and legacy LEDE Project’s targets, sources, toolchain, core packages, build procedures, distribution and infrastructure. Guidelines for submitting a good bug report can be found at the OpenWrt 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 openwrt-bugs@infradead.org.

OpenedIDCategoryTask TypePrioritySeveritySummary  ascReported InStatus
29.05.20213835Base systemBug ReportVery LowLow [MT7621] Hardware flow offloading doesn't work for PPP...openwrt-21.02Unconfirmed Task Description

Netgear R6220
OpenWrt 21.02-SNAPSHOT r16122-c213

Hardware flow offloading doesn’t work for PPPoE with VLAN (802.1q), so LAN to WAN is slow and CPU heavy. It does work on 19,07, though.

31.10.20203417Base systemBug ReportVery LowMedium /etc/config/luci seems to be corrupt, unable to find s...openwrt-19.07Unconfirmed Task Description

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

 

OpenWRT 19.07.4 on xRX200 rev 1.2 (BT Home Hub 5A) with all packages up to date.
After running the router for a while I’ll try to login to the page and get this error:
/usr/lib/lua/luci/dispatcher.lua:426: /etc/config/luci seems to be corrupt, unable to find section ‘main’

This would normally be accompanied with the 5GHz channel set to 149 (which is a paid-for channel in the UK).
Checking /etc/config/luci looks fine to me and sometimes service rcpd restart works but other times it leaves Luci in an unusable state.

07.06.20203159Base systemBug ReportVery LowMedium 802.11r default settings are inappropriate, need to ch...TrunkUnconfirmed Task Description

Enabling 802.11r in LuCI auto populates with two default settings that break 802.11r functionality for most devices (though tested extensively on latest Apple iOS devices).

Bug: The current defaults for FT Protocol (FT Over DS) and Reassociation Deadline (1000) break iOS and other devices support for 802.11r.

Solution: Change the current default for FT Protocol to FT over the air and for Reassociation Deadline to 20000.

Support for these new defaults: According to papers from Cisco (https://www.cisco.com/c/dam/en/us/td/docs/wireless/controller/technotes/8-6/Enterprise_Best_Practices_for_iOS_devices_and_Mac_computers_on_Cisco_Wireless_LAN.pdf) FT over the air is the method supported by Apple devices and recommended. Furthermore, Cisco’s Reassocation Deadline is a default value of 20 seconds (https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/80211r-ft/b-80211r-dg.html), which would translate to roughly 20000 when used as an OpenWRT setting.

My testing confirms the OpenWRT default values do not work with iOS (FT Over DS is not recognized, and if FT over the air is used with the original Reassocation Deadline of 1000 (roughly 1 second) transition is badly broken as devices will get kicked from their initial AP before associating with the next AP, which removes them from WiFi completely).

For one final piece of support, the 802.11r implementation used with Ubiquity systems is also FT Over the Air: https://community.ui.com/questions/802-11r-question/743b903c-3ad1-4ab6-897f-ebc24269130d I am unsure of their Reassocation Deadline default but I have found the setting of 20000 (which matches Cisco) to work very well in my testing.

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

Periodically (every 4 to 12 hours) the AP (Ubiquiti UniFi-AC-LITE) resets its kernel firmware, dropping all clients and resetting. It then recovers and clients re-connect after about 5 to 10 minutes. I get the following in the system log:

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

Supply the following if possible:
- Device problem occurs on

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

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

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

- Steps to reproduce

 

- Occurs every 4-12 hours of normal use.

08.06.20213860ToolchainBuild FailureVery LowHigh bcm53xx: Image Builder fails with "os-image partition ...openwrt-21.02Unconfirmed Task Description

I use the Image Builder to build image for my NETGEAR R8000.
Firstly, I tried to build with the command which I had use many times in 19.07.03.But I got error message like this:

WARNING: maxlen exceeds default maximum!  Beware of overwriting nvram!
os-image partition too big (more than 2097152 bytes): Success
make[3]: *** [Makefile:456: /media/nautilus/Data/Personal/Router/openwrt/21.02-RC2/openwrt-imagebuilder-21.02.0-rc2-bcm53xx-generic.Linux-x86_64/build_dir/target-arm_cortex-a9_musl_eabi/linux-bcm53xx_generic/tmp/openwrt-21.02.0-rc2-bcm53xx-generic-tplink_archer-c5-v2-squashfs.bin] Error 1
make[2]: *** [Makefile:186: build_image] Error 2
make[1]: *** [Makefile:124: _call_image] Error 2
make: *** [Makefile:240: image] Error 2

Then, I use the default command like this:

make image PROFILE=netgear_r8000

But I got the same error message.
I can’t get any useful message from the error message. And I can build image successfully with v19.07.03. That means the envirment is well.

21.02.20192139Base systemBug ReportVery LowMedium broadcom-wl don't work on rt-n16openwrt-19.07Unconfirmed Task Description

wifi on lede 17.01.6, with the same config, works great
install openwrt 18.06
opkg remove kmod-b43 kmod-b43legacy kmod-mac80211 kmod-cfg80211 kmod-brcmsmac
opkg install kmod-brcm-wl nas wlc wl
wl -i wl0 chanspec -c 9 -b 2 -w 40 -s -1

config wifi-device ‘wl0’

      option type 'broadcom'
      option channel '9'
      option hwmode '11ng'
      option htmode 'HT40'
      option txpower '16'
      option txantenna '3'
      option rxantenna '3'

config wifi-iface

      option device 'wl0'
      option network 'lan'
      option mode 'ap'
      option ssid 'point'
      option encryption 'psk2'
      option key 'pass'
      option wmm '1'
      option disabled '0'

After, my laptop (windows) does not connect and the phone on the android
connects for 15-20 minutes, disconnects, manually connects from the third fourth attempt
and disconnects again after a while

ifconfig shows that the interface wl0-1 is automatically created with non-existent mac address E2:CB:4E:C0:18:14 (wl0 E0:CB:4E:C0:18:13)
Wi-Fi scanner shows two access points with the same name, channels, but different MAC addresses (E2:CB:4E:C0:18:14, E0:CB:4E:C0:18:13)

I compiled two firmware with
CONFIG_TARGET_brcm47xx=y
CONFIG_TARGET_brcm47xx_mips74k=y
CONFIG_TARGET_brcm47xx_mips74k_DEVICE_asus-rt-n16=y
and
CONFIG_TARGET_brcm47xx=y
CONFIG_TARGET_brcm47xx_mips74k=y
CONFIG_TARGET_brcm47xx_mips74k_Broadcom-mips74k-wl=y

but it did not help

 



11.08.20213974Base systemBug ReportVery LowLow CONFIG_KERNEL_KALLSYMS not set for x86 images making b...TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

Virtualbox VM 64 bit

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

19.07.8

- Steps to reproduce

An example of a backtrace sans symbols is attached.

 


02.07.20213910KernelBug ReportVery LowMedium hilink's hlk7628n board has a reboot problemopenwrt-21.02Unconfirmed Task Description

the 7628 board from hilink has a problem when rebooting.
When requesting reboot both by luci and by console the board stops working.

root@OpenWrt:/# reboot
root@OpenWrt:/# [ 143.119741] br-lan: port 1(eth0.1) entered disabled state
[ 143.148530] device eth0.1 left promiscuous mode
[ 143.157595] device eth0 left promiscuous mode
[ 143.166398] br-lan: port 1(eth0.1) entered disabled state
[ 147.583416] reboot: Restarting system

08.10.20214071Base systemBug ReportVery LowMedium Lantiq-VRX200 modem is using wrong line modeopenwrt-21.02Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on
- AVM Fritz 7412
- Lantiq-VRX200

- Software versions of OpenWrt/LEDE release, packages, etc.
21.02.0 (r16279-5cc0535800)

- Steps to reproduce
- Flash firmware
- Enter ISP configuration for 1&1 (https://openwrt.org/docs/guide-user/network/wan/isp-configurations)
- Download and use the modem firmware supplied by AVM: 5.9.0.12.1.7 or 5.9.1.4.0.7

Openwrt will be using: Line Mode: G.993.2 (VDSL2 with down- and upstream vectoring)
instead of: Line Mode: G.993.5 (VDSL2 with down- and upstream vectoring)
which is used by the stock fritz box firmware. This results in a speed decrease from possible
Max. Attainable Data Rate (ATTNDR): 133.841 Mb/s (down) to 25.000 Mb/s (down)


21.07.20213946PackagesBug ReportVery LowCritical lldpd needs update to fix CVE-2020-27827openwrt-19.07Unconfirmed Task Description

the current verion 1.0.3 on 19.07 needs a update to fix CVE-2020-27827

read https://github.com/lldpd/lldpd/releases

21.03.20213699Base systemBug ReportVery LowLow MT7620 platform with spi flash has very low read & wri...TrunkUnconfirmed Task Description

Device: Youku YK-L1(in fact I believe in all mt7620, rt3883, rt305x devices)
Software versions: v19.07
Problem: YK-L1 has a 32 MB flash chip and device has very poor flash read and write performance. It will need 10 minutes to format filesystem after install OpenWrt.
Reason: In kernel config file(/target/linux/ramips/mt7620/config-xxx) it defined CONFIG_MTD_SPI_NOR_USE_4K_SECTORS=y. But MT7621 and MT7628 do not has this define. So one block is only 4 KB in MT7620 but 64 KB in MT7628/MT7621. MT7628 is much faster than MT7620 in the same spi frequency.
I do not know why we use 4K sectors in these platform because it seems like won’t waste storage space by set block size to 64 KB.

Here is a rt5350 device and we can see erasesize is 4 KB, same as mt7620.
root@OpenWrt:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00020000 00001000 “u-boot” mtd1: 00010000 00001000 “factory” mtd2: 003d0000 00001000 “firmware” mtd3: 0013891e 00001000 “kernel” mtd4: 002976e2 00001000 “rootfs” mtd5: 00039000 00001000 “rootfs_data”

12.06.20213871Base systemBug ReportVery LowLow netifd: radioX (pid): ./mac80211.sh: eval: line 1: 1=0...TrunkUnconfirmed Task Description

Device: Totolink x5000r
OpenWrt SNAPSHOT r16925-b721579842
LUCI Master (git-21.160.71743-e3bf521)

Message in syslog when configuring AX radio from LUCI:

Sat Jun 12 09:24:17 2021 daemon.notice netifd: radio0 (27492): ./mac80211.sh: eval: line 1: 1=0: not found

Function mac80211_add_he_capabilities in file /lib/netifd/wireless/mac80211.sh is called with arguments:

he_su_beamformer:12:0x80:1 he_su_beamformee:6d:0x1:0 he_mu_beamformer:6d:0x2:1 he_spr_sr_control:06:0x1:0 he_twt_required:08:0x6:0

Line 119 should probably be eval “$1=0” instead of eval “$4=0”

12.04.20181486PackagesBug ReportVery LowLow`ping` from `iputils-ping` is not respecting the `-I` o...TrunkUnconfirmed Task Description

There’re two WAN connections in my router. I installed `iputils-ping` for some fancy features. If I use `ping -I wan2 x.x.x.x`, the ICMP Echo request will still be sent from the main wan interface, ignoring the `-I` option. Busybox ping doesn’t have this problem.

The iputils-* packages are version 20101006. This issue is solved by this commit and I suggest that the iputils packages should be updated.

22.11.20214150Base systemBug ReportVery LowLow./script/feeds does not return error on failureTrunkUnconfirmed Task Description

Hello,

Script feeds always returns 0, no matter if it did what it was asked to or not

$ ./scripts/feeds install foobar && echo ok || echo err
WARNING: No feed for package 'foobar' found
ok


15.08.20181781Base systemBug ReportVery LowMedium"/sbin/block detect" reports improper uuid for raid par...AllWaiting on reporter Task Description

This bug is device independent (I think).

As a result of this bug, /etc/config/fstab may contain damaged content, and also block mount may fail.

‘block detect’ reports bad uuid for /dev/sda1 (and others) mixing inside uuid of raid volume with outside of the partitions.
Bug is ‘block detect’ showing the same uuid for /dev/sda1 and /dev/md1 while they are different, as you can observe in /sbin/blkid output at the middle of output below.

Important: /sbin/blkid from busybox may have same/similar bug as its reporting even different uuid. The standalone /usr/sbin/blkid works properly (shown in the middle of below) and should be basis for comparison.

root@bee:/tmp# block detect
config 'global'
        option  anon_swap       '0'
        option  anon_mount      '0'
        option  auto_swap       '1'
        option  auto_mount      '1'
        option  delay_root      '5'
        option  check_fs        '0'

config 'mount'
        option  target  '/mnt/sda1'
        option  uuid    '48f38899-5efb-4477-adca-bf11d81df99f'
        option  enabled '0'

config 'mount'
        option  target  '/mnt/sdb1'
        option  uuid    '48f38899-5efb-4477-adca-bf11d81df99f'
        option  enabled '0'

config 'mount'
        option  target  '/mnt/md1'
        option  uuid    '48f38899-5efb-4477-adca-bf11d81df99f'
        option  enabled '0'


root@bee:/tmp# which blkid
/usr/sbin/blkid
root@bee:/tmp# blkid
/dev/mtdblock5: TYPE="squashfs"
/dev/sda1: UUID="8b2d137c-4973-133d-6de4-7e91c4a4cdb0" TYPE="linux_raid_member" PARTUUID="f6eb912c-6ef7-4b8b-90d7-3ccc4e05d0c3"
/dev/sdb1: UUID="8b2d137c-4973-133d-6de4-7e91c4a4cdb0" TYPE="linux_raid_member" PARTUUID="731a8023-5734-463e-8866-46ea97a3f928"
/dev/md1: LABEL="OVERLAYROOT" UUID="48f38899-5efb-4477-adca-bf11d81df99f" TYPE="ext4"


root@bee:/tmp# /sbin/blkid
/dev/md1: LABEL="OVERLAYROOT" UUID="48f38899-5efb-4477-adca-bf11d81df99f" TYPE="ext4"
/dev/sda1: UUID="7c132d8b-3d13-7349-917e-e46db0cda4c4" TYPE="linux_raid_member"
/dev/sdb1: UUID="7c132d8b-3d13-7349-917e-e46db0cda4c4" TYPE="linux_raid_member"
18.01.20181282KernelBuild FailureVery LowLow"CONFIG_STRIP_KERNEL_EXPORTS" breaks kernel compilation...TrunkUnconfirmed Task Description

Target: brcm2708_bcm2710 (rpi-3)
Affected openwrt revision: git-head (26045049baf646aa2ce3dce78106da5acf4936ea)
(openwrt-17.01 is not affected)

  • Reproducing

git clone https://git.openwrt.org/openwrt/openwrt.git ; cd openwrt
make menuconfig
# Select:
# Target: Broadcom BCM27xx
# Subtarget: BCM2710 64 bit based boards
# Global build settings —> Strip unnecessary exports from the kernel image: Enabled
make -j 1 V=s

  • Build log
make -C /home/torte/openwrt/nfs/openwrt/build_dir/target-aarch64_cortex-a53_musl/linux-brcm2708_bcm2710/linux-4.9.76 HOSTCFLAGS="-O2 -I/home/torte/openwrt/nfs/openwrt/staging_dir/host/include  -Wall -Wmissing-prototypes -Wstrict-prototypes" CROSS_COMPILE="aarch64-openwrt-linux-musl-" ARCH="arm64" KBUILD_HAVE_NLS=no KBUILD_BUILD_USER="" KBUILD_BUILD_HOST="" KBUILD_BUILD_TIMESTAMP="Thu Jan 18 10:39:42 2018" KBUILD_BUILD_VERSION="0" HOST_LOADLIBES="-L/home/torte/openwrt/nfs/openwrt/staging_dir/host/lib" CONFIG_SHELL="bash" V=''  cmd_syscalls= KERNELRELEASE=4.9.76 EXTRA_LDSFLAGS="-I/home/torte/openwrt/nfs/openwrt/build_dir/target-aarch64_cortex-a53_musl/linux-brcm2708_bcm2710 -include symtab.h" CC="aarch64-openwrt-linux-musl-gcc" modules
make[5]: Entering directory '/home/torte/openwrt/nfs/openwrt/build_dir/target-aarch64_cortex-a53_musl/linux-brcm2708_bcm2710/linux-4.9.76'
  CHK     include/config/kernel.release
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
  CHK     include/generated/bounds.h
  CHK     include/generated/timeconst.h
  CHK     include/generated/asm-offsets.h
  CALL    scripts/checksyscalls.sh
  LDS     arch/arm64/kernel/vdso/vdso.lds
cc1: fatal error: symtab.h: No such file or directory
compilation terminated.
scripts/Makefile.build:405: recipe for target 'arch/arm64/kernel/vdso/vdso.lds' failed
make[6]: *** [arch/arm64/kernel/vdso/vdso.lds] Error 1
arch/arm64/Makefile:145: recipe for target 'vdso_prepare' failed
make[5]: *** [vdso_prepare] Error 2
  • Details

The option CONFIG_STRIP_KERNEL_EXPORTS adds “-include symtab.h” for all linker script invokations. See openwrt/include/kernel-defaults.mk:

ifdef CONFIG_STRIP_KERNEL_EXPORTS
  KERNEL_MAKEOPTS += \
        EXTRA_LDSFLAGS="-I$(KERNEL_BUILD_DIR) -include symtab.h"
endif

On recent kernels (4.9.x, arm64 build), linker scripts are used to generate “vdso.lds” at the “make modules” stage.
But the file “symtab.h” is generated later (at the install/image generation stage). See openwrt/include/kernel-build.mk:

  $(LINUX_DIR)/.image: $(STAMP_CONFIGURED) $(if $(CONFIG_STRIP_KERNEL_EXPORTS),$(KERNEL_BUILD_DIR)/symtab.h) FORCE
        $(Kernel/CompileImage)
        $(Kernel/CollectDebug)
        touch $$@

As a result, kernel compilation fails.

  • Sidenotes:

- 32bit arm (brcm2708_bcm2708) is not affected, the vdso stuff is generated by normal .c files

- On arm64 4.4 kernels, the vdso stuff is not compiled for reasons, that I don’t know. Anyway, openwrt-17.01 is not affected

20.10.20214097Base systemBug ReportVery LowMedium"Fails": setting TxPower to 0,1,2 dBm with mt76 on GL-M...openwrt-21.02Unconfirmed Task Description

I own a power density meter (and now how to use it) and checked how 0..20 dBm setting and applying with LuCi affects power density.

Surprising not expected result: 0,1,2 dBm result in slightly higher power densities than 20 dBm. As expected: 3 dBm is a very lowe value, increasing with higher settings up to 20 dBm.

So either the driver or the hardware does not support that values, for whatever reason; might be a bug. I found nothing in the mt7628n data sheet for this issue.

Suggestion - LuCi should not allow to set these values, or mt76 (if it’s not a bug in mt76) should set 3 dBm for 0,1,2 dBm.

30.03.2017666Base systemBug ReportVery LowMedium"Wireless is disabled or not associated" when channel m...AllUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on Banana Pi R1
- Software versions: all

When I set the channel mode to “auto”, then the message appears “Wireless is disabled or not associated” and the WLAN does’nt work.
I set the channel manually, then WLAN works fine.

The problem is already known with OpenWrt:
https://dev.openwrt.org/changeset/32630


29.04.20192262Base systemBug ReportVery LowMedium“Reset to defaults” does not remove all files/directori...TrunkUnconfirmed Task Description

In the GUI, if you wipe your router with “Reset to defaults”, it does not correctly remove “hidden” directories such as .ssh/

The file and directory walking in jffs2reset.c, when done from the GUI, is not including the “hidden” subdirectories (and possibly hidden files).

When I do “umount /overlay && jffs2reset && reboot” from the command line, the .ssh/ directory is fully removed as expected.

Full discussion can be found at https://forum.openwrt.org/t/reset-to-defaults-does-not-remove-root-ssh-directory/34804

04.02.20202807Base systemBug ReportVery LowMedium(Wavlink WL-WN575A3) Signal strength LEDs don't work - ...openwrt-19.07Unconfirmed Task Description

Wavlink WL-WN575A3, Openwrt 19.07
Clean install set signal LEDs to rssi trigger but any of 3 LEDs don’t light due to missing rssileds package in default set of packages. After manual rssileds package install all 3 signal LEDs works as expected.

13.07.20213932Base systemBug ReportVery LowCritical[21.02] Autonegotiation speed fails with my provider's ...openwrt-21.02Unconfirmed Task Description

Supply the following if possible:
- Device problem occurs on: xiaomi mir3g
- 21.02 rc3
- My provider uses pppoe, cable is 4-wire 100baseT and my router is 1000baseT xiaomi mir3g

 

openwrt 21.02 fails to establish pppoe link because of failing to autonegotiate (Speed: Unknown!, Link detected: no, etc):

# ethtool wan
Settings for wan:
	Supported ports: [ TP MII ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: Symmetric Receive-only
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Advertised pause frame use: Symmetric Receive-only
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Speed: Unknown!
	Duplex: Unknown! (255)
	Port: MII
	PHYAD: 1
	Transceiver: external
	Auto-negotiation: on
	Supports Wake-on: d
	Wake-on: d
	Link detected: no

When I set autonegotiation to off and forced to 100baseT/Full, pppoe worked like a charm.

/usr/sbin/ethtool -s wan speed 100 duplex full autoneg off
# ethtool wan
Settings for wan:
	Supported ports: [ TP MII ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: Symmetric Receive-only
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  100baseT/Full 
	Advertised pause frame use: Symmetric Receive-only
	Advertised auto-negotiation: No
	Advertised FEC modes: Not reported
	Speed: 100Mb/s
	Duplex: Full
	Port: MII
	PHYAD: 1
	Transceiver: external
	Auto-negotiation: off
	Supports Wake-on: d
	Wake-on: d
	Link detected: yes
12.12.20192670KernelBug ReportVery LowHigh[ATH79] unstable USB on WR1043 v2openwrt-19.07Unconfirmed Task Description

Hi there!

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

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

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

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

25.10.20192567KernelBug ReportVery LowMedium[ATH79] USB speed degradation on WDR4300openwrt-19.07Assigned Task Description

Hello!

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

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

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

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

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

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

Best regards

09.06.20213862Base systemBug ReportVery LowLow[ATH79][19.07.7] unstable USB on Archer C7 v1/v2/v4openwrt-19.07Unconfirmed Task Description

Hi!

I have some problems with multiple host and usb devices, while using 19.07 release. I tried 19.07, 19.07.1, 19.07.3 and 19.07.7.
I tried three Archer C7 versions over the time, and different USB devices and even different overlay filesystems, but the symptoms are the same.
With overlayfs the devices losts it's USB storage after ~1-2 days, however without overlay it works up to 4 days. Unfortunately SSH or web access is mostly not possible after the device looses the USB device(9 out of 10).
I opened previously bug report for 1043v2, this device batch (MIPS and TP-Link) seem to be affected.

[263194.198081] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[263199.378038] usb 2-1: device descriptor read/64, error -145
[263214.737906] usb 2-1: device descriptor read/64, error -145
[263215.007920] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[263215.167912] usb 2-1: device descriptor read/64, error -71
[263215.447908] usb 2-1: device descriptor read/64, error -71
[263215.717902] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[263216.167896] usb 2-1: device not accepting address 2, error -71
[263216.317897] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[263216.767886] usb 2-1: device not accepting address 2, error -71
[263216.774186] usb 2-1: USB disconnect, device number 2
[263216.807934] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[263216.816500] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 04 2b 26 b8 00 00 20 00
[263216.824449] print_req_error: I/O error, dev sda, sector 69936824
[263216.833972] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[263216.842578] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 04 2b 26 d8 00 00 20 00
[263216.850508] print_req_error: I/O error, dev sda, sector 69936856
[263217.035893] blk_partition_remap: fail for partition 3
[263217.084319] blk_partition_remap: fail for partition 3
[263217.089747] usb 2-1: new high-speed USB device number 3 using ehci-platform
[263217.220988] blk_partition_remap: fail for partition 3
[263217.226496] blk_partition_remap: fail for partition 3
[263217.335635] blk_partition_remap: fail for partition 3
[263217.378953] usb 2-1: device descriptor read/64, error -71
[263217.403255] blk_partition_remap: fail for partition 3
[263217.716297] usb 2-1: device descriptor read/64, error -71
[263217.766228] blk_partition_remap: fail for partition 3
[263217.900631] blk_partition_remap: fail for partition 3
[263217.939582] blk_partition_remap: fail for partition 3
[263217.945175] blk_partition_remap: fail for partition 3
[263217.987923] usb 2-1: new high-speed USB device number 4 using ehci-platform
[263218.157896] usb 2-1: device descriptor read/64, error -71
[263218.437883] usb 2-1: device descriptor read/64, error -71
[263218.558126] usb usb2-port1: attempt power cycle
[263219.267879] usb 2-1: new high-speed USB device number 5 using ehci-platform
[263219.717866] usb 2-1: device not accepting address 5, error -71
[263219.867910] usb 2-1: new high-speed USB device number 6 using ehci-platform
[263220.317873] usb 2-1: device not accepting address 6, error -71
[263220.324047] usb usb2-port1: unable to enumerate USB device
[304298.508857] blk_partition_remap: fail for partition 3
27.01.20224243Base systemBuild FailureVery LowCritical[BUILD] Failure due to recent feed system changeTrunkUnconfirmed Task Description

Recently the feed scripts were changed and the “custom” targets aren’t anymore installed on ./target/linux but instead on ./target/linux/feeds.

Due to change the Makefile of that custom target isn’t reachable, and consequently following build error:

“OpenWrt/include/kernel-version.mk:11: *** Missing kernel version/hash file for . "

Meaning the KERNEL_PATCHVER isn’t found!

 


20.09.20203352Base systemBug ReportVery LowMedium[dnsmasq] DHCP Option 6 doesn't proper auto-configuredTrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

DHCP Options 6(DNS Server) doesn’t correctly set after re-enable dns role on dnsmasq.

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

LuCI Master (git-20.223.26773-d18ef13) / OpenWrt R20.8.27
DNSMasq Version 2.81
Unbound Version 1.10.1

- Steps to reproduce

1. According to OpenWRT Wiki, https://openwrt.org/docs/guide-user/base-system/dhcp_configuration#disabling_dns_role , Disable DNS Role first.
2. Re-Enable DNS Role by reverting the changes above or configure unbound DNS with LuCI, make sure to set unbound linked to dnsmasq as DHCP Server.
3. Whatever choice you made on step 2, DHCP Option 6 won’t be set. According to the capture by wireshark, the DHCP response packet does NOT contain any DNS Server related setting, which will finally lead Windows set 127.0.0.1 as DNS server and your internet connection won’t be detected.


07.03.20181415Base systemFeature RequestVery LowVery Low[Enhancement] Consider shorter interface-name prefixesTrunkUnconfirmed Task Description

Given that `IFNAMSIZ` is typically 16, there are 15 characters available for an interface name.

OpenWRT prepends a prefix that can be at least 6 characters `gre4t-` as an example.

If one then creates pseudo/virtual-interfaces using VLAN notation, there are only 4 characters available for configuration

`gre4t-ABCD.1234`

As long as this limitation is known, there is no loss of functionality, only utility in the naming. I would have ideally been able to name my tunnels with a more readable indication of where the other endpoint was, for example `portal1` rather than `gt99`.

At some time in the future, shortening these generated prefixes would be welcome. I acknowledge that this likely impacts only a small fraction of advanced users and a change may impact scripts that rely on the generated name.

 


29.03.20181461Base systemBug ReportVery LowMedium[hostapd] wpa_supplicant and mesh fail to connect after...TrunkUnconfirmed Task Description

Even after changing /etc/config/wireless to use option sae_password, mesh node fails to connect with other nodes with builds on or after the indicated commit.

This may be an upstream issue, even though hostap/wpa_supplicant/wpa_supplicant.conf does call out sae_password

Reverting to the older version of /lib/netifd/hostapd.sh allows the mesh to properly connect. (The config file contains both key and sae_password entries.) Commenting out the option key line in the config file for the failing build does not change the behavior.

Reverting /lib/netifd/hostapd.sh is a work-around at this time.

Interface is up as per both iw dev and ip link

/var/run/wpa_supplicant-mesh0.conf has been confirmed to pick up sae_password in the impacted builds and be otherwise “the same” as functioning builds.

network={
	
	ssid="<mesh ID>"
	key_mgmt=SAE
	mode=5
	fixed_freq=1
	frequency=5745
	ht40=1
	vht=1
	max_oper_chwidth=1
	sae_password="<same for both>"
	beacon_int=100
}

The command line executing wpa_supplicant on the interface is the same in both cases
/usr/sbin/wpa_supplicant -B -b br-mesh -P /var/run/wpa_supplicant-mesh0.pid -D nl80211 -i mesh0 -c /var/run/wpa_supplicant-mesh0.conf -C/var/run/wpa_supplicant

config wifi-device 'radio5'
	option type 'mac80211'
	option channel '149'
	option hwmode '11a'
	option path 'pci0000:01/0000:01:00.0'
	option htmode 'VHT80'
	option require_mode 'ac'

config wifi-iface 'mesh0'
	option device 'radio5'
	option ifname 'mesh0'
	option mode 'mesh'
	option mesh_id '<mesh ID>'
	option mesh_fwding '1'
	option encryption 'psk2+ccmp'
	option key '<same for both>'
	option sae_password '<same for both>'
	option network 'mesh'

Four Archer C7 v2 units
5 GHz radio for all on the mesh; other units running older builds with identical config for 5 GHz radio, other than the addition of option sae_password

Clean builds for the DUT with identical .config for both builds.

OpenWRT tree:

Good: 9b92afa3aa3bf19986983f4dceb54b4952d4b970 uci: update to latest git
Fails: eba3b028e46dbfe54f1208e9edf47bb0c6f73ac8 hostapd: update to git snapshot of 2018-03-26

Makefile changes around hostap:

-PKG_SOURCE_DATE:=2018-03-26
-PKG_SOURCE_VERSION:=64624f31cf81dc6164462fa153ee7a5909e21183

+PKG_SOURCE_DATE:=2017-08-24
+PKG_SOURCE_VERSION:=c2d4f2eb5dba0b5c5a8c5805823084da958a9b52


21.03.20181453Base systemBug ReportVery LowLow[mac80211] kernel errors load or lock system with mesh+...TrunkUnconfirmed Task Description

Overview

On an Archer C7, configuring an mesh point and an AP on the same radio cause a flood of errors to the log.

The load on the system can become so severe as to lock the user out of the system and pings to be several seconds (yes, not a typo) late
(seen on several builds, my notes identify v17.01.4-219-g796bc21 and v17.01.4-301-g60f8d38 as two of them)

Behavior identified as beginning with git commit 0f17504

Steps To Replicate

  • Build an Archer C7 image off the lede-17.01 branch on or after 0f17504
  • Install the following as /etc/config/wireless
config wifi-device 'radio24'
	option type 'mac80211'
	option channel '6'
	option hwmode '11g'
	option path 'platform/qca955x_wmac'
	option htmode 'HT20'
	option require_mode 'g'

config wifi-device 'radio5'
	option type 'mac80211'
	option channel '149'
	option hwmode '11a'
	option path 'pci0000:01/0000:01:00.0'
	option htmode 'VHT80'
	option require_mode 'ac'

config wifi-iface 'mesh0'
	option device 'radio5'
	option ifname 'mesh0'
	option mode 'mesh'
	option mesh_id '<mesh0_id>'
	option mesh_fwding '1'
	option encryption 'psk2+ccmp'
	option key '<mesh0_secret>'
	option network 'LAN'

config wifi-iface '5Gap'
	option device 'radio5'
	option mode 'ap'
	option ssid '<5Gap_ssid>'
	option encryption 'psk2+ccmp'
	option key '<5Gap_secret>'
	option network 'LAN'
  • reboot
  • Note the log messages that begin, then repeat continuously
[   70.392580] random: nonblocking pool is initialized
[   70.447666] br-vlan100: topology change detected, sending tcn bpdu
[   70.453988] br-vlan100: port 5(wlan1-1) entered forwarding state
[   70.507659] br-vlan100: topology change detected, sending tcn bpdu
[   70.513951] br-vlan100: port 7(wlan1-2) entered forwarding state
[   70.727668] br-vlan100: topology change detected, sending tcn bpdu
[   70.733956] br-vlan100: port 8(wlan1-3) entered forwarding state
[   71.097691] br-vlan100: topology change detected, sending tcn bpdu
[   71.103997] br-vlan100: port 6(wlan0-1) entered forwarding state
[   71.437684] br-vlan100: topology change detected, sending tcn bpdu
[   71.443978] br-vlan100: port 9(wlan1-4) entered forwarding state
[   71.517659] br-vlan100: topology change detected, sending tcn bpdu
[   71.523944] br-vlan100: port 10(wlan1-5) entered forwarding state
[   71.726243] ------------[ cut here ]------------
[   71.731103] WARNING: CPU: 0 PID: 6 at compat-wireless-2017-01-31/net/mac80211/ieee80211_i.h:1011 ieee80211_debugfs_key_sta_del+0xd4/0x6d8 [mac80211]()
[   71.744801] Modules linked in: iptable_nat ath9k nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 ipt_REJECT ipt_MASQUERADE ath9k_common 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 nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables ath9k_hw ath10k_pci ath10k_core ath mac80211 cfg80211 compat ledtrig_usbport ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables ip6_gre ip_gre gre ip6_tunnel tunnel6 ip_tunnel ehci_platform ehci_hcd gpio_button_hotplug ext4 jbd2 mbcache usbcore nls_base usb_common crc16 crc32c_generic crypto_hash
[   71.815278] CPU: 0 PID: 6 Comm: kworker/u2:0 Not tainted 4.4.103 #0
[   71.821720] Workqueue: phy0 ieee80211_ibss_leave [mac80211]
[   71.827387] Stack : 87c4fd14 00000088 80410000 800a78a4 87c2dbac 80410d63 803a9a68 00000006
	  803d40c0 87c4fb44 80410000 800a5820 80410000 800a78a4 803af174 80410000
	  00000003 87c4fb44 80410000 80095804 80410000 87c4fb7c 00000000 801f8654
	  00000001 801f8600 87693adc 87ffc400 87ffc300 70687930 00000000 00000000
	  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
	  ...
[   71.863749] Call Trace:
[   71.866240] [<80071e7c>] show_stack+0x54/0x88
[   71.870677] [<80081c7c>] warn_slowpath_common+0xa0/0xd0
[   71.875979] [<80081d34>] warn_slowpath_null+0x18/0x24
[   71.881177] [<876c8654>] ieee80211_debugfs_key_sta_del+0xd4/0x6d8 [mac80211]
[   71.888390] [<800d7ef4>] get_page_from_freelist+0x33c/0x810
[   71.894039] 
[   71.895554] ---[ end trace d737184f1359b1c0 ]---
[   72.565911] ------------[ cut here ]------------
[   72.570821] WARNING: CPU: 0 PID: 6 at compat-wireless-2017-01-31/net/mac80211/ieee80211_i.h:1011 ieee80211_debugfs_key_sta_del+0xd4/0x6d8 [mac80211]()
[   72.584526] Modules linked in: iptable_nat ath9k nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 ipt_REJECT ipt_MASQUERADE ath9k_common 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 nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables ath9k_hw ath10k_pci ath10k_core ath mac80211 cfg80211 compat ledtrig_usbport ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables ip6_gre ip_gre gre ip6_tunnel tunnel6 ip_tunnel ehci_platform ehci_hcd gpio_button_hotplug ext4 jbd2 mbcache usbcore nls_base usb_common crc16 crc32c_generic crypto_hash
[   72.655001] CPU: 0 PID: 6 Comm: kworker/u2:0 Tainted: G        W       4.4.103 #0
[   72.662676] Workqueue: phy0 ieee80211_ibss_leave [mac80211]
[   72.668341] Stack : 87c4fd14 00000088 80410000 800a78a4 87c2dbac 80410d63 803a9a68 00000006
	  803d40c0 87c4fb44 80410000 800a5820 80410000 800a78a4 803af174 80410000
	  00000003 87c4fb44 80410000 80095804 80410000 87c4fb7c 00000000 801f8654
	  8040fe70 801f8600 87693adc 87ffc400 87ffc300 70687930 00000000 00000000
	  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
	  ...
[   72.704694] Call Trace:
[   72.707186] [<80071e7c>] show_stack+0x54/0x88
[   72.711622] [<80081c7c>] warn_slowpath_common+0xa0/0xd0
[   72.716925] [<80081d34>] warn_slowpath_null+0x18/0x24
[   72.722124] [<876c8654>] ieee80211_debugfs_key_sta_del+0xd4/0x6d8 [mac80211]
[   72.729338] 
[   72.730850] ---[ end trace d737184f1359b1c1 ]---
[   72.750381] ------------[ cut here ]------------

Expected Behavior

Mesh and AP would come up without notable errors or load.

Potential Cause

commit 0f175041ad03d381a575e2c2b1a1c9ca76fe0e99
Author: Antonio Quartulli <ordex@autistici.org>
Date:   Fri Nov 9 15:23:34 2012 +0100

    mac80211: don't pass the hostapd ctrl iface in adhoc
    
    Passing the ctrl iface to wpa_supplicant will automatically cause wpa_supplicant
    to send "STOP_AP" messages to the hostapd. This breaks the AP interfaces.
    
    Signed-off-by: Antonio Quartulli <ordex@autistici.org>
    (cherry picked from commit 0da54fa6428ea98d31b49f5d9a4a272214f5d188)

Other Notes

Additionally reported by @cititechs
https://forum.lede-project.org/t/802-11s-configuration-references-tp-link-archer-c7/4876/12?u=jeff

 

Exmaple ping log over a wired connection; unable to establish connection to examine logs

Request timeout for icmp_seq 57
64 bytes from <redacted>: icmp_seq=58 ttl=64 time=1.147 ms
64 bytes from <redacted>: icmp_seq=59 ttl=64 time=0.610 ms
64 bytes from <redacted>: icmp_seq=60 ttl=64 time=0.645 ms
64 bytes from <redacted>: icmp_seq=61 ttl=64 time=309.930 ms
Request timeout for icmp_seq 62
64 bytes from <redacted>: icmp_seq=62 ttl=64 time=1624.116 ms
64 bytes from <redacted>: icmp_seq=63 ttl=64 time=620.756 ms
64 bytes from <redacted>: icmp_seq=64 ttl=64 time=1721.540 ms
64 bytes from <redacted>: icmp_seq=65 ttl=64 time=719.600 ms
Request timeout for icmp_seq 67
Request timeout for icmp_seq 68
64 bytes from <redacted>: icmp_seq=66 ttl=64 time=3025.040 ms
64 bytes from <redacted>: icmp_seq=67 ttl=64 time=2020.629 ms
64 bytes from <redacted>: icmp_seq=68 ttl=64 time=1019.058 ms
64 bytes from <redacted>: icmp_seq=69 ttl=64 time=14.092 ms
Request timeout for icmp_seq 73
64 bytes from <redacted>: icmp_seq=70 ttl=64 time=4391.453 ms
64 bytes from <redacted>: icmp_seq=71 ttl=64 time=3388.555 ms
64 bytes from <redacted>: icmp_seq=72 ttl=64 time=2384.972 ms
64 bytes from <redacted>: icmp_seq=73 ttl=64 time=1384.871 ms
64 bytes from <redacted>: icmp_seq=74 ttl=64 time=384.382 ms
Request timeout for icmp_seq 79
Request timeout for icmp_seq 80
Request timeout for icmp_seq 81
64 bytes from <redacted>: icmp_seq=75 ttl=64 time=7244.993 ms
64 bytes from <redacted>: icmp_seq=76 ttl=64 time=6240.756 ms
64 bytes from <redacted>: icmp_seq=77 ttl=64 time=5240.605 ms
64 bytes from <redacted>: icmp_seq=78 ttl=64 time=4240.268 ms
64 bytes from <redacted>: icmp_seq=79 ttl=64 time=3235.217 ms
64 bytes from <redacted>: icmp_seq=80 ttl=64 time=2231.510 ms
64 bytes from <redacted>: icmp_seq=81 ttl=64 time=1393.878 ms
64 bytes from <redacted>: icmp_seq=82 ttl=64 time=388.886 ms
Request timeout for icmp_seq 90
Request timeout for icmp_seq 91
Request timeout for icmp_seq 92
Request timeout for icmp_seq 93
Request timeout for icmp_seq 94
64 bytes from <redacted>: icmp_seq=83 ttl=64 time=12157.520 ms
64 bytes from <redacted>: icmp_seq=84 ttl=64 time=11154.284 ms
64 bytes from <redacted>: icmp_seq=85 ttl=64 time=10154.189 ms
64 bytes from <redacted>: icmp_seq=86 ttl=64 time=9149.660 ms
64 bytes from <redacted>: icmp_seq=87 ttl=64 time=8146.267 ms
64 bytes from <redacted>: icmp_seq=88 ttl=64 time=7146.146 ms
64 bytes from <redacted>: icmp_seq=89 ttl=64 time=6145.438 ms
64 bytes from <redacted>: icmp_seq=90 ttl=64 time=5140.706 ms
64 bytes from <redacted>: icmp_seq=91 ttl=64 time=4137.406 ms
64 bytes from <redacted>: icmp_seq=92 ttl=64 time=3137.265 ms
64 bytes from <redacted>: icmp_seq=93 ttl=64 time=2137.250 ms
64 bytes from <redacted>: icmp_seq=94 ttl=64 time=1134.170 ms
64 bytes from <redacted>: icmp_seq=95 ttl=64 time=136.361 ms
Request timeout for icmp_seq 108
Request timeout for icmp_seq 109
Request timeout for icmp_seq 110
Request timeout for icmp_seq 111
64 bytes from <redacted>: icmp_seq=96 ttl=64 time=16613.049 ms
64 bytes from <redacted>: icmp_seq=97 ttl=64 time=15611.720 ms
64 bytes from <redacted>: icmp_seq=98 ttl=64 time=14607.843 ms
64 bytes from <redacted>: icmp_seq=99 ttl=64 time=13603.671 ms
64 bytes from <redacted>: icmp_seq=100 ttl=64 time=12599.121 ms
64 bytes from <redacted>: icmp_seq=101 ttl=64 time=11594.289 ms
64 bytes from <redacted>: icmp_seq=102 ttl=64 time=10589.932 ms
64 bytes from <redacted>: icmp_seq=103 ttl=64 time=9585.828 ms
64 bytes from <redacted>: icmp_seq=104 ttl=64 time=8582.492 ms
64 bytes from <redacted>: icmp_seq=105 ttl=64 time=7580.545 ms
64 bytes from <redacted>: icmp_seq=106 ttl=64 time=6577.218 ms
64 bytes from <redacted>: icmp_seq=107 ttl=64 time=5573.081 ms
64 bytes from <redacted>: icmp_seq=108 ttl=64 time=4569.669 ms
64 bytes from <redacted>: icmp_seq=109 ttl=64 time=3564.700 ms
64 bytes from <redacted>: icmp_seq=110 ttl=64 time=2564.257 ms
64 bytes from <redacted>: icmp_seq=111 ttl=64 time=1563.785 ms
64 bytes from <redacted>: icmp_seq=112 ttl=64 time=558.610 ms


09.12.20203499Base systemBug ReportVery LowLow[netifd] no way to monitor the real state of a connecti...TrunkUnconfirmed Task Description

The current ModemManager integration in netifd is not fully operational right now, and usually requires an additional management script on top of it to properly reconnect the modems under certain scenarios.

The simplest and most common use case is the following:
* The network interface configured for “modemmanager” protocol is ifup-ed.
* netifd runs the connection start procedure in the protocol handler and the modem gets connected.
* Some time passes, and the network operator decides to disconnect the connection (network-initiated disconnection).
* ModemManager detects the disconnection, reports the bearer objects a “disconnected” and the modem back to only “registered”.
* netifd still thinks the interface is up, and reports it as up everywhere.

See e.g. https://github.com/openwrt/packages/issues/14096

What would be the best way to solve this issue?

Is there currently any way to extend the protocol handler in a way that allows some polling inside netifd to ensure the interface is still up? Would that be a big change? Any other solution suggested?

 


28.01.20213600Base systemBug ReportVery LowMedium[odhcp6c] prefix exclude sanity check fails for prefix ...openwrt-19.07Unconfirmed Task Description

odhcp6c fails to request a delegated prefix when the server returns an excluded prefix of length > 64.

According to RFC 6603:

o prefix-len: The length of the excluded prefix in bits. The
prefix-len MUST be between ‘OPTION_IAPREFIX prefix-length’+1 and
128.

However, values for excluded prefix length > 64 fail sanity, resulting in odhcp6c dropping the PD from the request.

The following patch fixes the issue.

13.07.20213928ToolchainBug ReportVery LowMedium[OPKG] Track installed/removed packages and provide imp...AllUnconfirmed Task Description

I tried to use opkg with this script “opkg extras” for upgrading:
https://openwrt.org/docs/guide-user/installation/generic.sysupgrade#savingrestoring_user-installed_packages

IMHO such a script is really basic functionality and I should not have to execute such a script just to keep the installed packages on upgrade.
IMHO this would make upgrading OpenWRT a lot easier and I would also do it a lot more frequent (potentially fixing security issues faster).

As I talked about this in the forum, too, the author said:
> In addition, as the author of those pages, I’d like to point out that the method for tracking installed and removed packages can be greatly simplified if someone decides to integrate that functionality into Opkg.

So more systematic:

Problem

I may fear to upgrade my OpenWRT router due to the loss of installed packages.
The existing alternatives are not sufficient and hard to use, especially for an average user. E.g. you need to use SSH/the CLI.
The existing alternative did not 100%ly work in my case. It e.g. also installed all dependencies as manually installed packages as far as I see.
Code-wise/Technically the author said the current way is much more complicated than what could be done if that were integrated into opkg.

Suggestion

It would be nice if these OPGK extras and hotplug extras were an opkg package itself. This would also solve the reinstallation issue, because by definition, they would reinstall “themselves”.

26.12.20192696Base systemBug ReportVery LowMedium[ramips/mt7621] Sysupgrade not working for master image...TrunkUnconfirmed Task Description

Recent builds from master seem to have broken sysupgrade on mt7621. I have observed this on the following devices:
- DIR-860L rev B1
- DIR-878 rev A1 (pull request here)

It first happened on the DIR-878 A1, where I flashed the author’s image and was unable to switch to either newer master builds or 19.07 builds. I then verified this on the DIR-860L, and it showed the same behaviour.

Sysupgrade does not show any errors. It closes all pending sessions and seems to proceed normally, but after a reboot the firmware has not been upgraded.

 


27.05.20213832Base systemBug ReportVery LowLow[Regression] xrx200 switch affecting AVM Fritz!Box 7362...TrunkUnconfirmed Task Description

The 7362sl by AVM has two gigabit ports labeled 1+2 and two fast ethernet ports labled 3+4.

They all used to work, but with OpenWrt 21.02.0 only the two gigabit ports work. Port 3+4 are dead. Linked (layer1) can be established, no layer2 or higher traffic possible.

OpenWrt 19.07.7 Kernel 4.14.221 supports ports 3 + 4
Openwrt 21.02.0-rc1 Kernel 5.4.111 ports 3 + 4 are dead

```
root@OpenWrt:~# dmesg|grep -A5 -B5 PHY
[ 0.163028] pinctrl core: initialized pinctrl subsystem
[ 0.170653] NET: Registered protocol family 16
[ 0.183980] dcdc-xrx200 1f106a00.dcdc: Core Voltage : 1016 mV
[ 0.198588] pinctrl-xway 1e100b10.pinmux: Init done
[ 0.205140] dma-xway 1e104100.dma: Init done - hw rev: 7, ports: 7, channels: 28
[ 0.216895] pcie-xrx200 1d900000.pcie: failed to get the PCIe PHY
[ 0.265910] usbcore: registered new interface driver usbfs
[ 0.271499] usbcore: registered new interface driver hub
[ 0.276869] usbcore: registered new device driver usb
[ 0.282522] workqueue: max_active 576 requested for napi_workq is out of range, clamping between 1 and 512
[ 0.294467] clocksource: Switched to clocksource MIPS
– [ 0.708199] NET: Registered protocol family 10
[ 0.715876] Segment Routing with IPv6
[ 0.718218] NET: Registered protocol family 17
[ 0.722769] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 0.735555] 8021q: 802.1Q VLAN Support v1.8
[ 0.746142] pcie-xrx200 1d900000.pcie: failed to get the PCIe PHY
[ 0.859313] libphy: lantiq,xrx200-mdio: probed
[ 0.869051] net-xrx200: invalid MAC, using random
[ 0.872575] Atheros 8030 ethernet 0:00: attached PHY driver [Atheros 8030 ethernet] (mii_bus:phy_addr=0:00, irq=POLL)
[ 0.883256] Atheros 8030 ethernet 0:01: attached PHY driver [Atheros 8030 ethernet] (mii_bus:phy_addr=0:01, irq=POLL)
[ 0.894242] Intel XWAY PHY11G (xRX v1.2 integrated) 0:11: attached PHY driver [Intel XWAY PHY11G (xRX v1.2 integrated)] (mii_bus:phy_addr=0:11, irq=POLL)
[ 0.907971] Intel XWAY PHY11G (xRX v1.2 integrated) 0:13: attached PHY driver [Intel XWAY PHY11G (xRX v1.2 integrated)] (mii_bus:phy_addr=0:13, irq=POLL)
[ 1.046546] PCI host bridge /fpi@10000000/pcie@d900000 ranges:
[ 1.051221] PCI host bridge to bus 0000:00
[ 1.055083] pci_bus 0000:00: root bus resource [mem 0x1c000000-0x1cffffff]
[ 1.061969] pci_bus 0000:00: root bus resource [io 0x1d800000-0x1d8fffff]
[ 1.068840] pci_bus 0000:00: root bus resource [??? 0×00000000 flags 0×0]
```

Notably might be the line ”failed to get the PCIe PHY“ which does not appear in 19.07.7.

As I didn’t notice any changes regarding this particular device model, it might be a problem with the kernel driver for the switch module.

03.05.2017756Base systemBug ReportVery LowLow/boot filesystem isn't mounted by preinit on x86TrunkUnconfirmed Task Description

Problem occurs on x86 builds (both x86-32 and x86-64).

Is observed with HEAD (6138d842433).

Install a recent build. Boot. “ls /boot”

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

Supply the following if possible:
- Device problem occurs on

specifically tested & confirmed on x86-64 and ipq806x

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

18.06.1 and snapshot

- Steps to reproduce

opkg install mdadm

08.01.20202718Base systemBug ReportVery LowCritical/overlay is empty and nothing can be written thereTrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

Only on TPLink Archer C7 v5 (current model).
Other models are OK: A7 (”V5”) (also current), C7 V2, C7 V4 (both earlier)

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

Only Trunk has this problem, and only on C7 v5. rc19.07 does *not* have this problem.

- Steps to reproduce

make menuconfig for target C7 V5
load squashfs-factory version in a C7 V5
boot

...and presto, there’s nothing in /overlay. /rom/overlay is populated. I have found no way to write anything on /overlay. Luci can’t save anything either – not even a password.

There’s nothing weird in my make menuconfig config, unless you count python3-light, bind-dig, ca-certificates, etc. as weird. And the other C7 and C7-like models work fine.

 


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): ?


10.03.2017614Base systemBug ReportVery LowMedium/usr/lib/lua/luci/util.lua:623: Unable to establish ubu...TrunkUnconfirmed Task Description

when save&apply on system>mount luci always crash
error message:
/usr/lib/lua/luci/util.lua:623: Unable to establish ubus connection
stack traceback:

[C]: in function 'assert'
/usr/lib/lua/luci/util.lua:623: in function 'ubus'
/usr/lib/lua/luci/dispatcher.lua:347: in function 'dispatch'
/usr/lib/lua/luci/dispatcher.lua:141: in function </usr/lib/lua/luci/dispatcher.lua:140>
 


14.06.20203179Base systemBug ReportVery LowLow<dnsmasq 2.81-3> on latest snapshot r13546-4f38063640TrunkUnconfirmed Task Description

I’m on WRT1900ACS with latest snpashot r13546-4f38063640.
I have an issue with latest dnsmasq, the resolv file is in /tmp/resolv.conf.d/resolv.conf.auto. On old was on /tmp/resolv.conf.auto.

With openvpn I have script to prevent dns leak I have tried to change on right location but doesn’t work.
If I set up the dnsmasq to old location /tmp/resolv.conf.auto all the up and down script working, but, when I flash new firmware and I try to reload backup the setting of resolv file is not restored and must be set again.

I hope that I was clear, let me know if you need more info and sorry if I was not accurate on bug report.


25.11.20214155PackagesBug ReportVery LowMedium<dnsmasq_2.86-10_aarch64_cortex-a53.ipk>: unable to sta...TrunkUnconfirmed Task Description

Linksys e8450 on OpenWrt SNAPSHOT, r18161-00ce13490a

A bug in dnsmasq 2.86-10 would render the whole DHCP system down. Once you modify the /etc/dnsmasq.conf with additional line:

conf-dir=/etc/dnsmasq.d/

Your dnsmasq will refuse to start

Workaround: Add following lines to /etc/config/dhcp to bypass this bug:
option confdir ‘/etc/dnsmasq.d/’

This workaround will change the default behavior which dnsmasq was including the conf files in the /tmp/dnsmasq.d
And I’m not sure if the option confdir ‘/etc/dnsmasq.d/’ actually works.

The dnsmasq 2.85-8 package shipped with 21.02.1 has no such bug.

22.03.20202919Base systemBug ReportVery LowLow18.06 to 19.07 upgrade fails [Netgear WNDR4300 v1]openwrt-19.07Unconfirmed Task Description

> If your device is not supported by the image You may encounter the error “Device not supported by this image” or “Image check failed”. In that case, please report the issue so that it can be fixed for the next 19.07.X minor release.

https://openwrt.org/docs/guide-user/installation/ar71xx.to.ath79


Tried to upgrade from

openwrt-18.06 branch (git-19.020.41695-6f6641d) / OpenWrt 18.06.2 r7676-cddd7b4c77

[to]

http://downloads.openwrt.org/releases/19.07.2/targets/ar71xx/nand/openwrt-19.07.2-ar71xx-nand-wndr4300-squashfs-sysupgrade.tar

I alternately receive the error “The connection was reset” or “Device not supported by this image”


> for LuCI: check “Force upgrade”

This option was not available

> for command-line sysupgrade: use sysupgrade -F -n <your-device-19.07-image-sysupgrade.bin>

This option succeeded and the new build is working normally, thanks

note: Once this issue is resolved, would it be feasible to host upgrade images on a free service like GitHub, so checks for new version could be performed through the web interface (similar to GL.Inet routers)

22.07.20181684Base systemBug ReportVery LowLow18.06.0-rc2 dos not save settings when applyed ramips/r...TrunkWaiting on reporter Task Description

D-Link DIR-615 D but using a D2 version
18.06.0-rc2 but 17.01.5 is working fine!
OpenWrt 18.06.0-rc2 r7141-e4d0ee5af5

I have a issue with Luci or maybe is issue with ramips/rt305x device’s but when i go to apply settings in the webgui and reboot my d-link it goes back to the default openwrt settings however 17.01.5 is working fine no issue here but 18.06.0-rc2 is a no no unless i manual change them in the SSH/SCP folder.

Just to be clear when save&apply is ok but once reboot or turn off by the mains power it resolves into default settings.

16.07.20203234ToolchainBug ReportVery LowLow19.07.2 imagebuilder does not work with (detect) gcc 10...openwrt-19.07Unconfirmed Task Description

Imagebuilder is unable to detect gcc/g++ on my system running gcc 10.1 FORCE=1 makes no difference, and seems to be ignored.

[naguz@blaptop openwrt-imagebuilder-19.07.2]$ make image FORCE=1 PROFILE=tplink_archer-c7-v2 FILES=files/
Checking 'working-make'... ok.
Checking 'case-sensitive-fs'... ok.
Checking 'proper-umask'... ok.
Checking 'gcc'... failed.
Checking 'working-gcc'... ok.
Checking 'g++'... failed.
Checking 'working-g++'... ok.
Checking 'ncurses'... ok.
Checking 'perl-thread-queue'... ok.
Checking 'tar'... ok.
Checking 'find'... ok.
Checking 'bash'... ok.
Checking 'patch'... ok.
Checking 'diff'... ok.
Checking 'cp'... ok.
Checking 'seq'... ok.
Checking 'awk'... ok.
Checking 'grep'... ok.
Checking 'getopt'... ok.
Checking 'stat'... ok.
Checking 'unzip'... ok.
Checking 'bzip2'... ok.
Checking 'wget'... ok.
Checking 'perl'... ok.
Checking 'python3-cleanup'... ok.
Checking 'python'... ok.
Checking 'git'... ok.
Checking 'file'... ok.
Checking 'ldconfig-stub'... ok.

Build dependency: Please install the GNU C Compiler (gcc) 4.8 or later
Build dependency: Please install the GNU C++ Compiler (g++) 4.8 or later

Prerequisite check failed. Use FORCE=1 to override.
make[1]: *** [Makefile:87: staging_dir/host/.prereq-build] Error 1
make: *** [Makefile:197: image] Error 2
[gert@blad openwrt-imagebuilder-19.07.2]$ 
08.01.20213565KernelBug ReportVery LowCritical19.07.5 wifi for WRT1900AC v1 regressionopenwrt-19.07Unconfirmed Task Description

Device problem occurs on: Supply the following if possible:
Software versions of OpenWrt/LEDE release: OpenWrt 19.07.5, r11257-5090152ae3
WiFi dies every now and then, I had to roll back to 19.07.4.

[ 757.192788] wlan1: failed to remove key (0, 98:09:cf:ae:1d:1e) from hardware (-5)
[ 757.212705] ieee80211 phy1: MACREG_REG_INT_CODE: 0×0000 [ 777.284194] ieee80211 phy1: cmd 0×9122=UpdateEncryption timed out
[ 777.290372] ieee80211 phy1: return code: 0×1122 [ 777.294925] ieee80211 phy1: timeout: 0×1122 [ 777.299158] wlan1: failed to remove key (0, 54:60:09:fd:b0:72) from hardware (-5)
[ 777.324342] ieee80211 phy1: MACREG_REG_INT_CODE: 0×0000

kernel log in attachment

01.02.20202795Base systemBug ReportVery LowLow19.07.x , TP-Link TL-WR841N v9, kernell panic openwrt-19.07Unconfirmed Task Description

Used TP-Link TL-WR841N/D v9 with mod 8M
tested with build for 8M firmware.

updated via:
scp copy to /tmp
mtd -r write /tmp/firmwaew.bin firmware

18.06 work ok on this hardware, report:https://lexxai.blogspot.com/2019/07/hardware-modding-tp-link-tl-wr841n-v9.html.

***************************************
*     U-Boot 1.1.4-7a540a78-clean     *
*          Build: 2018-02-23          *
***************************************

** Warning: bad env CRC, using default,
   use 'saveenv' to save it in FLASH

  BOARD: TP-Link TL-WR841N/D v9
    SOC: QCA953x ver. 1 rev. 1
    CPU: MIPS 24Kc
    RAM: 32 MB DDR1 16-bit CL3-3-3-8
  FLASH: 8 MB Winbond W25Q64
    MAC: E8:DE:27:CD:0C:C4
 CLOCKS: CPU/RAM/AHB/SPI/REF
         550/400/200/ 25/ 25 MHz

Hit any key to stop booting:  0

Booting image from 0x9F020000...

   Vendor/image name:    OpenWrt r10911-c155900f66
   Hardware ID:          0x8410009
   Whole image size:     0 kB (0 bytes)
   Kernel size:          3.4 MB (3579760 bytes)
   Rootfs size:          0 kB (0 bytes)
   Kernel load address:  0x80060000
   Kernel entry point:   0x80060000

   Header CRC...  skipped
   Data CRC...    skipped

Stopping network... OK!
Uncompressing Kernel... OK!
Starting kernel...

[    0.000000] Linux version 4.14.167 (builder@buildhost) (gcc version 7.5.0 (OpenWrt GCC 7.5.0 r10911-c155900f66)) #0 Wed Jan 29 16:05:35 2020
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019374 (MIPS 24Kc)
[    0.000000] MIPS: machine is TP-Link TL-WR841N/ND v9
[    0.000000] SoC: Qualcomm Atheros QCA9533 ver 1 rev 1
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 02000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] random: get_random_bytes called from 0x804776ec with crng_init=0
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 8128
[    0.000000] Kernel command line: console=ttyS0,115200n8 rootfstype=squashfs,jffs2
[    0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[    0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 19648K/32768K available (3544K kernel code, 144K rwdata, 492K rodata, 7972K init, 203K bss, 13120K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 51
[    0.000000] CPU clock: 550.000 MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6950037990 ns
[    0.000011] sched_clock: 32 bits at 275MHz, resolution 3ns, wraps every 7809031678ns
[    0.008899] Calibrating delay loop... 366.18 BogoMIPS (lpj=1830912)
[    0.075976] pid_max: default: 32768 minimum: 301
[    0.081456] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.088993] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.102006] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.113239] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.120271] pinctrl core: initialized pinctrl subsystem
[    0.129130] NET: Registered protocol family 16
[    0.159871] clocksource: Switched to clocksource MIPS
[    0.166986] NET: Registered protocol family 2
[    0.173070] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.181077] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.188304] TCP: Hash tables configured (established 1024 bind 1024)
[    0.195734] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.202443] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.209932] NET: Registered protocol family 1
[    0.441778] Crashlog allocated RAM at address 0x1f00000
[    0.449761] workingset: timestamp_bits=30 max_order=13 bucket_order=0
[    0.463652] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.470338] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.573035] io scheduler noop registered
[    0.577495] io scheduler deadline registered (default)
[    0.586478] pinctrl-single 1804002c.pinmux: 576 pins at pa b804002c size 72
[    0.595622] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.605887] console [ttyS0] disabled
[    0.610067] 18020000.uart: ttyS0 at MMIO 0x18020000 (irq = 9, base_baud = 1562500) is a 16550A
[    0.619896] console [ttyS0] enabled
[    0.619896] console [ttyS0] enabled
[    0.627446] bootconsole [early0] disabled
[    0.627446] bootconsole [early0] disabled
[    0.655906] m25p80 spi0.0: s25fl064k (8192 Kbytes)
[    0.660968] 3 fixed-partitions partitions found on MTD device spi0.0
[    0.667534] Creating 3 MTD partitions on "spi0.0":
[    0.672514] 0x000000000000-0x000000020000 : "u-boot"
[    0.678707] 0x000000020000-0x0000003f0000 : "firmware"
[    0.685921] 2 tplink-fw partitions found on MTD device firmware
[    0.692126] Creating 2 MTD partitions on "firmware":
[    0.697268] 0x000000000000-0x00000036a170 : "kernel"
[    0.703347] 0x000000370000-0x0000003d0000 : "rootfs"
[    0.709470] mtd: device 3 (rootfs) set to be root filesystem
[    0.715429] mtdsplit: no squashfs found in "rootfs"
[    0.720527] 0x0000003f0000-0x000000400000 : "art"
[    0.727132] libphy: Fixed MDIO Bus: probed
[    1.071005] ag71xx 19000000.eth: Could not connect to PHY device. Deferring probe.
[    1.750303] libphy: ag71xx_mdio: probed
[    1.755849] libphy: ar8xxx-mdio: probed
[    1.821951] switch0: Atheros AR8229 rev. 1 switch registered on mdio-bus.0
[    1.908098] ag71xx 1a000000.eth: connected to PHY at fixed-0:00 [uid=00000000, driver=Generic PHY]
[    1.918258] eth0: Atheros AG71xx at 0xba000000, irq 5, mode: gmii
[    1.927890] NET: Registered protocol family 10
[    1.939093] Segment Routing with IPv6
[    1.943086] NET: Registered protocol family 17
[    1.947742] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    1.961897] 8021q: 802.1Q VLAN Support v1.8
[    2.302222] ag71xx 19000000.eth: connected to PHY at mdio-bus.0:1f:04 [uid=004dd042, driver=Generic PHY]
[    2.313243] eth1: Atheros AG71xx at 0xb9000000, irq 4, mode: mii
[    2.370657] Freeing unused kernel memory: 7972K
[    2.375356] This architecture does not have kernel memory protection.
[    2.403375] init: Console is alive
[    2.407211] init: - watchdog -
[    2.437672] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    2.448667] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    2.466809] init: - preinit -
[    2.509932] random: fast init done
[    2.808648] random: jshn: uninitialized urandom read (4 bytes read)
[    2.917601] random: jshn: uninitialized urandom read (4 bytes read)
[    3.163179] random: jshn: uninitialized urandom read (4 bytes read)
[    3.805753] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    3.811977] IPv6: ADDRCONF(NETDEV_UP): eth0.1: link is not ready
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[    4.821087] eth0: link up (1000Mbps/Full duplex)
[    4.825913] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    4.833060] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready
[    7.014588] eth0: link down
[    7.042239] procd: - early -
[    7.045358] procd: - watchdog -
[    7.636953] procd: - watchdog -
[    7.640695] procd: - ubus -
[    7.652470] urandom_read: 5 callbacks suppressed
[    7.652481] random: ubusd: uninitialized urandom read (4 bytes read)
[    7.694505] random: ubusd: uninitialized urandom read (4 bytes read)
[    7.702822] procd: - init -
Please press Enter to activate this console.
[    8.251779] kmodloader: loading kernel modules from /etc/modules.d/*
[    8.275535] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    8.306112] Loading modules backported from Linux version v4.19.98-0-gd183c8e2647a
[    8.314024] Backport generated by backports.git v4.19.98-1-0-g8204eb99
[    8.342826] ip_tables: (C) 2000-2006 Netfilter Core Team
[    8.369084] nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
[    8.509039] xt_time: kernel timezone is -0000
[    8.643102] PPP generic driver version 2.4.2
[    8.661009] NET: Registered protocol family 24
[    8.746124] Data bus error, epc == 801f4180, ra == 8129febc
[    8.751898] Oops[#1]:
[    8.754255] CPU: 0 PID: 497 Comm: kmodloader Not tainted 4.14.167 #0
[    8.760819] task: 81878000 task.stack: 811f8000
[    8.765491] $ 0   : 00000000 00000001 deadc0de 00014000
[    8.770901] $ 4   : b81143fc 000143fc 00014000 00000004
[    8.776305] $ 8   : 00000001 7c7c3c7c 7c7c7c7c 7c7c7c7c
[    8.781707] $12   : 7c7c3c7c 81236500 ffffff80 7c7c7c3c
[    8.787120] $16   : 8115c080 00000018 00000000 00030000
[    8.792522] $20   : 00010000 00031018 00000004 000003ff
[    8.797925] $24   : 00000000 00000000
[    8.803328] $28   : 811f8000 811f9a30 811f9a84 8129febc
[    8.808740] Hi    : 00000003
[    8.811715] Lo    : 000000ff
[    8.814696] epc   : 801f4180 0x801f4180
[    8.818663] ra    : 8129febc 0x8129febc [ath9k_hw@81280000+0x51660]
[    8.825129] Status: 1000f403 KERNEL EXL IE
[    8.829458] Cause : 1080001c (ExcCode 07)
[    8.833598] PrId  : 00019374 (MIPS 24Kc)
[    8.837644] 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_FLOWOFFLOAD xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables crc_ccitt compat nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 gpio_button_hotplug
[    8.901314] Process kmodloader (pid: 497, threadinfo=811f8000, task=81878000, tls=77fb3efc)
[    8.909933] Stack : ffffffff 81236500 ffffff80 ffffffff 00002710 8115c080 000003ff 812a0000
[    8.918580]         8111a800 8115c080 811f9b14 00000004 812ccda8 8115c4bc 00000001 8129ea64
[    8.927226]         811f8000 811f9a98 00000220 00000220 00008000 ffffffff 811f9b14 812a0ab0
[    8.935872]         8115a080 81283e88 00000001 80450000 812d9500 81201ff0 000186a0 8115c080
[    8.944519]         8115c080 8115c0a8 00008000 00000001 811f9b14 00000004 812ccda8 99999999
[    8.953165]         ...
[    8.955692] Call Trace:
[    8.955740] [<812a0000>] 0x812a0000 [ath9k_hw@81280000+0x51660]
[    8.964387] [<8129ea64>] 0x8129ea64 [ath9k_hw@81280000+0x51660]
[    8.970516] [<812a0ab0>] 0x812a0ab0 [ath9k_hw@81280000+0x51660]
[    8.976635] [<81283e88>] 0x81283e88 [ath9k_hw@81280000+0x51660]
[    8.982755] [<81201ff0>] 0x81201ff0 [ath9k@81200000+0x16bb0]
[    8.988619] [<812930f8>] 0x812930f8 [ath9k_hw@81280000+0x51660]
[    8.994739] [<80093348>] 0x80093348
[    8.998350] [<812864d0>] 0x812864d0 [ath9k_hw@81280000+0x51660]
[    9.004467] [<80250bd8>] 0x80250bd8
[    9.008081] [<80093348>] 0x80093348
[    9.011691] [<812026a4>] 0x812026a4 [ath9k@81200000+0x16bb0]
[    9.017543] [<800aefec>] 0x800aefec
[    9.021168] [<8120e468>] 0x8120e468 [ath9k@81200000+0x16bb0]
[    9.027023] [<80299160>] 0x80299160
[    9.030649] [<8024f43c>] 0x8024f43c
[    9.034250] [<8029367c>] 0x8029367c
[    9.037852] [<8024db98>] 0x8024db98
[    9.041454] [<8024fabc>] 0x8024fabc
[    9.045058] [<8024dce4>] 0x8024dce4
[    9.048656] [<8024bd38>] 0x8024bd38
[    9.052263] [<8024dc60>] 0x8024dc60
[    9.055870] [<8024bdf0>] 0x8024bdf0
[    9.059471] [<803bf270>] 0x803bf270
[    9.063074] [<8024bc3c>] 0x8024bc3c
[    9.066680] [<8024d124>] 0x8024d124
[    9.070291] [<8024e300>] 0x8024e300
[    9.073905] [<81217000>] 0x81217000 [ath9k@81200000+0x16bb0]
[    9.079748] [<8024e4a8>] 0x8024e4a8
[    9.083366] [<81217018>] 0x81217018 [ath9k@81200000+0x16bb0]
[    9.089214] [<80060a00>] 0x80060a00
[    9.092822] [<800e6a40>] 0x800e6a40
[    9.096423] [<800912d4>] 0x800912d4
[    9.100025] [<8010fbe0>] 0x8010fbe0
[    9.103642] [<800cbee4>] 0x800cbee4
[    9.107247] [<80111044>] 0x80111044
[    9.110854] [<800cb81c>] 0x800cb81c
[    9.114462] [<800c9680>] 0x800c9680
[    9.118071] [<80111a14>] 0x80111a14
[    9.121673] [<8011c4e0>] 0x8011c4e0
[    9.125275] [<800cbb3c>] 0x800cbb3c
[    9.128878] [<800cbc28>] 0x800cbc28
[    9.132487] [<8006ed8c>] 0x8006ed8c
[    9.136093] [<803d0c74>] 0x803d0c74
[    9.139698] [<800698a0>] 0x800698a0
[    9.143307]
[    9.144847] Code: 26310001  8c820000  0000000f <03e00008> 00000000  27bdffe8  afbf0014  0c0a76b2  00000000
[    9.154936]
[    9.156551] ---[ end trace eb9837c2a907321b ]---
[    9.163433] Kernel panic - not syncing: Fatal exception
[    9.169959] Rebooting in 1 seconds..


same crash and with public images:
https://downloads.openwrt.org/releases/19.07.0/targets/ath79/tiny/openwrt-19.07.0-ath79-tiny-tplink_tl-wr841-v9-initramfs-kernel.bin

25.11.20171192Base systemBug ReportVery LowHigh2.4Ghz wifi AP on mt7621 / Afoundry EW1200 doesn't workTrunkUnconfirmed Task Description

Hi LEDE folks!

I’m running the latest snapshot (r5406-5e6792e) of LEDE on an Afoundry EW1200. It’s a vast improvement from the stock firmware - my heartfelt gratitude to the author(s) of the port.

There’s one problem. 5Ghz wifi works fine but 2.4Ghz doesn’t. It detects my 2.4Ghz device and when I hit “scan” in LuCI it returns a list of nearby SSIDs.

But when I try to configure the device as an access point it isn’t visible to any of my devices. I’ve tried various channels / settings but nothing makes a difference.

Steps to reproduce:

1. Install LEDE r5406-5e6792e snapshot (latest at the time of writing) on an Afoundry EW1200
2. Use opkg to install LuCI [NB: I don’t think LuCI is to blame; it’s just the interface I use]
3. In Network/Wireless hit “Scan” for “Generic MAC80211 802.11bgn” and verify it can detect other people’s networks
4. Back in Network/Wireless, hit add (or edit) to configure an access point on that device. Use any settings you like.
5. LuCI shows the AP as running but no other device can detect the SSID it’s broadcasting.

06.05.20213787Base systemBug ReportVery LowMedium21.02 RC1: BUG: Bad page state in process swapper/0openwrt-21.02Unconfirmed Task Description

Device used: RT-AC57U (mt7621 based device)
Version used: 21.02 RC1
Steps to reproduce: This ended up in my kernel log after a few days of uptime. I am unsure what exactly caused the issue.

I am currently beta testing the new 21.02 RC1 release on two different devices. Stability seems very good, but I did run into an issue with the aforementioned RT-AC57U. I found this stacktrace in the kernel log. I am unsure if this caused the network to go down, since I am not sure if I was using the network at that time. Does anyone have any idea what is causing this?

[410758.374134] BUG: Bad page state in process swapper/0  pfn:05edc
[410758.386105] page:809236f0 refcount:-1 mapcount:0 mapping:00000000 index:0x0
[410758.400121] flags: 0x0()
[410758.405331] raw: 00000000 00000000 00000122 00000000 00000000 00000000 ffffffff ffffffff
[410758.421588] raw: 00000000
[410758.426956] page dumped because: nonzero _refcount
[410758.436644] Modules linked in: xt_connlimit pppoe ppp_async nf_conncount iptable_nat xt_state xt_nat xt_helper xt_conntrack xt_connmark xt_connbytes xt_REDIRECT xt_MASQUERADE xt_FLOWOFFLOAD xt_CT wireguard pppox ppp_generic nf_nat_pptp nf_nat nf_flow_table_hw nf_flow_table nf_conntrack_rtcache nf_conntrack_pptp nf_conntrack_netlink nf_conntrack mt76x2e mt76x2_common mt76x02_lib mt7603e mt76 mac80211 libchacha20poly1305 libblake2s ipt_REJECT cfg80211 xt_time xt_tcpudp xt_tcpmss xt_statistic xt_recent xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_ecn xt_dscp xt_comment xt_TCPMSS xt_LOG xt_HL xt_DSCP xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc sch_cake poly1305_mips nf_reject_ipv4 nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 libcurve25519_generic libblake2s_generic iptable_raw iptable_mangle iptable_filter ipt_ECN ip_tables crc_ccitt compat chacha_mips br_netfilter sch_tbf sch_ingress sch_htb sch_hfsc em_u32 cls_u32 cls_tcindex cls_route cls_matchall cls_fw cls_flow cls_basic act_skbedit
[410758.436829]  act_mirred ledtrig_usbport xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ifb ip6_udp_tunnel udp_tunnel kpp leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd gpio_button_hotplug usbcore nls_base usb_common
[410758.712580] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.4.111 #0
[410758.724692] Stack : 00000000 80840000 00000003 8007d6e0 00000000 00000000 00000000 00000000
[410758.741481]         00000000 00000000 00000000 00000000 00000000 00000001 87c0db80 5fc2ce17
[410758.758268]         87c0dc18 00000000 00000000 00000000 00000038 805e1804 2e352064 31312e34
[410758.775053]         00000000 00004fd5 00000000 70617773 00000000 87c0db60 00000000 80840000
[410758.791840]         80604b20 806b0000 00000000 806d7f20 00000000 80359e2c 00000000 80810000
[410758.808627]         ...
[410758.813649] Call Trace:
[410758.813663] [<8007d6e0>] 0x8007d6e0
[410758.825779] [<805e1804>] 0x805e1804
[410758.832880] [<80359e2c>] 0x80359e2c
[410758.839978] [<8000b05c>] 0x8000b05c
[410758.847075] [<8000b064>] 0x8000b064
[410758.854173] [<805c6f9c>] 0x805c6f9c
[410758.861271] [<8014dabc>] 0x8014dabc
[410758.868420] [<80150ca4>] 0x80150ca4
[410758.875519] [<804a8b28>] 0x804a8b28
[410758.882662] [<806e0000>] 0x806e0000
[410758.889769] [<80151c80>] 0x80151c80
[410758.896866] [<80063508>] 0x80063508
[410758.903966] [<80150015>] 0x80150015
[410758.911063] [<804326ac>] 0x804326ac
[410758.918163] [<8001e448>] 0x8001e448
[410758.925262] [<80152bc4>] 0x80152bc4
[410758.932359] [<80433040>] 0x80433040
[410758.939456] [<800939cc>] 0x800939cc
[410758.946554] [<803dd720>] 0x803dd720
[410758.953652] [<800104dc>] 0x800104dc
[410758.960754] [<80433858>] 0x80433858
[410758.967852] [<80433acc>] 0x80433acc
[410758.974952] [<805e7d1c>] 0x805e7d1c
[410758.982053] [<80030768>] 0x80030768
[410758.989150] [<802f8404>] 0x802f8404
[410758.996249] [<80006c28>] 0x80006c28
[410759.003344] 
[410759.006466] Disabling lock debugging due to kernel taint
17.09.20214043Base systemBug ReportVery LowLow21.02 x86 generic ext4 combined image does not bootopenwrt-21.02Unconfirmed Task Description

x86 image “generic-ext4-combined.img.gz” of 21.02.0 does not boot — it can’t find rootfs and either panics or hangs.
Tested on qemu and virtualbox.

Broken image link:
https://downloads.openwrt.org/releases/21.02.0/targets/x86/generic/openwrt-21.02.0-x86-generic-generic-ext4-combined.img.gz

The efi image, “generic-ext4-combined-efi.img.gz”, works fine (tested with BIOS boot), that’s why I assume that “generic-ext4-combined.img.gz” is broken.

19.05.20213816KernelBug ReportVery LowHigh21.02-SNAPSHOT - Building with LXC-Support breaks passw...openwrt-21.02Waiting on reporter Task Description

Device: EspressoBin v5 Non-EMMC
Version: OpenWrt 21.02-SNAPSHOT, r0-bbbc01e

Nailed it down by starting from a fresh config a few times and cleaning up the build-chain.

As soon as I include LXC-Support from make menuconfig → utilities → LXC passwd seems broken (encryption?).

LuCi reports that it isn’t able to change the password - if I ssh into the box, use passwd it seemingly succeeds (it does set something) but afterwards login fails both via SSH and passwd.

Even if I build without LuCi the same is happening. dmesg shows nothing ... out of the ordinary - despite the Kernel being build with debug-flags.

Any clue how to debug that further? I’m pretty new to building OpenWRT myself.

 


Showing tasks 1 - 50 of 1430 Page 1 of 291 - 2 - 3 - 4 - 5 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing