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 TypePrioritySeverity  descSummaryReported InStatus
04.08.20192426KernelBug ReportVery LowHighX86 platform kernel error reportTrunkUnconfirmed Task Description

platform: x86_64
kernel: 4.19.62
Source version: commit 2caf747116337645420653ec003799a8eef69229

System log:

Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.434155] WARNING: CPU: 1 PID: 1086 at __nf_unregister_net_hook+0x43/0x110
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.441249] Modules linked in: pppoe ppp_async snd_usb_audio snd_hda_intel snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_codec pptp pppox ppp_mppe ppp_generic nf_nat_pptp nf_conntrack_pptp iptable_nat ipt_REJECT ipt_MASQUERADE xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda ts_fsm ts_bm snd_usbmidi_lib snd_hda_core slhc r8169 nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_proto_gre nf_nat_irc nf_nat_ipv4 nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.512738]  nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast ts_kmp nf_conntrack_amanda iptable_raw iptable_mangle iptable_filter ip_tables e1000e crc_ccitt bnx2 asn1_decoder arptable_filter arpt_mangle arp_tables fuse sg evdev i2c_dev cryptodev xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6table_nat ip6t_NPT ip6t_MASQUERADE nf_nat_ipv6 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6t_rt ip6t_mh ip6t_ipv6header ip6t_hbh ip6t_frag ip6t_eui64 ip6t_ah nf_log_ipv6 nf_log_common
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.584829]  ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 msdos ip_gre gre ixgbe igbvf igb e1000 mdio ip_tunnel snd_rawmidi snd_seq_device snd_pcm_oss snd_pcm snd_timer snd_mixer_oss snd_hwdep snd_compress snd soundcore vfat fat udf crc_itu_t hfsplus raid456 async_raid6_recov async_pq async_xor xor raid6_pq async_memcpy async_tx raid10 raid1 raid0 md_mod nls_utf8 nls_iso8859_1 nls_cp936 nls_cp437 sha1_ssse3 sha1_generic authenc uas sdhci_pltfm xhci_plat_hcd ehci_platform xfs libcrc32c reiserfs exfat button_hotplug ptp realtek pps_core mii libphy
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.636678] CPU: 1 PID: 1086 Comm: kworker/u8:6 Not tainted 4.19.62 #0
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.643239] Hardware name:  YL-1900L4-V2/YL-1900L4-V2, BIOS 5.6.5 05/08/2017
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.650343] Workqueue: netns cleanup_net
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.654304] RIP: 0010:__nf_unregister_net_hook+0x43/0x110
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.659739] Code: f9 ff ff 48 85 c0 0f 84 e0 00 00 00 49 89 c5 49 89 ff 48 c7 c7 e0 fd 07 82 41 89 f6 e8 76 41 0e 00 4d 8b 65 00 4d 85 e4 75 13 <0f> 0b 48 c7 c7 e0 fd 07 82 e8 bf 3b 0e 00 e9 af 00 00 00 41 0f b7
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.678640] RSP: 0018:ffffc90001b07d88 EFLAGS: 00010246
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.683901] RAX: 0000000000000000 RBX: ffffffffa0578040 RCX: 0000000000000000
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.691089] RDX: ffff88813a784200 RSI: 0000000000000002 RDI: ffffffff8207fde0
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.698279] RBP: ffffc90001b07db0 R08: 00000000000226e0 R09: ffff88813be1cb40
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.705475] R10: ffffc90001b07cd8 R11: 0000000000000001 R12: 0000000000000000
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.712671] R13: ffff888134c38e00 R14: 0000000000000002 R15: ffff888134c38000
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.719868] FS:  0000000000000000(0000) GS:ffff88813ba80000(0000) knlGS:0000000000000000
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.728017] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.733798] CR2: 00007f1d8ba05da4 CR3: 0000000002008000 CR4: 00000000001006e0
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.740985] Call Trace:
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.743445]  nf_unregister_net_hook+0x3b/0x40
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.747837]  nf_unregister_net_hooks+0x2a/0x40
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.752319]  0xffffffffa0576045
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.755501]  ops_exit_list.isra.9+0x39/0x60
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.759724]  cleanup_net+0x177/0x260
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.763339]  process_one_work+0x1d2/0x320
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.767386]  worker_thread+0x20d/0x3c0
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.771166]  kthread+0x113/0x120
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.774426]  ? process_one_work+0x320/0x320
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.778639]  ? kthread_create_worker_on_cpu+0x40/0x40
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.783723]  ret_from_fork+0x35/0x40
Sun Aug  4 23:57:18 2019 kern.warn kernel: [   85.787335] ---[ end trace 5bd85fc8f41823d7 ]---


16.08.20192445KernelBug ReportVery LowHighOmega2 reboot hangTrunkUnconfirmed Task Description

- Omega2
- OpenWRT 19.07 branch (and master earlier this year)
- Try rebooting, results in hang.

Old issue, which seems to still persist. See:
http://community.onion.io/topic/1254/omega2-reboot/3 https://patchwork.ozlabs.org/patch/713750/ https://github.com/lede-project/source/pull/620

24.08.20192462Base systemBug ReportVery LowHighwrt32x WIFI was breaking on 2 sec I did not get full co...AllUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on wrt32x
- Software versions of OpenWrt 19.07

I tested these images on wrt32x and wrt3600, but unfortunately I gave up there was a problem on wrt32x WIFI was breaking the computer and in the relayd wrt3600 → wrt32x the maximum speed on the bridge is 10Mb. I do not observe this for version 18.06 (images downloaded from eko.one.pl). And after disconnection I did not get full connection speed of 866.7 Mb / s to the router. Although I will say that options 19.07 in Lucia look encouraging.

29.08.20192473KernelBug ReportVery LowHighUsb not working on fonera 2.0n (ramips/rt305x)openwrt-18.06Unconfirmed Task Description

On openwrt 18.06.4 usb is no longer working. I’ve tried with 18.06.02 built by my own with the same result. With 18.06.1 everything was working correctly.


04.09.20192478Base systemBug ReportVery LowHighTP-Link CPE210v3 wifi not workingTrunkUnconfirmed Task Description

same bug as FS#2333 but occurs on CPE 210 v3 as well

- Device problem occurs on
TP-Link CPE 210v3

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

- Steps to reproduce
Migrated from ar71xx to ath79 with fresh settings.

Clients can’t see the AP and “iw dev wlan0 scan” is returning nothing. Wifi doesn’t seem to work.

wifi bug hint: seen somebody mentioned in CPE210 bug threads different irqs

wifi not working:

ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
ieee80211 phy0: Atheros AR9531 Rev:2 mem=0xb8100000, irq=12

wifi working:

ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
ieee80211 phy0: Atheros AR9531 Rev:2 mem=0xb8100000, irq=47

iwinfo

root@OpenWrt:~# iwinfo
wlan0     ESSID: unknown
          Access Point: 98:DA:C4:5B:9C:26
          Mode: Client  Channel: unknown (unknown)
          Tx-Power: 3 dBm  Link Quality: unknown/70
          Signal: unknown  Noise: -95 dBm
          Bit Rate: unknown
          Encryption: unknown
          Type: nl80211  HW Mode(s): 802.11bgn
          Hardware: unknown [Generic MAC80211]
          TX power offset: unknown
          Frequency offset: unknown
          Supports VAPs: yes  PHY name: phy0

iw phy

root@OpenWrt:~# iw phy
Wiphy phy0
        max # scan SSIDs: 4
        max scan IEs length: 2257 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports AP-side u-APSD.
        Device supports T-DLS.
        Available Antennas: TX 0x3 RX 0x3
        Configured Antennas: TX 0x3 RX 0x3
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
                 * outside context of a BSS
        Band 1:
                Capabilities: 0x11ef
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-15
                Frequencies:
                        * 2412 MHz [1] (25.0 dBm)
                        * 2417 MHz [2] (25.0 dBm)
                        * 2422 MHz [3] (25.0 dBm)
                        * 2427 MHz [4] (25.0 dBm)
                        * 2432 MHz [5] (25.0 dBm)
                        * 2437 MHz [6] (25.0 dBm)
                        * 2442 MHz [7] (25.0 dBm)
                        * 2447 MHz [8] (25.0 dBm)
                        * 2452 MHz [9] (25.0 dBm)
                        * 2457 MHz [10] (25.0 dBm)
                        * 2462 MHz [11] (25.0 dBm)
                        * 2467 MHz [12] (disabled)
                        * 2472 MHz [13] (disabled)
                        * 2484 MHz [14] (disabled)
        valid interface combinations:
                 * #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client, P2P-GO } <= 1, #{ IBSS } <= 1,
                   total <= 2048, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz }

        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing
        Supported extended features:
                * [ RRM ]: RRM
                * [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
                * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
                * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs

uci show wireless

root@OpenWrt:~# uci show wireless
wireless.radio0=wifi-device
wireless.radio0.type='mac80211'
wireless.radio0.channel='11'
wireless.radio0.hwmode='11g'
wireless.radio0.path='platform/ahb/18100000.wmac'
wireless.radio0.htmode='HT20'
wireless.radio0.disabled='1'
wireless.default_radio0=wifi-iface
wireless.default_radio0.device='radio0'
wireless.default_radio0.network='lan'
wireless.default_radio0.mode='ap'
wireless.default_radio0.ssid='OpenWrt'
wireless.default_radio0.encryption='none'

15.09.20192496Base systemBug ReportVery LowHighWPA3-SAE can't be enabled on mt76 deviceTrunkUnconfirmed Task Description

Device: Netgear EX2700

Version: OpenWrt 19.07-SNAPSHOT r10532-cf3b50377e / LuCI openwrt-19.07 branch (git-19.256.45060-8a2f1c7)

Steps to reproduce: Enable WPA3 or WPA3-Mixed Mode via LuCI.

Result:
Wifi won’t come up. Works fine with WPA2.

Sun Sep 15 20:08:18 2019 kern.info kernel: [ 1638.740004] device wlan0 left promiscuous mode
Sun Sep 15 20:08:18 2019 kern.info kernel: [ 1638.740123] br-lan: port 2(wlan0) entered disabled state
Sun Sep 15 20:08:18 2019 daemon.notice hostapd: wlan0: interface state ENABLED->DISABLED
Sun Sep 15 20:08:18 2019 daemon.notice hostapd: wlan0-1: AP-DISABLED
Sun Sep 15 20:08:18 2019 daemon.notice hostapd: wlan0-1: CTRL-EVENT-TERMINATING
Sun Sep 15 20:08:18 2019 daemon.notice netifd: Network device 'wlan0-1' link is down
Sun Sep 15 20:08:19 2019 kern.info kernel: [ 1639.020561] br-guest: port 2(wlan0-1) entered disabled state
Sun Sep 15 20:08:19 2019 kern.info kernel: [ 1639.023338] device wlan0-1 left promiscuous mode
Sun Sep 15 20:08:19 2019 kern.info kernel: [ 1639.023357] br-guest: port 2(wlan0-1) entered disabled state
Sun Sep 15 20:08:19 2019 daemon.notice hostapd: nl80211: Failed to remove interface wlan0-1 from bridge br-guest: No such device
Sun Sep 15 20:08:19 2019 daemon.notice hostapd: wlan0: AP-DISABLED
Sun Sep 15 20:08:19 2019 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Sun Sep 15 20:08:19 2019 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Sun Sep 15 20:08:19 2019 daemon.notice hostapd: nl80211: Failed to remove interface wlan0 from bridge br-lan: Invalid argument
Sun Sep 15 20:08:19 2019 user.notice mac80211: Failed command: iw phy phy0 set antenna 0xffffffff 0xffffffff
Sun Sep 15 20:08:19 2019 daemon.notice netifd: radio0 (1867): command failed: Not supported (-122)
Sun Sep 15 20:08:19 2019 user.notice mac80211: Failed command: iw phy phy0 set distance 0
Sun Sep 15 20:08:19 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Sun Sep 15 20:08:21 2019 kern.info kernel: [ 1639.912716] ieee80211 phy0: rt2800_rf_self_txdc_cal: Info - RF Tx self calibration start
Sun Sep 15 20:08:21 2019 kern.info kernel: [ 1639.913245] ieee80211 phy0: rt2800_rf_self_txdc_cal: Info - RF Tx self calibration end
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.824164] ieee80211 phy0: rt2800_loft_iq_calibration: Info - LOFT Calibration Done!
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.828164] ieee80211 phy0: rt2800_iq_search: Info - IQCalibration Start!
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.842569] ieee80211 phy0: rt2800_iq_search: Info - IQCalibration Done! CH = 0, (gain= 0, phase=3f)
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.843488] ieee80211 phy0: rt2800_iq_search: Info - IQCalibration Start!
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.857895] ieee80211 phy0: rt2800_iq_search: Info - IQCalibration Done! CH = 1, (gain= 0, phase= 2)
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.857931] ieee80211 phy0: rt2800_loft_iq_calibration: Info - TX IQ Calibration Done!
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.871433] ieee80211 phy0: rt2800_rxiq_calibration: Info - RXIQ G_imb=1, Ph_rx=-6
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.881694] ieee80211 phy0: rt2800_rxiq_calibration: Info - RXIQ G_imb=0, Ph_rx=2
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.888849] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.894441] br-lan: port 2(wlan0) entered blocking state
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.894456] br-lan: port 2(wlan0) entered disabled state
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.894799] device wlan0 entered promiscuous mode
Sun Sep 15 20:08:22 2019 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Sun Sep 15 20:08:22 2019 daemon.err hostapd: Using interface wlan0 with hwaddr XX:XX:XX:XX:XX:XX and ssid "HOME"
Sun Sep 15 20:08:22 2019 daemon.err hostapd: Interface initialization failed
Sun Sep 15 20:08:22 2019 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->DISABLED
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.994731] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.994904] br-lan: port 2(wlan0) entered blocking state
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1641.994914] br-lan: port 2(wlan0) entered forwarding state
Sun Sep 15 20:08:22 2019 daemon.notice hostapd: wlan0: AP-DISABLED
Sun Sep 15 20:08:22 2019 daemon.err hostapd: wlan0: Unable to setup interface.
Sun Sep 15 20:08:22 2019 daemon.notice hostapd: wlan0: interface state DISABLED->DISABLED
Sun Sep 15 20:08:22 2019 daemon.notice hostapd: wlan0-1: AP-DISABLED
Sun Sep 15 20:08:22 2019 daemon.notice hostapd: wlan0-1: CTRL-EVENT-TERMINATING
Sun Sep 15 20:08:22 2019 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0-1 wasn't started
Sun Sep 15 20:08:22 2019 daemon.notice hostapd: wlan0: AP-DISABLED
Sun Sep 15 20:08:22 2019 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Sun Sep 15 20:08:22 2019 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
Sun Sep 15 20:08:22 2019 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1642.002616] device wlan0 left promiscuous mode
Sun Sep 15 20:08:22 2019 kern.info kernel: [ 1642.002723] br-lan: port 2(wlan0) entered disabled state
Sun Sep 15 20:08:22 2019 daemon.notice hostapd: ELOOP: remaining socket: sock=22 eloop_data=0x77d76c60 user_data=0 handler=0x46a4f5
Sun Sep 15 20:08:22 2019 daemon.notice netifd: radio0 (1867): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 1120 path ()
Sun Sep 15 20:08:22 2019 daemon.notice netifd: radio0 (1867): Device setup failed: HOSTAPD_START_FAILED


17.09.20192508Base systemBug ReportVery LowHighoxnas pogoplug3 warm booting, no serial, kernel hang?TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

CloudEngines Pogoplug v3

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

# cat /etc/openwrt_release 
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='SNAPSHOT'
DISTRIB_REVISION='r11027-f39f4b2f6d'
DISTRIB_TARGET='oxnas/ox820'
DISTRIB_ARCH='arm_mpcore'
DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r11027-f39f4b2f6d'
DISTRIB_TAINTS='no-all busybox'

- Steps to reproduce

 

When the device reboots with power on, I get a bootlog like this:

root@pogoplug:/# reboot
root@pogoplug:/# [   58.722024] reboot: Restarting system

U-Boot SPL 2013.10 (Apr 27 2014 - 19:08:27)
  Boot device: NAND
Attempting to set PLLA to 800 MHz ...
  plla_ctrl0 : 0000030a
  plla_ctrl1 : 00400000
  plla_ctrl2 : 007f0068
  plla_ctrl3 : 00000193

PLLA Set


U-Boot 2013.10-tld-3 (May 15 2014 - 14:54:14) for OXNAS

DRAM:  128 MiB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   
Led:    GREEN
mii0
Main Loop
Hit any key to stop autoboot:  0 

Loading from nand0, offset 0x440000
   Image Name:   ARM OpenWrt Linux-4.14.143
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3057200 Bytes = 2.9 MiB
   Load Address: 60008000
   Entry Point:  60008000
## Booting kernel from Legacy Image at 60500000 ...
   Image Name:   ARM OpenWrt Linux-4.14.143
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3057200 Bytes = 2.9 MiB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Led:    GREEN

Starting kernel ...

and hangs there, can’t connect to it over the network, so it doesn’t seem like just a serial problem.

From a cold start (power cycle), the bootlog looks like this:

U-Boot SPL 2013.10 (Apr 27 2014 - 19:08:27)
  Boot device: NAND
Attempting to set PLLA to 800 MHz ...
  plla_ctrl0 : 0000030a
  plla_ctrl1 : 00400000
  plla_ctrl2 : 007f0068
  plla_ctrl3 : 00000193

PLLA Set


U-Boot 2013.10-tld-3 (May 15 2014 - 14:54:14) for OXNAS

DRAM:  128 MiB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   
Led:    GREEN
mii0
Main Loop
Hit any key to stop autoboot:  0 

Loading from nand0, offset 0x440000
   Image Name:   ARM OpenWrt Linux-4.14.143
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3057200 Bytes = 2.9 MiB
   Load Address: 60008000
   Entry Point:  60008000
## Booting kernel from Legacy Image at 60500000 ...
   Image Name:   ARM OpenWrt Linux-4.14.143
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3057200 Bytes = 2.9 MiB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Led:    GREEN

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.143 (openwrt@hawg) (gcc version 7.4.0 (OpenWrt GCC 7.4.0 r8984-6ba58b7b02)) #0 SMP Mon Sep 16 06:37:06 2019
[    0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5787d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Cloud Engines PogoPlug Series 3
[...]

and it continues to boot normally. Up until recently (10561-gff7909f69e) reboots would just hang (see also https://bugs.openwrt.org/index.php?do=details&task_id=1711), so this is an improvement, but still not fully working.

29.09.20192523KernelBug ReportVery LowHighRB750 randomly reboots after kernel warningsopenwrt-19.07Unconfirmed Task Description

Mikrotik RB750Gr3
LuCI openwrt-19.07 branch (git-19.267.59428-7b36dae) / OpenWrt 19.07-SNAPSHOT r10532-cf3b50377e

Router randomly reboots (it may be stable for hours or can reboot in a minute after power up). Seems like kernel problem.

Here are some logs I managed to fetch before the reboots:

Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.010562] ------------[ cut here ]------------
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.015202] WARNING: CPU: 2 PID: 0 at net/ipv4/tcp_output.c:2509 0x803cc8bc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.022158] invalid inflight: 1 state 1 cwnd 10 mss 1388
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.027441] Modules linked in: qcserial pppoe ppp_async option cdc_mbim usb_wwan sierra_net sierra rndis_host qmi_wwan pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cdc_ncm cdc_ether 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 wireguard usbserial usbnet usblp ts_fsm ts_bm slhc nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.097872]  nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda nf_conntrack iptable_raw iptable_mangle iptable_filter ip_tables crc_ccitt cdc_wdm cdc_acm fuse ledtrig_usbport gpio_beeper input_core xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ip6_udp_tunnel udp_tunnel tun vfat fat nls_utf8 nls_iso8859_1 nls_cp437 uas usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd ehci_platform
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.169233]  sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4 mbcache jbd2 usbcore nls_base usb_common mii crc32c_generic
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.180291] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.14.143 #0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.186357] Stack : 00000000 00000000 00000000 81230398 00000000 00000000 00000000 00000000
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.194691]         00000000 00000000 00000000 00000000 00000000 00000001 8fc0dd30 ac07f596
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.203026]         8fc0ddc8 00000000 00000000 00004ea0 00000038 8049db58 00000007 00000000
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.211359]         00000000 80550000 0002c043 00000000 8fc0dd10 00000000 80570000 8050c6a0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.219690]         803cc8bc 000009cd 812303d8 81230398 00000000 802af9e8 00000008 805b0008
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.228022]         ...
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.230459] Call Trace:
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.230475] [<8049db58>] 0x8049db58
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.236372] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.239840] [<802af9e8>] 0x802af9e8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.243312] [<800101a0>] 0x800101a0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.246782] [<800101a8>] 0x800101a8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.250250] [<80486a9c>] 0x80486a9c
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.253722] [<800758a0>] 0x800758a0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.257243] [<80032588>] 0x80032588
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.260714] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.264185] [<80032610>] 0x80032610
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.267654] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.271126] [<803cf3d0>] 0x803cf3d0
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.274596] [<8009d750>] 0x8009d750
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.278064] [<803cf7a8>] 0x803cf7a8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.281537] [<8009dd80>] 0x8009dd80
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.285007] [<803cf770>] 0x803cf770
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.288474] [<8008c2cc>] 0x8008c2cc
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.291945] [<8008c588>] 0x8008c588
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.295413] [<8007cee8>] 0x8007cee8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.298883] [<804a49b8>] 0x804a49b8
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.302357] [<80036f14>] 0x80036f14
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.305827] [<8025d440>] 0x8025d440
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.309296] [<8000b488>] 0x8000b488
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.312764]
Sun Sep 29 20:08:08 2019 kern.warn kernel: [   92.314310] ---[ end trace a36c893f27b6a6f3 ]---
Sun Sep 29 18:56:25 2019 kern.alert kernel: [ 2442.525228] CPU 1 Unable to handle kernel paging request at virtual address 00000010, epc == 803be4a0, ra == 803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.535821] Oops[#1]:
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.538087] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G        W       4.14.143 #0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.545363] task: 8fc3be80 task.stack: 8fc5c000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.549869] $ 0   : 00000000 00000001 0000004a 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.555080] $ 4   : 8ea76f3c 00000001 0000d706 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.560290] $ 8   : 00034501 00000321 811d7440 00000322
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.565501] $12   : 8ea22180 8ea22180 8e9a8e00 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.570712] $16   : 8ea76e40 00001204 6375f4c6 ffffffff
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.575923] $20   : 00001204 00000001 00000000 00000002
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.581133] $24   : 00000000 8034b220
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.586344] $28   : 8fc5c000 8fc0bbb8 00000000 803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.591555] Hi    : 0000caa1
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.594419] Lo    : 47aec5c8
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.597285] epc   : 803be4a0 0x803be4a0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.601098] ra    : 803c4104 0x803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.604912] Status: 11007c03      KERNEL EXL IE
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.609082] Cause : 40800008 (ExcCode 02)
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.613066] BadVA : 00000010
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.615931] PrId  : 0001992f (MIPS 1004Kc)
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.620003] Modules linked in: qcserial pppoe ppp_async option cdc_mbim usb_wwan sierra_net sierra rndis_host qmi_wwan pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cdc_ncm cdc_ether 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 wireguard usbserial usbnet usblp ts_fsm ts_bm slhc nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.690391]  nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda nf_conntrack iptable_raw iptable_mangle iptable_filter ip_tables crc_ccitt cdc_wdm cdc_acm fuse ledtrig_usbport gpio_beeper input_core xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ip6_udp_tunnel udp_tunnel tun vfat fat nls_utf8 nls_iso8859_1 nls_cp437 uas usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd ehci_platform
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.761710]  sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4 mbcache jbd2 usbcore nls_base usb_common mii crc32c_generic
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.772740] Process swapper/1 (pid: 0, threadinfo=8fc5c000, task=8fc3be80, tls=00000000)
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.780788] Stack : 00000204 8034def4 8ea76e40 00000000 8ea76e40 8ea76e40 00001204 803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.789123]         8f346480 8056ba00 00000000 8015000a 00018bc3 8fc0bc74 00000004 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.797457]         80550000 8ea76f3c 00000002 00000001 91946e37 00000000 00000018 91946e37
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.805791]         00000000 91946e37 00000000 00000001 80570000 8050c458 00000000 00000002
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.814125]         00018bc3 00000018 8ee92564 8e9a0600 00000000 00000000 00000001 00000000
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.822457]         ...
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.824891] Call Trace:
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.824903] [<8034def4>] 0x8034def4
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.830852] [<803c4104>] 0x803c4104
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.834335] [<8015000a>] 0x8015000a
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.837825] [<803c4efc>] 0x803c4efc
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.841318] [<803c6f34>] 0x803c6f34
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.844788] [<803a98a0>] 0x803a98a0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.848313] [<803d1bc0>] 0x803d1bc0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.851802] [<803d2f18>] 0x803d2f18
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.855307] [<8e86426c>] 0x8e86426c [nf_conntrack_ipv4@8e864000+0x1420]
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.861893] [<803a9da0>] 0x803a9da0
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.865406] [<803aa078>] 0x803aa078
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.868887] [<803a9940>] 0x803a9940
Sun Sep 29 18:56:25 2019 kern.warn kernel: [ 2442.872360] [<803a9c10>] 0x803a9c10
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.402270] ------------[ cut here ]------------
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.406908] WARNING: CPU: 1 PID: 0 at net/ipv4/tcp_output.c:2509 0x803cc8bc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.413864] invalid inflight: 1 state 1 cwnd 10 mss 1388
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.419148] Modules linked in: qcserial pppoe ppp_async option cdc_mbim usb_wwan sierra_net sierra rndis_host qmi_wwan pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cdc_ncm cdc_ether 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 wireguard usbserial usbnet usblp ts_fsm ts_bm slhc nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.489628]  nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda nf_conntrack iptable_raw iptable_mangle iptable_filter ip_tables crc_ccitt cdc_wdm cdc_acm fuse ledtrig_usbport gpio_beeper input_core xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ip6_udp_tunnel udp_tunnel tun vfat fat nls_utf8 nls_iso8859_1 nls_cp437 uas usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd ehci_platform
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.561103]  sd_mod scsi_mod ehci_hcd gpio_button_hotplug ext4 mbcache jbd2 usbcore nls_base usb_common mii crc32c_generic
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.572189] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.14.143 #0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.578264] Stack : 00000000 00000000 00000000 81222398 00000000 00000000 00000000 00000000
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.586600]         00000000 00000000 00000000 00000000 00000000 00000001 8fc0bd30 ac07f596
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.594938]         8fc0bdc8 00000000 00000000 00004f18 00000038 8049db58 00000007 00000000
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.603273]         00000000 80550000 0008bb1d 00000000 8fc0bd10 00000000 80570000 8050c6a0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.611605]         803cc8bc 000009cd 812223d8 81222398 00000000 802af9e8 00000004 805b0004
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.619937]         ...
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.622376] Call Trace:
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.622394] [<8049db58>] 0x8049db58
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.628288] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.631755] [<802af9e8>] 0x802af9e8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.635228] [<800101a0>] 0x800101a0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.638699] [<800101a8>] 0x800101a8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.642170] [<80486a9c>] 0x80486a9c
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.645638] [<800758a0>] 0x800758a0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.649107] [<80032588>] 0x80032588
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.652580] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.656052] [<80032610>] 0x80032610
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.659528] [<803cc8bc>] 0x803cc8bc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.663008] [<803cf3d0>] 0x803cf3d0
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.666478] [<8009d750>] 0x8009d750
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.669947] [<803cf7a8>] 0x803cf7a8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.673420] [<8009dd80>] 0x8009dd80
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.676890] [<803cf770>] 0x803cf770
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.680358] [<8008c2cc>] 0x8008c2cc
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.683829] [<80063018>] 0x80063018
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.687300] [<8008c588>] 0x8008c588
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.690768] [<8007cee8>] 0x8007cee8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.694244] [<804a49b8>] 0x804a49b8
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.697717] [<80036f14>] 0x80036f14
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.701185] [<8025d440>] 0x8025d440
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.704662] [<8000b488>] 0x8000b488
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.708131]
Sun Sep 29 18:19:29 2019 kern.warn kernel: [  226.709665] ---[ end trace 0dde230055179878 ]---
10.10.20192543Base systemBug ReportVery LowHighCloud Engines Pogoplug V4 USB3 Does Not Workopenwrt-18.06Unconfirmed Task Description

In the configuration added

define Device/cloudengines_pogoplugv4

DEVICE_TITLE := Cloud Engines Pogoplug V4
DEVICE_DTS := kirkwood-pogoplug-series-4
DEVICE_PACKAGES := kmod-usb3

endef
TARGET_DEVICES += cloudengines_pogoplugv4

But kmod-usb3 has built and included. I need to enabled CONFIG_PACKAGE_kmod-usb3=y which also enables CONFIG_PACKAGE_kmod-usb-core=y as dependency the USB3 is working. This is build issue.

16.08.201694Base systemBug ReportVery LowMediumnetifd: PPPoE MTU problemTrunkNew Task Description

When you set the MTU of a ppp interface with proto=pppoe and ifname=nas0 via the mtu option,
the configured mtu will not be set on the ppp interface (what you want), but on the
underlying interface named by ifname (what you normally don’t want to change).

This leeds to log messages like this:


pppd[5641]: Interface nas0 has MTU of 1448 – should be at least 1500.


and MTUs other than what you really want.

example:


desired PPPoE MTU: 1448
actual nas0 MTU: 1448
actual PPPoE MTU: 1440

This issue seems to be related to the commit 7ac29b75319fd69a8a7c0aeea7804d381ec07d3d of netifd.

Regards,
Martin

24.08.2016115Base systemBug ReportVery LowMediumWWAN-connections using 3g with HUAWEI ME909u-521 unstab...TrunkUnconfirmed Task Description

Actually, I am trying to stabilize wwan (3g actually; LTE later on) using pppd with my HUAWEI ME909u-521,
because either my MT7620-based router locks up during boot already; or after short period of real usage.
During night, when router is almost idle, just some watchdog date sent via wwan, no problem.

First trace of a possible problem was this msg in logread:
daemon.notice netifd: wwan (1676): Error setting WWAN mode!

Wich is expected, as in /lib/netifd/proto/3g.sh:

...

                      elif echo "$cardinfo" | grep -qi huawei; then
                              case "$service" in
                                      umts_only) CODE="14,2";;
                                      gprs_only) CODE="13,1";;
                                      *) CODE="2,2";;
                              esac
                              export MODE="AT^SYSCFG=${CODE},3FFFFFFF,2,4"    #####Will not work !!!!! Switching USB-Stick to 3g-preferred ?

...
...

                      [ -n "$MODE" ] && gcom -d "$device" -s /etc/gcom/setmode.gcom

Will not work, because the ME909u-521 rejects AT^SYSCFG . However, AT^SYSCFGEX will work, but having different syntax.
MODE=”AT^SYSCFG=${CODE},3FFFFFFF,2,4” will be effective for simpler modems.

/etc/gcom/setmode.gcom returns exit 1; but this error is not checked in 3g.sh

Not shure, whether this is the reason for my problems; however, reason of concern, as high speed modems
are more and more common.
Willing to participate in testing/debugging.

For details regarding my modem, consult
HUAWEI ME909u-521 LTE LGA Module AT Command Interface Specification
http://www.paoli.cz/out/media/HUAWEI_ME909u-521_LTE_LGA_Module_AT_Command_Interface_Specification-V100R001_02.pdf

30.08.2016126KernelBug ReportVery LowMediumkernel panic on brcm47xx (netgear wgt634u) when routing...TrunkUnconfirmed Task Description

With LEDE version reboot-1444-g1bb914d, when pulling data through the WAN interface to the LAN interface at a sufficiently high speed, e.g. on a Raspberry Pi connected by ethernet to a LAN port, and the WAN interface connected to a gigabit internet service and issuing a command like:

curl https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.7.2.tar.xz > /dev/null

From the pi, I see something like:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  9 86.2M    9 7977k    0     0  1834k      0  0:00:48  0:00:04  0:00:44 1835k[  352.295252] smsc95xx 1-1.1:1.0 eth0: link down
  9 86.2M    9 7977k    0     0  1255k      0  0:01:10  0:00:06  0:01:04 1155k[  353.959380] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
  9 86.2M    9 7977k    0     0  43292      0  0:34:48  0:03:08  0:31:40     0

or

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  8 86.2M    8 7440k    0     0  1478k      0  0:00:59  0:00:05  0:00:54 1478k[ 1100.164849] smsc95xx 1-1.1:1.0 eth0: link down
  8 86.2M    8 7440k    0     0  1232k      0  0:01:11  0:00:06  0:01:05 1300k[ 1101.836954] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
  8 86.2M    8 7440k    0     0   740k      0  0:01:59  0:00:10  0:01:49     0

Where the “link down” is the WGT634U panic’ing and rebooting. The panic on the WGT634U looks like this:

[  171.966841] CPU 0 Unable to handle kernel paging request at virtual address 008224d8, epc == 80077ecc, ra == 801d8100
[  171.977700] Oops[#1]:
[  171.980093] CPU: 0 PID: 3 Comm: ksoftirqd/0 Not tainted 4.1.20 #0
[  171.986265] task: 8181e008 ti: 8182a000 task.ti: 8182a000
[  171.991711] $ 0   : 00000000 1000b800 008224d8 b41c479b
[  171.997140] $ 4   : 008224d8 00010000 80361ef8 00000000
[  172.002557] $ 8   : 81018b14 8101da14 00100100 dceb27b8
[  172.007983] $12   : ffffffff 00000001 ffffff80 000042c6
[  172.013400] $16   : b41c479b 00000001 81b450a8 81b7d260
[  172.018817] $20   : 803b5dcc 00000002 00000008 0000000a
[  172.024235] $24   : 00000000 80072b24                  
[  172.029653] $28   : 8182a000 8182bdb8 00000100 801d8100
[  172.035083] Hi    : 00000000
[  172.038026] Lo    : 0000006c
[  172.041036] epc   : 80077ecc put_compound_page+0x78/0x240
[  172.046547] ra    : 801d8100 skb_release_data+0xa8/0x10c
[  172.051920] Status: 1000b803 KERNEL EXL IE 
[  172.056254] Cause : 00800008
[  172.059194] BadVA : 008224d8
[  172.062144] PrId  : 00029007 (Broadcom BMIPS3300)
[  172.066891] Modules linked in: pppoe ppp_async iptable_nat ath5k ath pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_id xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_raw iptable_mangle iptable_filter ip_tables crc_ccitt compat ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables leds_gpio ehci_platform ehci_hcd gpio_button_hotplug usbcore nls_base usb_common ssb_hcd
[  172.132913] Process ksoftirqd/0 (pid: 3, threadinfo=8182a000, task=8181e008, tls=00000000)
[  172.141213] Stack : 1000b803 00000000 0000006c b41c479b 81b45080 801d8100 00000000 0000012c
          00000001 801e7d60 81becb60 81b7d260 81b7d260 80335b3c 81bece60 801d818c
          80360000 803623e0 81becb60 80335b3c 803623e0 801e63d8 8182be10 8182be10
          00000001 00000002 803b5dd0 00000001 803b5dd4 00000003 803b0000 80024fec
          81841048 80361100 819bb770 80007664 80364510 8181e008 80362898 04208040
          ...
[  172.178058] Call Trace:
[  172.180640] [<80077ecc>] put_compound_page+0x78/0x240
[  172.185822] [<801d8100>] skb_release_data+0xa8/0x10c
[  172.190895] [<801d818c>] __kfree_skb+0x28/0xb4
[  172.195466] [<801e63d8>] net_tx_action+0xd8/0x140
[  172.200329] [<80024fec>] __do_softirq+0x184/0x2b0
[  172.205184] [<80025140>] run_ksoftirqd+0x28/0x80
[  172.209953] [<8003bae0>] smpboot_thread_fn+0x148/0x178
[  172.215246] [<80039390>] kthread+0xdc/0xe8
[  172.219459] [<800010a8>] ret_from_kernel_thread+0x14/0x1c
[  172.224921] 
[  172.226470] 
Code: 30840001  0204100a  00402021 <8c420000> 000211c2  30420001  10400018  00000000  8e020000 
[  172.237022] ---[ end trace 89a3318b662df6d8 ]---
[  172.250536] Kernel panic - not syncing: Fatal exception in interrupt
[  172.262338] Rebooting in 3 seconds..

or

[ 1317.958261] Unhandled kernel unaligned access[#1]:
[ 1317.963173] CPU: 0 PID: 3 Comm: ksoftirqd/0 Not tainted 4.1.20 #0
[ 1317.969349] task: 8181e008 ti: 8182a000 task.ti: 8182a000
[ 1317.974795] $ 0   : 00000000 1000b801 00000001 00200000
[ 1317.980232] $ 4   : 647b394a 00010000 00018da4 00000000
[ 1317.985658] $ 8   : 8181e040 b1e1b104 00000017 40000000
[ 1317.991085] $12   : 500018dd 00000000 00000000 010102f2
[ 1317.996510] $16   : 80e4d1e0 00000001 80e4d208 81acb0e0
[ 1318.001936] $20   : 803b5dcc 00000002 00000008 0000000a
[ 1318.007362] $24   : 00000010 8001ead0                  
[ 1318.012789] $28   : 8182a000 8182bdd0 00000100 801d8100
[ 1318.018220] Hi    : 00000001
[ 1318.021160] Lo    : 00000001
[ 1318.024169] epc   : 80078474 put_page+0x0/0x4c
[ 1318.028732] ra    : 801d8100 skb_release_data+0xa8/0x10c
[ 1318.034104] Status: 1000b803 KERNEL EXL IE 
[ 1318.038439] Cause : 00800010
[ 1318.041380] BadVA : 647b394a
[ 1318.044330] PrId  : 00029007 (Broadcom BMIPS3300)
[ 1318.049076] Modules linked in: pppoe ppp_async iptable_nat ath5k ath pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_id xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_raw iptable_mangle iptable_filter ip_tables crc_ccitt compat ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables leds_gpio ehci_platform ehci_hcd gpio_button_hotplug usbcore nls_base usb_common ssb_hcd
[ 1318.115124] Process ksoftirqd/0 (pid: 3, threadinfo=8182a000, task=8181e008, tls=00000000)
[ 1318.123424] Stack : 00000000 80c60c94 00db35c0 626a006e ff330000 81acb0e0 81acb0e0 80335b3c
          80c28260 801d818c 80360000 8004f368 00000018 0000000a 803623e0 801e63d8
          8182be10 8182be10 80361100 00000002 803b5dd0 00000001 803b5dd4 00000013
          803b0000 80024fec 80364510 80361100 80360000 8000736c 80364510 8181e008
          80362898 04208040 00018da4 80360000 80310000 803b5dcc 803615a0 803114f4
          ...
[ 1318.160295] Call Trace:
[ 1318.162885] [<80078474>] put_page+0x0/0x4c
[ 1318.167108] [<801d8100>] skb_release_data+0xa8/0x10c
[ 1318.172182] [<801d818c>] __kfree_skb+0x28/0xb4
[ 1318.176752] [<801e63d8>] net_tx_action+0xd8/0x140
[ 1318.181614] [<80024fec>] __do_softirq+0x184/0x2b0
[ 1318.186471] [<80025140>] run_ksoftirqd+0x28/0x80
[ 1318.191238] [<8003bae0>] smpboot_thread_fn+0x148/0x178
[ 1318.196530] [<80039390>] kthread+0xdc/0xe8
[ 1318.200744] [<800010a8>] ret_from_kernel_thread+0x14/0x1c
[ 1318.206200] 
[ 1318.207747] 
Code: 00003021  0801e0ce  24a57888 <8c820000> 3042c000  10400003  00801821  0801df95  00000000 
[ 1318.218397] ---[ end trace 2502a626803fb4b9 ]---
[ 1318.231740] Kernel panic - not syncing: Fatal exception in interrupt
[ 1318.243362] Rebooting in 3 seconds..

This looks similar to: https://dev.openwrt.org/ticket/11091

17.09.2016181Base systemBug ReportVery LowMediumChanging TX power doesn't nothing (MediaTek MT7628AN ve...TrunkUnconfirmed Task Description

Hello,

As I said, if I change the TX power from 0 dBm to 20 dBm doesn’t nothing. There isn’t any visible change in tx power. I tested other powers too (5, 8, 15,..).

It is a Xiaomi Nano (lite).

SoC Type: MediaTek MT7628AN ver:1 eco:2
MIPS: machine is MiWiFi Nano
Linux version 4.4.19 (-) (gcc version 5.4.0 (LEDE GCC 5.4.0 r1444) ) #0 Fri Aug 26 15:03:40 2016.

29.11.2016315Base systemFeature RequestVery LowMediumImprove sysupgrade (CLI) on dual-partition routersTrunkUnconfirmed Task Description

Some of the recent Linksys (maybe other) routers have two partitions: WRT1900, EA8500, etc.

Would be great if when running sysupgrade on those routers it did NOT kill all active processes and kept the router working while writing an image to the inactive partition.

Would also be great if there was an option to prevent automatic reboot after writing an image.

Ultimate goal is to have an upgrade process where current working state is uninterrupted and only when you reboot – you boot into new image.

08.01.2017375ToolchainBuild FailureVery LowMediumBulidbots should have multilib support installed to pre...TrunkUnconfirmed Task Description

I’ve run into this earlier myself and now we are seeing at least one package failing because of it.
https://github.com/openwrt/packages/pull/2823

People seem to have run into this issue before since it’s listed as a requirement for Ubuntu 64-bit as an example.
https://wiki.openwrt.org/doc/howto/buildroot.exigence#examples_of_package_installations

24.01.2017427Base systemBug ReportVery LowMediumSwitch broken with WRT3200ACM (removes wifi adapters an...TrunkUnconfirmed Task Description

- Device problem occurs on:

WRT3200ACM

- Software versions of LEDE release, packages, etc.:

master tree (and v17.01), bisected to f24ffb901e0408917748773b883841eca52eea05.

- Steps to reproduce

* Flash a recent LEDE snapshot on the WRT3200ACM (and factory reset),
* enable wifi (2 or 5 Gz) → Wifi works
* disable wifi → errors in the dmesg about not being able to set a feature (can’t remember the exact error)
* re-enable wifi → errors in the dmesg saying that the adapter does not exist. This gets shouted in the dmesg every 5 seconds

A reboot doesn’t fix the issue. I need to downgrade the firmware prior to f24ffb901e0408917748773b883841eca52eea05 and factory reset to get the wifi adapters back.

For the Vlan bridge, symptoms are easier to detect:
* create a new adapter bridged on eth0.100 eth1.100
* no traffic goes through it. An snapshot before f24ffb901 used to work
(the setup is the Free french provider which has a vlan between the modem and the TV adapter over VLAN 100. So the LEDE box should act like a pass-through here only)

I bisected to the commit mentioned above (which, to me seems suspicious given that the driver is for mvsw61xx and the switch in the WRT3200ACM is MV88E6352, so a different generation). I don’t have enough knowledge of the chip to understand why this fails, but I don’t feel confident enough to simply send a PR with the revert.

Reverting f24ffb901e on top of master makes the Wifi and VLAN back to normal.


04.02.2017461Base systemBug ReportVery LowMediumMass Cascade of DHCP ULA Prefix Assignments with DHCP-P...AllUnconfirmed Task Description

Here is one that gets a bit ugly. Lets say we chain a bunch of LEDE based routers together. Lets also enable a nice numbering system in IP4 and IP6. Lets enable DHCP-PD through the network, because our ISP was generous with a /56. The IP4 is only static and is easy to control, see table below. Its tedious, but easy. The problem is in parallel the IP6 addresses compound in the ULA region. Each router DHCP-PD the ULA above it, and gets its own ULA from Global settings in Network UCI. There seems no easy way to control this mass cascade of ULA, and get good fail over.

Ideal Requirements:
(1) If router above is unavailable, then next tier router uses ULA (network global UCI) to begin assigning addresses to clients and subnets.
(2) If router above is available, then next tier router expires its self-generated ULA and subnets, and gets ULA from delegation above to then re-delegate to subnets.
(*) Bonus: make some parts optional

IP4 WAN Name Serves Subnet
(NAT) Router-1 172.16.0.1/24
172.16.0.2 Router-2A 172.17.0.1/24
172.17.0.2 Router-3A 172.24.0.1/24
172.17.0.3 Router-3B 172.25.0.1/24
172.16.0.3 Router-2B 172.18.0.1/24

IP6 Roots Name Serves Subnet Delegates Subnet
2001:db8/56 Router-1 2001:db8::1/64 2001:db8:0:10/60
fd00:ac10/48 fd00:ac10::1/64 2001:db8:0:20/60

                                                fd00:ac10:0:10/60
                                                fd00:ac10:0:20/60

2001:db8:0:10/60 Router-2A 2001:db8:0:10::1/64 2001:db8:0:14/62
fd00:ac10:0:10/60 fd00:ac10:0:10::1/64 2001:db8:0:18/62
fd00:ac11/48 fd00:ac11::1/64 fd00:ac10:0:14/62

                                                fd00:ac10:0:18/62
                                                fd00:ac11:0:14/62
                                                fd00:ac11:0:18/62

* please, i don’t want to type more. see how the ULA prefixes just keep multiplying.
** ‘172.16’ = ‘ac10’

06.02.2017472Base systemBug ReportVery LowMedium6to4 support with 1:1 natTrunkWaiting on reporter Task Description

One-to-one NAT means you have LAN address on interface and its mapped 1:1 to external ip addresses.
You can have incoming connections.

In such configuration “ipaddr” must be specified in 6to4 protocol section.
But due to bug this addr is submitted as local address for tunnel creation.
It does not work.

I fixed this with the following patch to /lib/netifd/proto/6to4.sh

48,53c48,53
< [ -z “$ipaddr” ] && {
< if ! network_get_ipaddr ipaddr “$wanif”; then
< proto_notify_error “$cfg” “NO_WAN_ADDRESS” < return
< fi
< }

if ! network_get_ipaddr ipladdr “$wanif”; then
> proto_notify_error “$cfg” “NO_WAN_ADDRESS”
return
> fi
>
> [ -z “$ipaddr” ] && ipaddr=$ipladdr
76c76
< json_add_string local “$ipaddr”

json_add_string local “$ipladdr”

I suggest you integrate this patch or do something similar yourself.

12.02.2017503KernelBuild FailureVery LowMediumBuild fails with CONFIG_KERNEL_GIT_CLONE_URI beig setAllAssigned Task Description

When specifying

CONFIG_KERNEL_GIT_CLONE_URI

a clean build fails, as the system assumes a already downloaded/cloned/packed linux-source is present in dl/ which on a freshly checked out openwrt/lede source isn’t the case yet, when

toolchain/kernel-headers

is about to be built.

The build error looks like:

make[3]: Entering directory `/build/lede.git/toolchain/kernel-headers'
zcat /build/lede.git/dl/linux-4.4.42.tar.gz | tar -C /build/lede.git/build_dir/toolchain-arm_cortex-a9+neon_gcc-6.3.0_glibc-2.24_eabi -xf -
gzip: /build/lede.git/dl/linux-4.4.42.tar.gz: No such file or directory
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors

The issue apparently is located in

include/kernel-defaults.mk

, line 53ff::

  ifeq ($(strip $(CONFIG_KERNEL_GIT_CLONE_URI)),"")
    define Kernel/Prepare/Default
        zcat $(DL_DIR)/$(LINUX_SOURCE) | $(TAR) -C $(KERNEL_BUILD_DIR) $(TAR_OPTIONS)
        $(Kernel/Patch)
        $(if $(QUILT),touch $(LINUX_DIR)/.quilt_used)
    endef
  else
    define Kernel/Prepare/Default
        zcat $(DL_DIR)/$(LINUX_SOURCE) | $(TAR) -C $(KERNEL_BUILD_DIR) $(TAR_OPTIONS)
    endef
  endif

For the package

kernel-headers

it just tries to access the not-yet downloaded/cloned/packed linux kernel source archive.

13.02.2017506Base systemBug ReportVery LowMediumBT Home Hub 5: 5g WiFi jumps to channel 36 and stops wo...TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on BT Home Hub 5
- Software versions of LEDE release, packages, r3425-f28eef4 and previous versions
- Steps to reproduce

It can be after a few hours, if WiFi 5g radio0 Qualcomm Atheros QCA9880 802.11nac (radio0) is configured to a Band B channel, it jumps to Channel 36 even though there is no apparent interference.
This appears to happen more frequently overnight during long periods of inactivity. Whilst the device is being used it does not happen.

After it does make the jump, if I stop and restart the device (using luci disable/enable) the device stops, but it fails to restart. Attempts to change the channel and re-enable the device also do not help.

It requires a reboot to restore service.

 


17.02.2017527PackagesBug ReportVery LowMediumQMI modem Olivetti Techcenter (0b3c:c00a) freezes on uq...lede-17.01Unconfirmed Task Description

Hello,

I used to use modem Olivetti Techcenter (0b3c:c00a) on OpenWRT CC.1 without problems.
However, testing on LEDE 17.01.0-rc2, I’m unable to connect.

I traced the problem to ‘uqmi -s -d “$device” –sync’ at https://github.com/lede-project/source/blob/master/package/network/utils/uqmi/files/lib/netifd/proto/qmi.sh#L101.

My config is simple as:

config interface 'wwan'
        option ifname 'wwan0'
        option proto 'qmi'
        option device '/dev/cdc-wdm0'
        option apn 'gprs.oi.com.br'
        option auth 'none'

Using strace, it always stops at this point:

...
open("/dev/cdc-wdm0", O_RDWR|O_EXCL|O_NOCTTY|O_NONBLOCK|O_LARGEFILE) = 6
fcntl64(6, F_GETFL)                     = 0x2082 (flags O_RDWR|O_NONBLOCK|O_LARGEFILE)
fcntl64(6, F_SETFL, O_RDWR|O_NONBLOCK|O_LARGEFILE) = 0
epoll_ctl(3, EPOLL_CTL_ADD, 6, {EPOLLIN|EPOLLRDHUP|EPOLLET, {u32=4305304, u64=18491139879337984}}) = 0
write(6, "\1\v\0\0\0\0\0\1'\0\0\0", 12) = 12
rt_sigaction(SIGINT, NULL, {sa_handler=0x401071, sa_mask=[RT_66 RT_67 RT_68 RT_69 RT_70 RT_71], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0}, 16) = 0
rt_sigaction(SIGTERM, NULL, {sa_handler=0x401071, sa_mask=[RT_66 RT_67 RT_68 RT_69 RT_70 RT_71], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0}, 16) = 0
rt_sigaction(SIGCHLD, NULL, {sa_handler=SIG_DFL, sa_mask=[RT_66 RT_67 RT_68 RT_69 RT_70 RT_71], sa_flags=0}, 16) = 0
rt_sigaction(SIGCHLD, {sa_handler=0x77d85541, sa_mask=[RT_68 RT_69 RT_73 RT_74 RT_75 RT_76 RT_78 RT_80 RT_82 RT_84 RT_85 RT_87 RT_88 RT_89 RT_90 RT_91 RT_93 RT_94 RT_95], sa_flags=SA_RESTORER, sa_restorer=0}, NULL, 16) = 0
rt_sigaction(SIGPIPE, NULL, {sa_handler=SIG_DFL, sa_mask=[RT_65 RT_68 RT_70], sa_flags=0}, 16) = 0
rt_sigaction(SIGPIPE, {sa_handler=SIG_IGN, sa_mask=[RT_68 RT_69 RT_73 RT_74 RT_75 RT_76 RT_78 RT_80 RT_82 RT_84 RT_85 RT_87 RT_88 RT_89 RT_90 RT_91 RT_93 RT_94 RT_95], sa_flags=SA_RESTORER, sa_restorer=0}, NULL, 16) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=7909, tv_nsec=543507701}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=7909, tv_nsec=544052152}) = 0
epoll_pwait(3, 

If I comment the “uqmi –sync” call, it simply works. “–sync” is a new action for uqmi since OpenWRT CC.1

My System is:



LEDE 17.01.0-rc2, r3131-42f3c1f
uqmi 2016-12-19-8ceeab69-1
machine: TP-LINK TL-WDR3600/4300/4310 (ar71xx) with QMI modem Olivetti Techcenter (0b3c:c00a)

18.02.2017532Base systemBug ReportVery LowMediumXiaomi mi nano (miwifi nano) unstable as WiFi Repeaterlede-17.01Unconfirmed Task Description

I run version 17.01.0-rc2 on my Xiaomi mi nano (https://lede-project.org/toh/hwdata/xiaomi/xiaomi_miwifi_nano)

I want to use it as wireless repeater with extra SSID (i think someone call it WISP client).

The miwifi is connected to my home wifi. And my device is connected to the SSID provided by the miwifi nano (no LAN connection).

If i do a speed test or download a large file to test the connection speed, the speed drops to a very low rate after some seconds. On the serial console i can see a call trace at this moment. After this, i have to reboot the miwifi nano to get a working WAN connection.

I will attach the serial console output. Hope that helps.

Tested with LAN connected was stable and fast.

drombo

26.02.2017557Base systemBug ReportVery LowMediumNexx wt3020 wifi rx sensitivity low with LEDE 17.01lede-17.01Unconfirmed Task Description

The rx sensitivity reported by a Nexx wt3020 is ~ 20dB lower than a comparable tp-link device located sided by side with the Nexx wt3020.
There have been reports of a similar problem with OpenWRT versions.

There is a ticket open with openwrt with a similar reported issue https://dev.openwrt.org/ticket/20369 as well as on the openwrt forum https://forum.openwrt.org/viewtopic.php?id=69042

lede trunk (and openwrt trunk) as of 24/2/17 also display similar poor rx sensitivity.

 


01.03.2017576Base systemBug ReportVery LowMediumath10k fails to load reporting a 'firmware crash' on QC...lede-17.01Unconfirmed Task Description

Problem occurs on a ZYXEL NBG6716. (802.11ac should be a QCA9880)
running 17.01.1 i.e. lede-17.01.0-r3205-59508e3-ar71xx-nand-nbg6716-squashfs-sysupgrade.bin
Crash occurs every time ath10k attempts to load

log with driver included in release

[   14.783881] ath10k_pci 0000:01:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[   15.000294] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
[   15.011181] ath10k_pci 0000:01:00.0: Falling back to user helper
[   15.090655] firmware ath10k!pre-cal-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed
[   15.299839] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[   15.309251] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[   15.322304] ath10k_pci 0000:01:00.0: firmware ver 10.2.4-1.0-00016 api 5 features no-p2p,raw-mode,mfp crc32 0c5668f8
[   15.333090] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[   15.343695] ath10k_pci 0000:01:00.0: Falling back to user helper
[   15.423744] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
[   15.442629] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[   16.551704] ath10k_pci 0000:01:00.0: firmware crashed! (uuid 68334050-5a5e-48bf-bccc-87f25cba960e)
[   16.560832] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[   16.570194] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[   16.583244] ath10k_pci 0000:01:00.0: firmware ver 10.2.4-1.0-00016 api 5 features no-p2p,raw-mode,mfp crc32 0c5668f8
[   16.593975] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[   16.601395] ath10k_pci 0000:01:00.0: htt-ver 0.0 wmi-op 5 htt-op 2 cal file max-sta 128 raw 0 hwcrypto 1
[   16.613031] ath10k_pci 0000:01:00.0: firmware register dump:
[   16.618783] ath10k_pci 0000:01:00.0: [00]: 0x4100016C 0x000015B3 0x009BA6A2 0x00955B31
[   16.626822] ath10k_pci 0000:01:00.0: [04]: 0x009BA6A2 0x00060130 0x0000001D 0x00000000
[   16.634857] ath10k_pci 0000:01:00.0: [08]: 0xFFFFFFFF 0x00401F6A 0x0000096C 0xFFFFFFFF
[   16.642883] ath10k_pci 0000:01:00.0: [12]: 0x00000009 0x00000000 0x009BAB4C 0x009BABA7
[   16.650916] ath10k_pci 0000:01:00.0: [16]: 0x00958080 0x0094E9B1 0x00000000 0x00000000
[   16.658951] ath10k_pci 0000:01:00.0: [20]: 0x409BA6A2 0x0040AA24 0x0040AAD4 0x00000001
[   16.666985] ath10k_pci 0000:01:00.0: [24]: 0x809BB189 0x0040AA84 0x0040EE0C 0xC09BA6A2
[   16.675020] ath10k_pci 0000:01:00.0: [28]: 0x809BB612 0x0040AAB4 0x000000E2 0x00000001
[   16.683047] ath10k_pci 0000:01:00.0: [32]: 0x80984880 0x0040ABA4 0x0040EE3C 0x0000003F
[   16.691089] ath10k_pci 0000:01:00.0: [36]: 0x8098FBA5 0x0040ABE4 0x0040E270 0x004062DC
[   16.699131] ath10k_pci 0000:01:00.0: [40]: 0x8098A79E 0x0040AC34 0x0040AC94 0x004062DC
[   16.707166] ath10k_pci 0000:01:00.0: [44]: 0x80988785 0x0040AC94 0x00410670 0x00400000
[   16.715200] ath10k_pci 0000:01:00.0: [48]: 0x8098AE78 0x0040AD44 0x00410670 0x00000001
[   16.723227] ath10k_pci 0000:01:00.0: [52]: 0x809B66F0 0x0040AD84 0x00410670 0x00411254
[   16.731269] ath10k_pci 0000:01:00.0: [56]: 0x809B2868 0x0040ADA4 0x00400000 0x00416EB4
[   21.543818] ath10k_pci 0000:01:00.0: wmi unified ready event not received
[   21.646943] ath10k_pci 0000:01:00.0: could not init core (-145)
[   21.653075] ath10k_pci 0000:01:00.0: could not probe fw (-145)
[   21.664514] ath10k_pci 0000:01:00.0: cannot restart a device that hasn't been started

log with alernative ath10k-ct from packages

Sun Feb 26 20:09:36 2017 kern.info kernel: [   15.991374] ath10k driver, optimized for CT firmware, probing pci.
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   15.998923] PCI: Enabling device 0000:01:00.0 (0000 -> 0002)
Sun Feb 26 20:09:36 2017 kern.info kernel: [   16.004876] ath10k_pci 0000:01:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
Sun Feb 26 20:09:36 2017 kern.info kernel: [   16.115573] EXT4-fs (sda1): mounted filesystem without journal. Opts: 
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.220291] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.231178] ath10k_pci 0000:01:00.0: Falling back to user helper
Sun Feb 26 20:09:36 2017 kern.err kernel: [   16.309980] firmware ath10k!pre-cal-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.322702] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/fwcfg-pci-0000:01:00.0.txt failed with error -2
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.333430] ath10k_pci 0000:01:00.0: Falling back to user helper
Sun Feb 26 20:09:36 2017 kern.err kernel: [   16.483479] firmware ath10k!fwcfg-pci-0000:01:00.0.txt: firmware_loading_store: map pages failed
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.502812] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-5.bin failed with error -2
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.513707] ath10k_pci 0000:01:00.0: Falling back to user helper
Sun Feb 26 20:09:36 2017 kern.err kernel: [   16.656794] firmware ath10k!QCA988X!hw2.0!firmware-5.bin: firmware_loading_store: map pages failed
Sun Feb 26 20:09:36 2017 kern.err kernel: [   16.666061] ath10k_pci 0000:01:00.0: could not fetch firmware file 'ath10k/QCA988X/hw2.0/firmware-5.bin': -11
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.676241] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-4.bin failed with error -2
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.687110] ath10k_pci 0000:01:00.0: Falling back to user helper
Sun Feb 26 20:09:36 2017 kern.err kernel: [   16.839245] firmware ath10k!QCA988X!hw2.0!firmware-4.bin: firmware_loading_store: map pages failed
Sun Feb 26 20:09:36 2017 kern.err kernel: [   16.848512] ath10k_pci 0000:01:00.0: could not fetch firmware file 'ath10k/QCA988X/hw2.0/firmware-4.bin': -11
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.858690] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-3.bin failed with error -2
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   16.869560] ath10k_pci 0000:01:00.0: Falling back to user helper
Sun Feb 26 20:09:36 2017 kern.err kernel: [   17.020761] firmware ath10k!QCA988X!hw2.0!firmware-3.bin: firmware_loading_store: map pages failed
Sun Feb 26 20:09:36 2017 kern.err kernel: [   17.030028] ath10k_pci 0000:01:00.0: could not fetch firmware file 'ath10k/QCA988X/hw2.0/firmware-3.bin': -11
Sun Feb 26 20:09:36 2017 kern.info kernel: [   17.152659] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
Sun Feb 26 20:09:36 2017 kern.info kernel: [   17.162062] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
Sun Feb 26 20:09:36 2017 kern.info kernel: [   17.174406] ath10k_pci 0000:01:00.0: firmware ver 10.1.467-ct-_fW-019-647197c api 2 features wmi-10.x,has-wmi-mgmt-tx,txstatus-noack,wmi-10.x-CT,ratemask-CT crc32 ce5082a8
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   17.190041] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   17.200645] ath10k_pci 0000:01:00.0: Falling back to user helper
Sun Feb 26 20:09:36 2017 kern.err kernel: [   17.280425] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
Sun Feb 26 20:09:36 2017 kern.info kernel: [   17.293109] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   18.216205] ath10k_pci 0000:01:00.0: 10.1 wmi init: vdevs: 16  peers: 127  tid: 256
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.224910] ath10k_pci 0000:01:00.0: firmware crashed! (uuid 44fc9f0a-8adb-4077-ae4e-82113c83f387)
Sun Feb 26 20:09:36 2017 kern.info kernel: [   18.234031] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
Sun Feb 26 20:09:36 2017 kern.info kernel: [   18.243382] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
Sun Feb 26 20:09:36 2017 kern.info kernel: [   18.255705] ath10k_pci 0000:01:00.0: firmware ver 10.1.467-ct-_fW-019-647197c api 2 features wmi-10.x,has-wmi-mgmt-tx,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT crc32 ce5082a8
Sun Feb 26 20:09:36 2017 kern.info kernel: [   18.278224] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
Sun Feb 26 20:09:36 2017 kern.info kernel: [   18.285650] ath10k_pci 0000:01:00.0: htt-ver 0.0 wmi-op 2 htt-op 2 cal file max-sta 128 raw 0 hwcrypto 1
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.297288] ath10k_pci 0000:01:00.0: firmware register dump:
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.303030] ath10k_pci 0000:01:00.0: [00]: 0x4100016C 0x000015B3 0x009B1635 0x00955B31
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.311074] ath10k_pci 0000:01:00.0: [04]: 0x009B1635 0x00060130 0x0000001D 0x009BAB8B
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.319114] ath10k_pci 0000:01:00.0: [08]: 0xFFFFFFFF 0x00401F6A 0x0000096C 0xFFFFFFFF
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.327147] ath10k_pci 0000:01:00.0: [12]: 0x00000009 0x00000000 0x009B1AD1 0x009B1B29
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.335182] ath10k_pci 0000:01:00.0: [16]: 0x00958080 0x0094085D 0x00000000 0x00000000
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.343210] ath10k_pci 0000:01:00.0: [20]: 0x409B1635 0x0040AA44 0x0040AAF4 0x00000001
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.351251] ath10k_pci 0000:01:00.0: [24]: 0x809B21C2 0x0040AAA4 0x00401F7E 0xC09B1635
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.359290] ath10k_pci 0000:01:00.0: [28]: 0x809B2676 0x0040AAD4 0x00401CC0 0x000000E2
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.367329] ath10k_pci 0000:01:00.0: [32]: 0x8098494F 0x0040ABC4 0x0040E07C 0x0000003F
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.375362] ath10k_pci 0000:01:00.0: [36]: 0x8098ED6F 0x0040AC04 0x0040D4B0 0x004062DC
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.383391] ath10k_pci 0000:01:00.0: [40]: 0x809892DD 0x0040AC54 0x0040ACB4 0x00400000
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.391431] ath10k_pci 0000:01:00.0: [44]: 0x809887C9 0x0040ACA4 0x0040F7B8 0x00400000
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.399463] ath10k_pci 0000:01:00.0: [48]: 0x809897B4 0x0040AD44 0x0040F7B8 0x00000001
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.407500] ath10k_pci 0000:01:00.0: [52]: 0x809AD74A 0x0040AD84 0x0040F7B8 0x0000A000
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.415535] ath10k_pci 0000:01:00.0: [56]: 0x809AA392 0x0040ADA4 0x00400000 0x00414F44
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   18.425582] ath10k_pci 0000:01:00.0: debug log header, dbuf: 0x412598  dropped: 0
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   18.434191] ath10k_pci 0000:01:00.0: [0] next: 0x4125b0 buf: 0x4103fc sz: 1500 len: 56 count: 2 free: 0
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.444731] ath10k_pci 0000:01:00.0: ath10k_pci ATH10K_DBG_BUFFER:
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.451001] ath10k: [0000]: 38700000 0500FC17 70201031 08000000 80000000 B8F74000 01000600 39700000
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.460186] ath10k: [0008]: 0100FC17 B3150000 B3150000 34A94000 6C010041 09000000
Sun Feb 26 20:09:36 2017 kern.err kernel: [   18.467775] ath10k_pci 0000:01:00.0: ATH10K_END
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   18.473385] ath10k_pci 0000:01:00.0: [1] next: 0x412598 buf: 0x4109ec sz: 1500 len: 0 count: 0 free: 0
Sun Feb 26 20:09:36 2017 kern.err kernel: [   23.223848] ath10k_pci 0000:01:00.0: wmi unified ready event not received
Sun Feb 26 20:09:36 2017 kern.err kernel: [   23.325855] ath10k_pci 0000:01:00.0: could not init core (-145)
Sun Feb 26 20:09:36 2017 kern.err kernel: [   23.331970] ath10k_pci 0000:01:00.0: could not probe fw (-145)
Sun Feb 26 20:09:36 2017 kern.info kernel: [   23.338980] i2c /dev entries driver
Sun Feb 26 20:09:36 2017 kern.warn kernel: [   23.344460] ath10k_pci 0000:01:00.0: cannot restart a device that hasn't been started


05.03.2017599Base systemBug ReportVery LowMediumHame MPR-A2 switch has unknown topologyTrunkUnconfirmed Task Description

Vlan don’t work.


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

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

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


13.03.2017625PackagesBug ReportVery LowMediumno default route written using proto=wwanlede-17.01Unconfirmed Task Description

LEDE_RELEASE=”LEDE Reboot 17.01-SNAPSHOT r6469+17-c114383”

Configure steps as follows:

Run ubus listen in backround
ubus -t 9999 listen &

uci del network.wwan
uci set network.wwan=interface
uci set network.wwan.proto=wwan
uci set network.wwan.defaultroute=’0’ uci set network.wwan.pincode= uci set network.wwan.apn= uci commit && /etc/init.d/network restart
...
{ “ubus.object.add”: {”id”:107055350,”path”:”network.interface.wwan_4”} }
{ “network.interface”: {”action”:”ifup”,”interface”:”wwan_4”} }
...

As you see default route should not be written immediately. You see default route in inactive section in ubus. So now lets set the default route for this interface

uci set network.wwan.defaultroute=’1’ uci commit && /etc/init.d/network reload

You see no ubus message as well no change of default route. Now lets use QMI proto directly

uci del network.wwan
uci set network.wwan=interface
uci set network.wwan.proto=qmi
uci set network.wwan.device=/dev/cdc-wdm0
uci set network.wwan.defaultroute=’0’ uci set network.wwan.pincode= uci set network.wwan.apn= uci commit && /etc/init.d/network restart
...
{ “ubus.object.add”: {”id”:107055350,”path”:”network.interface.wwan_4”} }
{ “network.interface”: {”action”:”ifup”,”interface”:”wwan_4”} }
...

So now lets set the default route for this interface and you see ubus messages comming up as well default route is set

uci set network.wwan.defaultroute=’1’ uci commit && /etc/init.d/network reload
{ “network.interface”: {”action”:”ifdown”,”interface”:”wwan”} }
{ “network.interface”: {”action”:”ifdown”,”interface”:”wwan_4”} }
root@RED50:/lib# { “ubus.object.remove”: {”id”:399408035,”path”:”network.interface.wwan_4”} }
{ “network.interface”: {”action”:”ifup”,”interface”:”wan2”} }
{ “network.interface”: {”action”:”ifup”,”interface”:”wwan”} }
{ “ubus.object.add”: {”id”:828745890,”path”:”network.interface.wwan_4”} }
{ “network.interface”: {”action”:”ifup”,”interface”:”wwan_4”} }


17.03.2017634Base systemBug ReportMediumMediumFactory flashing fails because LEDE filename is too lon...AllNew Task Description

On a TP-Link TL-WR841N v11, flashing LEDE from the web interface of the stock firmware is not possible.

This is caused by a stupid check that refuses filename longer than 64 chars in the web interface. The check is implemented in javascript and returns a cryptic error message like “Please select a file to upload”, as if no file was selected.

The current naming scheme is quite long:

$ echo ‘lede-17.01.0-r3205-59508e3-ar71xx-generic-tl-wr841-v11-squashfs-factory-eu.bin’ | wc -c
79

Shortening the name like the following would decrease the length below 64 chars, and leave some space for a custom suffix (e.g. using EXTRA_IMAGE_NAME in the Imagebuilder):

$ echo ‘lede-17.01.0-ar71xx-tlwr841v11-squashfs-factory-eu.bin’ | wc -c
55

25.03.2017654PackagesBug ReportVery LowMediumdial on demand not workinglede-17.01Unconfirmed Task Description

Using LEDE Reboot 17.01.0 r3205-59508e3 on Lenovo Y1.
After setting the Inactivity timeout to something not 0 in luci (option demand ‘5’ in the config file),the dial procedure will be stopping at some stage,can’t establish a connect.
And the log will be like this:

May  7 08:48:52 OpenWrt daemon.info pppd[9714]: Plugin rp-pppoe.so loaded.
May  7 08:48:52 OpenWrt daemon.info pppd[9714]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.5
May  7 08:48:52 OpenWrt daemon.notice pppd[9714]: pppd 2.4.5 started by root, uid 0
May  7 08:48:52 OpenWrt daemon.info pppd[9714]: Using interface pppoe-wan
May  7 08:48:52 OpenWrt daemon.notice pppd[9714]: local  IP address 10.64.64.64
May  7 08:48:52 OpenWrt daemon.notice pppd[9714]: remote IP address 10.112.112.112

Without the demand option everything works fine:

May  7 09:08:43 OpenWrt daemon.info pppd[2712]: Plugin rp-pppoe.so loaded.
May  7 09:08:43 OpenWrt daemon.info pppd[2712]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.5
May  7 09:08:43 OpenWrt daemon.notice pppd[2712]: pppd 2.4.5 started by root, uid 0
May  7 09:08:48 OpenWrt daemon.info pppd[2712]: PPP session is 9873
May  7 09:08:48 OpenWrt daemon.warn pppd[2712]: Connected to 00:30:88:1f:30:07 via interface eth2
May  7 09:08:48 OpenWrt daemon.info pppd[2712]: Using interface pppoe-wan
May  7 09:08:48 OpenWrt daemon.notice pppd[2712]: Connect: pppoe-wan <--> eth2
May  7 09:08:48 OpenWrt daemon.notice pppd[2712]: PAP authentication succeeded
May  7 09:08:48 OpenWrt daemon.notice pppd[2712]: peer from calling number 00:30:88:1F:30:07 authorized
May  7 09:08:49 OpenWrt daemon.notice pppd[2712]: local  IP address 93.232.124.118
May  7 09:08:49 OpenWrt daemon.notice pppd[2712]: remote IP address 217.0.119.51
May  7 09:08:49 OpenWrt daemon.notice pppd[2712]: primary   DNS address 217.0.43.17
May  7 09:08:49 OpenWrt daemon.notice pppd[2712]: secondary DNS address 217.0.43.49

(these logs is copy from the openwrt bug ticketExternal Link because my log for this part had be override by massive “ieee80211 phy1: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2”,sincere apology,smile)
It seems to be a historied legacy bug from Openwrt BB (or AA),and there is a solution by changing 2 files to make pppd disconnect when inactivity but can’t re-dial:
1./etc/config/network, disable IPv6

config interface 'wan'
        option ipv6 0

2./lib/netifd/proto/ppp.sh: change nodefaultroute to defaultroute in the function of ppp_generic_setup()

	proto_run_command "$config" /usr/sbin/pppd \
		nodetach ipparam "$config" \
		ifname "$pppname" \
		${keepalive:+lcp-echo-interval $interval lcp-echo-failure ${keepalive%%[, ]*}} \
		${ipv6:++ipv6} \
		defaultroute \

Hope this stinking bug can be terminated in LEDE

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

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

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

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


08.04.2017689Base systemBug ReportVery LowMedium WiFi disconnects on Dir300 b7lede-17.01Unconfirmed Task Description

This: https://github.com/nodemcu/nodemcu-firmware/issues/639 and this: https://forum.openwrt.org/viewtopic.php?id=43188

Device: Dlink Dir-300 b7 with latest LEDE 17.01

Solution: Adding an option ‘option disassoc_low_ack 0’ to /etc/config/wireless in the config wifi-iface section.

08.04.2017692Base systemBug ReportMediumMediumWLAN AP not working on RasPi (bcm2710 target)TrunkAssigned Task Description

When flashing the brcm2708 / bcm2710 target the WiFi interface gets stuck in “client mode” and the AP will not be able to be brought up.

Some screenshots and a load of discussion here:
https://forum.lede-project.org/t/ap-mode-radio0-in-raspi-3-always-acts-as-a-client-shows-as-wlan0-in-luci/2885

Two more days of tinkering, wifi-up’ing and -down’ing did not bring me further.
I flashed another Pi3 (to exclude a hardware defect) with the same result.

I tried latest snapshot and stable images.
I am happy to help debug – tell me what you need me to do.

Greetings,
–Thomas

19.04.2017723Base systemBug ReportVery LowMediumath10k fails station mode for QCA986x/988xlede-17.01Unconfirmed Task Description

Set-Up:

  • Board: NXP/Freescale Layerscape TWR-LS1021A Router/AP
  • Wireless Network Adapter: Qualcomm Atheros PCI QCA986x/988x 802.11ac
  • OS: LEDE (derivative from OpenWrt) Reboot/SNAPSHOT/r3044-21356a6

On host: menuconfig:

  • Kernel modules > Wireless Drivers: kmod-ath10k, kmod-ath, kmod-cfg80211, kmod-mac80211
  • Firmware: ath10k-firmware-qca988x
  • Network: wpad, wpa-cli
  • netifd + ubus + uci

On TWR-LS1021A:
Just in order to test if WiFi card is really QCA986x/988x 802.11ac:
root@lede:/# cat /sys/bus/pci/devices/0000\:01\:00.0/vendor

0x168c

root@lede:/# cat /sys/bus/pci/devices/0000\:01\:00.0/device

0x003c

Google: PCI 168c 0x003c gives QCA986x/988x


During the first boot, boot scripts create: /etc/config/wireless with the following contents:

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '36'
        option hwmode '11a'
        option path 'soc/3400000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
        option htmode 'VHT80'
        option disabled '1'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'LEDE'
        option encryption 'none'

We remove: option disabled ‘1’ (WiFi is disabled by default → enable it) and reboot.

Boot with USB-serial output:

…
[    6.270954] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[    6.450972] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
[    6.461643] ath10k_pci 0000:01:00.0: Falling back to user helper
[    6.474916] firmware ath10k!pre-cal-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed
[    6.484102] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-0000:01:00.0.bin failed with error -2
[    6.494431] ath10k_pci 0000:01:00.0: Falling back to user helper
[    6.507497] firmware ath10k!cal-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed
[    6.528736] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[    6.537986] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[    6.548737] ath10k_pci 0000:01:00.0: firmware ver 10.2.4-1.0-00016 api 5 features no-p2p,raw-mode,mfp crc32 0c5668f8
[    6.599443] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[    6.609853] ath10k_pci 0000:01:00.0: Falling back to user helper
[    6.623269] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
[    6.632927] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[    7.775018] ath10k_pci 0000:01:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
…
[   11.014199] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   11.022336] device wlan0 entered promiscuous mode
[   11.336732] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
…

Remarks:

  • pre-cal/cal-pci error messages are connected to pre-calibration issues, so ignore them
  • board-2.bin error: indeed /lib/firmware/ath10k/QCA988X/hw2.0/ contains only board.bin and firmware-5.bin. we have tried to copy hw2.0/board-2.bin from QCA proprietary driver but then: [ 6.590282] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003c,subsystem-vendor=0000,subsystem-device=0000 from ath10k/QCA988X/hw2.0/board-2.bin

Nevertheless, the driver is correctly started in AP mode:
root@lede:/# iwconfig

wlan0     IEEE 802.11  Mode:Master  Tx-Power=20 dBm   
          RTS thr:off   Fragment thr:off
          Power Management:off

root@lede:/# ifconfig

wlan0     Link encap:Ethernet  HWaddr 00:0E:8E:59:7D:8F  
          inet6 addr: fe80::20e:8eff:fe59:7d8f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:128 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:15588 (15.2 KiB)

Now try to switch to station mode with WPA:
AP: 802.11a, channel 36: 5.18 GHz, SSID: iwl3xxx, Security mode: WPA/PSK, CCMP/AES (WPA/RSN), Password: password

TWR-LS1021A: /etc/config/wireless:

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '36'
        option hwmode '11a'
        option path 'soc/3400000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'wlan'
        option mode 'sta'
        option ssid 'iwl3xxx'
        option encryption 'psk'
        option key 'password'

config interface 'wlan'
        option ifname 'default_radio0'
        option proto 'static'
        option ipaddr '192.168.0.2'
        option netmask '255.255.255.0'

root@lede:/# iwconfig

wlan0     IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm   
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

It correctly switches to managed mode but no ESSID and no AP are assigned. Direct WPA supplicant employment also fails:

We create WPA config file /a:

country=00
network={
  ssid="iwl3xxx"
  psk="password"
  scan_ssid=1
  key_mgmt=WPA-PSK
  pairwise=CCMP TKIP
  group=CCMP TKIP
}

Start WPA supplicant:
root@lede:/# wpa_supplicant -c /a -i wlan0 -D nl80211

Successfully initialized wpa_supplicant
wlan0: SME: Trying to authenticate with 00:18:92:05:b6:ec (SSID='iwl3xxx' freq=5180 MHz)
[ 2736.691425] wlan0: authenticate with 00:18:92:05:b6:ec
[ 2736.702348] wlan0: send auth to 00:18:92:05:b6:ec (try 1/3)
[ 2736.709540] wlan0: authenticated
wlan0: Trying to associate with 00:18:92:05:b6:ec (SSID='iwl3xxx' freq=5180 MHz)
[ 2736.717183] wlan0: associate with 00:18:92:05:b6:ec (try 1/3)
[ 2736.725522] wlan0: RX AssocResp from 00:18:92:05:b6:ec (capab=0x411 status=0 aid=1)
[ 2736.734827] wlan0: associated
[ 2736.738114] wlan0: deauthenticating from 00:18:92:05:b6:ec by local choice (Reason: 3=DEAUTH_LEAVING)
wlan0: Associated with 00:18:92:05:b6:ec
wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:18:92:05:b6:ec reason=3 locally_generated=1
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="iwl3xxx" auth_failures=1 duration=10 reason=WRONG_KEY

Though the key is correct, the driver delivers WRONG_KEY message. In order to eliminate any security issues, we switch to insecure communication:
AP: 802.11a, channel 36: 5.18 GHz, SSID: iwl3xxx, Security mode: NONE

TWR-LS1021A: WPA config file /a:

country=00
network={
  ssid="iwl3xxx"
  scan_ssid=1
  key_mgmt=NONE
}

Start WPA supplicant:
root@lede:/# wpa_supplicant -c /a -i wlan0 -D nl80211

Successfully initialized wpa_supplicant
wlan0: SME: Trying to authenticate with 00:18:92:05:b6:ec (SSID='iwl3xxx' freq=5180 MHz)
[   26.011997] wlan0: authenticate with 00:18:92:05:b6:ec
[   26.069291] wlan0: send auth to 00:18:92:05:b6:ec (try 1/3)
[   26.075992] wlan0: authenticated
wlan0: Trying to associate with 00:18:92:05:b6:ec (SSID='iwl3xxx' freq=5180 MHz)
[   26.087236] wlan0: associate with 00:18:92:05:b6:ec (try 1/3)
[   26.094140] wlan0: RX AssocResp from 00:18:92:05:b6:ec (capab=0x401 status=0 aid=1)
[   26.103088] wlan0: associated
[   26.106163] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: Associated with 00:18:92:05:b6:ec
wlan0: CTRL-EVENT-CONNECTED - Connection to 00:18:92:05:b6:ec completed [id=0 id_str=]
wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[   36.117315] wlan0: deauthenticating from 00:18:92:05:b6:ec by local choice (Reason: 3=DEAUTH_LEAVING)
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:18:92:05:b6:ec reason=3 locally_generated=1

So, WPA supplicant reports: we were authenticated and associated, connection completed. And then we leave WiFi by local choice. WireShark shows that deauthenticate-request comes from from us to access point.

Result: ath10k fails station mode for QCA986x/988x

23.04.2017731Base systemBug ReportVery LowMediumOffline build not possible after "make download"lede-17.01Unconfirmed Task Description

I tried to do an offline build of almost the default configuration for x86_64 of 17.01.1. So I did “make download” (with that configuration) on a machine connected to the internet and then tried to build from there offline, but “make” tried to download files, that “make download” did not and failed.

The first few files were the following, then I gave up:

ncurses-6.0.tar.gz
lzo-2.09.tar.gz
usign-2015-07-04-ef641914.tar.xz
mbedtls-2.4.2-gpl.tgz
ustream-ssl-2016-07-02-ec80adaa.tar.xz
openssl-1.0.2k.tar.gz

28.04.2017740Base systemBug ReportVery LowMediumWRT54 Router Power LED continually flasheslede-17.01Unconfirmed Task Description
  • LEDE 17.01.1
  • WRT54G v3 and WRT54GS
  • after installing, power LED continually flashes
  • no noticeable difference in LED between failsafe/actual moment of soft reboot//when router is up
  • I had to failsafe the WRT54G multiple times due to other initial config errors (attempting to bridge wlan0 to LAN, which was possible in another OS), I could only identify failsafe by Pinging it then SSHing quickly
  • The method I described to identify failsafe is not mentioned in documentation
03.05.2017752Base systemBug ReportVery LowMediummtk7688 radio in client mode throwing kernel stack trac...TrunkUnconfirmed Task Description

Supply the following if possible:
- Device problem occurs on

AsiaRF AWM688, based on the mtk7688 SoC, similar to the LinkIt 7688

- Software versions of LEDE release, packages, etc.

current HEAD (21c2e93e67bc44c1b72dbbe2dc9f9451d44f81a0)

- Steps to reproduce

Put your wifi interface into station mode, with something like this:

uci set wireless.@wifi-iface[0].mode=sta
uci set wireless.@wifi-iface[0].network=wan
uci set wireless.@wifi-iface[0].ssid="<yournetworkssid>"
uci set wireless.@wifi-iface[0].encryption=<yournetworkencryption>
uci set wireless.@wifi-iface[0].key=<yournetworkkey>
uci set network.wan.ifname=''
uci commit wireless
uci commit network
/etc/init.d/network restart

The stack traces look like this:

[  381.712245] ------------[ cut here ]------------
[  381.721603] WARNING: CPU: 0 PID: 0 at compat-wireless-2017-01-31/net/mac80211/tx.c:4230 ieee80211_csa_is_complete+0x4d4/0x668 [mac80211]()
[  381.746243] Modules linked in: pppoe ppp_async snd_usb_audio pppox ppp_generic pl2303 nf_conntrack_ipv6 mmc_spi iptable_nat ipt_REJECT ipt_MASQUERADE ftdi_sio cp210x ch341 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 usbserial usbmon ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda spidev snd_usbmidi_lib slhc pwm_mediatek of_mmc_spi nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables crc7 crc_itu_t crc_ccitt snd_soc_simple_card snd_soc_ralink_i2s snd_soc_wm8960 i2c_mt7621 snd_soc_core ralink_gdma virt_dma mt76x2e mt7603e i2c_dev mt76 mac80211 cfg80211 compat ledtrig_oneshot ledtrig_heartbeat ledtrig_gpio ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables snd_pcm_dmaengine snd_compress snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_rawmidi snd_seq_device snd_hwdep snd input_core soundcore vfat fat nls_utf8 nls_iso8859_1 nls_cp437 regmap_spi regmap_mmio regmap_i2c i2c_core regmap_core lzo_decompress lzo_compress mmc_block usb_storage mtk_sd mmc_core leds_gpio ohci_platform ohci_hcd ledtrig_transient ehci_platform sd_mod scsi_mod ehci_hcd gpio_button_hotplug usbcore nls_base usb_common
[  381.997790] CPU: 0 PID: 0 Comm: swapper Tainted: G        W       4.4.61 #0
[  382.011576] Stack : 8035bff4 00000000 00000001 803a0000 803a10dc 803a0d63 8033d94c 00000000
          803f3438 8380de90 00000000 82d2b630 00000001 8004ae6c 80342e54 803a0000
          00000003 8380de90 80341258 8380dd74 00000001 80048dd8 83012b40 00000000
          8039fe50 00000000 00000000 00000000 00000000 00000000 00000000 00000000
          00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
          ...
[  382.082022] Call Trace:
[  382.086872] [<8001486c>] show_stack+0x50/0x84
[  382.095501] [<8002544c>] warn_slowpath_common+0xa0/0xd0
[  382.105857] [<80025504>] warn_slowpath_null+0x18/0x24
[  382.115987] [<832aa34c>] ieee80211_csa_is_complete+0x4d4/0x668 [mac80211]
[  382.129537] 
[  382.132479] ---[ end trace cedc8f2cca6a57da ]---
[  448.821439] ------------[ cut here ]------------
[  448.830796] WARNING: CPU: 0 PID: 0 at compat-wireless-2017-01-31/net/mac80211/tx.c:4230 ieee80211_csa_is_complete+0x4d4/0x668 [mac80211]()
[  448.855431] Modules linked in: pppoe ppp_async snd_usb_audio pppox ppp_generic pl2303 nf_conntrack_ipv6 mmc_spi iptable_nat ipt_REJECT ipt_MASQUERADE ftdi_sio cp210x ch341 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 usbserial usbmon ums_usbat ums_sddr55 ums_sddr09 ums_karma ms_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda spidev snd_usbmidi_lib slhc pwm_mediatek of_mmc_spi nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables crc7 crc_itu_t crc_ccitt snd_soc_simple_card snd_soc_ralink_i2s snd_soc_wm8960 i2c_mt7621 snd_soc_core ralink_gdma virt_dma mt76x2e mt7603e i2c_dev mt76 mac80211 cfg80211 compat ledtrig_oneshot ledtrig_heartbeat ledtrig_gpio ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables snd_pcm_dmaengine snd_compress snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_rawmidi snd_seq_device snd_hwdep snd input_core soundcore vfat fat nls_utf8 nls_iso8859_1 nls_cp437 regmap_spi regmap_mmio regmap_i2c i2c_core regmap_core lzo_decompress lzo_compress mmc_block usb_storage mtk_sd mmc_core leds_gpio ohci_platform ohci_hcd ledtrig_transient ehci_platform sd_mod scsi_mod ehci_hcd gpio_button_hotplug usbcore nls_base usb_common
[  449.106963] CPU: 0 PID: 0 Comm: swapper Tainted: G        W       4.4.61 #0
[  449.120752] Stack : 8035bff4 00000000 00000001 803a0000 803a10dc 803a0d63 8033d94c 00000000
          803f3438 8380de90 00000000 82d2b630 00000001 8004ae6c 80342e54 803a0000
          00000003 8380de90 80341258 8380dd74 00000001 80048dd8 831a7852 00000000
          8039fe50 00000000 00000000 00000000 00000000 00000000 00000000 00000000
          00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
          ...
[  449.191202] Call Trace:
[  449.196044] [<8001486c>] show_stack+0x50/0x84
[  449.204680] [<8002544c>] warn_slowpath_common+0xa0/0xd0
[  449.215034] [<80025504>] warn_slowpath_null+0x18/0x24
[  449.225170] [<832aa34c>] ieee80211_csa_is_complete+0x4d4/0x668 [mac80211]
[  449.238722] 
[  449.241679] ---[ end trace cedc8f2cca6a57db ]---

The line number is a bit off, but it looks like maybe ieee80211_csa_is_complete is complaining because vif→type == station mode isn’t handled. I don’t know what “csa” means here.

04.05.2017761Base systemBug ReportVery LowMediumWRT54G image is too big for device.lede-17.01Unconfirmed Task Description

Device: WRT54G v2
Lede version/build: lede-17.01.1-brcm47xx-legacy-linksys-wrt54g-squashfs.bin

The image provided is 4001824 bytes, whereas device flash is 3866624 bytes.
Cannot upload firmware to device.

Source old wiki: https://wiki.openwrt.org/toh/linksys/wrt54g

08.05.2017767ToolchainBug ReportVery LowMediumuml: Imagebuilder does not honor default packages for u...TrunkUnconfirmed Task Description

Stock LEDE - r4099-4c3953b

Plain UML images are fine and work. If you want to build images with the imagebuilder the default package list is not honored and modules are missing - like kmod-80211-hwsim and all related packages.

The squashfs image also does not work:

[    0.270000] squashfs: SQUASHFS error: Filesystem uses "zlib" compression. This is not supported

profiles.mk in Imagebuilder dir seems wonky:

$ cat .profiles.mk
PROFILE_NAMES = Default
Default_NAME:=Default
Default_PACKAGES:=

.targetinfo looks okay, but I don’t know:

Source-Makefile: target/linux/uml/Makefile
Target: uml
Target-Board: uml
Target-Name: User Mode Linux
Target-Arch: x86_64
Target-Arch-Packages: x86_64
Target-Features: audio ext4 source-only squashfs
Target-Depends:
Target-Optimization: -Os -pipe
CPU-Type:
Linux-Version: 4.4.61
Linux-Release: 1
Linux-Kernel-Arch: um
Target-Description:

@@
Default-Packages: base-files libc libgcc busybox dropbear mtd uci opkg netifd fstools uclient-fetch logd dnsmasq iptables ip6tables ppp ppp-mod-pppoe firewall odhcpd odhcp6c wpad-mini kmod-mac80211-hwsim mkf2fs e2fsprogs iwinfo
14.05.2017783PackagesBug ReportVery LowMediumgpsd doesn't work with "Garmin USB binary" (nor NMEA200...TrunkUnconfirmed Task Description

Supply the following if possible:

- Device problem occurs on

I tried it on GL-AR150, but it should reproduce on any device w/ USB

- Software versions of LEDE release, packages, etc.

LEDE 17.01.1
gpsd 3.16-1

- Steps to reproduce

If you have a device with “Garmin USB binary” (eg : eTrex), then

gpsd -n -N -G -D 4 /dev/ttyUSB0

... should show data once a second.

From my reading of the code, even without a Garmin device, “-D 4” debug level should show a message of “Probing Garmin USB binary driver...\n”

From my reading of the code, it looks a a build problem. 2 “defines” need to be made :

NON_NMEA0183_ENABLE

HAVE_LIBUSB

FYI, there is a similiar bug for “NMEA2000” : If you do “gpsd -h”, you should see “NMEA2000” on the list of “drivers”. I can file a separate bug for this if you want.

Thanks !

15.05.2017786Base systemFeature RequestVery LowMediumPlease, add support to ecdsa key typelede-17.01Researching Task Description

At the moment dropbear tool is compiled without the ecdsa key type support.
ECDSA (https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm) is considere better than RSA as it requires fewer key bits to gain same security.

16.05.2017788Base systemBug ReportVery LowMediumMQMaker WiTi 5ghz interface does not workAllUnconfirmed Task Description

Supply the following if possible:
- MQMaker WiTi
- All released LEDE versions
- enable the 5ghz interface. LEDE reports that it’s up and running but it isn’t.

I tried 3 builds.

LEDE trunk - fail
LEDE 17.01.0 - fail
OpenWRT trunk - works.

Something broke in the mt76 driver between OpenWRT trunk and LEDE final.

AFAIK it’s after the bug fix to packet injection.

 


25.05.2017803PackagesBug ReportVery LowMediumNL80211_STA_INFO_INACTIVE_TIME incorrect value for IB...TrunkUnconfirmed Task Description

- ar71xx affected
- latest LEDE trunk affected and may be older versions
- Steps to reproduce

Buid current LEDE trunk with a10k-ct driver and CT firmware for QCA988x.
Flash devices with firmware.
Create IBSS interface for 2 or more ath10k devices and connect them.

 

iwinfo shows negative value for last activity. Value is rising. TX traffic can’t pass through interface.
All incoming packets come with “unknown” bitrate.

root@LEDE:~# iwinfo mesh5_0 assoclist
84:16:F9:B1:A0:3E -39 dBm / -103 dBm (SNR 64) -230820 ms ago

      RX: unknown                                      794 Pkts.
      TX: 6.0 MBit/s                                     0 Pkts.

root@LEDE:~# iwinfo mesh5_0 assoclist
84:16:F9:B1:A0:3E -39 dBm / -103 dBm (SNR 64) -127810 ms ago

      RX: unknown                                     2828 Pkts.
      TX: 6.0 MBit/s  
                                 0 Pkts.

root@LEDE:~# iwinfo mesh5_0 assoclist
84:16:F9:B1:A0:3E -40 dBm / -103 dBm (SNR 63) -117860 ms ago

      RX: unknown                                     3022 Pkts.
      TX: 6.0 MBit/s                                     0 Pkts.

According to iw output this value is close to th “unsigned long” value limit
root@LEDE:~# iw mesh5_0 station dump
Station 18:a6:f7:3e:b4:de (on mesh5_0)

      inactive time:  4294805756 ms
      rx bytes:       152352
      rx packets:     2208
      tx bytes:       0
      tx packets:     0
      tx retries:     0
      tx failed:      0
      rx drop misc:   0
      signal:         -39 dBm
      signal avg:     -37 dBm
      tx bitrate:     6.0 MBit/s
      authorized:     yes
      authenticated:  yes
      associated:     yes
      preamble:       long
      WMM/WME:        yes
      MFP:            no
      TDLS peer:      no
      DTIM period:    0
      beacon interval:100
      short slot time:yes
      connected time: 113 seconds

root@LEDE:~# iw mesh5_0 station dump
Station 18:a6:f7:3e:b4:de (on mesh5_0)

      inactive time:  4294878176 ms
      rx bytes:       250056
      rx packets:     3624
      tx bytes:       0
      tx packets:     0
      tx retries:     0
      tx failed:      0
      rx drop misc:   0
      signal:         -40 dBm
      signal avg:     -39 dBm
      tx bitrate:     6.0 MBit/s
      authorized:     yes
      authenticated:  yes
      associated:     yes
      preamble:       long
      WMM/WME:        yes
      MFP:            no
      TDLS peer:      no
      DTIM period:    0
      beacon interval:100
      short slot time:yes
      connected time: 185 seconds

After some time (3-5 minutes) the value overflows and starting from zero with normal values.

root@LEDE:~# iwinfo mesh5_0 assoclist
84:16:F9:B1:A0:3E -38 dBm / -103 dBm (SNR 65) 80 ms ago

      RX: unknown                                     5732 Pkts.
      TX: 6.0 MBit/s                                     0 Pkts.

root@LEDE:~# iw mesh5_0 station dump
Station 18:a6:f7:3e:b4:de (on mesh5_0)

      inactive time:  50 ms
      rx bytes:       399372
      rx packets:     5788
      tx bytes:       0
      tx packets:     0
      tx retries:     0
      tx failed:      0
      rx drop misc:   0
      signal:         -41 dBm
      signal avg:     -39 dBm
      tx bitrate:     6.0 MBit/s
      authorized:     yes
      authenticated:  yes
      associated:     yes
      preamble:       long
      WMM/WME:        yes
      MFP:            no
      TDLS peer:      no
      DTIM period:    0
      beacon interval:100
      short slot time:yes
      connected time: 296 seconds
09.06.2017833Base systemBug ReportVery LowMediumpppoe memory problemlede-17.01Unconfirmed Task Description

I have observed a problem with pppoe connection. PPP runs well, but if the connection is interrupted by synchronization etc. then the free memory is less.

If I pull the plug and wait, then the system rapidly loses free memory and then crashes by approximately 25 MB of free RAM.

echo 3> /proc/sys/vm/drop_caches does not help in this case.

Tested on Linksys WRT1200AC, kernel 4.4.69 and 4.4.70
LEDE 17.01

Is there a way to investigate the problem more closely?

Many Thanks

Edy

14.06.2017845KernelBug ReportVery LowMediumMT7628 : wrong data reading the I2C busAllUnconfirmed Task Description

Hi,

I’ve already talked to blogic about this issue. He asked me to perform some tests on the platform even back to openwrt CC.

The bug in question occurs with the MT7628 chip and the I2C bus (WRTNode 2p board).
Configuring the pinmux and enabling the driver, the kernel correctly sees the i2c bus. But then going to use the “i2cdetect” command from i2c-tools package has a surprising result: devices are actually sees devices that are not connected.

Curious about the problem I connected my DSO and I did the probe of the SDA and SCL pins. Data and clock seem to be transferred correctly. So the problem seems to be in the “reading”.

According to the i2c specification if SDA is pull-low and you do an i2cdetect the system should identify in the bus an ACK for each slave address, this does does not happen and the same list appear again.

Turning back to different versions this still happens, unfortunately I have not been able to test every single commit.
The test I’ve made:

  • Openwrt CC the device was not supported.
  • Openwrt first commit of the device support: the i2c bus was not recognized by the driver.
  • Openwrt trunk, the i2c bus is not registered
  • LEDE 12.01 the problem as described above.
  • LEDE HEAD: the problem as described above.
  • LEDE HEAD 4.9 (kernel): The problem as described above.

i2cdetect result (same result with SDA pulled low) .config wrtnode2p.dts

Regards,
hitech95

18.06.2017855Base systemBug ReportVery LowMediumWrong MAC address (00:00:00:00:00:01) on Arcadyan AR751...lede-17.01Unconfirmed Task Description
root@LEDE:~# ifconfig | grep HW
br-lan    Link encap:Ethernet  HWaddr 00:00:00:00:00:01  
eth0      Link encap:Ethernet  HWaddr 00:00:00:00:00:01  
eth0.1    Link encap:Ethernet  HWaddr 00:00:00:00:00:01  
eth0.2    Link encap:Ethernet  HWaddr 00:00:00:00:00:01  
wlan0     Link encap:Ethernet  HWaddr 00:00:00:00:00:02

I know MAC addresses can be overriden in config, but is it possible to automatically detect the original addresses?

20.06.2017858Base systemBug ReportVery LowMediumInstalling bind / named will cause resolving names fail...TrunkUnconfirmed Task Description

Device TP-LINK MR-3220 v2.1 and 2.3 and 2.4 tested, LEDE 17.01.1 version.

After installing bind-server, setting “option port ‘0’” for dnsmasq (to disable DNS configuration) and using provided named.conf file (below), resolution of domain names to IP addresses breaks down.

I was able to track down the problem. There is race condition in bringing interfaces up, starting nptd service and named service, resulting in:
* named service beeing unable to open sockets and/or
* ntpd service beeing unable to connect to ntp pool and set router time correctly and/or
* incorrect time setting causes dnssec of named to reject proper answers for dns resolving.

With no named installed, the dnsmasq itself often starts too early, but this is masked by it beeing reinitialized on lan interface up event.

This is a known openwrt problem, the workaround is described here: https://dev.openwrt.org/ticket/19427 and involves creating a “netwait” service. I have tested this workaround and confirmed it works, however it is not nice.

Here my named.conf:

This is the primary configuration file for the BIND DNS server named. acl locals {
localhost;
10.10.10/24;
}; options {
directory “/tmp”; forwarders {
8.8.8.8;
8.8.4.4;
}; recursion yes;
allow-query { locals; }; dnssec-validation auto;
auth-nxdomain no; # conform to RFC1035
listen-on-v6 { none; };
listen-on { 127.0.0.1; 10.10.10.10; };
};
prime the server with knowledge of the root servers
zone “.” {

type hint;
file "/etc/bind/db.root";

};

be authoritative for the localhost forward and reverse zones, and for
broadcast zones as per RFC 1912

zone “localhost” {

type master;
file "/etc/bind/db.local";

};

zone “127.in-addr.arpa” {

type master;
file "/etc/bind/db.127";

};

zone “0.in-addr.arpa” {

type master;
file "/etc/bind/db.0";

};

zone “255.in-addr.arpa” {

type master;
file "/etc/bind/db.255";

};

 


22.06.2017863KernelBug ReportMediumMediumath9k failure with AP+11s VIFs ("unsupported hw bitrate...lede-17.01Assigned Task Description

A Gluon user reported the following issue, observed on a TL-WR841N v9 (QCA953x). LEDE version is 17.01.2.

Gluon uses AP+11s VIFs, with multicast_rate set to 12000.

The WLAN became unusable (no connection possible, WLAN LED permantently on) after a few hours of operation. Both VIFs were affected. The system recovered on its own after an hour in this state. Unfortunately, I have no information if beacons were still running in the broken state.

After the recovery, the large number of messages like the following were found in the kernel log:

[40085.953696] ath: phy0: unsupported hw bitrate detected 0x73 using 1 Mbit
[40200.844082] ath: phy0: unsupported hw bitrate detected 0x48 using 1 Mbit
[40281.298039] ------------[ cut here ]------------
[40281.303081] WARNING: CPU: 0 PID: 0 at compat-wireless-2017-01-31/net/mac80211/rx.c:4214 ieee80211_rx_napi+0x130/0x8b0 [mac80211]()
[40281.315230] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 100 (0x64)
[40281.325023] Modules linked in: iptable_nat ath9k nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 ipt_REJECT ipt_MASQUERADE ebtable_nat ebtable_filter ebtable_broute ath9k_common xt_time xt_tcpudp xt_state xt_quota xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_LOG xt_CT nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack mac80211 iptable_mangle iptable_filter ip_tables ebtables ebt_vlan ebt_stp ebt_snat ebt_redirect ebt_pkttype ebt_mark_m ebt_mark ebt_limit ebt_ip6 ebt_ip ebt_dnat ebt_arpreply ebt_arp ebt_among ebt_802_3 br_netfilter ath9k_hw ath em_nbyte em_cmp sch_pie em_meta sch_gred sch_teql act_ipt sch_prio em_text sch_codel sch_red sch_fq sch_sfq sch_dsmark act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_htb sch_hfsc batman_adv libcrc32c cfg80211 compat ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables dummy veth tun act_police cls_basic sch_tbf sch_ingress gpio_button_hotplug crc16 crc32c_generic crypto_hash
[40281.433128] CPU: 0 PID: 0 Comm: swapper Tainted: G        W       4.4.71 #0
[40281.440330] Stack : 803e32a4 00000000 00000001 80440000 8042d1dc 8042ce63 803c48ac 00000000
[40281.440330]    804a378c 00000004 00000000 8180e918 00000000 800a7664 803c9fa8 80430000
[40281.440330]    00000003 00000004 803c83b4 81809d5c 00000000 800a55e0 00000002 00000000
[40281.440330]    8042bf70 801f5300 00000000 00000000 00000000 00000000 00000000 00000000
[40281.440330]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[40281.440330]    ...
[40281.477351] Call Trace:
[40281.479951] [<800a7664>] vprintk_default+0x24/0x30
[40281.484917] [<800a55e0>] printk+0x2c/0x38
[40281.489077] [<801f5300>] serial8250_get_mctrl+0x30/0x54
[40281.494512] [<80081c60>] warn_slowpath_common+0xa0/0xd0
[40281.499949] [<801a772c>] dump_stack+0x14/0x28
[40281.504473] [<80071ea8>] show_stack+0x50/0x84
[40281.509003] [<80081c60>] warn_slowpath_common+0xa0/0xd0
[40281.514543] [<80e25cf0>] ieee80211_rx_napi+0x130/0x8b0 [mac80211]
[40281.520918] [<80081cbc>] warn_slowpath_fmt+0x2c/0x38
[40281.526158] [<80e25cf0>] ieee80211_rx_napi+0x130/0x8b0 [mac80211]
[40281.532495] [<802623ec>] __build_skb+0x48/0xc8
[40281.537148] [<802625d0>] __netdev_alloc_skb+0xd0/0x148
[40281.542477] [<80060bf4>] handle_int+0x134/0x140
[40281.547181] [<80de8388>] ath9k_cmn_rx_skb_postprocess+0x50/0x168 [ath9k_common]
[40281.554852] [<80e88374>] ath_rx_tasklet+0xee8/0xf4c [ath9k]
[40281.560635] [<8006503c>] __bzero+0xa0/0x164
[40281.565012] [<80e88340>] ath_rx_tasklet+0xeb4/0xf4c [ath9k]
[40281.570828] [<80e851b8>] ath9k_tasklet+0x200/0x28c [ath9k]
[40281.576512] [<80084820>] tasklet_action+0x80/0xc8
[40281.581390] [<800841dc>] __do_softirq+0x250/0x298
[40281.586284] [<800a82bc>] generic_handle_irq+0x24/0x3c
[40281.591540] [<8006a9e0>] plat_irq_dispatch+0xd4/0x10c
[40281.596760] [<80060bf4>] handle_int+0x134/0x140
[40281.601447]
[40281.602992] ---[ end trace f41ea26ed5101c02 ]---

Both the numbers in the “unsupported hw bitrate detected” messages and the status→rate_idx values in the WARNINGs are seemingly random.

28.06.2017873Base systemBug ReportVery LowMediumproblems of mt7628 wifi driver on miwifi nanoAllUnconfirmed Task Description

I started using lede on my miwifi nano since the release of version 17.01.1. All function works well except its wireless function.

What makes it a problem is its stability. After a random period of time(ranging from a quarter of an hour to half of a day), it suddenly disconnected. If you try to reconnect, my device shows something like “setting the network address”(varing from devices to devices). After reboot, I found something like “deauthenticated due to inactivity (timer DEAUTH/REMOVE)”. Unfortunately, I haven’t found a way to reproduce the problem till now.

I thought there might be bugs on its wireless driver because on another firmware(http://downloads.pandorabox.com.cn/pandorabox/Xiaomi-Mini-R1CL/firmware/PandoraBox-ralink-mt7628-xiaomi-r1cl-squashfs-sysupgrade-r1752-20151201.bin) which is a variant of Openwrt, it works well.

There are many other problems like the inability to set channel to auto and the txpower option is of no use. But for my daily use, they may not so important compared to the connectivity problem.

Sorry for my bad English and thank you for fixing it.

16.07.2017910KernelBug ReportVery LowMediumRaspberry Pi 3 keeps attempting to change CPU frequency...TrunkUnconfirmed Task Description

I recently updated a Raspberry Pi 3 to a recent LEDE git master build: Reboot (SNAPSHOT, r4576-9fe9175)

The kernel keeps logging the following errors:

[  103.041158] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:84: Failed to set clock: 600000 (-12)
[  103.044492] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:183: Error occurred setting a new frequency (600000)
[  103.047857] cpufreq: __target_index: Failed to change cpu frequency: -22
[  103.401167] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:84: Failed to set clock: 600000 (-12)
[  103.404517] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:183: Error occurred setting a new frequency (600000)
[  103.407890] cpufreq: __target_index: Failed to change cpu frequency: -22
[  103.761155] bcm2835-cpufreq:bcm2835_cpufreq_set_clock:84: Failed to set clock: 600000 (-12)
[  103.764491] bcm2835-cpufreq:bcm2835_cpufreq_driver_target_index:183: Error occurred setting a new frequency (600000)
[  103.767870] cpufreq: __target_index: Failed to change cpu frequency: -22

I am seeing ~10ms latency spikes for traffic through the device and I believe these errors are the reason. If I force the scheduler to only run the CPU at its maximum speed with the command below then then errors cease and the latency spikes disappear:

# echo 1200000 > /sys/devices/system/cpu/cpufreq/policy0/scaling_min_freq

I looked into the kernel sources and the messages above appear to be saying that there was an error when asking the Pi firmware to change the CPU speed.

I know there is a HW quirk in the RPi3 which means the UART is effected by the CPU speed. I wonder whether this has anything to do with the firmware rejecting the speed change:
https://github.com/RPi-Distro/repo/issues/22

11.08.2017954Base systemBug ReportVery LowMediumIGMP queries redirected to CPU port when snooping enabl...AllUnconfirmed Task Description

The Netgear R7800 has a QCA8337N switch chip, and the CPU has two interfaces (eth0/port 0 and eth1/port 6) connected to the switch. The default in LEDE is that WAN is on port0/eth0, and LAN is on port6/eth1.

When using multicast, it is often desirable to enable IGMP snooping on the switch to avoid flooding the multicast stream to all ports. A multicast server will normally send IGMP general queries to the all hosts address 224.0.0.1 at a regular interval (every few minutes) to check if there are still clients that wants to receive the multicast.

However, when IGMP snooping is enabled on this device, these queries are all redirected to port 0 on the switch, which is a problem if the multicast server is within the LAN. In this scenario, the server sends queries, but these queries are not being broadcast to the clients within the LAN, instead they end up at port 0 (eth0) where they are not needed. The server will then receive no responses to the queries, and subsequently times out and stops the stream multicast.

I think I found a viable fix for this, which is to set bit 3 (IGMP_COPY_EN) of the GLOBAL_FW_CTRL0 register in the switch chip to 1. This causes the IGMP queries to be broadcast on all switch ports (provided they are members of the same VLAN), instead of being redirected only to port 0. In my testing, I have found no adverse effects from this change.

I have attached a patch for this change, to make testing easy:

Assuming that the LAN interface is br-lan, run tcpdump on the router and inject IGMP general queries from a computer in the LAN, for example using Ostinato. With IGMP snooping off, the query is seen on br-lan:

root@R7800:/# tcpdump -i br-lan igmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br-lan, link-type EN10MB (Ethernet), capture size 262144 bytes
11:47:06.832511 IP 192.168.20.1 > all-systems.mcast.net: igmp query v2

If IGMP snooping is turned on (globally or for the port where the query is received), then the query no longer appears at br-lan,
but instead only on eth0. Applying the attached patch fixes this.

Showing tasks 201 - 250 of 906 Page 5 of 19<<First - 3 - 4 - 5 - 6 - 7 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing