OpenWrt/LEDE Project

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

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

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

OpenedIDCategoryTask TypePrioritySeveritySummary  descReported InStatus
15.11.20181952Base systemBug ReportVery LowHighwifi with hidden ssid and mac-filter doesn't work on IO...AllUnconfirmed Task Description

on tp-link_tl-wr842nd_v1 18.06 and 18.06.1

If hidden ssid and mac-filter is enabled, IOS 12 doesn't able to connect on this wifi network.

But if ssid broadcast is running with mac-filter enabled or ssid broadcast hidden and mac-filter disabled, then it works.

24.10.20171110Base systemBug ReportVery LowLowWifi unusable on HG556a using current trunkTrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on: Huawei ECHOLIFE HG556a Type B
- Software versions of LEDE release, packages, etc: Current Trunk - Powered by LuCI Master (git-17.294.24601-59a4e40) / LEDE Reboot SNAPSHOT r5122-f7a6fd3153

- Steps to reproduce: reboot

I did an update to trunk and made a lede build for the HG556a type B the other day. I have two of these HG556a type B routers both configured as wireless repeaters. I made no changes to the config, I simply wanted the latest security patches installed on my wifi repeaters. The first HG556a connects to a WWAN router that broadcasts 802.11n only, the other WWAN router broadcasts legacy wifi modes and 802.11n. The first works perfectly. The second throws up numerous errors in syslog from boot time, reboot every few hours and repeatedly disconnects from clients and the WWAN router. See syslog below:

Powered by LuCI Master (git-17.294.24601-59a4e40) / LEDE Reboot SNAPSHOT r5122-f7a6fd3153

Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.596484] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.604568] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.604568] 80543fac 00000000 00000004 81f73908 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.604568] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.604568] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.604568] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.604568] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.641077] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.643652] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.648182] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.653588] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.659056] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.665646] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.671458] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.676979] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.683219] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.690367]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.691843] —[ end trace 0902623f520cb0c7 ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.698309] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.703376] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.715140] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19932.858376] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.866468] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.866468] 80543fac 00000000 00000004 81f76648 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.866468] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.866468] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.866468] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.866468] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.902968] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.905544] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.910072] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.915479] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.920933] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.927490] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.933304] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.938829] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.945064] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.952230]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.953769] —[ end trace 0902623f520cb0c8 ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.958850] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.963902] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19932.975678] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19933.118913] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.126999] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.126999] 80543fac 00000000 00000004 81f76b18 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.126999] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.126999] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.126999] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.126999] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.163508] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.166083] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.170613] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.176018] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.181482] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.188060] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.193877] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.199401] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.205641] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.212796]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.214330] —[ end trace 0902623f520cb0c9 ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.219582] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.224643] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.236421] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19933.379658] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.387752] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.387752] 80543fac 00000000 00000004 81e79bc8 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.387752] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.387752] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.387752] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.387752] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.424254] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.426828] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.431359] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.436764] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.442218] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.448774] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.454587] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.460111] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.466350] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.473507]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.474982] —[ end trace 0902623f520cb0ca ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.480524] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.485601] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.497400] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19933.640637] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.648719] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.648719] 80543fac 00000000 00000004 82f334e8 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.648719] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.648719] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.648719] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.648719] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.685231] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.687807] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.692346] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.697751] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.703222] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.709776] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.715590] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.721115] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.727354] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.734503]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.735978] —[ end trace 0902623f520cb0cb ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.741140] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.746190] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.757949] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19933.901184] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.909277] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.909277] 80543fac 00000000 00000004 82f822d8 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.909277] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.909277] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.909277] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.909277] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.945779] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.948307] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.952874] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.958280] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.963731] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.970280] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.976092] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.981608] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.987845] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.994995]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19933.996472] —[ end trace 0902623f520cb0cc ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.001802] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.006851] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.018628] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19934.161867] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.169949] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.169949] 80543fac 00000000 00000004 82f82a68 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.169949] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.169949] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.169949] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.169949] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.206460] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.208989] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.213559] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.218963] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.224427] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.230982] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.236793] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.242310] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.248546] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.255694]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.257173] —[ end trace 0902623f520cb0cd ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.263788] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.268875] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.280640] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19934.423875] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.431969] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.431969] 80543fac 00000000 00000004 82f85598 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.431969] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.431969] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.431969] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.431969] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.468470] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.471043] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.475571] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.480985] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.486443] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.492998] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.498812] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.504334] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.510574] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.517723]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.519198] —[ end trace 0902623f520cb0ce ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.524808] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.529872] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.541651] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19934.684889] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.692972] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.692972] 80543fac 00000000 00000004 832f2f38 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.692972] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.692972] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.692972] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.692972] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.729518] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.732012] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.736580] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.741986] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.747459] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.754014] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.759824] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.765340] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.771598] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.778745]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.780221] —[ end trace 0902623f520cb0cf ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.785086] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.790094] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.801851] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19934.945087] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.953182] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.953182] 80543fac 00000000 00000004 82face88 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.953182] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.953182] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.953182] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.953182] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.989682] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.992210] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19934.996777] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.002184] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.007645] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.014194] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.020006] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.025529] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.031769] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.038926]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.040402] —[ end trace 0902623f520cb0d0 ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.045585] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.050620] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.062398] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19935.205636] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.213720] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.213720] 80543fac 00000000 00000004 82facbc8 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.213720] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.213720] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.213720] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.213720] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.250228] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.252758] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.257326] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.262734] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.268204] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.274764] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.280582] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.286105] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.292342] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.299491]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.300968] —[ end trace 0902623f520cb0d1 ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.306459] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.311521] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.323280] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19935.466515] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.474607] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.474607] 80543fac 00000000 00000004 82e5fc78 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.474607] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.474607] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.474607] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.474607] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.511109] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.513687] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.518223] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.523627] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.529085] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.535639] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.541450] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.546964] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.553203] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.560352]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.561886] —[ end trace 0902623f520cb0d2 ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.566864] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.571907] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.583683] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19935.726919] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.735002] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.735002] 80543fac 00000000 00000004 81cb0438 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.735002] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.735002] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.735002] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.735002] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.771513] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.774086] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.778616] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.784025] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.789498] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.796088] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.801901] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.807424] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.813664] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.820820]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.822353] —[ end trace 0902623f520cb0d3 ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.827454] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.832505] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.844268] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19935.987502] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.995596] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.995596] 80543fac 00000000 00000004 82ea0388 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.995596] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.995596] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.995596] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19935.995596] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.032096] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.034672] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.039202] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.044605] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.050060] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.056609] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.062421] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.067946] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.074183] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.081379]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.082854] —[ end trace 0902623f520cb0d4 ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.088001] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.093055] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.104833] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19936.248068] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.256152] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.256152] 80543fac 00000000 00000004 81f19178 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.256152] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.256152] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.256152] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.256152] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.292662] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.295236] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.299769] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.305173] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.310640] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.317193] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.323006] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.328528] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.334767] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.341917]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.343392] —[ end trace 0902623f520cb0d5 ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.348255] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.353264] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.365024] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19936.508257] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.516351] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.516351] 80543fac 00000000 00000004 81f19388 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.516351] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.516351] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.516351] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.516351] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.552851] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.555426] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.559954] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.565385] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.570846] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.577439] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.583234] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.588753] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.594994] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.602141]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.603617] —[ end trace 0902623f520cb0d6 ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.608659] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.613702] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.625478] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19936.768715] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.776800] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.776800] 80543fac 00000000 00000004 82ea09b8 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.776800] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.776800] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.776800] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.776800] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.813310] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.815844] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.820406] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.825814] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.831286] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.837839] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.843652] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.849166] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.855406] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.862554]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.864030] —[ end trace 0902623f520cb0d7 ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.869073] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.874115] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19936.885876] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19937.029111] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.037203] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.037203] 80543fac 00000000 00000004 81f19908 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.037203] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.037203] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.037203] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.037203] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.073706] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.076235] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.080803] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.086208] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.091662] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.098218] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.104028] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.109546] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.115783] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.122932]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.124408] —[ end trace 0902623f520cb0d8 ]— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.129917] ————[ cut here ]———— Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.134978] WARNING: CPU: 0 PID: 1399 at backports-2017-10-06/net/mac80211/rx.c:629 ieee80211_rx_napi+0×240/0x97c [mac80211]()
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.146753] Modules linked in: ath9k ath9k_htc ath9k_common pppoe ppp_async option cdc_mbim ath9k_hw ath usb_wwan rndis_host qmi_wwan pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_subset cdc_ncm cdc_ether cdc_eem xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_cTue Oct 24 13:08:04 2017 kern.warn kernel: [19937.289992] CPU: 0 PID: 1399 Comm: wpa_supplicant Tainted: G W 4.4.93 #0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.298075] Stack : 80546d42 00000049 00000000 803f0000 82f116a4 803e6da3 80372ae0 00000577
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.298075] 80543fac 00000000 00000004 82e2f858 00000000 800594cc 8037d094 803e0000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.298075] 00000000 00000000 8037b4a0 82f0f8d4 00000000 800573d0 80546d42 00000072
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.298075] 803e5e50 801bdc00 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.298075] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.298075] ...
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.334586] Call Trace:
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.337114] [<80024f84>] show_stack+0×54/0×88 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.341682] [<80032f00>] warn_slowpath_common+0xa0/0xd0
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.347086] [<80032fb8>] warn_slowpath_null+0×18/0×24 Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.352552] [<82c262e4>] ieee80211_rx_napi+0×240/0x97c [mac80211]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.359107] [<832c7260>] ath_rx_tasklet+0xc24/0xc88 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.364916] [<832c733c>] ath_stoprecv+0×78/0xf34 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.370434] [<832c3230>] ath9k_deinit_device+0x6d0/0×944 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.376670] [<832c503c>] ath9k_calculate_summary_state+0×500/0×600 [ath9k]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.383819]
Tue Oct 24 13:08:04 2017 kern.warn kernel: [19937.385297] —[ end trace 0902623f520cb0d9 ]— Tue Oct 24 13:08:04 2017 daemon.info odhcpd[914]: Using a RA lifetime of 0 seconds on br-lan
Tue Oct 24 13:08:04 2017 daemon.notice hostapd: nl80211: nl80211_recv_beacons→nl_recvmsgs failed: -5
Tue Oct 24 13:10:24 2017 daemon.info hostapd: wlan0-1: STA f0:25:b7:b2:fe:ea IEEE 802.11: authenticated
Tue Oct 24 13:10:24 2017 daemon.info hostapd: wlan0-1: STA f0:25:b7:b2:fe:ea IEEE 802.11: associated (aid 1)
Tue Oct 24 13:10:24 2017 daemon.notice hostapd: wlan0-1: AP-STA-CONNECTED f0:25:b7:b2:fe:ea
Tue Oct 24 13:10:24 2017 daemon.info hostapd: wlan0-1: STA f0:25:b7:b2:fe:ea RADIUS: starting accounting session 747735F6C298AD3B
Tue Oct 24 13:10:24 2017 daemon.info hostapd: wlan0-1: STA f0:25:b7:b2:fe:ea WPA: pairwise key handshake completed (RSN)
Tue Oct 24 13:10:24 2017 daemon.info dnsmasq-dhcp[2988]: DHCPDISCOVER(br-lan) f0:25:b7:b2:fe:ea

 


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

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

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

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

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

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


18.08.20181792KernelBug ReportVery LowMediumwifi stick based on atheros AR9271 doesn't work with 18...openwrt-18.06Unconfirmed Task Description

- Device problem occurs on

 Astoria Networks ARV7518PW

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

OpenWrt 18.06.0-rc2 r7141-e4d0ee5af5

My wifi stick based on the AR9271 that worked with openwrt 17.01.05 doesn’t work with this new rc (I cannot test it on development snapshots due to bug #1634).

dmesg show this

[  244.724712] usb 1-1: new high-speed USB device number 3 using dwc2
[  244.740095] dwc2 1e101000.ifxhcd: Mode Mismatch Interrupt: currently in Host mode
[  244.746127] dwc2 1e101000.ifxhcd: Mode Mismatch Interrupt: currently in Host mode
[  244.972976] usb 1-1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[  245.279016] usb 1-1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
[  245.532487] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
[  245.965179] ath: phy2: Mac Chip Rev 0x0f.3 is not supported by this driver
[  245.970678] ath: phy2: Unable to initialize hardware; initialization status: -122
[  245.978013] ath: phy2: Unable to initialize hardware; initialization status: -122
[  245.985233] ath9k_htc: Failed to initialize the device
[  246.093496] usb 1-1: ath9k_htc: USB layer deinitialized

The error is Mac Chip Rev 0x0f.3 is not supported by this driver which I googled and found a couple of reports regarding ARM based SBC (on my laptop, x86_64, the stick works fine), with no solution though.

One of them suggests that the device works if it’s plugged in while the system boots. I tried that and, while it doesn’t complain about the mac chip not supported, it still doesn’t work:

[   15.833888] usb 1-1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
[   16.048965] kmodloader: done loading kernel modules from /etc/modules.d/*
[   16.884889] ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive
[   16.889498] ath9k_htc: Failed to initialize the device
[   16.929806] usb 1-1: ath9k_htc: USB layer deinitialized



06.12.20171209Base systemBug ReportVery LowMediumWiFi random disconnection on WRT3200ACMTrunkUnconfirmed Task Description

Router: Linksys WRT3200ACM

LEDE: Powered by LuCI lede-17.01 branch (git-17.290.79498-d3f0685) / LEDE Reboot 17.01.4 r3560-79f57e422d

Kernel: 4.4.92

Forum thread: https://forum.openwrt.org/viewtopic.php?pid=369295#p369295

mwlwifi version: kmod-mwlwifi - 4.4.92+10.3.4.0.git-2017-06-06-1

Wireless radio0 is working perfectly fine but not on radio1 or radio2. There’s random disconnection, can happen 3 times a day or once per 3 day. Only solution is to reboot the router. See the forum thread for more information.

13.02.20181356Base systemBug ReportVery LowLowWiFi Monitor interface is created on wrong channelTrunkUnconfirmed Task Description

- Device problem occurs on: PC-Engines APU3
- Software versions of OpenWrt/LEDE release: LEDE 17.01.4

Just created a monitor interface with an WLE200NX:

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '5'
        option hwmode '11g'
        option path 'pci0000:00/0000:00:02.5/0000:04:00.0'
        option htmode 'HT40'
        option disabled '0'

config wifi-iface
        option mode 'monitor'
        option device 'radio0'
        option ifname 'mon0'

And restarted the device. It was expected that the monitor interface is now in HT40 mode (able to receive on HT40) and on channel 5. But in reality, the device was now on channel 1 and used a 20MHz (non-HT) channel setting:

root@LEDE:/# iw dev
phy#0
        Interface mon0
                ifindex 7
                wdev 0x2
                addr 00:11:22:33:44:55
                type monitor
                channel 1 (2412 MHz), width: 20 MHz (no HT), center1: 2412 MHz
                txpower 20.00 dBm
18.12.20192687Base systemBug ReportVery LowVery LowWiFi LED does not dynamically track state of radio on Z...openwrt-19.07Unconfirmed Task Description

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

 

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

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

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

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

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

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

21.02.20192137Base systemBug ReportVery LowLowwifi isolate clients not working on several routersAllUnconfirmed Task Description

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

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

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

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

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

05.02.2017469Base systemBug ReportVery LowLowWifi firmware file is not available on ZyXEL P-2812HNU-...lede-17.01Unconfirmed Task Description

Kernel log:

[   11.336056] PCI: Enabling device 0000:00:0e.0 (0000 -> 0002)
[   11.340485] ieee80211 phy0: rt2x00lib_request_eeprom_file: Info - Loading EEPROM data from 'RT3062.eeprom'.
[   11.350276] rt2800pci 0000:00:0e.0: Direct firmware load for RT3062.eeprom failed with error -2
[   11.358782] rt2800pci 0000:00:0e.0: Falling back to user helper
[   11.479331] firmware RT3062.eeprom: firmware_loading_store: map pages failed
[   11.485217] ieee80211 phy0: rt2x00lib_request_eeprom_file: Error - Failed to request EEPROM.
[   11.493519] rt2800pci: probe of 0000:00:0e.0 failed with error -11

Firmware files:

root@lede:/lib/firmware# ls /lib/firmware/
lantiq-vrx200-a-to-b.bspatch                 rt2860.bin                                   xcpe_581816_580B11.LICENSE                   xcpe_581816_580B11_to_579906_574402.bspatch
lantiq-vrx200-a.bin                          rt3290.bin                                   xcpe_581816_580B11.bin

After adding a RT3062.eeprom the wifi port is available.

 


23.11.20192625Base systemBug ReportVery LowLowWiFi clients are isolated on WRT1900acs v2 running 19.0...TrunkUnconfirmed Task Description

I did an upgrade on a WRT1900acs v2 router (my backup router) that was running 18.06.4 (I think) via LuCI using the image “openwrt-19.07.0-rc1-mvebu-cortexa9-linksys_wrt1900acs-squashfs-sysupgrade.bin” keeping the old configuration. Everything seemed good except the clients could not connect or ping each other. The router could reach/ping the clients. This was the case whether or not “Isolate Clients” is set in the LuCI Wireless → Edit → Advanced Settings.

I noticed that if I connect an ethernet wire to one of the clients (a Raspberry Pi) and hook it to the router that I could connect/ping the Pi using either the IP associated with the ethernet connection or the IP associated with the WiFi connection from another client. When I disconnect the ethernet on the Pi I can no longer connect to the Pi’s wireless IP
address.

I decided to reinstall 19.07.0-rc1 to see where the isolated client behavior starts. After I reinstalled 19.07.0-rc1 I restored the configuration using LuCI System → Backup / Flash Firmware → Restore Backup. After it rebooted it was working, clients were not isolated. I installed a few packages that I wanted, here’s the list:

ca-bundle_20190110-1_all.ipk
ca-certificates_20190110-1_all.ipk
kmod-tun_4.14.151-1_arm_cortex-a9_vfpv3.ipk
liblzo2_2.10-2_arm_cortex-a9_vfpv3.ipk
libmbedtls12_2.16.3-1_arm_cortex-a9_vfpv3.ipk
libopenssl1.1_1.1.1d-2_arm_cortex-a9_vfpv3.ipk
libustream-mbedtls20150806_2019-11-05-c9b66682-2_arm_cortex-a9_vfpv3.ipk
openvpn-mbedtls_2.4.7-2_arm_cortex-a9_vfpv3.ipk

Everything still working. I wanted WPA3 so I removed wpad-basic and installed

wpad-openssl_2019-08-08-ca8c2bd2-1_arm_cortex-a9_vfpv3.ipk

Everything still working. I changed the 5 Ghz wifi from WPA2-SPK to WPA3-SAE. Everything still working. I changed the 2.4 Ghz wifi from WPA2-SPK to WPA2-SPK/WPA3-SAE mixed. This is when it stopped working. I don’t know if this last step actually caused the problem since setting both wifi networks back to WPA2-SPK and rebooting (and unplugging for 5 minutes) does not fix the problem, clients are still isolated. Pretty much all clients are on the 2.4 Ghz network.

Here are a couple bits of diagnostic which may or may not be helpful:

————→ when everything is working (clients not isolated):

# cat /sys/devices/virtual/net/eth0.1/brport/hairpin_mode
0

# cat /sys/devices/virtual/net/eth0.1/brport/isolated
0

# cat /var/run/hostapd-phy0.conf
driver=nl80211
logger_syslog=127
logger_syslog_level=2
logger_stdout=127
logger_stdout_level=2
country_code=US
ieee80211d=1
ieee80211h=1
hw_mode=a
beacon_int=100
channel=36

tx_queue_data2_burst=2.0
ieee80211n=1
ht_coex=0
ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][DSSS_CCK-40]
vht_oper_chwidth=1
vht_oper_centr_freq_seg0_idx=42
ieee80211ac=1
vht_capab=[RXLDPC][SHORT-GI-80][SU-BEAMFORMER][SU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][MAX-A-MPDU-LEN-EXP7]

interface=wlan0
ctrl_interface=/var/run/hostapd
ap_isolate=1
bss_load_update_period=60
chan_util_avg_period=600
disassoc_low_ack=1
preamble=1
wmm_enabled=1
ignore_broadcast_ssid=0
uapsd_advertisement_enabled=1
utf8_ssid=1
multi_ap=0
wpa_passphrase=XXXXXXXXXX
auth_algs=1
wpa=2
wpa_pairwise=CCMP
ssid=folly_5g
bridge=br-lan
wpa_disable_eapol_key_retries=0
wpa_key_mgmt=WPA-PSK
okc=0
disable_pmksa_caching=1
bssid=62:38:e0:12:78:f3

# cat /var/run/hostapd-phy1.conf
driver=nl80211
logger_syslog=127
logger_syslog_level=2
logger_stdout=127
logger_stdout_level=2
country_code=US
ieee80211d=1
hw_mode=g
beacon_int=100
channel=7

ieee80211n=1
ht_coex=0
ht_capab=[LDPC][SHORT-GI-20][SHORT-GI-40][DSSS_CCK-40]

interface=wlan1
ctrl_interface=/var/run/hostapd
ap_isolate=1
bss_load_update_period=60
chan_util_avg_period=600
disassoc_low_ack=1
preamble=1
wmm_enabled=1
ignore_broadcast_ssid=0
uapsd_advertisement_enabled=1
utf8_ssid=1
multi_ap=0
wpa_passphrase=XXXXXXXXXX
auth_algs=1
wpa=2
wpa_pairwise=CCMP
ssid=folly
bridge=br-lan
wpa_disable_eapol_key_retries=0
wpa_key_mgmt=WPA-PSK
okc=0
disable_pmksa_caching=1
bssid=62:38:e0:12:78:f2

————→ when it’s not working (clients isolated)

# cat /sys/devices/virtual/net/eth0.1/brport/hairpin_mode
0

# cat /sys/devices/virtual/net/eth0.1/brport/isolated
0

# cat /var/run/hostapd-phy0.conf
driver=nl80211
logger_syslog=127
logger_syslog_level=2
logger_stdout=127
logger_stdout_level=2
country_code=US
ieee80211d=1
ieee80211h=1
hw_mode=a
beacon_int=100
channel=36

tx_queue_data2_burst=2.0
ieee80211n=1
ht_coex=0
ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][DSSS_CCK-40]
vht_oper_chwidth=1
vht_oper_centr_freq_seg0_idx=42
ieee80211ac=1
vht_capab=[RXLDPC][SHORT-GI-80][SU-BEAMFORMER][SU-BEAMFORMEE][RX-ANTENNA-PATTERN
][TX-ANTENNA-PATTERN][RX-STBC-1][MAX-A-MPDU-LEN-EXP7]

interface=wlan0
ctrl_interface=/var/run/hostapd
ap_isolate=1
bss_load_update_period=60
chan_util_avg_period=600
disassoc_low_ack=1
preamble=1
wmm_enabled=1
ignore_broadcast_ssid=0
uapsd_advertisement_enabled=1
utf8_ssid=1
multi_ap=0
sae_require_mfp=1
wpa_passphrase=XXXXXXXXXX
auth_algs=1
wpa=2
wpa_pairwise=CCMP
ssid=folly_5g
bridge=br-lan
wpa_disable_eapol_key_retries=0
wpa_key_mgmt=SAE
okc=1
ieee80211w=2
group_mgmt_cipher=AES-128-CMAC
bssid=62:38:e0:12:78:f3

# cat /var/run/hostapd-phy1.conf
driver=nl80211
logger_syslog=127
logger_syslog_level=2
logger_stdout=127
logger_stdout_level=2
country_code=US
ieee80211d=1
hw_mode=g
beacon_int=100
channel=7

ieee80211n=1
ht_coex=0
ht_capab=[LDPC][SHORT-GI-20][SHORT-GI-40][DSSS_CCK-40]

interface=wlan1
ctrl_interface=/var/run/hostapd
ap_isolate=1
bss_load_update_period=60
chan_util_avg_period=600
disassoc_low_ack=1
preamble=1
wmm_enabled=1
ignore_broadcast_ssid=0
uapsd_advertisement_enabled=1
utf8_ssid=1
multi_ap=0
wpa_passphrase=XXXXXXXXXX
auth_algs=1
wpa=2
wpa_pairwise=CCMP
ssid=folly
bridge=br-lan
wpa_disable_eapol_key_retries=0
wpa_key_mgmt=WPA-PSK WPA-PSK-SHA256
okc=0
disable_pmksa_caching=1
ieee80211w=1
group_mgmt_cipher=AES-128-CMAC
bssid=62:38:e0:12:78:f2

11.02.2017499Base systemBug ReportVery LowLowWiFi client mode leaves router inaccessible if upstream...TrunkUnconfirmed Task Description

This bug was originally reported to the OpenWrt team and there is a discussion of it in their mailing list. Luiz Angelo Daros de Luca suggested reporting here (and switching to LEDE, which I will do).

I have a TP-Link TL-MR3020 v1.9 with Chaos Calmer 15.05.01. I’m using it to provide a WiFi access point to my phone/tablet while I travel, and it’s acting as a WiFi client for the various hostels I visit.

If you configure it as a wifi client with a wwan interface using the LuCI scan/join wizard, and then you configure a wifi access point on the same radio, the router works as expected and when you connect to the router’s AP, you get Internet via the client connection.

However, if you move out of range of the network the router is a client of, or if it goes down, when you power off the OpenWrt router and power back on, the access point won’t come up.

The AP will only come up if the client network you configured is also working; so you have no way to connect to the router over wifi, and no way to reconfigure the router, if that client network is down or out of range.

This is a particular problem for a travel router because it will often move it out of range of the original upstream network, and you may only have a wifi-capable device with which to reconfigure it.

The Ethernet port on the router does remain active, so I can tell it does actually boot. It’s just the radio that doesn’t come up. I managed to get back in range of a network once, and the router worked as expected.

It doesn’t matter whether the AP or client connection are configured first or second on the radio interface, and, unticking “bring up on boot” for the wwan interface has no effect on the behaviour.

Steps to reproduce: Connect the router to a wifi network as a client using the Join wizard. Add a wifi master-mode access point on the same radio interface. Verify you can access the Internet by joining the router’s new master AP. Reboot the router with the original network it was a client of turned off. Notice the router’s AP you configured never comes up.

Expected behaviour: The master access point of the router should always come up, regardless of the availability of the client network.

The OpenWRT team will not fix it, but had some explanation as to why it is happening. IMO, it’s still a very frustrating bug and most users would expect the behaviour I did.

07.03.20181416PackagesBug ReportVery LowMediumWiFi cannot up on Comfast E355AC v2(patch file for fix ...lede-17.01Unconfirmed Task Description

Hi,

Device problem occurs on:

  Comfast-EA355AC-V2 (QCA9531 + QCA9886)

Software versions:

  LEDE v17.01.4
  netifd: c92106e3048ae10cb04a7c7303ba5f53bc057953

Steps to reproduce:

  It need to continuely reset to factory default and reboot.

When it occurs, system boot up successful. but wireless interface will setup and teardown for several times and wireless interface will disappear in the final.
After i dived into the code, I found that, check_pid_path() @177 of utils.c of netifd project will report process(hostapd) dead when system booting up during pivot_root processing.
the result of readlink of “/proc/PID/exe” will return the execution file name with “/tmp/root” as prefix(maybe something other too).
So I am trying to fix it by the patch file attached.

Please review and merge into master if it looks good.

Sorry for my bad english.

And thanks in advance.

Best Regards,
Michael


25.02.20202856Base systemBug ReportVery LowHighWifi "dies" (hostapd drops all clients) on some ar71xx ...openwrt-19.07New Task Description

This issue is very strange, i don’t even know if it’s just faulty hardware but i have it happening on multiple devices now

Most affected hardware

  • Nanobridge M5 , in this case transmitting enough data can trigger it almost instantly
  • TL-WR841ND , in this case i had it happen like 3-4 times a year
  • CPE 210 v3 , in this case it happens like each week

For the last one, which is running 19.07 i found on the system log

Tue Feb 25 07:38:58 2020 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED [redacted mac1]
Tue Feb 25 07:38:58 2020 daemon.info hostapd: wlan0: STA [redacted mac1] IEEE 802.11: disassociated due to inactivity
Tue Feb 25 07:38:59 2020 daemon.info hostapd: wlan0: STA [redacted mac1] IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Tue Feb 25 07:41:32 2020 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED [redacted mac2]
Tue Feb 25 07:41:32 2020 daemon.info hostapd: wlan0: STA [redacted mac2] IEEE 802.11: disassociated due to inactivity
Tue Feb 25 07:41:33 2020 daemon.info hostapd: wlan0: STA [redacted mac2] IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Tue Feb 25 07:42:49 2020 daemon.notice hostapd: wlan0: AP-STA-POLL-OK [redacted mac3]
Tue Feb 25 07:49:55 2020 daemon.notice hostapd: wlan0: AP-STA-POLL-OK [redacted mac3]
Tue Feb 25 07:55:02 2020 daemon.notice hostapd: wlan0: AP-STA-POLL-OK [redacted mac3]
Tue Feb 25 08:00:15 2020 daemon.notice hostapd: wlan0: AP-STA-POLL-OK [redacted mac3]
Tue Feb 25 08:05:25 2020 daemon.notice hostapd: wlan0: AP-STA-POLL-OK [redacted mac3]
Tue Feb 25 08:10:44 2020 daemon.notice hostapd: wlan0: AP-STA-POLL-OK [redacted mac3]
Tue Feb 25 08:16:00 2020 daemon.notice hostapd: wlan0: AP-STA-POLL-OK [redacted mac3]
02.05.20203061Base systemBug ReportVery LowLowWi-Fi: Cannot set country code on AVM FRITZ 1750ETrunkUnconfirmed Task Description

It is not possible to set the country code on both 2.4 and 5 GHz.

 

Device: AVM FRITZ!WLAN REPEATER 1750E (target ath79 generic)
Software version: OpenWrt SNAPSHOT r13136-ad27c133eb
Steps to reproduce:

Console:
Execute iw reg set DE and then iw reg get, and see how “global” sets to “DE” but phy#1 and phy#0 remain on “US”.

LuCI:
Sign in to LuCI, go to Network>Wireless (click Edit and then the “Advanced” tab) try to change the country code on either Wi-Fi device/frequency to “DE” and see how it resets to “driver default” after apply, which seems to be “US”.

02.05.20203062Base systemBug ReportVery LowLowWi-Fi 5GHz: Cannot use some channels on AVM FRITZ 1750ETrunkUnconfirmed Task Description

It is not possible to use some channels with OpenWrt on this particular device, which are known to work with the stock firmware.

Device: AVM FRITZ!WLAN REPEATER 1750E (target ath79 generic)
Software version: OpenWrt SNAPSHOT r13136-ad27c133eb
Steps to reproduce:

Try to set the 5GHz Wi-Fi channel to 100 (some others affected as well), and see how transmit power falls to 0 dBm and Wi-Fi does not seem to work.

Possibly related issue: https://bugs.openwrt.org/index.php?do=details&task_id=3061

31.08.20181827Base systemBug ReportVery LowHighwhy has uci no package which depends on?AllUnconfirmed Task Description

Hi,
today I did a bad thing, which only could happen, because uci have no package which depends on: I uninstalled which my currently developed clean script uci package and after reboot the router doesnt came up again :D

But why is this main package no refereed anywhere?

Regards,
Thomas

30.05.20181569Base systemBug ReportVery LowLowWhy comment out firewall rules when we can disable them...TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

1U Xeon D-1518 server

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

x86_64, master, r5968, firewall

- Steps to reproduce

Looking at /etc/config/firewall I see:

# port redirect of remapped ssh port (22001) on wan
#config redirect
#      option src              wan
#      option src_dport        22001
#      option dest             lan
#      option dest_port        22
#      option proto            tcp

but would like to see:

# port redirect of remapped ssh port (22001) on wan
config redirect
      option src              wan
      option src_dport        22001
      option dest             lan
      option dest_port        22
      option proto            tcp
      option enabled          false

instead. Note the “option enabled false” line.

22.05.20203114Base systemBug ReportVery LowMediumWhen using CLIENT+AP with 5GHZ on same radio, AP doesn'...openwrt-19.07Unconfirmed Task Description

Workaround is to set the channel on the AP to an arbitrary channel other than ‘auto’. It’s still auto since it has to be the same channel as the client uses, but at least now it shows up.
Verified the issue on 19.07.3 with both Xiaomi MIR3G and Netgear WNDR3700v5, both MT7621 based.

 


14.03.20192184Base systemBug ReportVery LowLowWhen interface is deleted from LuCI, it's name isn't de...openwrt-18.06Unconfirmed Task Description

If an interface is created and assigned a firewall zone, then this interface is deleted form LuCI, its name remains in /etc/config/firewall

13.04.20192235Base systemBug ReportVery LowLowWhen filtering the packages list in LuCI then adding or...openwrt-18.06Unconfirmed Task Description

Observed the issue on Archer C7 v2 running 18.06.01

When filtering the package list in LuCI then adding or removing a packages, the filter is reset, and the user has to filter again if they want to add or remove more packages.

Let’s say that you want to add ddns support. So you filter by “ddns” and you get a lit of the packages that match the filter. When you install one of them, the filter is reset and the full list of the packages is displayed, so you have to apply the filter again if you want to ad more packages.

The same happens when you remove packages.

Ideal situation is that the filter doesn’t reset, and that the scroll position through the list isn’t maintained as well.


12.09.20192492ToolchainBuild FailureVery LowMediumWhen building an image from an imagebuilder the build f...TrunkUnconfirmed Task Description

When building an image (from git commit 81764319637f408623ed9f4bae3f0d149b010f07) from already built imagebuilder for ar71xx target, the build fails at the end (after “Finalizing root filesystem”) because of missing ‘mips-openwrt-linux-musl’. I searched the original build directory in openwrt tree and this lib seems to be to find (among others) in:

./staging_dir/toolchain-mips_24kc_gcc-8.3.0_musl/mips-openwrt-linux-musl

but for some reason is not saved into the imagebuilder image.

This is the message from the end of imagebuilder build.

Finalizing root filesystem...
...
Enabling urandom_seed
Enabling urngd
/home/risa/openwrt/openwrt-imagebuilder-ar71xx-generic.Linux-x86_64/staging_dir/host/bin/find: '/home/risa/openwrt/openwrt-imagebuilder-ar71xx-generic.Linux-x86_64/staging_dir/target-mips_24kc_musl/root-ar71xx': No such file or directory
/home/risa/openwrt/openwrt-imagebuilder-ar71xx-generic.Linux-x86_64/staging_dir/host/bin/find: '/home/risa/openwrt/openwrt-imagebuilder-ar71xx-generic.Linux-x86_64/staging_dir/target-mips_24kc_musl/root-ar71xx': No such file or directory
Traceback (most recent call last):
  File "/home/risa/openwrt/openwrt-imagebuilder-ar71xx-generic.Linux-x86_64/staging_dir/host/bin/mklibs", line 426, in <module>
    inode = os.stat(prog)[ST_INO]
FileNotFoundError: [Errno 2] No such file or directory: 'mips-openwrt-linux-musl'
make[2]: *** [Makefile:163: prepare_rootfs] Error 1
make[1]: *** [Makefile:119: _call_image] Error 2
make: *** [Makefile:197: image] Error 2
05.04.20202968Base systemBug ReportVery LowLowwget/uclient issue, when using Basic AuthTrunkUnconfirmed Task Description

0.0.0.0 - - [05/Apr/2020:07:01:00 +0200] “GET /url.php HTTP/1.1” 401 681 “-” “uclient-fetch” 0.0.0.0 - user [05/Apr/2020:07:01:00 +0200] “GET /url.php HTTP/1.1” 200 358 “-” “uclient-fetch”

Reproducable at will, whenever Basic Auth used
wget –user=user –password=mypassword http://url.php

When using Basic Auth, wget/uclient-fetch first tries without credentials.
This might trigger intrusion protection on the server. And is a waste of bandwidth.


10.02.20192114Base systemBug ReportVery LowHighWG302v1 (ixp4xx-generic) LAN (eth0) start and then stop...openwrt-18.06Unconfirmed Task Description

Hello

Device: Netgear WG302v1 ixp4xx
FW: 18.06.1 & 18.06.2

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

No packages are installed only stock zImage and Shashfs.

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

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

Step to reproduce:
Flash & boot.

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

Kind Regards

26.05.20192295Base systemBug ReportVery LowMediumWebsite interface not accessible via port 80openwrt-18.06Unconfirmed Task Description

Model Buffalo WZR-HP-G300NH
Architecture Atheros AR9132 rev 2
Firmware Version OpenWrt 18.06.2 r7676-cddd7b4c77 / LuCI openwrt-18.06 branch (git-19.020.41695-6f6641d)
Kernel Version 4.9.152

After boot, I cannot access the configuration interface via port 80.
Investigation reveals the following:

- netstat: uhttpd is not listening on port 80

# netstat -anp | grep uhttpd
tcp 0 0 0.0.0.0:9443 0.0.0.0:* LISTEN 921/uhttpd
tcp 0 0 0.0.0.0:9080 0.0.0.0:* LISTEN 921/uhttpd

- ps: uhttpd _should_ be listening on port 80

# ps | grep uhttpd

921 root      1328 S    /usr/sbin/uhttpd -f -h /www -r skynet -x /cgi-bin -t 60 -T 30 -A 1 -n 3 -R -p 0.0.0.0:9080 -p <br-lan IP>:80 -p 0.0.0.0:9443

- logread: Something went screwy at startup

# logread | grep httpd
Sun May 26 11:51:26 2019 daemon.err uhttpd[921]: bind(): Address not available

If I run `/etc/init.d/uhttpd restart`, the service comes up properly, listening on port 80; this suggests that something is interfering during early startup, though I have no idea what it could possibly be.

21.03.2017649Base systemBug ReportVery LowLowWDS not working on ath9k-htc TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on: Any device with an wifi USB adapter with the chipset AR9271 (TPLink WN722N in my case).
- Software versions of LEDE release, packages, etc: Latest trunk LEDE versions.
- Steps to reproduce

 

Configure the USB AR9271 adapter as WDS AP, try to associate any other router as WDS Client (in my case the WDS Client is a TPLink WR741ND router, also compiled with latest trunk).
They both associate correctly, but there is no connection between them.

Here is a hostapd log on the WDS AP:

Mon Mar 20 14:05:00 2017 daemon.notice hostapd: wlan1: interface state ENABLED->DISABLED
Mon Mar 20 14:05:00 2017 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 94:0c:6d:b0:f4:ac
Mon Mar 20 14:05:00 2017 daemon.notice hostapd: wlan1: AP-DISABLED
Mon Mar 20 14:05:00 2017 daemon.notice hostapd: wlan1: CTRL-EVENT-TERMINATING
Mon Mar 20 14:05:00 2017 daemon.notice hostapd: nl80211: deinit ifname=wlan1 disabled_11b_rates=0
Mon Mar 20 14:05:01 2017 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf
Mon Mar 20 14:05:02 2017 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Mon Mar 20 14:05:02 2017 daemon.err hostapd: Using interface wlan1 with hwaddr e8:de:27:a4:58:21 and ssid "EB1DJ"
Mon Mar 20 14:05:02 2017 daemon.notice hostapd: wlan1: interface state COUNTRY_UPDATE->ENABLED
Mon Mar 20 14:05:02 2017 daemon.notice hostapd: wlan1: AP-ENABLED
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: authentication OK (open system)
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac MLME: MLME-AUTHENTICATE.indication(94:0c:6d:b0:f4:ac, OPEN_SYSTEM)
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac MLME: MLME-DELETEKEYS.request(94:0c:6d:b0:f4:ac)
Mon Mar 20 14:05:03 2017 daemon.info hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: authenticated
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: association OK (aid 1)
Mon Mar 20 14:05:03 2017 daemon.info hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: associated (aid 1)
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac MLME: MLME-ASSOCIATE.indication(94:0c:6d:b0:f4:ac)
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac MLME: MLME-DELETEKEYS.request(94:0c:6d:b0:f4:ac)
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: binding station to interface 'wlan1'
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: event 1 notification
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: start authentication
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.1X: unauthorizing port
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: sending 1/4 msg of 4-Way Handshake
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: EAPOL-Key timeout
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: sending 1/4 msg of 4-Way Handshake
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: received EAPOL-Key frame (2/4 Pairwise)
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: sending 3/4 msg of 4-Way Handshake
Mon Mar 20 14:05:03 2017 daemon.err hostapd: nl80211: EAPOL TX: No message of desired type
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: ignore retransmitted EAPOL-Key 2/4 Pairwise - SNonce did not change
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: EAPOL-Key timeout
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: sending 3/4 msg of 4-Way Handshake
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: received EAPOL-Key frame (4/4 Pairwise)
Mon Mar 20 14:05:03 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 94:0c:6d:b0:f4:ac
Mon Mar 20 14:05:03 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.1X: authorizing port
Mon Mar 20 14:05:03 2017 daemon.info hostapd: wlan1: STA 94:0c:6d:b0:f4:ac RADIUS: starting accounting session 7797AE68AEE646F3
Mon Mar 20 14:05:03 2017 daemon.info hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: pairwise key handshake completed (RSN)
Tue Mar 21 09:58:59 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: authentication OK (open system)
Tue Mar 21 09:58:59 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac WPA: event 0 notification
Tue Mar 21 09:58:59 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac MLME: MLME-AUTHENTICATE.indication(94:0c:6d:b0:f4:ac, OPEN_SYSTEM)
Tue Mar 21 09:58:59 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac MLME: MLME-DELETEKEYS.request(94:0c:6d:b0:f4:ac)
Tue Mar 21 09:58:59 2017 daemon.info hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: authenticated
Tue Mar 21 09:58:59 2017 daemon.debug hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: association OK (aid 1)
Tue Mar 21 09:58:59 2017 daemon.info hostapd: wlan1: STA 94:0c:6d:b0:f4:ac IEEE 802.11: associated (aid 1)

I think the error Mon Mar 20 14:05:03 2017 daemon.err hostapd: nl80211: EAPOL TX: No message of desired type has something to do with WDS not working?.

If there is any other info, tests etc you require feel free to ask.

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

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

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

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

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

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

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

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

R7800 network config

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

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

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

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

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

R7800 wireless config

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

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

ArcherC7v2 network config

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

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

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

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

ArcherC7v2 wireless config

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

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

WAN zone on firewall on R7800 has

option mtu_fix '1'
15.12.20182002KernelBug ReportVery LowLowWDR4300 lost USB storageopenwrt-18.06Unconfirmed Task Description

Hi!

After a fresh install on a WDR4300, I decided to set up the extroot overlay.
After heavy IO usage (vsftpd copy to PC) the usb storage just got disappeared and reconnected as a new device (sdb) later.
It’s such a pain, because none of luci or ssh connection works this case. (I can have a try without password and telnet, but the logs are there)
The flash device (Transcend 790K) is so reliable, has been working on the previous 1043 v1 and v2 installations for years (with overlay as well).

I had something similar before with both the 1043 devices before, when there was a better quality usb hub in place.
I assume, this device is not so stable when the flash device is a connected with an external (1043) or built-in (4300) usb hub.
I tried my other 790K device with a simple DD test to find out maybe the older drive is problematic, but the newer failed as well. The power consumption is maximum ~0.05Amps at heavy use (nothing). I will have a try with another Kingston drive tomorrow.
In the attached dmesg log the newer drive was in place used without the overlay function.

Regards

06.11.20171152Base systemBug ReportVery LowHighWDR3600: Wifi randomly turns off and get disabledlede-17.01Unconfirmed Task Description

Running LEDE 17.01.4

I’m not sure how do I reproduce this problem, it just happen randomly at random time.

This never happened back when I used OpenWRT, were there some regression somewhere?

So with LEDE, my router’s wifi randomly disconnect and disable itself. I have read the logs (provided below) yet I can’t see anything suspicious. I only see these:

Mon Nov  6 13:54:45 2017 daemon.notice procd: /etc/init.d/network: 'radio0' is disabled
Mon Nov  6 13:54:45 2017 daemon.notice procd: /etc/init.d/network: 'radio1' is disabled
Mon Nov  6 13:54:45 2017 daemon.notice procd: /etc/init.d/network: 'radio0' is disabled
Mon Nov  6 13:54:45 2017 daemon.notice procd: /etc/init.d/network: 'radio1' is disabled

This was around the time people in my home messaged me that they cannot find the access point from their devices

It bugs me because I usually go to the office in the afternoon and people in my house complains to me that Wifi stops working without anything being done to the router, I have not set up VPN access to my home network so I cannot do anything until I go home in the evening.

25.07.20192407Base systemBug ReportVery LowLowwdr3600 5ghz wireless keeps cutting outTrunkUnconfirmed Task Description

Supply the following if possible:

- Device problem occurs on
TL WDR3600 v1

- Software versions of OpenWrt/LEDE release, packages, etc.
Powered by LuCI Master (git-19.204.23774-bd44189) / OpenWrt SNAPSHOT r10574-273b803623 (also tried with 18.06.01 & 02 & 04)
Atheros AR9580

- Steps to reproduce

 

Set up Wireless 5g to Canada, N mode, auto channel, auto power, 20 Mhz width.

wireless wlan1 will not associate.

root@OpenWrt:~# iwinfo wlan1 info
wlan1 ESSID: “Wrigley5”

        Access Point: E8:DE:27:FF:9F:99
        Mode: Master  Channel: 149 (5.745 GHz)
        Tx-Power: 19 dBm  Link Quality: unknown/70
        Signal: unknown  Noise: -95 dBm
        Bit Rate: unknown
        Encryption: WPA2 PSK (CCMP)
        Type: nl80211  HW Mode(s): 802.11an
        Hardware: 168C:0033 168C:A120 [Atheros AR9580]
        TX power offset: none
        Frequency offset: none
        Supports VAPs: yes  PHY name: phy1
27.05.20203130KernelBug ReportVery LowMediumWARNING: CPU: 0 PID: 2865 at net/core/flow_dissector.c:...TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

Linksys EA8500

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

OpenWrt SNAPSHOT r13373-e8fbb98c6d

- Steps to reproduce

Run dmesg and look for this exception stack. The system appears to run normally after boot.

[ 43.556644] ————[ cut here ]———— [ 43.556725] WARNING: CPU: 0 PID: 2865 at net/core/flow_dissector.c:942 skb_flow_dissect+0×448/0x156c
[ 43.560479] Modules linked in: ath10k_pci ath10k_core ath mac80211 iptable_nat ipt_REJECT cfg80211 xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_policy xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_MASQUERADE xt_LOG xt_HL xt_FLOWOFFLOAD xt_DSCP xt_CT xt_CLASSIFY nf_reject_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_conntrack_rtcache nf_conntrack_netlink nf_conncount iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables compat br_netfilter fuse act_connmark nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 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 act_mirred ledtrig_usbport ledtrig_heartbeat 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
[ 43.560909] 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 ipcomp6 xfrm6_tunnel esp6 ah6 xfrm4_tunnel ipcomp esp4 ah4 tunnel6 tunnel4 tun xfrm_user xfrm_ipcomp af_key xfrm_algo vfat fat ntfs nls_utf8 nls_iso8859_1 nls_cp437 sha1_generic md5 echainiv des_generic libdes cbc authenc usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_qcom ohci_platform ohci_hcd phy_qcom_dwc3 ahci fsl_mph_dr_of ehci_platform ehci_fsl sd_mod ahci_platform libahci_platform libahci libata scsi_mod ehci_hcd gpio_button_hotplug ext4 mbcache jbd2 exfat(C) crc32c_generic
[ 43.702907] CPU: 0 PID: 2865 Comm: charon Tainted: G C 5.4.42 #0
[ 43.725016] Hardware name: Generic DT based system
[ 43.732162] [<c030f954>] (unwind_backtrace) from [<c030b96c>] (show_stack+0×14/0×20)
[ 43.737012] [<c030b96c>] (show_stack) from [<c08c61e0>] (dump_stack+0×94/0xa8)
[ 43.744922] [<c08c61e0>] (dump_stack) from [<c031e7c0>] (
warn+0xb4/0xd0)
[ 43.751944] [<c031e7c0>] (warn) from [<c031e82c>] (warn_slowpath_fmt+0×50/0×90)
[ 43.758805] [<c031e82c>] (warn_slowpath_fmt) from [<c075aa10>] (
skb_flow_dissect+0×448/0x156c)
[ 43.766357] [<c075aa10>] (skb_flow_dissect) from [<c075bfd0>] (skb_get_hash_perturb+0x6c/0x1ac)
[ 43.775380] [<c075bfd0>] (skb_get_hash_perturb) from [<bf63dc80>] (ieee80211_reserve_tid+0xb50/0xf74 [mac80211])
[ 43.784311] [<bf63dc80>] (ieee80211_reserve_tid [mac80211]) from [<bf642154>] (ieee80211_tx_prepare_skb+0x23c/0×294 [mac80211])
[ 43.794456] [<bf642154>] (ieee80211_tx_prepare_skb [mac80211]) from [<bf643e6c>] (ieee80211_tx_pending+0xc4/0×294 [mac80211])
[ 43.805544] [<bf643e6c>] (ieee80211_tx_pending [mac80211]) from [<c0322740>] (tasklet_action_common.constprop.3+0×74/0x10c)
[ 43.816879] [<c0322740>] (tasklet_action_common.constprop.3) from [<c0302298>] (
do_softirq+0×130/0x2d4)
[ 43.827812] [<c0302298>] (do_softirq) from [<c0322948>] (do_softirq.part.2+0×48/0×58)
[ 43.837524] [<c0322948>] (do_softirq.part.2) from [<c0322a30>] (
local_bh_enable_ip+0xd8/0xe8)
[ 43.845354] [<c0322a30>] (__local_bh_enable_ip) from [<c08974e4>] (packet_poll+0×84/0×118)
[ 43.854038] [<c08974e4>] (packet_poll) from [<c0740fcc>] (sock_poll+0×98/0xc0)
[ 43.862370] [<c0740fcc>] (sock_poll) from [<c04647b0>] (do_sys_poll+0x2f0/0×558)
[ 43.869576] [<c04647b0>] (do_sys_poll) from [<c046552c>] (sys_poll+0×24/0×120)
[ 43.877118] [<c046552c>] (sys_poll) from [<c0301000>] (ret_fast_syscall+0×0/0×54)
[ 43.884136] Exception stack(0xd8fabfa8 to 0xd8fabff0)
[ 43.891708] bfa0: 00000000 00000000 b6920c40 00000006 ffffffff 00000000
[ 43.896756] bfc0: 00000000 00000000 012b4470 000000a8 b6920ce8 b6f3a8a4 b6920c40 b6920cbc
[ 43.904896] bfe0: b6920c00 b6920bf0 b6f8d5cc b6f8caa4
[ 43.913185] —[ end trace 36ce985abed2ad7b ]—


01.08.20181723KernelBug ReportVery LowLowWARNING: CPU: 0 PID: 0 at backports-2017-11-01/drivers/...openwrt-18.06Unconfirmed Task Description

I am running openwrt-18.06 on Linksys EA8500 (ipq806x).

I see the following warning in the kernel log (nothing for 10+ minutes in dmesg prior to this, and nothing after):

[  745.944042] ------------[ cut here ]------------
[  745.944108] WARNING: CPU: 0 PID: 0 at backports-2017-11-01/drivers/net/wireless/ath/ath10k/htt_rx.c:1015 0xbf2caf0c [ath10k_core@bf2b5000+0x3d000]
[  745.947840] Modules linked in: pppoe ppp_async ath10k_pci ath10k_core ath pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables crc_ccitt compat ledtrig_usbport ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_of_simple ohci_platform ohci_hcd phy_qcom_dwc3 ahci ehci_platform
[  746.009232]  sd_mod ahci_platform libahci_platform libahci libata scsi_mod ehci_hcd gpio_button_hotplug
[  746.031433] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.14.54 #0
[  746.040610] Hardware name: Generic DT based system
[  746.046865] Function entered at [<c030f7e8>] from [<c030ba24>]
[  746.051463] Function entered at [<c030ba24>] from [<c07a5138>]
[  746.057278] Function entered at [<c07a5138>] from [<c0318dcc>]
[  746.063094] Function entered at [<c0318dcc>] from [<c0318eb8>]
[  746.068908] Function entered at [<c0318eb8>] from [<bf2caf0c>]
[  746.074768] Function entered at [<bf2caf0c>] from [<bf2cc404>]
[  746.080544] Function entered at [<bf2cc404>] from [<bf2f5b48>]
[  746.086374] Function entered at [<bf2f5b48>] from [<c06956f8>]
[  746.092173] Function entered at [<c06956f8>] from [<c03015c8>]
[  746.097989] Function entered at [<c03015c8>] from [<c031d13c>]
[  746.103805] Function entered at [<c031d13c>] from [<c0359ba8>]
[  746.109621] Function entered at [<c0359ba8>] from [<c0301488>]
[  746.115436] Function entered at [<c0301488>] from [<c030c60c>]
[  746.121253] Exception stack(0xc0a01f48 to 0xc0a01f90)
[  746.127092] 1f40:                   00000001 00000000 00000000 c03154c0 ffffe000 c0a03c70
[  746.132225] 1f60: c0a03c24 00000000 00000000 c092da28 00000000 00000000 c0a01f90 c0a01f98
[  746.140369] 1f80: c0308844 c0308848 60000013 ffffffff
[  746.148510] Function entered at [<c030c60c>] from [<c0308848>]
[  746.153544] Function entered at [<c0308848>] from [<c034fc18>]
[  746.159273] Function entered at [<c034fc18>] from [<c034ff60>]
[  746.165087] Function entered at [<c034ff60>] from [<c0900c68>]
[  746.170998] ---[ end trace d7b584a1e69fa5ab ]---
[  746.179889] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[  746.181533] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 1, skipped old beacon

not sure what if anything provoked it, and wireless appears to work fine afterwards.

I looked at the backports-2017-11-01 tarball but apparently the source doesn’t quite correspond to what I’m actually running (prebuilt binary from openwrt release downloads):

 998 static void ath10k_htt_rx_h_undecap_raw(struct ath10k *ar,
 999                                         struct sk_buff *msdu,
1000                                         struct ieee80211_rx_status *status,
1001                                         enum htt_rx_mpdu_encrypt_type enctype,
1002                                         bool is_decrypted)
1003 {
1004         struct ieee80211_hdr *hdr;
1005         struct htt_rx_desc *rxd;
1006         size_t hdr_len;
1007         size_t crypto_len;
1008         bool is_first;
1009         bool is_last;
1010 
1011         rxd = (void *)msdu->data - sizeof(*rxd);
1012         is_first = !!(rxd->msdu_end.common.info0 &
1013                       __cpu_to_le32(RX_MSDU_END_INFO0_FIRST_MSDU));
1014         is_last = !!(rxd->msdu_end.common.info0 &
1015                      __cpu_to_le32(RX_MSDU_END_INFO0_LAST_MSDU));
1016 
1017         /* Delivered decapped frame:
1018          * [802.11 header]
1019          * [crypto param] <-- can be trimmed if !fcs_err &&
1020          *                    !decrypt_err && !peer_idx_invalid
1021          * [amsdu header] <-- only if A-MSDU
1022          * [rfc1042/llc]
1023          * [payload]
1024          * [FCS] <-- at end, needs to be trimmed
1025          */
1026 
1027         /* This probably shouldn't happen but warn just in case */
1028         if (unlikely(WARN_ON_ONCE(!is_first)))
1029                 return;
1030 
1031         /* This probably shouldn't happen but warn just in case */
1032         if (unlikely(WARN_ON_ONCE(!(is_first && is_last))))
1033                 return;

I suspect one of those two warnings is what is being hit but neither of them is quite at line 1015...

20.04.20203023Base systemBug ReportVery LowMediumWarning CPUopenwrt-19.07Unconfirmed Task Description

Device: Mikrotik RB750Gr3
Software: OpenWrt 19.07.2 (with no default package updates yet)
Installed Packages: installed_packages.txt (attached)
How to reproduce: Unknown
Consequence: None. The device continues to operate normally.

I have removed personal information and some garbage from the log files.

Compass.

31.01.20202789KernelBug ReportVery LowLowWAN-LAN leakage during boot on Asus RT-N11PAllUnconfirmed Task Description

On Asus RT-N11P (MT7620N) not work properly DHCP. Zero-day bug. Affected all firmwares from 18.06.0 to 19.07.1. No additional packages used.

Steps to reproduce:

1: Reboot router when any OS fully loaded.
2: After reboot router give through DHCP internal ip my ISP.
3: No internet connection.

If restart OS network, router give normal ip. But if again reboot router then the problem is repeated. Its a bug MT7620N but official router firmware have solution to bypass it and DHCP gives normal ip.
For now, to bypass the bug, I use manual entry in OS network settings:

Addres 192.168.1.127
Netmask 255.255.255.0
Gateway 192.168.1.1
DNS 192.168.1.1

09.03.2017612Base systemBug ReportVery LowHighWAN to LAN leakage on MT7620 devicesTrunkUnconfirmed Task Description

I am currently testing two MT7620 devices - the ZBT WE826 and the Sanlinking D240. During the first seconds of the boot, I see that packets leak between the WAN and LAN ports. Typically, this results in clients receiving a DHCP reply from my upstream router, rendering the clients without connectivity when the switch is properly initialized. I have also tested with the default firmware and do not see this behavior. Also, if I stop the devices in the bootloader, then packets do not leak until I resume boot again.

In order to try to solve this bug, I have tried to port some (at least to me) missing steps from the bootloader switch code and to the mt7620 switch driver in LEDE. This did not have an effect, at least not on the packet leak. A work-around I have found is to update u-boot and remove the input delay, so that the device will boot immediately. However, this is quite cumbersome to install and not very reliable. I suspect my luck with this work-around is more due to the timing of the DHCP clients in Ubuntu and Windows 10.

Does anyone have any idea as to what could be wrong and where to start looking?

Thanks in advance for any help.

 


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

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

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

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

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

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

network config is attached.



Cromagnon31

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

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

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

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

Steps to reproduce:

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

What happens:

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

What should happen:

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

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

18.08.20181794Base systemBug ReportVery LowLowW8970 - ADSL stops working after some timeTrunkUnconfirmed Task Description

Hi,

I have installed Openwrt 18.06.0 on my TD-W8970 device.
There is a problem that randomly, after average 2-5 days pppoe wan connection just stops working.

DSL is synchronized:
Annex: A
Line Mode: G.992.5 (ADSL2+)
Line State: UP [0×801: showtime_tc_sync]
(...)
Power Management Mode: L0 - Synchronized

No “leave showtime” message, kernel log is clean, system log is full of pppd restarting messages. Pppd keeps restarting and timeouts.

The only solution is to reboot machine, it always helps. How to debug and diagnose the problem?

16.01.20181279KernelBug ReportVery LowMediumVRX200 / BT Home Hub 5A does not correctly configure mo...lede-17.01Unconfirmed Task Description

Device: BT Home Hub 5A (xRX200 rev 1.2)
Version: LEDE 17.01.4
Kernel: 4.4.92 / swconfig: 11

I have configured up 3 VLANs using Luci. These are correctly added to /etc/config/network and “uci show | grep switch” shows the entries I’d expect. However only 2 VLANs are correctly configured. The 3rd can be brought up with a manual invocation of “swconfig”. I’ve tried the same thing on an DGN3500 (VR9 platform), also with LEDE 17.01.4, and it works there, leading me to suspect this is a kernel issue with the VRX200 driver.

The switch config in /etc/config/network looks like:

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

config switch_vlan
	option device 'switch0'
	option vlan '1'
	option vid '3'
	option ports '0 4 5t 6t'

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

config switch_vlan
	option device 'switch0'
	option vlan '3'
	option ports '1 5t 6t'
	option vid '5'

Running “swconfig dev switch0 load network” leads to the following switch config:

VLAN 1:
	vid: 3
	enable: 1
	ports: 0 4 5t 6t 
VLAN 2:
	vid: 4
	enable: 1
	ports: 2 6t

No other VLAN stanza are shown but ‘swconfig dev switch0 vlan 3 show’ shows that while no ports have been added VLAN ID 5 has been correctly configured:

VLAN 3:
	vid: 5
	enable: 1
	ports:

Manually executing “swconfig dev switch0 vlan 3 set ports ‘1 5t 6t’” brings up the VLAN as expected:

VLAN 3:
	vid: 5
	enable: 1
	ports: 1 5t 6t

uci shows the correct details (uci show | grep switch):

network.@switch[0]=switch
network.@switch[0].name='switch0'
network.@switch[0].reset='1'
network.@switch[0].enable_vlan='1'
network.@switch_vlan[0]=switch_vlan
network.@switch_vlan[0].device='switch0'
network.@switch_vlan[0].vlan='1'
network.@switch_vlan[0].vid='3'
network.@switch_vlan[0].ports='0 4 5t 6t'
network.@switch_vlan[1]=switch_vlan
network.@switch_vlan[1].device='switch0'
network.@switch_vlan[1].vlan='2'
network.@switch_vlan[1].ports='2 6t'
network.@switch_vlan[1].vid='4'
network.@switch_vlan[2]=switch_vlan
network.@switch_vlan[2].device='switch0'
network.@switch_vlan[2].vlan='3'
network.@switch_vlan[2].ports='1 5t 6t'
network.@switch_vlan[2].vid='5'
14.10.2016227Base systemBug ReportMediumHighVLAN support mismatch between preinit and default netwo...TrunkResearching Task Description

PPPoE is broken on WRT1900ACS

Upgraded from Lede r578 to latest Lede r1814 and PPPOE doesn’t work anymore altough the pppd version and PPPoE version are the same:
- Linksys WRT1900ACS
- LEDE reboot r1814

pppd debug log:

Plugin rp-pppoe.so loaded.
RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Send PPPOE Discovery V1T1 PADI session 0×0 length 4
dst ff:ff:ff:ff:ff:ff src c2:56:27:ca:d7:d4
[service-name]
Send PPPOE Discovery V1T1 PADI session 0×0 length 4
dst ff:ff:ff:ff:ff:ff src c2:56:27:ca:d7:d4
[service-name]
Send PPPOE Discovery V1T1 PADI session 0×0 length 4
dst ff:ff:ff:ff:ff:ff src c2:56:27:ca:d7:d4
[service-name]
Timeout waiting for PADO packets
Unable to complete PPPoE Discovery
Plugin rp-pppoe.so loaded.
RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Send PPPOE Discovery V1T1 PADI session 0×0 length 4
dst ff:ff:ff:ff:ff:ff src c2:56:27:ca:d7:d4
[service-name]
Send PPPOE Discovery V1T1 PADI session 0×0 length 4
dst ff:ff:ff:ff:ff:ff src c2:56:27:ca:d7:d4
[service-name]
Send PPPOE Discovery V1T1 PADI session 0×0 length 4
dst ff:ff:ff:ff:ff:ff src c2:56:27:ca:d7:d4
[service-name]

While on the same hardware running LEDE r578, the PPPoE module works as expected:

Plugin rp-pppoe.so loaded.
RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Send PPPOE Discovery V1T1 PADI session 0×0 length 4
dst ff:ff:ff:ff:ff:ff src c2:56:27:ca:d7:d4
[service-name]
Recv PPPOE Discovery V1T1 PADO session 0×0 length 40
dst c2:56:27:ca:d7:d4 src a0:f3:e4:34:d8:21
[service-name] [AC-name acc-aln1.hac] [AC-cookie 75 58 37 a5 ba 3c e4 a5 2a 61 bb 23 92 5c 1b dc]
Send PPPOE Discovery V1T1 PADR session 0×0 length 24
dst a0:f3:e4:34:d8:21 src c2:56:27:ca:d7:d4
[service-name] [AC-cookie 75 58 37 a5 ba 3c e4 a5 2a 61 bb 23 92 5c 1b dc]
Recv PPPOE Discovery V1T1 PADS session 0x30b length 4
dst c2:56:27:ca:d7:d4 src a0:f3:e4:34:d8:21
[service-name]
PADS: Service-Name: ‘’ PPP session is 779
Connected to a0:f3:e4:34:d8:21 via interface eth0
using channel 2
Using interface pppoe-wan
Connect: pppoe-wan ←→ eth0
sent [LCP ConfReq id=0×1 <mru 1492> <magic 0xc6952556>]
rcvd [LCP ConfReq id=0×66 <mru 1492> <auth chap MD5> <magic 0x4cc73648>]
sent [LCP ConfAck id=0×66 <mru 1492> <auth chap MD5> <magic 0x4cc73648>]
rcvd [LCP ConfAck id=0×1 <mru 1492> <magic 0xc6952556>]
sent [LCP EchoReq id=0×0 magic=0xc6952556]
rcvd [CHAP Challenge id=0×1 <7131a44524d1de8f1cd1061cac6d8c071d8bfe7351bc4ea7bd08f56684428475f229ba177a192696ebab32>, name = “acc-aln1.hac”]
sent [CHAP Response id=0×1 <4bb1a418b298790b128ad4d7ef3109ad>, name = “bthomehub@btbroadband.com”]
rcvd [LCP EchoRep id=0×0 magic=0x4cc73648]
rcvd [CHAP Success id=0×1 “CHAP authentication success”]
CHAP authentication succeeded: CHAP authentication success
CHAP authentication succeeded
peer from calling number A0:F3:E4:34:D8:21 authorized
sent [IPCP ConfReq id=0×1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
sent [IPV6CP ConfReq id=0×1 <addr fe80::c595:37d1:3987:1929>]
rcvd [IPV6CP ConfReq id=0x7b <addr fe80::0221:05ff:feb4:8824>]
sent [IPV6CP ConfAck id=0x7b <addr fe80::0221:05ff:feb4:8824>]
rcvd [IPCP ConfReq id=0×38 <addr 172.16.12.12>]
sent [IPCP ConfAck id=0×38 <addr 172.16.12.12>]
rcvd [IPCP ConfNak id=0×1 <addr 81.146.2.155> <ms-dns1 81.139.57.100> <ms-dns2 81.139.56.100>]
sent [IPCP ConfReq id=0×2 <addr 81.146.2.155> <ms-dns1 81.139.57.100> <ms-dns2 81.139.56.100>]
rcvd [IPV6CP ConfAck id=0×1 <addr fe80::c595:37d1:3987:1929>]
local LL address fe80::c595:37d1:3987:1929
remote LL address fe80::0221:05ff:feb4:8824
Script /lib/netifd/ppp-up started (pid 2646)
rcvd [IPCP ConfAck id=0×2 <addr 81.146.2.155> <ms-dns1 81.139.57.100> <ms-dns2 81.139.56.100>]
local IP address 81.146.2.155
remote IP address 172.16.12.12
primary DNS address 81.139.57.100
secondary DNS address 81.139.56.100
ppp.log
secondary DNS address 81.139.56.100
Script /lib/netifd/ppp-up started (pid 2653)
Script /lib/netifd/ppp-up finished (pid 2646), status = 0×9 Script /lib/netifd/ppp-up finished (pid 2653), status = 0×9

05.02.20181328Base systemBug ReportVery LowLowVGV7510KW22 / o2 Box 6431: Spurious reboots and etherne...TrunkUnconfirmed Task Description

Device:
VGV7510KW22 / o2 Box 6431

Software version:
OpenWrt SNAPSHOT r5944-ad4232e
Linux version 4.9.77 (buildbot@slashdirt-03) (gcc version 5.5.0 (OpenWrt GCC 5.5.0 r5944-ad4232e) ) #0 SMP Thu Jan 25 10:00:48 2018

Environment:
Additional packages: asterisk13-chan-lantiq, strongswan

Steps to reproduce:
From time to time, the box will reboot spuriously. Uptimes vary, between 12 hours and 2 weeks. After such a reboot, some of the ethernet ports do not detect a link anymore. Unplugging and replugging the ethernet cable into the same port does not help, and the kernel will only notice a link if I plug the ethernet cable into another port.
Sometimes, the ethernet port loses link even without a reboot.
Syslog is logged to an external server via UDP and does not show any error message prior to the spurious reboot.

Workaround:
Performing a manual reboot after the spurious reboot fixes the ethernet link loss.

Possibly relevant difference between dmesg on a spurious and normal reboot:

--- dmesg-normal-reboot.txt.notimestamps        2018-02-05 11:42:10.656203272 +0100
+++ dmesg-spurious-reboot.txt.notimestamps      2018-02-05 11:40:47.264201277 +0100
@@ -30,8 +30,8 @@
 PID hash table entries: 256 (order: -2, 1024 bytes)
 Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
 Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
-Writing ErrCtl register=00014098
-Readback ErrCtl register=00014098
+Writing ErrCtl register=00014090
+Readback ErrCtl register=00014090
 Memory: 55392K/63488K available (4334K kernel code, 178K rwdata, 1324K rodata, 1252K init, 244K bss, 8096K reserved, 0K cma-reserved)
 SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
 Hierarchical RCU implementation.
@@ -123,12 +123,14 @@
 libphy: Fixed MDIO Bus: probed
 libphy: lantiq,xrx200-mdio: probed
 ICPlus IP101A/G 0:01: attached PHY driver [ICPlus IP101A/G] (mii_bus:phy_addr=0:01, irq=-1)
-Intel XWAY PHY22F (xRX integrated) 0:11: attached PHY driver [Intel XWAY PHY22F (xRX integrated)] (mii_bus:phy_addr=0:11, irq=-1)
-Intel XWAY PHY22F (xRX integrated) 0:12: attached PHY driver [Intel XWAY PHY22F (xRX integrated)] (mii_bus:phy_addr=0:12, irq=-1)
-random: fast init done
+lantiq,xrx200-net 1e108000.eth eth0 (uninitialized): no PHY found
+xrx200-mdio: probing phy of port 2 failed
+lantiq,xrx200-net 1e108000.eth eth0 (uninitialized): no PHY found
+xrx200-mdio: probing phy of port 3 failed
 Intel XWAY PHY22F (xRX integrated) 0:13: attached PHY driver [Intel XWAY PHY22F (xRX integrated)] (mii_bus:phy_addr=0:13, irq=-1)
+random: fast init done
 Intel XWAY PHY22F (xRX integrated) 0:14: attached PHY driver [Intel XWAY PHY22F (xRX integrated)] (mii_bus:phy_addr=0:14, irq=-1)
-ltq-cputemp cputemp@0: Current CPU die temperature: 54.0 °C
+ltq-cputemp cputemp@0: Current CPU die temperature: 52.5 °C
 wdt 1f8803f0.watchdog: Init done
 NET: Registered protocol family 10
 NET: Registered protocol family 17
@@ -139,7 +141,6 @@
 This architecture does not have kernel memory protection.
 init: Console is alive
 init: - watchdog -
-lantiq,xrx200-net 1e108000.eth eth0: port 2 got link
 kmodloader: loading kernel modules from /etc/modules-boot.d/*
 dwc2 1e101000.ifxhcd: requested GPIO 509
 dwc2 1e101000.ifxhcd: DWC OTG Controller
@@ -151,12 +152,12 @@
 hub 1-0:1.0: 1 port detected
 kmodloader: done loading kernel modules from /etc/modules-boot.d/*
 init: - preinit -
-jffs2: notice: (440) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
+IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
+jffs2: notice: (436) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
 mount_root: switching to jffs2 overlay
 urandom-seed: Seeding with /etc/urandom.seed
 procd: - early -
 procd: - watchdog -
-lantiq,xrx200-net 1e108000.eth eth0: port 2 lost link
 procd: - watchdog -
 procd: - ubus -
 procd: - init -
@@ -207,19 +208,19 @@
 device eth0 entered promiscuous mode
 IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
 IPv6: ADDRCONF(NETDEV_UP): eth0.13: link is not ready
-lantiq,xrx200-net 1e108000.eth eth0: port 2 got link
-IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
-br-lan: port 1(eth0.1) entered blocking state
-br-lan: port 1(eth0.1) entered forwarding state
-IPv6: ADDRCONF(NETDEV_CHANGE): eth0.13: link becomes ready
-IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
+random: crng init done
 PTM 1.0.27    PTM (E1) firmware version 0.30
 ifxmips_ptm: PTM init succeed
 IPv6: ADDRCONF(NETDEV_UP): dsl0: link is not ready
 IPv6: ADDRCONF(NETDEV_UP): dsl0.7: link is not ready
-random: crng init done
 enter showtime
 IPv6: ADDRCONF(NETDEV_CHANGE): dsl0: link becomes ready
 IPv6: ADDRCONF(NETDEV_CHANGE): dsl0.7: link becomes ready
 enter showtime
 pppoe-wan: renamed from ppp0
15.09.20192498KernelBug ReportVery LowMediumUsing "wifi" causes soft reboot after a certain kernel ...TrunkUnconfirmed Task Description

Device: Xiaomi Mi Router 3g
OpenWrt: SNAPSHOT r10890-7d542dc804
mt76: 4.14.140+2019-08-22-2a0edbb4-1
Full list of installed packages

Some time during the normal operation “ieee80211_ctstoself_get” warning happens which and I seemingly lose the ability to use 5ghz AP from my tablet(on my phone it’s perfectly fine).
If I try to restart APs via “wifi” Oops in hostapd happens and take the router with it to soft reboot. Attached 2 recent crashlogs.

10.04.20202991Base systemBug ReportVery LowLowUserland-only tarball to populate chrootTrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

ath79/mips

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

19.07.2

- Steps to reproduce

 Would be nice to have generic userland tarball also for less popular arches, for experiments involving a USB drive and facing the 'net


03.06.2017825DocumentationBug ReportVery LowLowUser guide does not mention "config hostrecord" section...TrunkUnconfirmed Task Description

The dhcp configuration file is documented in the user guide at:
https://lede-project.org/docs/user-guide/dhcp_configuration and
https://lede-project.org/docs/user-guide/dns_configuration but neither page mentions the “config hostrecord” section type of the dhcp configuration file. This section type was first proposed here:
https://lists.openwrt.org/pipermail/openwrt-devel/2013-June/020358.html and it was added to openwrt here:
https://dev.openwrt.org/changeset/36943 and it’s in the lede source here:
https://github.com/lede-project/source/blob/master/package/network/services/dnsmasq/files/dnsmasq.init#L658

31.01.2017446Base systemBug ReportVery LowLowusbport trigger: The default configuration for all fami...TrunkUnconfirmed Task Description

Recently LuCI has get ability to configure LED’s with the usbport trigger https://github.com/openwrt/luci/issues/971. There are issues when reading the old usbdev trigger. There is no need to stay with usbdev at all so if it’s possible it should be converted to use usbport.

09.03.20181424Base systemBug ReportVery LowLowusbmode sits in loop after installTrunkUnconfirmed Task Description

- Name the tree/revision/version

OpenWrt Snapshot r6397-7cc9914

- Name the affected device

Huawei ME909s-120 LTE Card (12d1:15c1) on a PC Engines APU2 (amd64) in MBIM Mode.

- What does it do that it should not do / what does it not do that it should do

usbmode sits in a loop right after installation, doesn’t switch the Modem in MBMI mode and thus no /dev/cdc-wdm0 device is created and prints constantly:

[ 59.838090] usb 1-1.3: usbfs: process 6946 (usbmode) did not claim interface 1 before use
[ 60.048534] usb 1-1.3: usbfs: interface 1 claimed by usbfs while ‘usbmode’ sets config #0
[ 60.131996] usb 1-1.3: usbfs: process 7032 (usbmode) did not claim interface 1 before use
[ 60.342459] usb 1-1.3: usbfs: interface 1 claimed by usbfs while ‘usbmode’ sets config #0

- Steps to reproduce

Install usb-modeswitch on OpenWrt Snapshot r6397-7cc9914

- What you have already done to workaround/fix the problem

Tried LEDE 17.01.4 r3560-79f57e422d without success, but messages are only printed once after “usbmode -s” is called, also there isn’t a cdc-wdm0 device created.

- Any additional info you thinks is important

This HW config is working fine with cdc_mbim on Debian with a 4.9 Kernel and their usb-modeswitch implementation.

08.12.20181988Base systemFeature RequestVery LowLowusbmode doesn't support HuaweiAltMode from USB_ModeSwit...TrunkUnconfirmed Task Description

USB_ModeSwitch v2.5.1 added a new option called HuaweiAltMode that isn’t present in usbmode yet. It would be great if this could be ported to usbmode as well, please.

14.06.20192319PackagesBug ReportVery LowHighusbmode bug which is fixed in usb-modeswitch...openwrt-18.06Unconfirmed Task Description

I wrote a bug report but then the bug report said wrong token and I lost the report... :(

Now again but shorter version. The usb-modeswitch (which seems to be an openwrt project, a rewrite of original usb_modeswitch https://git.openwrt.org/project/usbmode.git ) needs to set some devices to config 0 before switching to config 3.

BTW this is fixed in usb-modeswitch... Here is the link to discussion about this:
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=2710&start=22

Some devices need to be set to config 0 first to be able to switch to config 3. Otherwise they hang...

Here a working example:

root@OpenWrt:~# echo 0 > /sys/bus/usb/devices/1-2/bConfigurationValue
root@OpenWrt:~# echo 3 > /sys/bus/usb/devices/1-2/bConfigurationValue
root@OpenWrt:~# umbim -d /dev/cdc-wdm0 caps

devicetype: 0001 - embedded
cellularclass: 0001
voiceclass: 0001 - no-voice
simclass: 0002
dataclass: 8000003F
smscaps: 0003
controlcaps: 0001
maxsessions: 0003
deviceid: 867377023108313
firmwareinfo: 11.617.06.00.00
hardwareinfo: RM1ME909ASM

root@OpenWrt:~#

A non-working example (after reboot):

root@OpenWrt:~# echo 3 > /sys/bus/usb/devices/1-2/bConfigurationValue
root@OpenWrt:~# umbim -d /dev/cdc-wdm0 caps
ERROR: mbim message timeout
root@OpenWrt:~#

At least one other person in OpenWRT bug tracker confirms this:
https://bugs.openwrt.org/index.php?do=details&task_id=1424

Although he has another problem with looping messages (probably unrelated to this bug)
https://forum.openwrt.org/t/usbmode-sits-in-loop-after-install/12624

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

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

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

This problem exists in 18.06 and trunk.

16.03.20202904Base systemBug ReportVery LowLowusb-storage fails to load in pre-initopenwrt-19.07Unconfirmed Task Description

As per forum post:

https://forum.openwrt.org/t/usb-storage-fail-to-load-in-preinit/54903

Basically, installed openwrt, added external root, all looks correctly configured, but after reboot external root fails to mount.
searching in the logs we can see that usb-storage is only loaded after pre-init, but it is listed in /etc/modprobe-boot.d/ ... checking /rom/etc/modules-boot.d/ it is not there.

Either something is missing in the https://openwrt.org/docs/guide-user/additional-software/extroot_configuration to add the usb-storage to the pre-init, or something is broken that makes pre-init fail to load usb-storage when it should.

The same setup worked fine with a older openwrt version (15.01 IIRC)

Supply the following if possible:
- Device problem occurs on
asus wl-500w

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

- Steps to reproduce
Install openwrt
add external root
manually mount to confirm setup
reboot
external root not mounted nor switched to, logs show that usb-storage is only loaded after normal root is mounted
manual mount still works

 


05.09.2016160Base systemBug ReportVery LowLowusb-serial (pl2303) failures on mt7621 dlink dir860l-b1TrunkUnconfirmed Task Description
git describe
reboot-1497-ga810e77

with diffconfig:

CONFIG_TARGET_ramips=y
CONFIG_TARGET_ramips_mt7621=y
CONFIG_TARGET_ramips_mt7621_DEVICE_dir-860l-b1=y
CONFIG_DEVEL=y
CONFIG_BUILD_LOG=y
CONFIG_PACKAGE_ip=y
CONFIG_PACKAGE_kmod-usb-core=y
CONFIG_PACKAGE_kmod-usb-ohci=y
CONFIG_PACKAGE_kmod-usb-ohci-pci=y
CONFIG_PACKAGE_kmod-usb-serial=y
CONFIG_PACKAGE_kmod-usb-serial-ftdi=y
CONFIG_PACKAGE_kmod-usb-serial-pl2303=y
CONFIG_PACKAGE_kmod-usb2=y
CONFIG_PACKAGE_kmod-usb2-pci=y
CONFIG_PACKAGE_kmod-usb3=y
CONFIG_PACKAGE_screen=y

screen starts, but doesn’t work. The usb-relevant dmesg’s are:

[    4.550000] usbcore: registered new interface driver usbfs
[    4.560000] usbcore: registered new interface driver hub
[    4.570000] usbcore: registered new device driver usb
[    4.580000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    4.620000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    4.670000] xhci-mtk 1e1c0000.xhci: new USB bus registered, assigned bus number 1
[    4.720000] hub 1-0:1.0: USB hub found
[    4.740000] xhci-mtk 1e1c0000.xhci: new USB bus registered, assigned bus number 2
[    4.760000] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    4.770000] hub 2-0:1.0: USB hub found
[    5.260000] usb 1-1: new full-speed USB device number 2 using xhci-mtk
[    5.410000] usb 1-1: no of_node; not parsing pinctrl DT
[   10.150000] usbcore: registered new interface driver usbserial
[   10.160000] usbcore: registered new interface driver usbserial_generic
[   10.180000] usbserial: USB Serial support registered for generic
[   10.220000] usbcore: registered new interface driver ftdi_sio
[   10.240000] usbserial: USB Serial support registered for FTDI USB Serial Device
[   10.260000] usbcore: registered new interface driver pl2303
[   10.270000] usbserial: USB Serial support registered for pl2303
[   10.290000] pl2303 ttyUSB0: no of_node; not parsing pinctrl DT
[   10.290000] usb 1-1: pl2303 converter now attached to ttyUSB0
[  871.510000] pl2303 ttyUSB0: pl2303_get_line_request - failed: -145
[  871.620000] pl2303 ttyUSB0: pl2303_set_line_request - failed: -145
[  871.840000] pl2303 ttyUSB0: pl2303_set_control_lines - failed: -145

Screen also throws an error (which gets blanked out, but is captured by the serial console):

# screen /dev/ttyUSB0 115200
/dev/null/utmp: Not a directory
Showing tasks 51 - 100 of 1140 Page 2 of 23 - 1 - 2 - 3 - 4 - 5 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing