From lede-bugs at lists.infradead.org  Thu Dec  1 00:07:32 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 01 Dec 2016 08:07:32 +0000
Subject: [FS#313] e2fsprogs fail to build
In-Reply-To: <FS313@bugs.lede-project.org>
References: <FS313@bugs.lede-project.org>
Message-ID: <mailman.71662.1480579804.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#313 - e2fsprogs fail to build
User who did this - Mathias Kresin (mkresin)

Reason for closing: Fixed
Additional comments about closing: https://git.lede-project.org/4596f9b5ac4278d544040b2b3fc9ec5fce3d2b10

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=313


From lede-bugs at lists.infradead.org  Thu Dec  1 08:23:10 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 01 Dec 2016 16:23:10 +0000
Subject: [FS#317] Archer C7 v2 -> net/core/dev.c:4839 net_rx_action+0x138/0x2c8
In-Reply-To: <FS317@bugs.lede-project.org>
References: <FS317@bugs.lede-project.org>
Message-ID: <mailman.71770.1480609415.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - JD (DoubleQ) 

Attached to Project - LEDE Project
Summary - Archer C7 v2 -> net/core/dev.c:4839 net_rx_action+0x138/0x2c8
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Supply the following if possible:
 - Device problem occurs on
dont no. It comes sometimes. Router looks stable
Got an archer c7 v2 (eraly version)

 - Software versions of LEDE release, packages, etc.
Linux Archer-Lede 4.4.35 #0 Wed Nov 30 09:13:14 2016 mips GNU/Linux

 - Steps to reproduce
Cant
   

 [Thu Dec  1 14:23:40 2016] ------------[ cut here ]------------
[Thu Dec  1 14:23:40 2016] WARNING: CPU: 0 PID: 3 at net/core/dev.c:4839 net_rx_action+0x138/0x2c8()
[Thu Dec  1 14:23:40 2016] Modules linked in: pppoe ppp_async iptable_nat ath9k pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 ipt_REJECT ipt_MASQUERADE ath9k_common xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_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 ath9k_hw ath10k_pci ath10k_core ath mac80211 cfg80211 compat ledtrig_usbport ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ehci_platform ehci_hcd gpio_button_hotplug usbcore nls_base usb_common
[Thu Dec  1 14:23:40 2016] CPU: 0 PID: 3 Comm: ksoftirqd/0 Not tainted 4.4.35 #0
[Thu Dec  1 14:23:40 2016] Stack : 803e2104 00000000 00000001 80440000 87c28c80 8042ce63 803c37bc 00000003
                                  804a379c 00000040 00000042 000000ec 00000001 800a72e0 803c8e20 80430000
                                  00000003 00000040 803c722c 87c41d3c 00000001 800a525c 00000000 00000000
                                  00000001 801f4b00 00000000 00000000 00000000 00000000 00000000 00000000
                                  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
                                  ...
[Thu Dec  1 14:23:40 2016] Call Trace:
[Thu Dec  1 14:23:40 2016] [] show_stack+0x50/0x84
[Thu Dec  1 14:23:40 2016] [] warn_slowpath_common+0xa0/0xd0
[Thu Dec  1 14:23:40 2016] [] warn_slowpath_null+0x18/0x24
[Thu Dec  1 14:23:40 2016] [] net_rx_action+0x138/0x2c8
[Thu Dec  1 14:23:40 2016] [] __do_softirq+0x250/0x298
[Thu Dec  1 14:23:40 2016] [] run_ksoftirqd+0x28/0x60
[Thu Dec  1 14:23:40 2016] [] smpboot_thread_fn+0x158/0x188
[Thu Dec  1 14:23:40 2016] [] kthread+0xd8/0xec
[Thu Dec  1 14:23:40 2016] [] ret_from_kernel_thread+0x14/0x1c

[Thu Dec  1 14:23:40 2016] ---[ end trace e1b8bd80f94f0edd ]---
root at Archer-Lede:~#
root at Archer-Lede:~# uptime
 17:22:03 up 1 day,  1:32,  load average: 0.00, 0.00, 0.00
root at Archer-Lede:~# date
Thu Dec  1 17:22:04 CET 2016
root at Archer-Lede:~#


More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=317


From lede-bugs at lists.infradead.org  Thu Dec  1 09:32:00 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 01 Dec 2016 17:32:00 +0000
Subject: [FS#34] WRT160NL wireless issues
In-Reply-To: <FS34@bugs.lede-project.org>
References: <FS34@bugs.lede-project.org>
Message-ID: <mailman.71785.1480613673.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#34 - WRT160NL wireless issues
User who did this - ask google (pereba)

----------
Is there any solution in the horizon for this bug? I need to restart wifi manually 20+ times everyday in my TL-WR1043ND. Seriously, it is almost unusable for now o.0
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=34#comment988


From lede-bugs at lists.infradead.org  Thu Dec  1 11:13:14 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 01 Dec 2016 19:13:14 +0000
Subject: [FS#244] Belkin F5D8235-4 v1 does not boot with LEDE
In-Reply-To: <FS244@bugs.lede-project.org>
References: <FS244@bugs.lede-project.org>
Message-ID: <mailman.71799.1480619619.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#244 - Belkin F5D8235-4 v1 does not boot with LEDE
User who did this - NotTheEvilOne (NotTheEvilOne)

----------
Just as an information: The root cause has been identified and a fix has been proposed on the [[https://patchwork.linux-mips.org/patch/14627/|linux-mips mailing list]] as well as [[https://github.com/lede-project/source/pull/580|LEDE]].

As soon as they hit lede/source the issue should be resolved. Please be aware that additional issues are addressed [[[https://github.com/lede-project/source/pull/577|1]]] [[[https://github.com/lede-project/source/pull/579|2]]].
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=244#comment989


From lede-bugs at lists.infradead.org  Thu Dec  1 19:34:51 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 02 Dec 2016 03:34:51 +0000
Subject: [FS#306] 2.4 GHz WiFi does not work on wndr3700v5
In-Reply-To: <FS306@bugs.lede-project.org>
References: <FS306@bugs.lede-project.org>
Message-ID: <mailman.71917.1480649843.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#306 - 2.4 GHz WiFi does not work on wndr3700v5
User who did this - L. D. Pinney (ldpinney)

----------
I am currently without this device and seeking someone to verify the proposed changes via the OpenWrt forum.
Anyone willing to test/verify can contact me : ldpinney at yahoo.com

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=306#comment990


From lede-bugs at lists.infradead.org  Fri Dec  2 00:45:13 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 02 Dec 2016 08:45:13 +0000
Subject: [FS#307] ZBT-WG3526 - mt7621 - SD card (MMC) support - [solved] but
 not already added to TRUNK ??
In-Reply-To: <FS307@bugs.lede-project.org>
References: <FS307@bugs.lede-project.org>
Message-ID: <mailman.71964.1480668340.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#307 - ZBT-WG3526 - mt7621 - SD card (MMC) support - [solved] but not already added to TRUNK ??
User who did this - john (john)

Reason for closing: Fixed
Additional comments about closing: fixed in latest HEAD

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=307


From lede-bugs at lists.infradead.org  Fri Dec  2 00:45:22 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 02 Dec 2016 08:45:22 +0000
Subject: [FS#237] ramips: kmod-sdhci-mt7620 causes kernel panic
In-Reply-To: <FS237@bugs.lede-project.org>
References: <FS237@bugs.lede-project.org>
Message-ID: <mailman.71965.1480668343.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#237 - ramips: kmod-sdhci-mt7620 causes kernel panic
User who did this - john (john)

Reason for closing: Fixed
Additional comments about closing: fixed in latest HEAD

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=237


From lede-bugs at lists.infradead.org  Fri Dec  2 02:00:23 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 02 Dec 2016 10:00:23 +0000
Subject: [FS#307] ZBT-WG3526 - mt7621 - SD card (MMC) support - [solved] but
 not already added to TRUNK ??
In-Reply-To: <FS307@bugs.lede-project.org>
References: <FS307@bugs.lede-project.org>
Message-ID: <mailman.71974.1480672974.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#307 - ZBT-WG3526 - mt7621 - SD card (MMC) support - [solved] but not already added to TRUNK ??
User who did this - camel (camel)

----------
? really ? merged into ?
which link refer to the fixes in git ?
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=307#comment991


From lede-bugs at lists.infradead.org  Fri Dec  2 02:18:19 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 02 Dec 2016 10:18:19 +0000
Subject: [FS#307] ZBT-WG3526 - mt7621 - SD card (MMC) support - [solved] but
 not already added to TRUNK ??
In-Reply-To: <FS307@bugs.lede-project.org>
References: <FS307@bugs.lede-project.org>
Message-ID: <mailman.71982.1480673924.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#307 - ZBT-WG3526 - mt7621 - SD card (MMC) support - [solved] but not already added to TRUNK ??
User who did this - Jo-Philipp Wich (jow-)

----------
https://git.lede-project.org/?p=source.git;a=commitdiff;h=7c809f168790efb8b52147df38bf4c6ae56bf36a
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=307#comment992


From lede-bugs at lists.infradead.org  Fri Dec  2 09:46:17 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 02 Dec 2016 17:46:17 +0000
Subject: [FS#307] ZBT-WG3526 - mt7621 - SD card (MMC) support - [solved] but
 not already added to TRUNK ??
In-Reply-To: <FS307@bugs.lede-project.org>
References: <FS307@bugs.lede-project.org>
Message-ID: <mailman.72076.1480700928.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#307 - ZBT-WG3526 - mt7621 - SD card (MMC) support - [solved] but not already added to TRUNK ??
User who did this - camel (camel)

----------
hmm, not sure, if i should create another bug report ... but something is strange, or maybe is there somewhere a "DEBUG mode" in source ?

as if I'M doing anything on SD card, then:
eg: if I'm creating partition (fdisk) or checking fsck(ext2,3,4,vfat)

logread ...
Fri Dec  2 18:41:49 2016 kern.err kernel: [ 1011.220000] msdc-1 -> TUNE_BWRITE DSPL DATWRDLY MSDC_DAT_RDDLY0  TUNE_BWRITE DSPL DATWRDLY MSDC_DAT_RDDLY0  TUNE_BWRITE DSPL DATWRDLY MSDC_DAT_RDDLY0  TUNE_BWRITE DSPL DATWRDLY MSDC_DAT_RDDLY0  TUNE_BWRITE DSPL DATWRDLY MSDC_DAT_RDDLY0  TUNE_BWRITE DSPL DATWRDLY MSDC_DAT_RDDLY0  TUNE_BWRITE DSPL DATWRDLY MSDC_DAT_RDDLY0  TUNE_BWRITE DSPL DATWRDLY MSDC_DAT_RDDLY0  TUNE_BWRITE DSPL DATWRDLY MSDC_DAT_RDDLY0  TUNE_BWRITE DSPL DATWRDLY MSDC_DAT_RDDLY0  TUNE_BWRITE DSPL DATWRDLY MSDC_DAT_RDDLY0  TUNE_BWRITE DSPL DATWRDLY MSDC_DAT_RDDLY0  TUNE_BWRITE DSPL DATWRDLY MSDC_DAT_RDDLY0 


From lede-bugs at lists.infradead.org  Fri Dec  2 10:26:42 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 02 Dec 2016 18:26:42 +0000
Subject: [FS#307] ZBT-WG3526 - mt7621 - SD card (MMC) support - [solved] but
 not already added to TRUNK ??
In-Reply-To: <FS307@bugs.lede-project.org>
References: <FS307@bugs.lede-project.org>
Message-ID: <mailman.72087.1480703225.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#307 - ZBT-WG3526 - mt7621 - SD card (MMC) support - [solved] but not already added to TRUNK ??
User who did this - camel (camel)

----------
i found some lines on another .. part ... not sure, if it is commented in code ?

drivers/mmc/host/sdhci-mt7620.c

?
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=307#comment994


From lede-bugs at lists.infradead.org  Fri Dec  2 10:59:03 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 02 Dec 2016 18:59:03 +0000
Subject: [FS#307] ZBT-WG3526 - mt7621 - SD card (MMC) support - [solved] but
 not already added to TRUNK ??
In-Reply-To: <FS307@bugs.lede-project.org>
References: <FS307@bugs.lede-project.org>
Message-ID: <mailman.72094.1480705180.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#307 - ZBT-WG3526 - mt7621 - SD card (MMC) support - [solved] but not already added to TRUNK ??
User who did this - camel (camel)

----------
not sure, if you have seen these patches and if they are also cross-checked ?

see: https://dev.openwrt.org/ticket/21834

the 2patches are:
https://dev.openwrt.org/attachment/ticket/21834/001-openwrt-ramips-mt7621-set-ralink-soc.patch

Ticket #21834: 001-openwrt-ramips-mt7621-set-ralink-soc.patch
File 001-openwrt-ramips-mt7621-set-ralink-soc.patch, 699 bytes (added by shmygov, 4 weeks ago)
TabularUnifiednew file target/linux/ramips/patches-4.4/0906-arch-mips-ralink-mt7621-set-ralink-soc.patch
diff --git a/target/linux/ramips/patches-4.4/0906-arch-mips-ralink-mt7621-set-ralink-soc.patch b/target/linux/ramips/patches-4.4/0906-arch-mips-ralink-mt7621-set-ralink-soc.patch
new file mode 100644
index 0000000..df17b10
-	+	 
 	1	--- a/arch/mips/ralink/mt7621.c 
 	2	+++ b/arch/mips/ralink/mt7621.c 
 	3	@@ -175,6 +175,7 @@ void prom_soc_init(struct ralink_soc_inf 
 	4	        n1 = __raw_readl(sysc + SYSC_REG_CHIP_NAME1); 
 	5	  
 	6	        if (n0 == MT7621_CHIP_NAME0 && n1 == MT7621_CHIP_NAME1) { 
 	7	+               ralink_soc = MT762X_SOC_MT7621AT; 
 	8	                name = "MT7621"; 
 	9	                soc_info->compatible = "mtk,mt7621-soc"; 
 	10	        } else { 

and also:

https://dev.openwrt.org/attachment/ticket/21834/002-openwrt-ramips-mt7621-fix-wg3526-sd-card.patch


Ticket #21834: 002-openwrt-ramips-mt7621-fix-wg3526-sd-card.patch
File 002-openwrt-ramips-mt7621-fix-wg3526-sd-card.patch, 1.0 KB (added by shmygov, 4 weeks ago)
TabularUnifiednew file target/linux/ramips/patches-4.4/0907-MIPS-ralink-mt7621-mtk-sd-fix-irq.patch
diff --git a/target/linux/ramips/patches-4.4/0907-MIPS-ralink-mt7621-mtk-sd-fix-irq.patch b/target/linux/ramips/patches-4.4/0907-MIPS-ralink-mt7621-mtk-sd-fix-irq.patch
new file mode 100644
index 0000000..e9a3cf4
-	+	 
 	1	--- a/drivers/mmc/host/mtk-mmc/sd.c 
 	2	+++ b/drivers/mmc/host/mtk-mmc/sd.c 
 	3	@@ -2843,7 +2843,14 @@ static int msdc_drv_probe(struct platfor 
 	4	     spin_lock_init(&host->lock); 
 	5	     msdc_init_hw(host); 
 	6	  
 	7	-    ret = request_irq((unsigned int)irq, msdc_irq, IRQF_TRIGGER_LOW, dev_name(&pdev->dev), host); 
 	8	+    if (ralink_soc == MT762X_SOC_MT7621AT) { 
 	9	+    //#if defined (CONFIG_RALINK_MT7621) 
 	10	+        ret = request_irq((unsigned int)irq, msdc_irq, 0, dev_name(&pdev->dev), host); 
 	11	+    } else { 
 	12	+    //#else 
 	13	+        ret = request_irq((unsigned int)irq, msdc_irq, IRQF_TRIGGER_LOW, dev_name(&pdev->dev), host); 
 	14	+    //#endif 
 	15	+    } 
 	16	     if (ret) goto release; 
 	17	     // mt65xx_irq_unmask(irq); /* --- by chhung */ 
 	18	      



----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=307#comment995


From lede-bugs at lists.infradead.org  Sat Dec  3 02:56:32 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 03 Dec 2016 10:56:32 +0000
Subject: [FS#318] Relayd based bridge bugs. bug in init.d file
In-Reply-To: <FS318@bugs.lede-project.org>
References: <FS318@bugs.lede-project.org>
Message-ID: <mailman.72146.1480762746.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Pedro (finas) 

Attached to Project - LEDE Project
Summary - Relayd based bridge bugs. bug in init.d file
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - I found a couple of bugs with relayd based bridge configuration and I would like to suggest a feature request. Will fill one entry per issue:

On today's trunk

1- parameter -t is not properly set.

 1179 root       984 S    /usr/sbin/relayd -I eth0 -I wlan0 -L 172.28.241.80 -G 172.28.241.1 60 -p 20 -B -D ( it should be -t 60 )

this is the offending line in init.d/relayd

        [ -n "$expiry" ] && procd_append_param command  "$expiry"   ( adding -t before "$expiry" solves the issue )

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=318


From lede-bugs at lists.infradead.org  Sat Dec  3 02:57:33 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 03 Dec 2016 10:57:33 +0000
Subject: [FS#319] Relayd based bridge bugs. bug in luci not reloading relayd
 on configuration changes
In-Reply-To: <FS319@bugs.lede-project.org>
References: <FS319@bugs.lede-project.org>
Message-ID: <mailman.72147.1480762804.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Pedro (finas) 

Attached to Project - LEDE Project
Summary - Relayd based bridge bugs. bug in luci not reloading relayd on configuration changes
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - I found a couple of bugs with relayd based bridge configuration and I would like to suggest a feature request. Will fill one entry per issue:

On today's trunk


2- in luci, any change to whatever parameter in the bridge, like host timeout, gateway, whatever, does not lead to the reload or restart of the relayd daemon


 

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=319


From lede-bugs at lists.infradead.org  Sat Dec  3 02:58:38 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 03 Dec 2016 10:58:38 +0000
Subject: [FS#320] relayd feature request
In-Reply-To: <FS320@bugs.lede-project.org>
References: <FS320@bugs.lede-project.org>
Message-ID: <mailman.72148.1480762869.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Pedro (finas) 

Attached to Project - LEDE Project
Summary - relayd feature request
Task Type - Feature Request
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - I found a couple of bugs with relayd based bridge configuration and I would like to suggest a feature request. Will fill one entry per issue:

On today's trunk


3- in a configuration where the network attached to the wireless radio is configured via DHCP, the listening interface is not set up automatically. DD-WRT and Gargoyle do this automatically ( they overwrite the config/network file with the gateway parameter and reload relayd.

   

 

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=320


From lede-bugs at lists.infradead.org  Sat Dec  3 03:13:26 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 03 Dec 2016 11:13:26 +0000
Subject: [FS#320] relayd feature request
In-Reply-To: <FS320@bugs.lede-project.org>
References: <FS320@bugs.lede-project.org>
Message-ID: <mailman.72149.1480763629.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#320 - relayd feature request
User who did this - Jo-Philipp Wich (jow-)

----------
Rewriting user configurations based on DHCP events is an absolute no-go, we need to find a better solution here.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=320#comment996


From lede-bugs at lists.infradead.org  Sat Dec  3 06:45:42 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 03 Dec 2016 14:45:42 +0000
Subject: [FS#283] NAT Loopback ("reflections") not working correctly.
In-Reply-To: <FS283@bugs.lede-project.org>
References: <FS283@bugs.lede-project.org>
Message-ID: <mailman.72174.1480776367.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#283 - NAT Loopback ("reflections") not working correctly.
User who did this - Ted Hess (thess)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=283


From lede-bugs at lists.infradead.org  Sat Dec  3 08:48:55 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 03 Dec 2016 16:48:55 +0000
Subject: [FS#120] opkg fails with Out of memory on a device with 32 MB of RAM
In-Reply-To: <FS120@bugs.lede-project.org>
References: <FS120@bugs.lede-project.org>
Message-ID: <mailman.72180.1480783762.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#120 - opkg fails with Out of memory on a device with 32 MB of RAM
User who did this - Alberto Bursi (bobafetthotmail)

----------
@Jo-Philipp Wich
@cypa

I think the only way to solve this is to simply don't keep local package lists on "low mem" devices. Each time opkg needs to look at package lists it downloads, reads and deletes each package list singularly.

It will have a pretty big latency (as commands like "opkg list" will have to download and parse all lists before giving an output), but would preserve functionality.

Since opkg is a package manager, I think list reading performance can be sacrificed here.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=120#comment997


From lede-bugs at lists.infradead.org  Sat Dec  3 09:48:43 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 03 Dec 2016 17:48:43 +0000
Subject: [FS#321] BTHomeHub5 Type A dsl_notify.sh fails to set LED
In-Reply-To: <FS321@bugs.lede-project.org>
References: <FS321@bugs.lede-project.org>
Message-ID: <mailman.72185.1480787475.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Mauro Mozzarelli (ezplanet) 

Attached to Project - LEDE Project
Summary - BTHomeHub5 Type A dsl_notify.sh fails to set LED
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Device: BTHomeHub5 Type A
Software Version: LEDE r2391 to latest (I have not tried LEDE releases prior to 2391).
Steps to reproduce: connect to ADSL line

Problem: the RED DSL LED should flash according to the status of the DSL line (HANDSHAKE, TRAINING, UP) as managed by /sbin/dsl_notify.sh however the LED remains off all the time.

It was working perfectly in OpenWrt. I switched only 2 days ago to LEDE and I found this issue.
I have seen some differences in /sbin/dsl_control.sh (I tried also to replace the LEDE version with the old OpenWrt code without success, possibly because of the dependencies on various "includes").

Setting the LED manually by poking directly into /sys/class/leds/bthomehubv5a:red:broadband it behaves correctly, thus hardware and kernel problems can be excluded.




 

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=321


From lede-bugs at lists.infradead.org  Sat Dec  3 22:55:53 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 06:55:53 +0000
Subject: [FS#321] BTHomeHub5 Type A dsl_notify.sh fails to set LED
In-Reply-To: <FS321@bugs.lede-project.org>
References: <FS321@bugs.lede-project.org>
Message-ID: <mailman.72194.1480834706.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#321 - BTHomeHub5 Type A dsl_notify.sh fails to set LED
User who did this - Mathias Kresin (mkresin)

----------
First of all, it isn't a bug it's intentionally.

And things a complicated with the HH5a. The hub has only three LEDs, but these LEDs are RGB LEDs, where each LED is controlled by three GPIOs. That is why you have red:broadband, green:broadband, blue:broadband.

The GPIO LED driver does not have support for RGB LEDs and you can not use these colours intendant. Means, if you enable red + blue, the LED will be purple. With red + blue + green the LED will be white. If you use some kind of blinking pattern you get nice colour effects. What is missing in the kernel driver is the possibility to define an LED with multiple GPIOs and the value of each GPIO.

I've implemented some kind of [[https://git.lede-project.org/?p=source.git;a=commitdiff;h=551c9c830027b7749895e3ba6b37004570b89e74;hp=32012decc327486bdf6564e6cf55a4acfc744efe|workaround for the power LED]] in failsafe, which disables the green power LED before enabling the red power LED.

I've decided back in the OpenWrt days(!), to show the Internet connection (ppp) status via the broadband LED. The broadband LED will shine blue if a ppp connection is established (link) and will blink blue on rx/tx.

But even having full support for RGB LEDs wouldn't allow to use a single LED for DSL and Internet connection status. It is not possible to use multiple trigger for a single LED.

Assuming we are using broadband:orange (red + green?) for the DSL line status (using red if everything is fine seams to me a bad idea). If the internet connection is terminated but the DSL line is still in sync, you would expect that the broadband LED switches back from blue to orange. But it isn't possible, since the link/rx/tx ppp trigger switches the LED off.

I'm not saying it isn't possible, but to my knowledge it requires a lot of hacks and workarounds to get such a config working. And at least to me it's questionable if the use case is worse adding these workarounds/hacks.

If you still interested in showing the DSL line status via the broadband LED, remove the "config led 'led_internet'" from your /etc/config/system and add the following instead:


config led 'led_dsl'
	option name 'dsl'
	option sysfs 'bthomehubv5a:red:broadband'
	option default '0'

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=321#comment998


From lede-bugs at lists.infradead.org  Sat Dec  3 22:55:59 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 06:55:59 +0000
Subject: [FS#321] BTHomeHub5 Type A dsl_notify.sh fails to set LED
In-Reply-To: <FS321@bugs.lede-project.org>
References: <FS321@bugs.lede-project.org>
Message-ID: <mailman.72195.1480834709.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#321 - BTHomeHub5 Type A dsl_notify.sh fails to set LED
User who did this - Mathias Kresin (mkresin)

Reason for closing: Not a bug
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=321


From lede-bugs at lists.infradead.org  Sat Dec  3 23:33:32 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 07:33:32 +0000
Subject: [FS#322] LAN doesn't get the ipv6 address when WAN6 uses DHCPv6
In-Reply-To: <FS322@bugs.lede-project.org>
References: <FS322@bugs.lede-project.org>
Message-ID: <mailman.72205.1480836835.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - hzdrro (hzdrro) 

Attached to Project - LEDE Project
Summary - LAN doesn't get the ipv6 address when WAN6 uses DHCPv6
Task Type - Bug Report
Category - Other
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - fireware version:LEDE Reboot CURRENT r2395

LAN doesn't get the ipv6 address when WAN6 uses DHCPv6, and openwrt cc works well.



One or more files have been attached.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=322


From lede-bugs at lists.infradead.org  Sun Dec  4 00:46:55 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 08:46:55 +0000
Subject: [FS#322] LAN doesn't get the ipv6 address when WAN6 uses DHCPv6
In-Reply-To: <FS322@bugs.lede-project.org>
References: <FS322@bugs.lede-project.org>
Message-ID: <mailman.72208.1480841240.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#322 - LAN doesn't get the ipv6 address when WAN6 uses DHCPv6
User who did this - Mathias Kresin (mkresin)

----------
You obviously misunderstood some ipv6 concepts.

With IPv6 you get an IPv6 address for your WAN interface. But your ISP (or whatever your upstream is) additionally have to provide an IPv6 prefix to you as well. This prefix will be used for the LAN interface and announce to the other clients in your LAN.

The problem you are seeing is that for some reason you don't get this IPv6 prefix. Most likely it's an configuration issue.

Please attach your LEDE /etc/config/network and the one from OpenWrt.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=322#comment999


From lede-bugs at lists.infradead.org  Sun Dec  4 00:48:45 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 08:48:45 +0000
Subject: [FS#322] LAN doesn't get the ipv6 address when WAN6 uses DHCPv6
In-Reply-To: <FS322@bugs.lede-project.org>
References: <FS322@bugs.lede-project.org>
Message-ID: <mailman.72209.1480841349.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#322 - LAN doesn't get the ipv6 address when WAN6 uses DHCPv6
User who did this: Mathias Kresin (mkresin)
Status: Unconfirmed -> Waiting on reporter

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=322


From lede-bugs at lists.infradead.org  Sun Dec  4 00:52:12 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 08:52:12 +0000
Subject: [FS#294] linksys 1200ac (and most likely other mvneta) has a
 multi-flow lockout problem
In-Reply-To: <FS294@bugs.lede-project.org>
References: <FS294@bugs.lede-project.org>
Message-ID: <mailman.72210.1480841552.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#294 - linksys 1200ac (and most likely other mvneta) has a multi-flow lockout problem
User who did this: Mathias Kresin (mkresin)
Status: Unconfirmed -> Waiting on reporter

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=294


From lede-bugs at lists.infradead.org  Sun Dec  4 00:52:08 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 08:52:08 +0000
Subject: [FS#294] linksys 1200ac (and most likely other mvneta) has a
 multi-flow lockout problem
In-Reply-To: <FS294@bugs.lede-project.org>
References: <FS294@bugs.lede-project.org>
Message-ID: <mailman.72211.1480841552.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#294 - linksys 1200ac (and most likely other mvneta) has a multi-flow lockout problem
User who did this - Mathias Kresin (mkresin)

----------
Dave, would you please test if the issue is fixed for you as well!
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=294#comment1000


From lede-bugs at lists.infradead.org  Sun Dec  4 01:00:12 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 09:00:12 +0000
Subject: [FS#311] ath10k thermal support
In-Reply-To: <FS311@bugs.lede-project.org>
References: <FS311@bugs.lede-project.org>
Message-ID: <mailman.72212.1480842037.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#311 - ath10k thermal support
User who did this - Mathias Kresin (mkresin)

----------
I will close this ticket as invalid. I mean, you are enabling something that possibly was disabled for a reason.

Please don't post bug reports if you have issues backporting stuff or enabling former disabled options as long as these option are not required to fix some other issues.

Please ask for help via mailing list or forum.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=311#comment1001


From lede-bugs at lists.infradead.org  Sun Dec  4 01:00:19 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 09:00:19 +0000
Subject: [FS#311] ath10k thermal support
In-Reply-To: <FS311@bugs.lede-project.org>
References: <FS311@bugs.lede-project.org>
Message-ID: <mailman.72213.1480842042.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#311 - ath10k thermal support
User who did this - Mathias Kresin (mkresin)

Reason for closing: Invalid report
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=311


From lede-bugs at lists.infradead.org  Sun Dec  4 01:02:03 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 09:02:03 +0000
Subject: [FS#317] Archer C7 v2 -> net/core/dev.c:4839 net_rx_action+0x138/0x2c8
In-Reply-To: <FS317@bugs.lede-project.org>
References: <FS317@bugs.lede-project.org>
Message-ID: <mailman.72214.1480842147.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#317 - Archer C7 v2 -> net/core/dev.c:4839 net_rx_action+0x138/0x2c8
User who did this: Mathias Kresin (mkresin)
Task details edited:
-------
Supply the following if possible:
 - Device problem occurs on
dont no. It comes sometimes. Router looks stable
Got an archer c7 v2 (eraly version)

 - Software versions of LEDE release, packages, etc.
Linux Archer-Lede 4.4.35 #0 Wed Nov 30 09:13:14 2016 mips GNU/Linux

 - Steps to reproduce
Cant


[Thu Dec  1 14:23:40 2016] ------------[ cut here ]------------
[Thu Dec  1 14:23:40 2016] WARNING: CPU: 0 PID: 3 at net/core/dev.c:4839 net_rx_action+0x138/0x2c8()
[Thu Dec  1 14:23:40 2016] Modules linked in: pppoe ppp_async iptable_nat ath9k pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 ipt_REJECT ipt_MASQUERADE ath9k_common xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_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 ath9k_hw ath10k_pci ath10k_core ath mac80211 cfg80211 compat ledtrig_usbport ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ehci_platform ehci_hcd gpio_button_hotplug usbcore nls_base usb_common
[Thu Dec  1 14:23:40 2016] CPU: 0 PID: 3 Comm: ksoftirqd/0 Not tainted 4.4.35 #0
[Thu Dec  1 14:23:40 2016] Stack : 803e2104 00000000 00000001 80440000 87c28c80 8042ce63 803c37bc 00000003
                                  804a379c 00000040 00000042 000000ec 00000001 800a72e0 803c8e20 80430000
                                  00000003 00000040 803c722c 87c41d3c 00000001 800a525c 00000000 00000000
                                  00000001 801f4b00 00000000 00000000 00000000 00000000 00000000 00000000
                                  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
                                  ...
[Thu Dec  1 14:23:40 2016] Call Trace:
[Thu Dec  1 14:23:40 2016] [] show_stack+0x50/0x84
[Thu Dec  1 14:23:40 2016] [] warn_slowpath_common+0xa0/0xd0
[Thu Dec  1 14:23:40 2016] [] warn_slowpath_null+0x18/0x24
[Thu Dec  1 14:23:40 2016] [] net_rx_action+0x138/0x2c8
[Thu Dec  1 14:23:40 2016] [] __do_softirq+0x250/0x298
[Thu Dec  1 14:23:40 2016] [] run_ksoftirqd+0x28/0x60
[Thu Dec  1 14:23:40 2016] [] smpboot_thread_fn+0x158/0x188
[Thu Dec  1 14:23:40 2016] [] kthread+0xd8/0xec
[Thu Dec  1 14:23:40 2016] [] ret_from_kernel_thread+0x14/0x1c

[Thu Dec  1 14:23:40 2016] ---[ end trace e1b8bd80f94f0edd ]---



root at Archer-Lede:~#
root at Archer-Lede:~# uptime
 17:22:03 up 1 day,  1:32,  load average: 0.00, 0.00, 0.00
root at Archer-Lede:~# date
Thu Dec  1 17:22:04 CET 2016
root at Archer-Lede:~#

-------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=317


From lede-bugs at lists.infradead.org  Sun Dec  4 01:04:19 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 09:04:19 +0000
Subject: [FS#280] iptables kerneltz an hour off from displayed time after DST
In-Reply-To: <FS280@bugs.lede-project.org>
References: <FS280@bugs.lede-project.org>
Message-ID: <mailman.72215.1480842288.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#280 - iptables kerneltz an hour off from displayed time after DST
User who did this: Mathias Kresin (mkresin)
Status: Unconfirmed -> Waiting on reporter

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=280


From lede-bugs at lists.infradead.org  Sun Dec  4 01:38:01 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 09:38:01 +0000
Subject: [FS#322] LAN doesn't get the ipv6 address when WAN6 uses DHCPv6
In-Reply-To: <FS322@bugs.lede-project.org>
References: <FS322@bugs.lede-project.org>
Message-ID: <mailman.72216.1480844306.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#322 - LAN doesn't get the ipv6 address when WAN6 uses DHCPv6
User who did this - hzdrro (hzdrro)

----------
I don't think I need to get a IPv6 prefix, my computer can get a IPv6 address by setting "Interfaces - LAN"-"DHCP Server"-"DHCP Server" to "relay mode" on OpenWrt CC.
----------

One or more files have been attached.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=322#comment1002


From lede-bugs at lists.infradead.org  Sun Dec  4 02:06:51 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 10:06:51 +0000
Subject: [FS#322] LAN doesn't get the ipv6 address when WAN6 uses DHCPv6
In-Reply-To: <FS322@bugs.lede-project.org>
References: <FS322@bugs.lede-project.org>
Message-ID: <mailman.72217.1480846036.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#322 - LAN doesn't get the ipv6 address when WAN6 uses DHCPv6
User who did this - Mathias Kresin (mkresin)

----------
> my computer can get a IPv6 address by setting "Interfaces - LAN"-"DHCP Server"-"DHCP Server" to "relay mode" on OpenWrt CC.

Yeah, my crystal ball failed to tell me what configuration you are using...
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=322#comment1003


From lede-bugs at lists.infradead.org  Sun Dec  4 02:44:31 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 10:44:31 +0000
Subject: [FS#103] mt7620a leaks traffic during bootloader step
In-Reply-To: <FS103@bugs.lede-project.org>
References: <FS103@bugs.lede-project.org>
Message-ID: <mailman.72232.1480848294.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#103 - mt7620a leaks traffic during bootloader step
User who did this - Felix Fietkau (nbd)

----------
Tested the fix myself and pushed it to master
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=103#comment1004


From lede-bugs at lists.infradead.org  Sun Dec  4 02:44:37 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 10:44:37 +0000
Subject: [FS#103] mt7620a leaks traffic during bootloader step
In-Reply-To: <FS103@bugs.lede-project.org>
References: <FS103@bugs.lede-project.org>
Message-ID: <mailman.72233.1480848299.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#103 - mt7620a leaks traffic during bootloader step
User who did this - Felix Fietkau (nbd)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=103


From lede-bugs at lists.infradead.org  Sun Dec  4 04:03:58 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 12:03:58 +0000
Subject: [FS#322] LAN doesn't get the ipv6 address when WAN6 uses DHCPv6
In-Reply-To: <FS322@bugs.lede-project.org>
References: <FS322@bugs.lede-project.org>
Message-ID: <mailman.72263.1480853066.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#322 - LAN doesn't get the ipv6 address when WAN6 uses DHCPv6
User who did this: Mathias Kresin (mkresin)
Status: Waiting on reporter -> Unconfirmed

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=322


From lede-bugs at lists.infradead.org  Sun Dec  4 04:05:21 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 12:05:21 +0000
Subject: [FS#244] Belkin F5D8235-4 v1 does not boot with LEDE
In-Reply-To: <FS244@bugs.lede-project.org>
References: <FS244@bugs.lede-project.org>
Message-ID: <mailman.72264.1480853145.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#244 - Belkin F5D8235-4 v1 does not boot with LEDE
User who did this - Mathias Kresin (mkresin)

Reason for closing: Fixed
Additional comments about closing: Fixed with with the recent commits to the LEDE repository. Thanks a lot NotTheEvilOne for providing the patches.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=244


From lede-bugs at lists.infradead.org  Sun Dec  4 06:33:19 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 04 Dec 2016 14:33:19 +0000
Subject: [FS#323] Add an option to include VERSION_CODE in binary filename
In-Reply-To: <FS323@bugs.lede-project.org>
References: <FS323@bugs.lede-project.org>
Message-ID: <mailman.72265.1480862152.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - juanriccio (juanriccio) 

Attached to Project - LEDE Project
Summary - Add an option to include VERSION_CODE in binary filename
Task Type - Feature Request
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Very Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - After [[https://git.lede-project.org/?p=source.git;a=commit;h=5f3c96c28503b8a0aad1514ef144b15e670d338b|Commit 5f3c96c28503b8a0aad1514ef144b15e670d338b (build: adjust version number handling)]], the binaries have no mention of the revision number (or revision code) in the filename, which makes it harder than necessary to keep track of things.

It would be nice to add a build option to include VERSION_CODE in the filename, rather than VERSION as it is now (VERSION simply defaults to "CURRENT").

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=323


From lede-bugs at lists.infradead.org  Mon Dec  5 05:49:52 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 05 Dec 2016 13:49:52 +0000
Subject: [FS#321] BTHomeHub5 Type A dsl_notify.sh fails to set LED
In-Reply-To: <FS321@bugs.lede-project.org>
References: <FS321@bugs.lede-project.org>
Message-ID: <mailman.72414.1480945819.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#321 - BTHomeHub5 Type A dsl_notify.sh fails to set LED
User who did this - Mauro Mozzarelli (ezplanet)

----------
It would be nice to have it back as it was with OpenWrt. It was just fine.
That is: ppp is down, "b" blue goes out and turns red thanks to my trigger:

/etc/hotplug.d/05-wan_led

#!/bin/sh
BROADBAND_RED="/sys/class/leds/bthomehubv5a:red:broadband/brightness"
POWER_RED="/sys/class/leds/bthomehubv5a:red:power/brightness"
if [ $INTERFACE == "wan" ]; then
	case "$ACTION" in
		ifup)
			echo 0 > $BROADBAND_RED
			;;
		ifdown)
			echo 255 > $BROADBAND_RED
			;;
	esac
fi

When DSL changes status it flashes accordingly.
Now instead it does nothing at all.

I would be nice, as I said, if you could put it back as it was. Or at least give an option to configure it as it was. Never mind the RGB LED. That is even better because I could mix the colours and have even more states reported as if it were more LEDs!

PLEASE CHANGE IT BACK.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=321#comment1005


From lede-bugs at lists.infradead.org  Mon Dec  5 06:27:42 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 05 Dec 2016 14:27:42 +0000
Subject: [FS#324] DDNS spawns processes continously - LUCI web DDNS page hangs
In-Reply-To: <FS324@bugs.lede-project.org>
References: <FS324@bugs.lede-project.org>
Message-ID: <mailman.72421.1480948086.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Mauro Mozzarelli (ezplanet) 

Attached to Project - LEDE Project
Summary - DDNS spawns processes continously - LUCI web DDNS page hangs
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Critical
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Supply the following if possible:
 - Device problem occurs on
 - Software versions of LEDE release, packages, etc.
 - Steps to reproduce
   
Device BTHomeHub5
Version: r2438
Configure DDNS with zzzz.io

LUCI web configure hangs
I had it previously configured. At boot it goes into loop and spanwns several ddns processes taking 100% resources.

It was fine in previous up to r2395 (which is the latest I tested before this one).

 2693 root      1188 S    -ash
 2905 root      1184 S    sh -c /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet.zzzz.io -- get_registered_ip
 2906 root      1356 S    {dynamic_dns_luc} /bin/sh /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet.zzzz.io -
 4298 root      1184 S    sh -c /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet.zzzz.io -- get_registered_ip
 4299 root      1356 S    {dynamic_dns_luc} /bin/sh /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet.zzzz.io -
 4478 root      1184 S    sh -c /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet.zzzz.io -- get_registered_ip
 4479 root      1356 S    {dynamic_dns_luc} /bin/sh /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet.zzzz.io -
 5461 root      1184 S    sh -c /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet.zzzz.io -- get_registered_ip
 5462 root      1356 S    {dynamic_dns_luc} /bin/sh /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet.zzzz.io -
13008 root      1184 S    sh -c /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet.zzzz.io -- get_registered_ip
13011 root      1356 S    {dynamic_dns_luc} /bin/sh /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet.zzzz.io -
18733 root      1184 S    sh -c /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet.zzzz.io -- get_registered_ip
18734 root      1356 S    {dynamic_dns_luc} /bin/sh /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet.zzzz.io -
23377 root      2988 S    {luci} /usr/bin/lua /www/cgi-bin/luci
24627 root      2816 S    {luci} /usr/bin/lua /www/cgi-bin/luci
25085 root      1184 S    sh -c /usr/lib/ddns/dynamic_dns_lucihelper.sh -V | awk {'print $2'}
25092 root      1236 S    {dynamic_dns_luc} /bin/sh /usr/lib/ddns/dynamic_dns_lucihelper.sh -V
25093 root      1188 S    awk {print $2}
25491 root      1184 S    sh -c /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet1.ddns.net -- get_registered_i
25493 root      1236 S    {dynamic_dns_luc} /bin/sh /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet1.ddns.net
25643 root      1184 R    ps
25704 root      1192 R    find /lib /usr/lib -name libcurl.so* -exec grep -i all_proxy {} ;
32188 root      1184 S    sh -c /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet.zzzz.io -- get_registered_ip
32193 root      1356 S    {dynamic_dns_luc} /bin/sh /usr/lib/ddns/dynamic_dns_lucihelper.sh -l ezplanet.zzzz.io -
32228 root      1128 S    /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 195.137.28.81:22 -p fdf6:5915:e8a5:

All of the above processes spawned in just a few seconds from boot!
At which point the router becomes unusable.


More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=324


From lede-bugs at lists.infradead.org  Mon Dec  5 06:50:01 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 05 Dec 2016 14:50:01 +0000
Subject: [FS#324] DDNS spawns processes continously - LUCI web DDNS page hangs
In-Reply-To: <FS324@bugs.lede-project.org>
References: <FS324@bugs.lede-project.org>
Message-ID: <mailman.72426.1480949425.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#324 - DDNS spawns processes continously - LUCI web DDNS page hangs
User who did this - Mathias Kresin (mkresin)

Reason for closing: Different project
Additional comments about closing: The dyndns scripts package is not part of the LEDE base system. It is maintained as part of the (external/additional) [[https://github.com/openwrt/packages/tree/master/net/ddns-scripts|packages feed]] which has its own bugtracker.

Would you please open a bug report at https://github.com/openwrt/packages/issues to make sure that the appropriate people get aware of the issue.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=324


From lede-bugs at lists.infradead.org  Mon Dec  5 10:12:29 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 05 Dec 2016 18:12:29 +0000
Subject: [FS#325] download statistics page is 404
In-Reply-To: <FS325@bugs.lede-project.org>
References: <FS325@bugs.lede-project.org>
Message-ID: <mailman.72457.1480961702.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Rich Brown (richb-hanover) 

Attached to Project - LEDE Project
Summary - download statistics page is 404
Task Type - Bug Report
Category - Website
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Critical
Priority - Very Low
Reported Version - All
Due in Version - Undecided
Due Date - Undecided
Details - Supply the following if possible:
 - Device problem occurs on
 - Software versions of LEDE release, packages, etc.
 - Steps to reproduce
   
http://downloads.lede-project.org/stats/ should display the awstats for the download site.

It returns 404 right now.
 

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=325


From lede-bugs at lists.infradead.org  Mon Dec  5 11:05:31 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 05 Dec 2016 19:05:31 +0000
Subject: [FS#325] download statistics page is 404
In-Reply-To: <FS325@bugs.lede-project.org>
References: <FS325@bugs.lede-project.org>
Message-ID: <mailman.72466.1480964754.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#325 - download statistics page is 404
User who did this - Ted Hess (thess)

----------
Works for me from down here in the BVI at the moment. The one which is problematic is the stats link from the forum to a non-forum page at the same site.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=325#comment1006


From lede-bugs at lists.infradead.org  Mon Dec  5 12:04:57 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 05 Dec 2016 20:04:57 +0000
Subject: [FS#325] download statistics page is 404
In-Reply-To: <FS325@bugs.lede-project.org>
References: <FS325@bugs.lede-project.org>
Message-ID: <mailman.72473.1480968320.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#325 - download statistics page is 404
User who did this - Rich Brown (richb-hanover)

----------
Curiouser and curiouser... It still fails for me. 

What's odder is that http://downloads.lede-project.org/stats/ winds up on "https://...same URL..."

The initial http request gets a 307 Internal Redirect to https, which then returns 404
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=325#comment1007


From lede-bugs at lists.infradead.org  Mon Dec  5 12:14:05 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 05 Dec 2016 20:14:05 +0000
Subject: [FS#325] download statistics page is 404
In-Reply-To: <FS325@bugs.lede-project.org>
References: <FS325@bugs.lede-project.org>
Message-ID: <mailman.72474.1480968870.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#325 - download statistics page is 404
User who did this - john (john)

----------
this is Firefox opportunistic encryption kicking in ... http://stackoverflow.com/questions/30532471/firefox-redirects-to-https/34033592#34033592
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=325#comment1008


From lede-bugs at lists.infradead.org  Mon Dec  5 12:35:44 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 05 Dec 2016 20:35:44 +0000
Subject: [FS#325] download statistics page is 404
In-Reply-To: <FS325@bugs.lede-project.org>
References: <FS325@bugs.lede-project.org>
Message-ID: <mailman.72475.1480970168.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#325 - download statistics page is 404
User who did this - Rich Brown (richb-hanover)

----------
Yes, but I'm using Chrome.

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=325#comment1009


From lede-bugs at lists.infradead.org  Mon Dec  5 14:09:58 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 05 Dec 2016 22:09:58 +0000
Subject: [FS#325] download statistics page is 404
In-Reply-To: <FS325@bugs.lede-project.org>
References: <FS325@bugs.lede-project.org>
Message-ID: <mailman.72478.1480975823.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#325 - download statistics page is 404
User who did this - Hannu Nyman (hnyman)

----------
Jow mentioned to me in email conversation that it happens also with Chrome.

I complained about the same issue (with buildbot and Firefox) in https://forum.lede-project.org/t/s-wiki-site-in-lede-wiki/392/17?u=hnyman

The "use only https for all lede-project.org services" started to happen since the www and wiki were combined. I guess that in that move also the HSTS setting enforcing https got somehow assigned to the whole domain :-( 

 > Strict-Transport-Securitymax-age=31536000; includeSubDomains

one reason may be that the www server also answers for domain-style https://lede-project.org address in addition of https://www.lede-project.org

The "only https" gets enforced once you visit https://lede-project.org 

The only cures I have found are in that stackoverflow discussion.

I hope that devs either 
* disable the enforcement of https via HSTS, 
* mitigate the problem by e.g. shortening the HSTS timeout significantly (from he current 31536000 seconds to a few minutes), or 
* install https for the web stats and buildbot web interfaces.

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=325#comment1010


From lede-bugs at lists.infradead.org  Mon Dec  5 18:28:24 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 06 Dec 2016 02:28:24 +0000
Subject: [FS#95] system looses IPv6 prefix after valid_lft reaches 0
In-Reply-To: <FS95@bugs.lede-project.org>
References: <FS95@bugs.lede-project.org>
Message-ID: <mailman.72533.1480991467.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#95 - system looses IPv6 prefix after valid_lft reaches 0
User who did this - satlan (satlan)

----------
I can confirm it's happening on my current LEDE build (WNDR3700). I can't pinpoint exactly when it started however.

And the above workaround worked. I've made it permanent for now.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=95#comment1011


From lede-bugs at lists.infradead.org  Tue Dec  6 04:28:50 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 06 Dec 2016 12:28:50 +0000
Subject: [FS#325] download statistics page is 404
In-Reply-To: <FS325@bugs.lede-project.org>
References: <FS325@bugs.lede-project.org>
Message-ID: <mailman.72632.1481027486.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#325 - download statistics page is 404
User who did this - Jo-Philipp Wich (jow-)

----------
Made the /stats location available via HTTPS as well. It should have been like this in the first place.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=325#comment1012


From lede-bugs at lists.infradead.org  Tue Dec  6 04:28:57 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 06 Dec 2016 12:28:57 +0000
Subject: [FS#325] download statistics page is 404
In-Reply-To: <FS325@bugs.lede-project.org>
References: <FS325@bugs.lede-project.org>
Message-ID: <mailman.72633.1481027489.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#325 - download statistics page is 404
User who did this - Jo-Philipp Wich (jow-)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=325


From lede-bugs at lists.infradead.org  Tue Dec  6 04:44:54 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 06 Dec 2016 12:44:54 +0000
Subject: [FS#326] Do not name MD5 SHA256. Its not MD5 when its SHA256
In-Reply-To: <FS326@bugs.lede-project.org>
References: <FS326@bugs.lede-project.org>
Message-ID: <mailman.72657.1481028385.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - hngsvtdu at sharklasers.com (hngsvtdu) 

Attached to Project - LEDE Project
Summary - Do not name MD5 SHA256. Its not MD5 when its SHA256
Task Type - Feature Request
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - This change and some changes before make use of some strange behavior. 

https://git.lede-project.org/?p=source.git;a=commit;h=a2457722918f602c4d9573c3d617ecc6af616bec

This change is named "tools/upslug2: add SHA256 hash to use mirror tarball."

But adds a line like this:
PKG_MIRROR_MD5SUM:=5c69eae3a2affef8f4f7194cfedfdb9175b04ca433f9ae046c85309b42bdb21e

This is not a "MD5SUM".

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=326


From lede-bugs at lists.infradead.org  Tue Dec  6 05:02:11 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 06 Dec 2016 13:02:11 +0000
Subject: [FS#325] download statistics page is 404
In-Reply-To: <FS325@bugs.lede-project.org>
References: <FS325@bugs.lede-project.org>
Message-ID: <mailman.72664.1481029373.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#325 - download statistics page is 404
User who did this - Rich Brown (richb-hanover)

----------
Thanks jow - I confirm it's fixed.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=325#comment1013


From lede-bugs at lists.infradead.org  Tue Dec  6 07:05:09 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 06 Dec 2016 15:05:09 +0000
Subject: [FS#326] Do not name MD5 SHA256. Its not MD5 when its SHA256
In-Reply-To: <FS326@bugs.lede-project.org>
References: <FS326@bugs.lede-project.org>
Message-ID: <mailman.72687.1481036736.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#326 - Do not name MD5 SHA256. Its not MD5 when its SHA256
User who did this - Jo-Philipp Wich (jow-)

----------
Yes, that field accepts SHA256SUMS as well.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=326#comment1014


From lede-bugs at lists.infradead.org  Tue Dec  6 07:05:19 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 06 Dec 2016 15:05:19 +0000
Subject: [FS#326] Do not name MD5 SHA256. Its not MD5 when its SHA256
In-Reply-To: <FS326@bugs.lede-project.org>
References: <FS326@bugs.lede-project.org>
Message-ID: <mailman.72688.1481036739.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#326 - Do not name MD5 SHA256. Its not MD5 when its SHA256
User who did this - Jo-Philipp Wich (jow-)

Reason for closing: Not a bug
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=326


From lede-bugs at lists.infradead.org  Tue Dec  6 09:54:30 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 06 Dec 2016 17:54:30 +0000
Subject: [FS#34] WRT160NL wireless issues
In-Reply-To: <FS34@bugs.lede-project.org>
References: <FS34@bugs.lede-project.org>
Message-ID: <mailman.72731.1481046899.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#34 - WRT160NL wireless issues
User who did this - ask google (pereba)

----------
Was checking this old link: https://dev.openwrt.org/ticket/10031

"Reconfiguration of the wireless interface (802.11bgn -> 802.11bg, setting another transmit power, etc.)"

Just changed here to Wireless G, fixed my issue apparently. Good workaround until a proper fix is done. Better than nothing!
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=34#comment1015


From lede-bugs at lists.infradead.org  Tue Dec  6 12:33:32 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 06 Dec 2016 20:33:32 +0000
Subject: [FS#309] Can't assign static IPv6 leases anymore
In-Reply-To: <FS309@bugs.lede-project.org>
References: <FS309@bugs.lede-project.org>
Message-ID: <mailman.72760.1481056436.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#309 - Can't assign static IPv6 leases anymore
User who did this - Hans Dedecker (dedeckeh)

----------
Bug is fixed meanwhile in commit https://git.lede-project.org/?p=project/odhcpd.git;a=commit;h=be6c5159a46bf2fb813456e53f217a415743ed4c
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=309#comment1016


From lede-bugs at lists.infradead.org  Tue Dec  6 13:37:43 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 06 Dec 2016 21:37:43 +0000
Subject: [FS#257] Xiaomi MiWiFi Mini - unstable 2.4G
In-Reply-To: <FS257@bugs.lede-project.org>
References: <FS257@bugs.lede-project.org>
Message-ID: <mailman.72767.1481060287.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#257 - Xiaomi MiWiFi Mini - unstable 2.4G
User who did this - Eelco Bosman (EBosman)

----------
I can confirm as well on a ZBT AE657
Trunk 2016-12-06 lede-ramips-mt7620-miwifi-mini-squashfs-sysupgrade.bin

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=257#comment1017


From lede-bugs at lists.infradead.org  Tue Dec  6 17:35:12 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 07 Dec 2016 01:35:12 +0000
Subject: [FS#251] sending SIGSEGV to dnsmasq for invalid read access from
 00000000
In-Reply-To: <FS251@bugs.lede-project.org>
References: <FS251@bugs.lede-project.org>
Message-ID: <mailman.72791.1481074930.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#251 - sending SIGSEGV to dnsmasq for invalid read access from 00000000
User who did this - fuzzle (fuzzle)

----------
i build several lede in the last days - and at least on tplink 841 i never see this. (with some days uptime)
just something on gluon like this
Sat Dec  3 14:46:38 2016 daemon.crit dnsmasq[2095]: unknown user or group: dnsmasq
Sat Dec  3 14:46:38 2016 daemon.crit dnsmasq[2095]: FAILED to start up

..
some dnsmasq is still running 
 1016 root      1116 S    /usr/sbin/dnsmasq -x /var/run/gluon-wan-dnsmasq.pid -u root -i lo -p 54 -h -r /var/gluon/wan-dnsmasq/resolv.conf

..
logread
Sat Dec  3 14:46:34 2016 daemon.crit dnsmasq[1985]: unknown user or group: dnsmasq
Sat Dec  3 14:46:34 2016 daemon.crit dnsmasq[1985]: FAILED to start up
Sat Dec  3 14:46:35 2016 user.notice firewall: Reloading firewall due to ifup of wan6 (br-wan)
Sat Dec  3 14:46:35 2016 daemon.warn fastd[1472]: sendmsg: Operation not permitted
Sat Dec  3 14:46:35 2016 daemon.warn fastd[1472]: sendmsg: Operation not permitted
Sat Dec  3 14:46:37 2016 daemon.info dnsmasq[1016]: reading /var/gluon/wan-dnsmasq/resolv.conf
Sat Dec  3 14:46:37 2016 daemon.info dnsmasq[1016]: using nameserver fd00::a96:d7ff:fe5d:1026#53
Sat Dec  3 14:46:37 2016 daemon.info dnsmasq[1016]: using nameserver 192.168.0.1#53
Sat Dec  3 14:46:37 2016 daemon.crit dnsmasq[2040]: unknown user or group: dnsmasq
Sat Dec  3 14:46:37 2016 daemon.crit dnsmasq[2040]: FAILED to start up
Sat Dec  3 14:46:38 2016 daemon.crit dnsmasq[2095]: unknown user or group: dnsmasq
Sat Dec  3 14:46:38 2016 daemon.crit dnsmasq[2095]: FAILED to start up
Sat Dec  3 14:46:38 2016 daemon.info procd: Instance dnsmasq::cfg02411c s in a crash loop 6 crashes, 0 seconds since last crash

this particular node:
Linux version 4.4.32 (fffr at v32412.1blu.de) (gcc version 5.4.0 (LEDE GCC 5.4.0 r2187+6) ) #0 Tue Sep 27 01:55:55 2016
based on https://kau.toke.dk/git/lede/commit/?id=18726b0ed2be546d1d2503c903d7d069ae5522d5
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=251#comment1018


From lede-bugs at lists.infradead.org  Tue Dec  6 17:57:11 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 07 Dec 2016 01:57:11 +0000
Subject: [FS#251] sending SIGSEGV to dnsmasq for invalid read access from
 00000000
In-Reply-To: <FS251@bugs.lede-project.org>
References: <FS251@bugs.lede-project.org>
Message-ID: <mailman.72794.1481075858.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#251 - sending SIGSEGV to dnsmasq for invalid read access from 00000000
User who did this - Matthias Schiffer (NeoRaider)

----------
fuzzle, that's not even close to the issues reported in this ticket. As mentioned in earlier comments, this ticket doesn't have to do anything with dnsmasq, but is about a segfault in busybox.

Also, please don't report Gluon bugs in the LEDE tracker.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=251#comment1019


From lede-bugs at lists.infradead.org  Tue Dec  6 18:01:24 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 07 Dec 2016 02:01:24 +0000
Subject: [FS#251] sending SIGSEGV to dnsmasq for invalid read access from
 00000000
In-Reply-To: <FS251@bugs.lede-project.org>
References: <FS251@bugs.lede-project.org>
Message-ID: <mailman.72795.1481076115.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#251 - sending SIGSEGV to dnsmasq for invalid read access from 00000000
User who did this - Matthias Schiffer (NeoRaider)

----------
Small update:

While I mostly see this issue on a TL-WR1043 v1, I've also observed it on a TL-WR841 v9 at least once; so it seems the bug is not hardware-specific after all (at least not limited to specific SoCs).

Unfortunately, I've been busy with other things last week, so I haven't been able to continue debugging the issue.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=251#comment1020


From lede-bugs at lists.infradead.org  Wed Dec  7 02:06:23 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 07 Dec 2016 10:06:23 +0000
Subject: [FS#34] WRT160NL wireless issues
In-Reply-To: <FS34@bugs.lede-project.org>
References: <FS34@bugs.lede-project.org>
Message-ID: <mailman.72836.1481105337.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#34 - WRT160NL wireless issues
User who did this - ask google (pereba)

----------
nvm sorry for msg above, next day I woke up and my wifi already was "down". :\
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=34#comment1021


From lede-bugs at lists.infradead.org  Thu Dec  8 07:14:09 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 08 Dec 2016 15:14:09 +0000
Subject: [FS#317] Archer C7 v2 -> net/core/dev.c:4839 net_rx_action+0x138/0x2c8
In-Reply-To: <FS317@bugs.lede-project.org>
References: <FS317@bugs.lede-project.org>
Message-ID: <mailman.73094.1481210202.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#317 - Archer C7 v2 -> net/core/dev.c:4839 net_rx_action+0x138/0x2c8
User who did this - JD (DoubleQ)

----------
Looks like its gone with the latest version....

Linux version 4.4.36 (buildbot at builds) (gcc version 5.4.0 (LEDE GCC 5.4.0 r2400-abedd71) ) #0 Mon Dec 5 10:37:54 2016
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=317#comment1022


From lede-bugs at lists.infradead.org  Thu Dec  8 12:24:29 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 08 Dec 2016 20:24:29 +0000
Subject: [FS#309] Can't assign static IPv6 leases anymore
In-Reply-To: <FS309@bugs.lede-project.org>
References: <FS309@bugs.lede-project.org>
Message-ID: <mailman.73145.1481228693.1639.lede-bugs@lists.infradead.org>

Hans Dedecker has taken ownership of the following task:

FS#309 - Can't assign static IPv6 leases anymore

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=309


From lede-bugs at lists.infradead.org  Thu Dec  8 12:26:03 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 08 Dec 2016 20:26:03 +0000
Subject: [FS#309] Can't assign static IPv6 leases anymore
In-Reply-To: <FS309@bugs.lede-project.org>
References: <FS309@bugs.lede-project.org>
Message-ID: <mailman.73146.1481228786.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#309 - Can't assign static IPv6 leases anymore
User who did this: Hans Dedecker (dedeckeh)
Percent Complete: 0% -> 100%

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=309


From lede-bugs at lists.infradead.org  Thu Dec  8 12:27:22 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 08 Dec 2016 20:27:22 +0000
Subject: [FS#309] Can't assign static IPv6 leases anymore
In-Reply-To: <FS309@bugs.lede-project.org>
References: <FS309@bugs.lede-project.org>
Message-ID: <mailman.73147.1481228864.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#309 - Can't assign static IPv6 leases anymore
User who did this - Hans Dedecker (dedeckeh)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=309


From lede-bugs at lists.infradead.org  Thu Dec  8 15:43:55 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 08 Dec 2016 23:43:55 +0000
Subject: [FS#327] https://forum.lede-project.org/ reports a certificate error
In-Reply-To: <FS327@bugs.lede-project.org>
References: <FS327@bugs.lede-project.org>
Message-ID: <mailman.73167.1481240787.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Stan (stangri) 

Attached to Project - LEDE Project
Summary - https://forum.lede-project.org/ reports a certificate error
Task Type - Bug Report
Category - Forum site
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Critical
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - https://forum.lede-project.org/ reports a certificate error and chrome refuses to proceed because of hsts.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=327


From lede-bugs at lists.infradead.org  Thu Dec  8 17:39:13 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 09 Dec 2016 01:39:13 +0000
Subject: [FS#327] https://forum.lede-project.org/ reports a certificate error
In-Reply-To: <FS327@bugs.lede-project.org>
References: <FS327@bugs.lede-project.org>
Message-ID: <mailman.73180.1481247579.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#327 - https://forum.lede-project.org/ reports a certificate error
User who did this - Jo-Philipp Wich (jow-)

----------
The certificate is fixed now.

Background info: we're running acme.sh to manage the Let's Encrypt certificates but a hook was missing to reload nginx in order to pick up the updated certificates which caused this expiry problem.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=327#comment1023


From lede-bugs at lists.infradead.org  Thu Dec  8 17:39:21 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 09 Dec 2016 01:39:21 +0000
Subject: [FS#327] https://forum.lede-project.org/ reports a certificate error
In-Reply-To: <FS327@bugs.lede-project.org>
References: <FS327@bugs.lede-project.org>
Message-ID: <mailman.73181.1481247582.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#327 - https://forum.lede-project.org/ reports a certificate error
User who did this - Jo-Philipp Wich (jow-)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=327


From lede-bugs at lists.infradead.org  Thu Dec  8 22:36:37 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 09 Dec 2016 06:36:37 +0000
Subject: [FS#328] Add in "region fix" for TP-Link routers (esp. Archer C7) to
 fix 18005 error
In-Reply-To: <FS328@bugs.lede-project.org>
References: <FS328@bugs.lede-project.org>
Message-ID: <mailman.73186.1481265549.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Rich Brown (richb-hanover) 

Attached to Project - LEDE Project
Summary - Add in "region fix" for TP-Link routers (esp. Archer C7) to fix 18005 error
Task Type - Feature Request
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Supply the following if possible:
 - Device problem occurs on
 - Software versions of LEDE release, packages, etc.
 - Steps to reproduce
   

 TP-Link, in its infinite wisdom, decided to put a kludge into their factory firmware update facility that "prevents" people from loading in third-party firmware. 

Well, shortly after they added this (mis)feature, a workaround was discovered and installed in OpenWrt DD trunk. Unfortunately, the discovery happened after LEDE forked from OpenWrt, so the fix is not in LEDE. (At least, a version tested from late November 2016 was not able to be imported over factory firmware. For more info, see: https://forum.openwrt.org/viewtopic.php?id=63107

My request: back port the fix from OpenWrt DD into LEDE. There's a bunch of info on the TP-Link Archer C7 device page at OpenWrt that may be helpful: https://wiki.openwrt.org/toh/tp-link/archer-c5-c7-wdr7500#quick_start_guide

Thanks.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=328


From lede-bugs at lists.infradead.org  Fri Dec  9 00:45:29 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 09 Dec 2016 08:45:29 +0000
Subject: [FS#328] Add in "region fix" for TP-Link routers (esp. Archer C7) to
 fix 18005 error
In-Reply-To: <FS328@bugs.lede-project.org>
References: <FS328@bugs.lede-project.org>
Message-ID: <mailman.73201.1481273153.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#328 - Add in "region fix" for TP-Link routers (esp. Archer C7) to fix 18005 error
User who did this - Matthias Schiffer (NeoRaider)

----------
We've had US and EU factory images for the Archer C7 v2 since https://git.lede-project.org/?p=source.git;a=commit;h=fa0096f6cc236e1346a344d3edf467945aa4a27e ; the forum thread you linked has no additional information on this (but it talks about DDwrt, not OpenWrt DD, maybe you mixed these up?; OpenWrt DD doesn't seem to have a fix as of now). I don't know what fix DDwrt applied, but I expect it is simlar to ours.

Note that LEDE will now generate 3 factory images for the Archer C7 v2: a "universal" one that can be flashed over non-region-coded stock firmwares, and two region-coded images (-factory-eu.bin, -factory-us.bin) for flashing over the regional stock firmwares.

Similar fixes will be applied to other devices as soon as we find out about TP-Link adding region codes to them.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=328#comment1024


From lede-bugs at lists.infradead.org  Fri Dec  9 00:45:44 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 09 Dec 2016 08:45:44 +0000
Subject: [FS#328] Add in "region fix" for TP-Link routers (esp. Archer C7) to
 fix 18005 error
In-Reply-To: <FS328@bugs.lede-project.org>
References: <FS328@bugs.lede-project.org>
Message-ID: <mailman.73202.1481273167.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#328 - Add in "region fix" for TP-Link routers (esp. Archer C7) to fix 18005 error
User who did this - Matthias Schiffer (NeoRaider)

Reason for closing: Works for me
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=328


From lede-bugs at lists.infradead.org  Fri Dec  9 05:39:34 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 09 Dec 2016 13:39:34 +0000
Subject: [FS#328] Add in "region fix" for TP-Link routers (esp. Archer C7) to
 fix 18005 error
In-Reply-To: <FS328@bugs.lede-project.org>
References: <FS328@bugs.lede-project.org>
Message-ID: <mailman.73247.1481290927.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#328 - Add in "region fix" for TP-Link routers (esp. Archer C7) to fix 18005 error
User who did this - Rich Brown (richb-hanover)

----------
Thanks, Matthias. I agree this can be closed. A couple other points:

1) I was attempting to flash Toke's factory image that has the "Make Wi-Fi Fast" fixes from: https://kau.toke.dk/lede/airtime-fairness-builds/ar71xx/generic/ I missed the US build, which I now see is there. That's my fault.

2) I believe that recent OpenWrt DD builds *do* have the fix. I was able to flash openwrt-ar71xx-generic-archer-c7-v2-squashfs-factory.bin from 18 Nov 2016 onto the stock factory firmware to get OpenWrt installed...

3) For people from the future, look for the US or EU factory images...

Thanks agin.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=328#comment1025


From lede-bugs at lists.infradead.org  Fri Dec  9 06:52:45 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 09 Dec 2016 14:52:45 +0000
Subject: [FS#320] relayd feature request
In-Reply-To: <FS320@bugs.lede-project.org>
References: <FS320@bugs.lede-project.org>
Message-ID: <mailman.73267.1481295189.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#320 - relayd feature request
User who did this - Pedro (finas)

----------
makes sense.
Do you have any idea on how this can be processed? maybe relayd must be extended to support this?

relayd was made by nbd, right?
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=320#comment1026


From lede-bugs at lists.infradead.org  Fri Dec  9 06:58:12 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 09 Dec 2016 14:58:12 +0000
Subject: [FS#320] relayd feature request
In-Reply-To: <FS320@bugs.lede-project.org>
References: <FS320@bugs.lede-project.org>
Message-ID: <mailman.73268.1481295515.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#320 - relayd feature request
User who did this - Jo-Philipp Wich (jow-)

----------
Yes, the easiest would be to extend relayd or to extend the init script of relayd to fetch the gateway info from ubus. Then we could install hotplug events to reload relayd on dhcp changes.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=320#comment1027


From lede-bugs at lists.infradead.org  Fri Dec  9 07:54:53 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 09 Dec 2016 15:54:53 +0000
Subject: [FS#307] ZBT-WG3526 - mt7621 - SD card (MMC) support - [solved] but
 not already added to TRUNK ??
In-Reply-To: <FS307@bugs.lede-project.org>
References: <FS307@bugs.lede-project.org>
Message-ID: <mailman.73273.1481298926.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#307 - ZBT-WG3526 - mt7621 - SD card (MMC) support - [solved] but not already added to TRUNK ??
User who did this - camel (camel)

----------
pls reopen, as it is not working with your patch.
pls can you compare what you missed from the working patch which i mentioned ?
is there a difference which would be important not to miss ?
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=307#comment1028


From lede-bugs at lists.infradead.org  Fri Dec  9 08:35:41 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 09 Dec 2016 16:35:41 +0000
Subject: [FS#323] Add an option to include VERSION_CODE in binary filename
In-Reply-To: <FS323@bugs.lede-project.org>
References: <FS323@bugs.lede-project.org>
Message-ID: <mailman.73277.1481301377.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#323 - Add an option to include VERSION_CODE in binary filename
User who did this - Jo-Philipp Wich (jow-)

----------
Build option added with http://git.lede-project.org/9791fb2
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=323#comment1029


From lede-bugs at lists.infradead.org  Fri Dec  9 08:36:14 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 09 Dec 2016 16:36:14 +0000
Subject: [FS#323] Add an option to include VERSION_CODE in binary filename
In-Reply-To: <FS323@bugs.lede-project.org>
References: <FS323@bugs.lede-project.org>
Message-ID: <mailman.73280.1481301397.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#323 - Add an option to include VERSION_CODE in binary filename
User who did this - Jo-Philipp Wich (jow-)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=323


From lede-bugs at lists.infradead.org  Fri Dec  9 10:23:36 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 09 Dec 2016 18:23:36 +0000
Subject: [FS#329] AR9341 needs analog switch reset
In-Reply-To: <FS329@bugs.lede-project.org>
References: <FS329@bugs.lede-project.org>
Message-ID: <mailman.73295.1481307840.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - vuhuy (vuhuy) 

Attached to Project - LEDE Project
Summary - AR9341 needs analog switch reset
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - This is a bug report for the AR9341 SOC on LEDE trunk reboot-2445-gee5a6c1.

I have builded a custom firmware for a unsupported device based on the Atheros DB120 reference board.

The analog port of the ethernet switch needs to be resetted before it can operate.

Part of bootlog without analog reset:

[    2.179262] ag71xx-mdio.1: unknown phy id 'ffff:ffff'


Br-lan is not intialized due no analog switch reset.

Part of bootlog with analog reset:

[    2.059037] ag71xx-mdio.1: Found an AR934X built-in switch


And br-lan is initialized and networking is working fine.

A reset is performed by the function ath79_register_eth (defined in dev-eth.c):

ath79_device_reset_set(AR934X_RESET_ETH_SWITCH);
ath79_device_reset_clear(AR934X_RESET_ETH_SWITCH);


However, no analog reset is performed, for example:

ath79_device_reset_set(AR934X_RESET_ETH_SWITCH);
ath79_device_reset_clear(AR934X_RESET_ETH_SWITCH);

ath79_device_reset_set(AR934X_RESET_ETH_SWITCH_ANALOG);
ath79_device_reset_clear(AR934X_RESET_ETH_SWITCH_ANALOG);


Omitting the analog reset does not break the DB120 builds because the analog reset is already performed by ar934x_nfc_hw_reset in dev-nfc.c.

An easy fix is to do a analog reset in the device's mach file. However, for the sake of consistency and autism, the reset should be performed by ath79_register_eth in dev_eth.c and not by ar934x_nfc_hw_reset in dev_nfc.c. My AR9341 device doesn't even use a NAND flash.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=329


From lede-bugs at lists.infradead.org  Fri Dec  9 10:34:49 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 09 Dec 2016 18:34:49 +0000
Subject: [FS#329] AR9341 needs analog switch reset
In-Reply-To: <FS329@bugs.lede-project.org>
References: <FS329@bugs.lede-project.org>
Message-ID: <mailman.73296.1481308515.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#329 - AR9341 needs analog switch reset
User who did this - vuhuy (vuhuy)

----------
Some additions:

On my device (Sitecom WLR2100 v2), a analog switch reset is automatically performed by the bootloader (U-BOOT) when loading the firmware via TFTP to the SDRAM, or booting via boot command line. However, standard booting does not perform a analog switch reset.

In other words, in order to replicate this problem you will need to flash the firmware on the device. Loading it with TFTP will just work fine without problems.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=329#comment1030


From lede-bugs at lists.infradead.org  Sat Dec 10 06:06:44 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 10 Dec 2016 14:06:44 +0000
Subject: [FS#330] From Lede 2443 ownwards on WND3700v4 causes panic on BT Home
 Hub 5 on boot
In-Reply-To: <FS330@bugs.lede-project.org>
References: <FS330@bugs.lede-project.org>
Message-ID: <mailman.73356.1481378958.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Mauro Mozzarelli (ezplanet) 

Attached to Project - LEDE Project
Summary - From Lede 2443 ownwards on WND3700v4 causes panic on BT Home Hub 5 on boot
Task Type - Bug Report
Category - Kernel
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Critical
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Supply the following if possible:
 - Device problem occurs on Bt Home Hub 5 Type A (caused by WNDR3700v4)
 - Software versions of LEDE release from 2395 on BT Home Hub 5, from 2443 on WNDR3700v4
 - Steps to reproduce
   
Bt Home Hub 5 is connected to the internet via ADSL and acquires a subnet.
The 4 ports Switch is on the fixed public IP Internet subnet, 1 port connected to WNDR3700v4 WAN port and the others to servers on fixed public IP subnet.
The red Ethernet is not connected.
Masquerading is not configured, used as proper router.
WiFi Disabled

WNDR3700v4 WAN port connected to BT Home Hub 5 Switch and assigned 1 IP in the public subnet
WNDR3700v4 4 port switch connected to local switch and other devices on local private lan.
Configured for Masquerading from LAN and WiFi to WAN.

Bt Home Hub 5 panics at boot only if:
1) the 4 port switch is connected to the WNDR3700v4 WAN port
2) WNDR3700v4 runs LEDE > r2393. I have no releases between r2393 and r2443, thus it begins to happen if I upgrade WNDR3700v4 to 2443.

It is really peculiar because a firmware upgrade on one router, WNDR3700v4, causes a panic on a Home Hub 5 type!

If I downgrade WNDR3700v4 to r2393, I can reboot the Home Hub as many times as I want and there is no panic.

Attached is the boot console log from Home Hub 5


 

One or more files have been attached.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=330


From lede-bugs at lists.infradead.org  Sat Dec 10 10:19:44 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 10 Dec 2016 18:19:44 +0000
Subject: [FS#317] Archer C7 v2 -> net/core/dev.c:4839 net_rx_action+0x138/0x2c8
In-Reply-To: <FS317@bugs.lede-project.org>
References: <FS317@bugs.lede-project.org>
Message-ID: <mailman.73366.1481394009.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#317 - Archer C7 v2 -> net/core/dev.c:4839 net_rx_action+0x138/0x2c8
User who did this - JD (DoubleQ)

----------
STOP....

dont close. It starts again.....

[Sat Dec 10 12:29:09 2016] ------------[ cut here ]------------
[Sat Dec 10 12:29:09 2016] WARNING: CPU: 0 PID: 3 at net/core/dev.c:4839 net_rx_action+0x138/0x2c8()
[Sat Dec 10 12:29:09 2016] Modules linked in: pppoe ppp_async iptable_nat ath9k pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 ipt_REJECT ipt_MASQUERADE ath9k_common xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_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 ath9k_hw ath10k_pci ath10k_core ath mac80211 cfg80211 compat ledtrig_usbport ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ehci_platform ehci_hcd gpio_button_hotplug usbcore nls_base usb_common
[Sat Dec 10 12:29:09 2016] CPU: 0 PID: 3 Comm: ksoftirqd/0 Not tainted 4.4.36 #0
[Sat Dec 10 12:29:09 2016] Stack : 803e2104 00000000 00000001 80440000 87c28c80 8042ce63 803c37bc 00000003
                                  804a379c 00000040 00000041 0000012c 00000001 800a72e0 803c8e20 80430000
                                  00000003 00000040 803c722c 87c41d3c 00000001 800a525c 00000000 00000000
                                  00000001 801f4b00 00000000 00000000 00000000 00000000 00000000 00000000
                                  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
                                  ...
[Sat Dec 10 12:29:09 2016] Call Trace:
[Sat Dec 10 12:29:09 2016] [] vprintk_default+0x24/0x30

[Sat Dec 10 12:29:09 2016] ---[ end trace 2f7d4b5c2c4ef660 ]---
root at Archer-Lede:~# uptime
 19:18:12 up 14:17,  load average: 0.00, 0.00, 0.00
root at Archer-Lede:~#


----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=317#comment1031


From lede-bugs at lists.infradead.org  Sat Dec 10 10:43:24 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 10 Dec 2016 18:43:24 +0000
Subject: [FS#330] From Lede 2443 ownwards on WND3700v4 causes panic on BT Home
 Hub 5 on boot
In-Reply-To: <FS330@bugs.lede-project.org>
References: <FS330@bugs.lede-project.org>
Message-ID: <mailman.73367.1481395428.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#330 - From Lede 2443 ownwards on WND3700v4 causes panic on BT Home Hub 5 on boot
User who did this - Mauro Mozzarelli (ezplanet)

----------
I have now recovered r2395 and flashed WNDR3700v4. Rebooted BT Home Hub 5 (with r2446) no panic. So up to r2395 on WNDR3700v4 Bt Home Hub 5 connected to WAN is OK. 
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=330#comment1032


From lede-bugs at lists.infradead.org  Sat Dec 10 12:31:09 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 10 Dec 2016 20:31:09 +0000
Subject: [FS#330] From Lede 2443 ownwards on WND3700v4 causes panic on BT Home
 Hub 5 on boot
In-Reply-To: <FS330@bugs.lede-project.org>
References: <FS330@bugs.lede-project.org>
Message-ID: <mailman.73368.1481402025.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#330 - From Lede 2443 ownwards on WND3700v4 causes panic on BT Home Hub 5 on boot
User who did this - Mauro Mozzarelli (ezplanet)

----------
I upgraded both BT Home Hub 5 and WNDR3700v4 to r2449, just pulled from GIT and built.
No more panics on boot for BT Home Hub 5!

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=330#comment1033


From lede-bugs at lists.infradead.org  Sun Dec 11 10:22:41 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 11 Dec 2016 18:22:41 +0000
Subject: [FS#177] ipq806x: USB3 ports fail if booted when USB3 flash drives
 inserted during boot time
In-Reply-To: <FS177@bugs.lede-project.org>
References: <FS177@bugs.lede-project.org>
Message-ID: <mailman.73410.1481480721.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#177 - ipq806x: USB3 ports fail if booted when USB3 flash drives inserted during boot time
User who did this - Zoltan Karpati (nwperfguy)

----------
Hi

Same problem on TP-Link Archer C2600. Extroot works with USB 2.0 only.
USB 3.0 pendrives have the same issue as above. LEDE version id: r2437+12-7c47f43


[   15.804603] xhci-hcd xhci-hcd.0.auto: xHCI host not responding to stop endpoint command.
[   15.804654] xhci-hcd xhci-hcd.0.auto: Assuming host is dying, halting host.
[   15.840270] xhci-hcd xhci-hcd.0.auto: Host not halted after 16000 microseconds.
[   15.840314] xhci-hcd xhci-hcd.0.auto: Non-responsive xHCI host is not halting.
[   15.846396] xhci-hcd xhci-hcd.0.auto: Completing active URBs anyway.
[   15.853751] xhci-hcd xhci-hcd.0.auto: HC died; cleaning up


Regards,

Zoltan


----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=177#comment1034


From lede-bugs at lists.infradead.org  Mon Dec 12 00:20:20 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 12 Dec 2016 08:20:20 +0000
Subject: [FS#331] mac80211 / warning / ieee80211_ibss_leave / r2449
In-Reply-To: <FS331@bugs.lede-project.org>
References: <FS331@bugs.lede-project.org>
Message-ID: <mailman.73441.1481530973.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Bastian Bittorf (bittorf) 

Attached to Project - LEDE Project
Summary - mac80211 / warning / ieee80211_ibss_leave / r2449
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - spotted on TP-Link 4900 v1 with LEDE r2449 (selfcompiled):


[ 2860.974569] ------------[ cut here ]------------
[ 2860.979191] WARNING: at compat-wireless-2016-10-08/net/mac80211/ibss.c:1082
[ 2860.986142] Modules linked in: ath9k ath9k_common iptable_nat ath9k_hw ath snd_usb_audio nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_id xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda snd_usbmidi_lib 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 macvlan iptable_raw iptable_mangle iptable_filter ipt_ECN ip_tables compat em_nbyte sch_dsmark sch_pie sch_codel sch_gred sch_htb em_cmp cls_basic act_ipt sch_red sch_prio em_meta act_police em_text sch_tbf sch_sfq sch_fq act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ipip tunnel4 ip_tunnel tun snd_compress snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_rawmidi snd_seq_device snd_hwdep snd soundcore nls_utf8 zram lz4_decompress lz4_compress lzo_compress lzo_decompress zsmalloc usb_storage gpio_keys leds_gpio ehci_fsl ehci_platform ehci_hcd scsi_mod fsl_mph_dr_of mbcache button_hotplug input_core usbcore nls_base usb_common crc16 crc32c_generic crypto_hash [last unloaded: sd_mod]
[ 2861.124825] CPU: 0 PID: 8624 Comm: kworker/u2:0 Not tainted 4.4.36 #0
[ 2861.131337] Workqueue: phy1 ieee80211_ibss_leave [mac80211]
[ 2861.136903] task: c783b840 ti: c68a4000 task.ti: c68a4000
[ 2861.142292] NIP: c99ab128 LR: c99ab354 CTR: 00000000
[ 2861.147247] REGS: c68a5b10 TRAP: 0700   Not tainted  (4.4.36)
[ 2861.152982] MSR: 00029000   CR: 28072422  XER: 20000000
[ 2861.159082]
[ 2861.159082] GPR00: c99ab004 c68a5bc0 c783b840 00000000 c68a5bf4 00000000 00000001 00000000
[ 2861.159082] GPR08: c724b114 00000001 c99f97f6 00000000 000000ff 00000000 c003c474 c790bfe0
[ 2861.159082] GPR16: c6f0f070 00000fff 00000fff c70b2138 c6ae5800 c6e30b40 00000000 00000087
[ 2861.159082] GPR24: 00000000 c68a5c68 c724b114 00000000 c6e30b40 c6e7a3d8 c6f25420 c6f0f070
[ 2861.188805] NIP [c99ab128] ieee80211_get_vht_mask_from_cap+0x1964/0x1c64 [mac80211]
[ 2861.196468] LR [c99ab354] ieee80211_get_vht_mask_from_cap+0x1b90/0x1c64 [mac80211]
[ 2861.204025] Call Trace:
[ 2861.206481] [c68a5bc0] [c99ab004] ieee80211_get_vht_mask_from_cap+0x1840/0x1c64 [mac80211] (unreliable)
[ 2861.215884] [c68a5c60] [c99ab414] ieee80211_get_vht_mask_from_cap+0x1c50/0x1c64 [mac80211]
[ 2861.224156] [c68a5d30] [c99ab9d0] ieee80211_ibss_rx_queued_mgmt+0x264/0x370 [mac80211]
[ 2861.232081] [c68a5e20] [c99acc44] ieee80211_ibss_leave+0x768/0x1770 [mac80211]
[ 2861.239307] [c68a5e80] [c00379f8] process_one_work+0x208/0x380
[ 2861.245135] [c68a5ea0] [c0037de0] worker_thread+0x270/0x48c
[ 2861.250704] [c68a5ef0] [c003c53c] kthread+0xc8/0xcc
[ 2861.255580] [c68a5f40] [c000cb3c] ret_from_kernel_thread+0x5c/0x64
[ 2861.261752] --- interrupt: 0 at   (null)
[ 2861.261752]     LR =   (null)
[ 2861.268618] Instruction dump:
[ 2861.271578] 38810034 387e0510 7f984800 419e024c 4bf410ed 2f830000 40be0030 3d40c9a0
[ 2861.279336] 394a97f6 3b600001 892a0003 69290001  2f890000 41be01d0 39200001
[ 2861.287267] ---[ end trace a37b58c3292c2cbf ]---



More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=331


From lede-bugs at lists.infradead.org  Mon Dec 12 02:59:55 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 12 Dec 2016 10:59:55 +0000
Subject: [FS#332] uci config enumeration flaw
In-Reply-To: <FS332@bugs.lede-project.org>
References: <FS332@bugs.lede-project.org>
Message-ID: <mailman.73523.1481540419.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - bolvan (bolvan) 

Attached to Project - LEDE Project
Summary - uci config enumeration flaw
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Original visible issue is seeing always "Changes: 0" in LUCI UI.
?https://github.com/openwrt/luci/issues/856#issuecomment-266218003

I traced the reason to libuci.so.
(file.c) uci_list_config_files enumerates all files in /etc/config including directories
if directory is found then get_filename returns null
configs[i] remains unset and in most cases contain NULL
all parts of code that use config enumeration stop on first NULL
If a directory exist in /etc/config then all fails

	char **configs = NULL;
	char **p;
	if ((uci_list_configs(ctx, &configs) != UCI_OK) || !configs) {
		cli_perror();
		goto out;
	}

	for (p = configs; *p; p++) {
		package_cmd(cmd, *p);
	}




This patch to file.c fixes the problem

838c838
<       int size, i;
---
>       int size, i, j;
862c862
<       for(i = 0; i < globbuf.gl_pathc; i++) {
---
>       for(i = 0, j = 0; i < globbuf.gl_pathc; i++) {
872c872
<               configs[i] = buf;
---
>               configs[j++] = buf;


More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=332


From lede-bugs at lists.infradead.org  Mon Dec 12 03:11:10 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 12 Dec 2016 11:11:10 +0000
Subject: [FS#332] uci config enumeration flaw
In-Reply-To: <FS332@bugs.lede-project.org>
References: <FS332@bugs.lede-project.org>
Message-ID: <mailman.73528.1481541093.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#332 - uci config enumeration flaw
User who did this - Jo-Philipp Wich (jow-)

----------
This has been recently patched upstream in uci.git, see http://git.lede-project.org/49ec6ef .
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=332#comment1035


From lede-bugs at lists.infradead.org  Mon Dec 12 03:11:18 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 12 Dec 2016 11:11:18 +0000
Subject: [FS#332] uci config enumeration flaw
In-Reply-To: <FS332@bugs.lede-project.org>
References: <FS332@bugs.lede-project.org>
Message-ID: <mailman.73529.1481541098.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#332 - uci config enumeration flaw
User who did this - Jo-Philipp Wich (jow-)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=332


From lede-bugs at lists.infradead.org  Mon Dec 12 04:23:13 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 12 Dec 2016 12:23:13 +0000
Subject: [FS#333] ath10k_pci: crash after ~10d uptime
In-Reply-To: <FS333@bugs.lede-project.org>
References: <FS333@bugs.lede-project.org>
Message-ID: <mailman.73534.1481545418.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Stijn Tintel (stintel) 

Attached to Project - LEDE Project
Summary - ath10k_pci: crash after ~10d uptime
Task Type - Bug Report
Category - Base system
Status - New
Assigned To - 
Operating System - All
Severity - Low
Priority - Medium
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - After ~10 days of uptime, ath10k crashed and I could no longer associate.

Device: D-Link DAP-2695 rev A1
Running: LEDE r2370

Wireless config:


config wifi-device  radio0
        option type     mac80211
        option channel  100
        option country  BE
        option txpower  20
        option hwmode   11a
        option path     'pci0000:00/0000:00:00.0'
        option htmode   VHT80
        option disabled 0

config wifi-iface
        option device 'radio0'
        option ifname 'wlan0'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '1'
        option network 'lan'
        option mode 'ap'
        option ssid 'xxxxxxxx'
        option key 'XXXXXXXX'

config wifi-iface
        option device 'radio0'
        option ifname 'wlan2'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '0'
        option network 'guest'
        option mode 'ap'
        option ssid 'Guests'
        option key 'YYYYYYYY'
        #option disassoc_low_ack '0'

config wifi-device  radio1
        option type     mac80211
        option channel  1
        option country  BE
        option txpower  20
        option hwmode   11g
        option path     'platform/qca955x_wmac'
        option htmode   HT40
        #option noscan   1

config wifi-iface
        option device 'radio1'
        option ifname 'wlan1'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '1'
        option mode 'ap'
        option network 'lan'
        option ssid 'xxxxxxxx'
        option key 'XXXXXXXX'

config wifi-iface
        option device 'radio1'
        option ifname 'wlan3'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '0'
        option network 'guest'
        option mode 'ap'
        option ssid 'Guests'
        option key 'YYYYYYYY'
        #option disassoc_low_ack '0'


Kernel log:

[920549.560152] ath10k_pci 0000:00:00.0: failed to delete peer c0:ee:fb:4a:18:b7 for vdev 0: -145
[920549.568951] ath10k_pci 0000:00:00.0: found sta peer c0:ee:fb:4a:18:b7 (ptr 8d43f600 id 95) entry on vdev 0 after it was supposedly removed
[920549.581722] ------------[ cut here ]------------
[920549.586618] WARNING: CPU: 0 PID: 1431 at compat-wireless-2016-10-08/net/mac80211/sta_info.c:964 sta_set_sinfo+0x92c/0x9e0 [mac80211]()
[920549.598968] Modules linked in: ath9k ath9k_common crc_ccitt ath9k_hw act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress ath10k_pci ath10k_core ath mac80211 cfg80211 compat gpio_button_hotplug
[920549.620582] CPU: 0 PID: 1431 Comm: hostapd Not tainted 4.4.35 #0
[920549.626772] Stack : 803c2d64 00000000 00000001 80420000 8fe26580 8040acc3 803a4424 00000597
[920549.626772]           8047379c 8ff8d000 00000000 77415e94 00000000 800a7198 803a9a90 80400000
[920549.626772]           00000003 8ff8d000 803a7e9c 8e5f3b2c 00000000 800a5114 80400000 00000000
[920549.626772]           00000001 801f3100 00000000 00000000 00000000 00000000 00000000 00000000
[920549.626772]           00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[920549.626772]           ...
[920549.663219] Call Trace:
[920549.665810] [] show_stack+0x50/0x84
[920549.670323] [] warn_slowpath_common+0xa0/0xd0
[920549.675724] [] warn_slowpath_null+0x18/0x24
[920549.680994] [] sta_set_sinfo+0x92c/0x9e0 [mac80211]
[920549.686990] [] __sta_info_destroy+0x30/0x48 [mac80211]
[920549.693222] [] sta_info_destroy_addr_bss+0x38/0x60 [mac80211]
[920549.700118] [] cfg80211_check_station_change+0xed8/0x1390 [cfg80211]
[920549.707564] 
[920549.709166] ---[ end trace e15a227055dd36c2 ]---
[920866.693883] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer b0:df:3a:12:79:80: -145
[920866.703088] wlan0: failed to remove key (0, b0:df:3a:12:79:80) from hardware (-145)
[920866.719519] ath10k_pci 0000:00:00.0: cipher 0 is not supported
[920866.725602] ath10k_pci 0000:00:00.0: failed to remove peer wep key 0: -122
[920866.732670] ath10k_pci 0000:00:00.0: failed to clear all peer wep keys for vdev 0: -122
[920866.740901] ath10k_pci 0000:00:00.0: failed to disassociate station: b0:df:3a:12:79:80 vdev 0: -122
[920866.750169] ------------[ cut here ]------------
[920866.755066] WARNING: CPU: 0 PID: 1431 at compat-wireless-2016-10-08/net/mac80211/sta_info.c:956 sta_set_sinfo+0x8d8/0x9e0 [mac80211]()
[920866.767421] Modules linked in: ath9k ath9k_common crc_ccitt ath9k_hw act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress ath10k_pci ath10k_core ath mac80211 cfg80211 compat gpio_button_hotplug
[920866.789044] CPU: 0 PID: 1431 Comm: hostapd Tainted: G        W       4.4.35 #0
[920866.796465] Stack : 803c2d64 00000000 00000001 80420000 8fe26580 8040acc3 803a4424 00000597
[920866.796465]           8047379c 8ff8d000 00000000 77415e94 00000000 800a7198 803a9a90 80400000
[920866.796465]           00000003 8ff8d000 803a7e9c 8e5f3b2c 00000000 800a5114 00000000 00000000
[920866.796465]           80409dd0 801f3100 00000000 00000000 00000000 00000000 00000000 00000000
[920866.796465]           00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[920866.796465]           ...
[920866.832912] Call Trace:
[920866.835502] [] show_stack+0x50/0x84
[920866.840016] [] warn_slowpath_common+0xa0/0xd0
[920866.845417] [] warn_slowpath_null+0x18/0x24
[920866.850691] [] sta_set_sinfo+0x8d8/0x9e0 [mac80211]
[920866.856685] [] __sta_info_destroy+0x30/0x48 [mac80211]
[920866.862914] [] sta_info_destroy_addr_bss+0x38/0x60 [mac80211]
[920866.869817] [] cfg80211_check_station_change+0xed8/0x1390 [cfg80211]
[920866.877266] 
[920866.878867] ---[ end trace e15a227055dd36c3 ]---
[920869.873901] ath10k_pci 0000:00:00.0: failed to delete peer b0:df:3a:12:79:80 for vdev 0: -11
[920869.882572] ath10k_pci 0000:00:00.0: found sta peer b0:df:3a:12:79:80 (ptr 8f3f3000 id 243) entry on vdev 0 after it was supposedly removed
[920872.893898] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 0: -11
[920875.893871] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 0: -11
[920878.913873] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 0: -11
[920881.913852] ath10k_pci 0000:00:00.0: failed to set protection mode 0 on vdev 0: -11
[920884.913828] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 0: -11
[920887.923826] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 1: -11
[920890.923830] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 1: -11
[920893.933787] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 1: -11
[920896.933770] ath10k_pci 0000:00:00.0: failed to set protection mode 0 on vdev 1: -11
[920899.933771] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 1: -11


Kernel log after running "wifi" in the crashed state:


[921144.042842] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer 9c:d6:43:29:cc:18: -11
[921144.051948] wlan0: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-11)
[921147.052846] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer 9c:d6:43:29:cc:18: -11
[921147.061984] wlan0: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-11)
[921150.082845] ath10k_pci 0000:00:00.0: failed to install key for vdev 1 peer 9e:d6:43:29:cc:18: -11
[921150.092017] wlan2: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-11)
[921153.092796] ath10k_pci 0000:00:00.0: failed to install key for vdev 1 peer 9e:d6:43:29:cc:18: -11
[921153.101928] wlan2: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-11)
[932082.286927] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
[932390.335807] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
[932607.674665] ath10k_pci 0000:00:00.0: failed to down vdev_id 1: -11
[932610.674753] ath10k_pci 0000:00:00.0: failed to stop WMI vdev 1: -11
[932610.682338] ath10k_pci 0000:00:00.0: failed to stop vdev 1: -11
[932613.684666] ath10k_pci 0000:00:00.0: failed to install key for vdev 1 peer 9e:d6:43:29:cc:18: -11
[932613.694955] wlan2: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-11)
[932616.694882] ath10k_pci 0000:00:00.0: failed to submit AP/IBSS self-peer removal on vdev 1: -11
[932619.694635] ath10k_pci 0000:00:00.0: failed to delete WMI vdev 1: -11
[932622.694758] ath10k_pci 0000:00:00.0: failed to remove AP self-peer on vdev 1: -145
[932622.704039] ath10k_pci 0000:00:00.0: found vif peer 9e:d6:43:29:cc:18 entry on vdev 1 after it was supposedly removed
[932622.715667] ath10k_pci 0000:00:00.0: removing stale peer 9e:d6:43:29:cc:18 from vdev_id 1
[932622.724455] br-guest: port 3(wlan2) entered disabled state
[932622.796620] device wlan2 left promiscuous mode
[932622.802446] br-guest: port 3(wlan2) entered disabled state
[932622.856835] br-guest: port 2(wlan3) entered disabled state
[932622.885493] device wlan3 left promiscuous mode
[932622.891306] br-guest: port 2(wlan3) entered disabled state
[932622.935955] device wlan0 left promiscuous mode
[932622.940833] br-lan: port 2(wlan0) entered disabled state
[932622.976382] device wlan1 left promiscuous mode
[932622.981149] br-lan: port 3(wlan1) entered disabled state
[932626.004584] ath10k_pci 0000:00:00.0: failed to down vdev_id 0: -11
[932629.004572] ath10k_pci 0000:00:00.0: failed to stop WMI vdev 0: -11
[932629.011031] ath10k_pci 0000:00:00.0: failed to stop vdev 0: -11
[932634.014537] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[932637.034556] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer 9c:d6:43:29:cc:18: -11
[932637.043707] wlan0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-11)
[932640.044532] ath10k_pci 0000:00:00.0: failed to submit AP/IBSS self-peer removal on vdev 0: -11
[932643.044507] ath10k_pci 0000:00:00.0: failed to delete WMI vdev 0: -11
[932646.044501] ath10k_pci 0000:00:00.0: failed to remove AP self-peer on vdev 0: -145
[932646.052277] ath10k_pci 0000:00:00.0: found vif peer 9c:d6:43:29:cc:18 entry on vdev 0 after it was supposedly removed
[932646.063205] ath10k_pci 0000:00:00.0: removing stale peer 9c:d6:43:29:cc:18 from vdev_id 0
[932652.064468] ath10k_pci 0000:00:00.0: could not suspend target (-11)
[932653.410146] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[932654.710106] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[932654.716877] device wlan1 entered promiscuous mode
[932654.755523] device wlan0 entered promiscuous mode
[932655.397455] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[932655.404141] br-lan: port 3(wlan0) entered forwarding state
[932655.409904] br-lan: port 3(wlan0) entered forwarding state
[932655.426138] device wlan2 entered promiscuous mode
[932655.445231] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
[932655.451454] br-guest: port 2(wlan2) entered forwarding state
[932655.457370] br-guest: port 2(wlan2) entered forwarding state
[932655.714483] br-guest: port 2(wlan2) entered disabled state
[932655.842761] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
[932655.849460] br-guest: port 2(wlan2) entered forwarding state
[932655.855380] br-guest: port 2(wlan2) entered forwarding state
[932656.428869] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[932656.435563] br-lan: port 2(wlan1) entered forwarding state
[932656.441274] br-lan: port 2(wlan1) entered forwarding state
[932656.466101] device wlan3 entered promiscuous mode
[932656.477745] IPv6: ADDRCONF(NETDEV_UP): wlan3: link is not ready
[932656.483865] br-guest: port 3(wlan3) entered forwarding state
[932656.489791] br-guest: port 3(wlan3) entered forwarding state
[932656.714486] br-guest: port 3(wlan3) entered disabled state
[932656.869320] IPv6: ADDRCONF(NETDEV_CHANGE): wlan3: link becomes ready
[932656.876022] br-guest: port 3(wlan3) entered forwarding state
[932656.881921] br-guest: port 3(wlan3) entered forwarding state
[932657.404425] br-lan: port 3(wlan0) entered forwarding state
[932657.854498] br-guest: port 2(wlan2) entered forwarding state
[932658.434436] br-lan: port 2(wlan1) entered forwarding state
[932658.874432] br-guest: port 3(wlan3) entered forwarding state
[932680.425787] br-guest: port 3(wlan3) entered disabled state
[932680.442596] device wlan3 left promiscuous mode
[932680.447279] br-guest: port 3(wlan3) entered disabled state
[932680.467863] br-guest: port 2(wlan2) entered disabled state
[932680.485729] device wlan2 left promiscuous mode
[932680.490436] br-guest: port 2(wlan2) entered disabled state
[932680.505002] device wlan1 left promiscuous mode
[932680.509700] br-lan: port 2(wlan1) entered disabled state
[932680.523775] device wlan0 left promiscuous mode
[932680.528530] br-lan: port 3(wlan0) entered disabled state
[932683.130864] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[932683.169412] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[932683.183967] device wlan0 entered promiscuous mode
[932683.197266] device wlan1 entered promiscuous mode
[932683.813544] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[932683.820249] br-lan: port 2(wlan0) entered forwarding state
[932683.826004] br-lan: port 2(wlan0) entered forwarding state
[932683.841229] device wlan2 entered promiscuous mode
[932683.857367] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
[932683.863484] br-guest: port 2(wlan2) entered forwarding state
[932683.869386] br-guest: port 2(wlan2) entered forwarding state
[932684.174365] br-guest: port 2(wlan2) entered disabled state
[932684.265577] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
[932684.272265] br-guest: port 2(wlan2) entered forwarding state
[932684.278193] br-guest: port 2(wlan2) entered forwarding state
[932684.868399] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[932684.875079] br-lan: port 3(wlan1) entered forwarding state
[932684.880820] br-lan: port 3(wlan1) entered forwarding state
[932684.905988] device wlan3 entered promiscuous mode
[932684.912111] IPv6: ADDRCONF(NETDEV_UP): wlan3: link is not ready
[932684.918275] br-guest: port 3(wlan3) entered forwarding state
[932684.924142] br-guest: port 3(wlan3) entered forwarding state
[932685.174351] br-guest: port 3(wlan3) entered disabled state
[932685.305978] IPv6: ADDRCONF(NETDEV_CHANGE): wlan3: link becomes ready
[932685.312646] br-guest: port 3(wlan3) entered forwarding state
[932685.318582] br-guest: port 3(wlan3) entered forwarding state
[932685.824311] br-lan: port 2(wlan0) entered forwarding state
[932686.274310] br-guest: port 2(wlan2) entered forwarding state
[932686.874321] br-lan: port 3(wlan1) entered forwarding state
[932687.314318] br-guest: port 3(wlan3) entered forwarding state


After running wifi, I am able to connect again.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=333


From lede-bugs at lists.infradead.org  Mon Dec 12 04:23:53 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 12 Dec 2016 12:23:53 +0000
Subject: [FS#333] ath10k_pci: crash after ~10d uptime
In-Reply-To: <FS333@bugs.lede-project.org>
References: <FS333@bugs.lede-project.org>
Message-ID: <mailman.73535.1481545456.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#333 - ath10k_pci: crash after ~10d uptime
User who did this: Stijn Tintel (stintel)
Category: Base system -> Kernel

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=333


From lede-bugs at lists.infradead.org  Mon Dec 12 04:31:02 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 12 Dec 2016 12:31:02 +0000
Subject: [FS#333] ath10k_pci: crash after ~10d uptime
In-Reply-To: <FS333@bugs.lede-project.org>
References: <FS333@bugs.lede-project.org>
Message-ID: <mailman.73538.1481545887.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#333 - ath10k_pci: crash after ~10d uptime
User who did this: Stijn Tintel (stintel)
Task details edited:
-------
After ~10 days of uptime, ath10k crashed and I could no longer associate.

Device: D-Link DAP-2695 rev A1
Running: LEDE r2370

Wireless config:


config wifi-device  radio0
        option type     mac80211
        option channel  100
        option country  BE
        option txpower  20
        option hwmode   11a
        option path     'pci0000:00/0000:00:00.0'
        option htmode   VHT80
        option disabled 0

config wifi-iface
        option device 'radio0'
        option ifname 'wlan0'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '1'
        option network 'lan'
        option mode 'ap'
        option ssid 'xxxxxxxx'
        option key 'XXXXXXXX'

config wifi-iface
        option device 'radio0'
        option ifname 'wlan2'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '0'
        option network 'guest'
        option mode 'ap'
        option ssid 'Guests'
        option key 'YYYYYYYY'
        #option disassoc_low_ack '0'

config wifi-device  radio1
        option type     mac80211
        option channel  1
        option country  BE
        option txpower  20
        option hwmode   11g
        option path     'platform/qca955x_wmac'
        option htmode   HT40
        #option noscan   1

config wifi-iface
        option device 'radio1'
        option ifname 'wlan1'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '1'
        option mode 'ap'
        option network 'lan'
        option ssid 'xxxxxxxx'
        option key 'XXXXXXXX'

config wifi-iface
        option device 'radio1'
        option ifname 'wlan3'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '0'
        option network 'guest'
        option mode 'ap'
        option ssid 'Guests'
        option key 'YYYYYYYY'
        #option disassoc_low_ack '0'


Kernel log:

[920549.560152] ath10k_pci 0000:00:00.0: failed to delete peer c0:ee:fb:4a:18:b7 for vdev 0: -145
[920549.568951] ath10k_pci 0000:00:00.0: found sta peer c0:ee:fb:4a:18:b7 (ptr 8d43f600 id 95) entry on vdev 0 after it was supposedly removed
[920549.581722] ------------[ cut here ]------------
[920549.586618] WARNING: CPU: 0 PID: 1431 at compat-wireless-2016-10-08/net/mac80211/sta_info.c:964 sta_set_sinfo+0x92c/0x9e0 [mac80211]()
[920549.598968] Modules linked in: ath9k ath9k_common crc_ccitt ath9k_hw act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress ath10k_pci ath10k_core ath mac80211 cfg80211 compat gpio_button_hotplug
[920549.620582] CPU: 0 PID: 1431 Comm: hostapd Not tainted 4.4.35 #0
[920549.626772] Stack : 803c2d64 00000000 00000001 80420000 8fe26580 8040acc3 803a4424 00000597
[920549.626772]           8047379c 8ff8d000 00000000 77415e94 00000000 800a7198 803a9a90 80400000
[920549.626772]           00000003 8ff8d000 803a7e9c 8e5f3b2c 00000000 800a5114 80400000 00000000
[920549.626772]           00000001 801f3100 00000000 00000000 00000000 00000000 00000000 00000000
[920549.626772]           00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[920549.626772]           ...
[920549.663219] Call Trace:
[920549.665810] [] show_stack+0x50/0x84
[920549.670323] [] warn_slowpath_common+0xa0/0xd0
[920549.675724] [] warn_slowpath_null+0x18/0x24
[920549.680994] [] sta_set_sinfo+0x92c/0x9e0 [mac80211]
[920549.686990] [] __sta_info_destroy+0x30/0x48 [mac80211]
[920549.693222] [] sta_info_destroy_addr_bss+0x38/0x60 [mac80211]
[920549.700118] [] cfg80211_check_station_change+0xed8/0x1390 [cfg80211]
[920549.707564] 
[920549.709166] ---[ end trace e15a227055dd36c2 ]---
[920866.693883] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer b0:df:3a:12:79:80: -145
[920866.703088] wlan0: failed to remove key (0, b0:df:3a:12:79:80) from hardware (-145)
[920866.719519] ath10k_pci 0000:00:00.0: cipher 0 is not supported
[920866.725602] ath10k_pci 0000:00:00.0: failed to remove peer wep key 0: -122
[920866.732670] ath10k_pci 0000:00:00.0: failed to clear all peer wep keys for vdev 0: -122
[920866.740901] ath10k_pci 0000:00:00.0: failed to disassociate station: b0:df:3a:12:79:80 vdev 0: -122
[920866.750169] ------------[ cut here ]------------
[920866.755066] WARNING: CPU: 0 PID: 1431 at compat-wireless-2016-10-08/net/mac80211/sta_info.c:956 sta_set_sinfo+0x8d8/0x9e0 [mac80211]()
[920866.767421] Modules linked in: ath9k ath9k_common crc_ccitt ath9k_hw act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress ath10k_pci ath10k_core ath mac80211 cfg80211 compat gpio_button_hotplug
[920866.789044] CPU: 0 PID: 1431 Comm: hostapd Tainted: G        W       4.4.35 #0
[920866.796465] Stack : 803c2d64 00000000 00000001 80420000 8fe26580 8040acc3 803a4424 00000597
[920866.796465]           8047379c 8ff8d000 00000000 77415e94 00000000 800a7198 803a9a90 80400000
[920866.796465]           00000003 8ff8d000 803a7e9c 8e5f3b2c 00000000 800a5114 00000000 00000000
[920866.796465]           80409dd0 801f3100 00000000 00000000 00000000 00000000 00000000 00000000
[920866.796465]           00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[920866.796465]           ...
[920866.832912] Call Trace:
[920866.835502] [] show_stack+0x50/0x84
[920866.840016] [] warn_slowpath_common+0xa0/0xd0
[920866.845417] [] warn_slowpath_null+0x18/0x24
[920866.850691] [] sta_set_sinfo+0x8d8/0x9e0 [mac80211]
[920866.856685] [] __sta_info_destroy+0x30/0x48 [mac80211]
[920866.862914] [] sta_info_destroy_addr_bss+0x38/0x60 [mac80211]
[920866.869817] [] cfg80211_check_station_change+0xed8/0x1390 [cfg80211]
[920866.877266] 
[920866.878867] ---[ end trace e15a227055dd36c3 ]---
[920869.873901] ath10k_pci 0000:00:00.0: failed to delete peer b0:df:3a:12:79:80 for vdev 0: -11
[920869.882572] ath10k_pci 0000:00:00.0: found sta peer b0:df:3a:12:79:80 (ptr 8f3f3000 id 243) entry on vdev 0 after it was supposedly removed
[920872.893898] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 0: -11
[920875.893871] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 0: -11
[920878.913873] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 0: -11
[920881.913852] ath10k_pci 0000:00:00.0: failed to set protection mode 0 on vdev 0: -11
[920884.913828] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 0: -11
[920887.923826] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 1: -11
[920890.923830] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 1: -11
[920893.933787] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 1: -11
[920896.933770] ath10k_pci 0000:00:00.0: failed to set protection mode 0 on vdev 1: -11
[920899.933771] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 1: -11


Kernel log after running "wifi" in the crashed state:


[921144.042842] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer 9c:d6:43:29:cc:18: -11
[921144.051948] wlan0: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-11)
[921147.052846] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer 9c:d6:43:29:cc:18: -11
[921147.061984] wlan0: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-11)
[921150.082845] ath10k_pci 0000:00:00.0: failed to install key for vdev 1 peer 9e:d6:43:29:cc:18: -11
[921150.092017] wlan2: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-11)
[921153.092796] ath10k_pci 0000:00:00.0: failed to install key for vdev 1 peer 9e:d6:43:29:cc:18: -11
[921153.101928] wlan2: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-11)
[932082.286927] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
[932390.335807] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
[932607.674665] ath10k_pci 0000:00:00.0: failed to down vdev_id 1: -11
[932610.674753] ath10k_pci 0000:00:00.0: failed to stop WMI vdev 1: -11
[932610.682338] ath10k_pci 0000:00:00.0: failed to stop vdev 1: -11
[932613.684666] ath10k_pci 0000:00:00.0: failed to install key for vdev 1 peer 9e:d6:43:29:cc:18: -11
[932613.694955] wlan2: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-11)
[932616.694882] ath10k_pci 0000:00:00.0: failed to submit AP/IBSS self-peer removal on vdev 1: -11
[932619.694635] ath10k_pci 0000:00:00.0: failed to delete WMI vdev 1: -11
[932622.694758] ath10k_pci 0000:00:00.0: failed to remove AP self-peer on vdev 1: -145
[932622.704039] ath10k_pci 0000:00:00.0: found vif peer 9e:d6:43:29:cc:18 entry on vdev 1 after it was supposedly removed
[932622.715667] ath10k_pci 0000:00:00.0: removing stale peer 9e:d6:43:29:cc:18 from vdev_id 1
[932622.724455] br-guest: port 3(wlan2) entered disabled state
[932622.796620] device wlan2 left promiscuous mode
[932622.802446] br-guest: port 3(wlan2) entered disabled state
[932622.856835] br-guest: port 2(wlan3) entered disabled state
[932622.885493] device wlan3 left promiscuous mode
[932622.891306] br-guest: port 2(wlan3) entered disabled state
[932622.935955] device wlan0 left promiscuous mode
[932622.940833] br-lan: port 2(wlan0) entered disabled state
[932622.976382] device wlan1 left promiscuous mode
[932622.981149] br-lan: port 3(wlan1) entered disabled state
[932626.004584] ath10k_pci 0000:00:00.0: failed to down vdev_id 0: -11
[932629.004572] ath10k_pci 0000:00:00.0: failed to stop WMI vdev 0: -11
[932629.011031] ath10k_pci 0000:00:00.0: failed to stop vdev 0: -11
[932634.014537] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[932637.034556] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer 9c:d6:43:29:cc:18: -11
[932637.043707] wlan0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-11)
[932640.044532] ath10k_pci 0000:00:00.0: failed to submit AP/IBSS self-peer removal on vdev 0: -11
[932643.044507] ath10k_pci 0000:00:00.0: failed to delete WMI vdev 0: -11
[932646.044501] ath10k_pci 0000:00:00.0: failed to remove AP self-peer on vdev 0: -145
[932646.052277] ath10k_pci 0000:00:00.0: found vif peer 9c:d6:43:29:cc:18 entry on vdev 0 after it was supposedly removed
[932646.063205] ath10k_pci 0000:00:00.0: removing stale peer 9c:d6:43:29:cc:18 from vdev_id 0
[932652.064468] ath10k_pci 0000:00:00.0: could not suspend target (-11)
[932653.410146] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[932654.710106] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[932654.716877] device wlan1 entered promiscuous mode
[932654.755523] device wlan0 entered promiscuous mode
[932655.397455] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[932655.404141] br-lan: port 3(wlan0) entered forwarding state
[932655.409904] br-lan: port 3(wlan0) entered forwarding state
[932655.426138] device wlan2 entered promiscuous mode
[932655.445231] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
[932655.451454] br-guest: port 2(wlan2) entered forwarding state
[932655.457370] br-guest: port 2(wlan2) entered forwarding state
[932655.714483] br-guest: port 2(wlan2) entered disabled state
[932655.842761] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
[932655.849460] br-guest: port 2(wlan2) entered forwarding state
[932655.855380] br-guest: port 2(wlan2) entered forwarding state
[932656.428869] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[932656.435563] br-lan: port 2(wlan1) entered forwarding state
[932656.441274] br-lan: port 2(wlan1) entered forwarding state
[932656.466101] device wlan3 entered promiscuous mode
[932656.477745] IPv6: ADDRCONF(NETDEV_UP): wlan3: link is not ready
[932656.483865] br-guest: port 3(wlan3) entered forwarding state
[932656.489791] br-guest: port 3(wlan3) entered forwarding state
[932656.714486] br-guest: port 3(wlan3) entered disabled state
[932656.869320] IPv6: ADDRCONF(NETDEV_CHANGE): wlan3: link becomes ready
[932656.876022] br-guest: port 3(wlan3) entered forwarding state
[932656.881921] br-guest: port 3(wlan3) entered forwarding state
[932657.404425] br-lan: port 3(wlan0) entered forwarding state
[932657.854498] br-guest: port 2(wlan2) entered forwarding state
[932658.434436] br-lan: port 2(wlan1) entered forwarding state
[932658.874432] br-guest: port 3(wlan3) entered forwarding state
[932680.425787] br-guest: port 3(wlan3) entered disabled state
[932680.442596] device wlan3 left promiscuous mode
[932680.447279] br-guest: port 3(wlan3) entered disabled state
[932680.467863] br-guest: port 2(wlan2) entered disabled state
[932680.485729] device wlan2 left promiscuous mode
[932680.490436] br-guest: port 2(wlan2) entered disabled state
[932680.505002] device wlan1 left promiscuous mode
[932680.509700] br-lan: port 2(wlan1) entered disabled state
[932680.523775] device wlan0 left promiscuous mode
[932680.528530] br-lan: port 3(wlan0) entered disabled state
[932683.130864] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[932683.169412] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[932683.183967] device wlan0 entered promiscuous mode
[932683.197266] device wlan1 entered promiscuous mode
[932683.813544] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[932683.820249] br-lan: port 2(wlan0) entered forwarding state
[932683.826004] br-lan: port 2(wlan0) entered forwarding state
[932683.841229] device wlan2 entered promiscuous mode
[932683.857367] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
[932683.863484] br-guest: port 2(wlan2) entered forwarding state
[932683.869386] br-guest: port 2(wlan2) entered forwarding state
[932684.174365] br-guest: port 2(wlan2) entered disabled state
[932684.265577] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
[932684.272265] br-guest: port 2(wlan2) entered forwarding state
[932684.278193] br-guest: port 2(wlan2) entered forwarding state
[932684.868399] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[932684.875079] br-lan: port 3(wlan1) entered forwarding state
[932684.880820] br-lan: port 3(wlan1) entered forwarding state
[932684.905988] device wlan3 entered promiscuous mode
[932684.912111] IPv6: ADDRCONF(NETDEV_UP): wlan3: link is not ready
[932684.918275] br-guest: port 3(wlan3) entered forwarding state
[932684.924142] br-guest: port 3(wlan3) entered forwarding state
[932685.174351] br-guest: port 3(wlan3) entered disabled state
[932685.305978] IPv6: ADDRCONF(NETDEV_CHANGE): wlan3: link becomes ready
[932685.312646] br-guest: port 3(wlan3) entered forwarding state
[932685.318582] br-guest: port 3(wlan3) entered forwarding state
[932685.824311] br-lan: port 2(wlan0) entered forwarding state
[932686.274310] br-guest: port 2(wlan2) entered forwarding state
[932686.874321] br-lan: port 3(wlan1) entered forwarding state
[932687.314318] br-guest: port 3(wlan3) entered forwarding state


After running wifi, I am able to connect again.

MAC addresses found in logs:
9c:d6:43:29:cc:18:  DAP-2695, wlan0
9e:d6:43:29:cc:18:  DAP-2695, wlan2

c0:ee:fb:4a:18:b7:  OnePlus 2, Android 6.0.1
b0:df:3a:12:79:80:  Samsung SM-T520, Android 5.1.1

-------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=333


From lede-bugs at lists.infradead.org  Mon Dec 12 04:35:49 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 12 Dec 2016 12:35:49 +0000
Subject: [FS#333] ath10k_pci: crash after ~10d uptime
In-Reply-To: <FS333@bugs.lede-project.org>
References: <FS333@bugs.lede-project.org>
Message-ID: <mailman.73539.1481546174.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#333 - ath10k_pci: crash after ~10d uptime
User who did this: Stijn Tintel (stintel)
Task details edited:
-------
After ~10 days of uptime, ath10k crashed and I could no longer associate.

Device: D-Link DAP-2695 rev A1
Running: LEDE r2370

Wireless config:


config wifi-device  radio0
        option type     mac80211
        option channel  100
        option country  BE
        option txpower  20
        option hwmode   11a
        option path     'pci0000:00/0000:00:00.0'
        option htmode   VHT80
        option disabled 0

config wifi-iface
        option device 'radio0'
        option ifname 'wlan0'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '1'
        option network 'lan'
        option mode 'ap'
        option ssid 'xxxxxxxx'
        option key 'XXXXXXXX'

config wifi-iface
        option device 'radio0'
        option ifname 'wlan2'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '0'
        option network 'guest'
        option mode 'ap'
        option ssid 'Guests'
        option key 'YYYYYYYY'
        #option disassoc_low_ack '0'

config wifi-device  radio1
        option type     mac80211
        option channel  1
        option country  BE
        option txpower  20
        option hwmode   11g
        option path     'platform/qca955x_wmac'
        option htmode   HT40
        #option noscan   1

config wifi-iface
        option device 'radio1'
        option ifname 'wlan1'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '1'
        option mode 'ap'
        option network 'lan'
        option ssid 'xxxxxxxx'
        option key 'XXXXXXXX'

config wifi-iface
        option device 'radio1'
        option ifname 'wlan3'
        option encryption 'psk2'
        option ieee80211d '1'
        option ieee80211w '1'
        option peerkey '1'
        option rsn_preauth '0'
        option network 'guest'
        option mode 'ap'
        option ssid 'Guests'
        option key 'YYYYYYYY'
        #option disassoc_low_ack '0'


Kernel log:

[   54.439387] ath10k_pci 0000:00:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[   54.652312] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:00:00.0.bin failed with error -2
[   54.663197] ath10k_pci 0000:00:00.0: Falling back to user helper
[   54.742675] firmware ath10k!pre-cal-pci-0000:00:00.0.bin: firmware_loading_store: map pages failed
[   54.752039] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/cal-pci-0000:00:00.0.bin failed with error -2
[   54.762568] ath10k_pci 0000:00:00.0: Falling back to user helper
[   61.648688] ath10k_pci 0000:00:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[   61.658088] ath10k_pci 0000:00:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[   61.671139] ath10k_pci 0000:00:00.0: firmware ver 10.2.4.70.54 api 5 features no-p2p,raw-mode,mfp crc32 9d340dd9
[   61.681571] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[   61.692178] ath10k_pci 0000:00:00.0: Falling back to user helper
[   61.771624] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
[   61.786987] ath10k_pci 0000:00:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[   62.893736] ath10k_pci 0000:00:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal file max-sta 128 raw 0 hwcrypto 1
[   63.001904] ath: EEPROM regdomain: 0x0
[   63.001920] ath: EEPROM indicates default country code should be used
[   63.001928] ath: doing EEPROM country->regdmn map search
[   63.001945] ath: country maps to regdmn code: 0x3a
[   63.001955] ath: Country alpha2 being used: US
[   63.001963] ath: Regpair used: 0x3a
[   63.284566] ath: EEPROM regdomain: 0x0
[   63.284583] ath: EEPROM indicates default country code should be used
[   63.284591] ath: doing EEPROM country->regdmn map search
[   63.284608] ath: country maps to regdmn code: 0x3a
[   63.284617] ath: Country alpha2 being used: US
[   63.284625] ath: Regpair used: 0x3a
[   72.829974] ath: EEPROM regdomain: 0x8038
[   72.834045] ath: EEPROM indicates we should expect a country code
[   72.840265] ath: doing EEPROM country->regdmn map search
[   72.845651] ath: country maps to regdmn code: 0x37
[   72.850522] ath: Country alpha2 being used: BE
[   72.855022] ath: Regpair used: 0x37
[   72.858554] ath: regdomain 0x8038 dynamically updated by user
[   72.864452] ath: EEPROM regdomain: 0x8038
[   72.868513] ath: EEPROM indicates we should expect a country code
[   72.874707] ath: doing EEPROM country->regdmn map search
[   72.880092] ath: country maps to regdmn code: 0x37
[   72.884943] ath: Country alpha2 being used: BE
[   72.889458] ath: Regpair used: 0x37
[   72.892996] ath: regdomain 0x8038 dynamically updated by user
[920549.560152] ath10k_pci 0000:00:00.0: failed to delete peer c0:ee:fb:4a:18:b7 for vdev 0: -145
[920549.568951] ath10k_pci 0000:00:00.0: found sta peer c0:ee:fb:4a:18:b7 (ptr 8d43f600 id 95) entry on vdev 0 after it was supposedly removed
[920549.581722] ------------[ cut here ]------------
[920549.586618] WARNING: CPU: 0 PID: 1431 at compat-wireless-2016-10-08/net/mac80211/sta_info.c:964 sta_set_sinfo+0x92c/0x9e0 [mac80211]()
[920549.598968] Modules linked in: ath9k ath9k_common crc_ccitt ath9k_hw act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress ath10k_pci ath10k_core ath mac80211 cfg80211 compat gpio_button_hotplug
[920549.620582] CPU: 0 PID: 1431 Comm: hostapd Not tainted 4.4.35 #0
[920549.626772] Stack : 803c2d64 00000000 00000001 80420000 8fe26580 8040acc3 803a4424 00000597
[920549.626772]           8047379c 8ff8d000 00000000 77415e94 00000000 800a7198 803a9a90 80400000
[920549.626772]           00000003 8ff8d000 803a7e9c 8e5f3b2c 00000000 800a5114 80400000 00000000
[920549.626772]           00000001 801f3100 00000000 00000000 00000000 00000000 00000000 00000000
[920549.626772]           00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[920549.626772]           ...
[920549.663219] Call Trace:
[920549.665810] [] show_stack+0x50/0x84
[920549.670323] [] warn_slowpath_common+0xa0/0xd0
[920549.675724] [] warn_slowpath_null+0x18/0x24
[920549.680994] [] sta_set_sinfo+0x92c/0x9e0 [mac80211]
[920549.686990] [] __sta_info_destroy+0x30/0x48 [mac80211]
[920549.693222] [] sta_info_destroy_addr_bss+0x38/0x60 [mac80211]
[920549.700118] [] cfg80211_check_station_change+0xed8/0x1390 [cfg80211]
[920549.707564] 
[920549.709166] ---[ end trace e15a227055dd36c2 ]---
[920866.693883] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer b0:df:3a:12:79:80: -145
[920866.703088] wlan0: failed to remove key (0, b0:df:3a:12:79:80) from hardware (-145)
[920866.719519] ath10k_pci 0000:00:00.0: cipher 0 is not supported
[920866.725602] ath10k_pci 0000:00:00.0: failed to remove peer wep key 0: -122
[920866.732670] ath10k_pci 0000:00:00.0: failed to clear all peer wep keys for vdev 0: -122
[920866.740901] ath10k_pci 0000:00:00.0: failed to disassociate station: b0:df:3a:12:79:80 vdev 0: -122
[920866.750169] ------------[ cut here ]------------
[920866.755066] WARNING: CPU: 0 PID: 1431 at compat-wireless-2016-10-08/net/mac80211/sta_info.c:956 sta_set_sinfo+0x8d8/0x9e0 [mac80211]()
[920866.767421] Modules linked in: ath9k ath9k_common crc_ccitt ath9k_hw act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress ath10k_pci ath10k_core ath mac80211 cfg80211 compat gpio_button_hotplug
[920866.789044] CPU: 0 PID: 1431 Comm: hostapd Tainted: G        W       4.4.35 #0
[920866.796465] Stack : 803c2d64 00000000 00000001 80420000 8fe26580 8040acc3 803a4424 00000597
[920866.796465]           8047379c 8ff8d000 00000000 77415e94 00000000 800a7198 803a9a90 80400000
[920866.796465]           00000003 8ff8d000 803a7e9c 8e5f3b2c 00000000 800a5114 00000000 00000000
[920866.796465]           80409dd0 801f3100 00000000 00000000 00000000 00000000 00000000 00000000
[920866.796465]           00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[920866.796465]           ...
[920866.832912] Call Trace:
[920866.835502] [] show_stack+0x50/0x84
[920866.840016] [] warn_slowpath_common+0xa0/0xd0
[920866.845417] [] warn_slowpath_null+0x18/0x24
[920866.850691] [] sta_set_sinfo+0x8d8/0x9e0 [mac80211]
[920866.856685] [] __sta_info_destroy+0x30/0x48 [mac80211]
[920866.862914] [] sta_info_destroy_addr_bss+0x38/0x60 [mac80211]
[920866.869817] [] cfg80211_check_station_change+0xed8/0x1390 [cfg80211]
[920866.877266] 
[920866.878867] ---[ end trace e15a227055dd36c3 ]---
[920869.873901] ath10k_pci 0000:00:00.0: failed to delete peer b0:df:3a:12:79:80 for vdev 0: -11
[920869.882572] ath10k_pci 0000:00:00.0: found sta peer b0:df:3a:12:79:80 (ptr 8f3f3000 id 243) entry on vdev 0 after it was supposedly removed
[920872.893898] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 0: -11
[920875.893871] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 0: -11
[920878.913873] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 0: -11
[920881.913852] ath10k_pci 0000:00:00.0: failed to set protection mode 0 on vdev 0: -11
[920884.913828] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 0: -11
[920887.923826] ath10k_pci 0000:00:00.0: failed to set beacon mode for vdev 1: -11
[920890.923830] ath10k_pci 0000:00:00.0: failed to set dtim period for vdev 1: -11
[920893.933787] ath10k_pci 0000:00:00.0: failed to recalculate rts/cts prot for vdev 1: -11
[920896.933770] ath10k_pci 0000:00:00.0: failed to set protection mode 0 on vdev 1: -11
[920899.933771] ath10k_pci 0000:00:00.0: failed to set preamble for vdev 1: -11


Kernel log after running "wifi" in the crashed state:


[921144.042842] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer 9c:d6:43:29:cc:18: -11
[921144.051948] wlan0: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-11)
[921147.052846] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer 9c:d6:43:29:cc:18: -11
[921147.061984] wlan0: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-11)
[921150.082845] ath10k_pci 0000:00:00.0: failed to install key for vdev 1 peer 9e:d6:43:29:cc:18: -11
[921150.092017] wlan2: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-11)
[921153.092796] ath10k_pci 0000:00:00.0: failed to install key for vdev 1 peer 9e:d6:43:29:cc:18: -11
[921153.101928] wlan2: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-11)
[932082.286927] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
[932390.335807] ath10k_pci 0000:00:00.0: failed to send pdev bss chan info request
[932607.674665] ath10k_pci 0000:00:00.0: failed to down vdev_id 1: -11
[932610.674753] ath10k_pci 0000:00:00.0: failed to stop WMI vdev 1: -11
[932610.682338] ath10k_pci 0000:00:00.0: failed to stop vdev 1: -11
[932613.684666] ath10k_pci 0000:00:00.0: failed to install key for vdev 1 peer 9e:d6:43:29:cc:18: -11
[932613.694955] wlan2: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-11)
[932616.694882] ath10k_pci 0000:00:00.0: failed to submit AP/IBSS self-peer removal on vdev 1: -11
[932619.694635] ath10k_pci 0000:00:00.0: failed to delete WMI vdev 1: -11
[932622.694758] ath10k_pci 0000:00:00.0: failed to remove AP self-peer on vdev 1: -145
[932622.704039] ath10k_pci 0000:00:00.0: found vif peer 9e:d6:43:29:cc:18 entry on vdev 1 after it was supposedly removed
[932622.715667] ath10k_pci 0000:00:00.0: removing stale peer 9e:d6:43:29:cc:18 from vdev_id 1
[932622.724455] br-guest: port 3(wlan2) entered disabled state
[932622.796620] device wlan2 left promiscuous mode
[932622.802446] br-guest: port 3(wlan2) entered disabled state
[932622.856835] br-guest: port 2(wlan3) entered disabled state
[932622.885493] device wlan3 left promiscuous mode
[932622.891306] br-guest: port 2(wlan3) entered disabled state
[932622.935955] device wlan0 left promiscuous mode
[932622.940833] br-lan: port 2(wlan0) entered disabled state
[932622.976382] device wlan1 left promiscuous mode
[932622.981149] br-lan: port 3(wlan1) entered disabled state
[932626.004584] ath10k_pci 0000:00:00.0: failed to down vdev_id 0: -11
[932629.004572] ath10k_pci 0000:00:00.0: failed to stop WMI vdev 0: -11
[932629.011031] ath10k_pci 0000:00:00.0: failed to stop vdev 0: -11
[932634.014537] ath10k_pci 0000:00:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[932637.034556] ath10k_pci 0000:00:00.0: failed to install key for vdev 0 peer 9c:d6:43:29:cc:18: -11
[932637.043707] wlan0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-11)
[932640.044532] ath10k_pci 0000:00:00.0: failed to submit AP/IBSS self-peer removal on vdev 0: -11
[932643.044507] ath10k_pci 0000:00:00.0: failed to delete WMI vdev 0: -11
[932646.044501] ath10k_pci 0000:00:00.0: failed to remove AP self-peer on vdev 0: -145
[932646.052277] ath10k_pci 0000:00:00.0: found vif peer 9c:d6:43:29:cc:18 entry on vdev 0 after it was supposedly removed
[932646.063205] ath10k_pci 0000:00:00.0: removing stale peer 9c:d6:43:29:cc:18 from vdev_id 0
[932652.064468] ath10k_pci 0000:00:00.0: could not suspend target (-11)
[932653.410146] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[932654.710106] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[932654.716877] device wlan1 entered promiscuous mode
[932654.755523] device wlan0 entered promiscuous mode
[932655.397455] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[932655.404141] br-lan: port 3(wlan0) entered forwarding state
[932655.409904] br-lan: port 3(wlan0) entered forwarding state
[932655.426138] device wlan2 entered promiscuous mode
[932655.445231] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
[932655.451454] br-guest: port 2(wlan2) entered forwarding state
[932655.457370] br-guest: port 2(wlan2) entered forwarding state
[932655.714483] br-guest: port 2(wlan2) entered disabled state
[932655.842761] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
[932655.849460] br-guest: port 2(wlan2) entered forwarding state
[932655.855380] br-guest: port 2(wlan2) entered forwarding state
[932656.428869] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[932656.435563] br-lan: port 2(wlan1) entered forwarding state
[932656.441274] br-lan: port 2(wlan1) entered forwarding state
[932656.466101] device wlan3 entered promiscuous mode
[932656.477745] IPv6: ADDRCONF(NETDEV_UP): wlan3: link is not ready
[932656.483865] br-guest: port 3(wlan3) entered forwarding state
[932656.489791] br-guest: port 3(wlan3) entered forwarding state
[932656.714486] br-guest: port 3(wlan3) entered disabled state
[932656.869320] IPv6: ADDRCONF(NETDEV_CHANGE): wlan3: link becomes ready
[932656.876022] br-guest: port 3(wlan3) entered forwarding state
[932656.881921] br-guest: port 3(wlan3) entered forwarding state
[932657.404425] br-lan: port 3(wlan0) entered forwarding state
[932657.854498] br-guest: port 2(wlan2) entered forwarding state
[932658.434436] br-lan: port 2(wlan1) entered forwarding state
[932658.874432] br-guest: port 3(wlan3) entered forwarding state
[932680.425787] br-guest: port 3(wlan3) entered disabled state
[932680.442596] device wlan3 left promiscuous mode
[932680.447279] br-guest: port 3(wlan3) entered disabled state
[932680.467863] br-guest: port 2(wlan2) entered disabled state
[932680.485729] device wlan2 left promiscuous mode
[932680.490436] br-guest: port 2(wlan2) entered disabled state
[932680.505002] device wlan1 left promiscuous mode
[932680.509700] br-lan: port 2(wlan1) entered disabled state
[932680.523775] device wlan0 left promiscuous mode
[932680.528530] br-lan: port 3(wlan0) entered disabled state
[932683.130864] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[932683.169412] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[932683.183967] device wlan0 entered promiscuous mode
[932683.197266] device wlan1 entered promiscuous mode
[932683.813544] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[932683.820249] br-lan: port 2(wlan0) entered forwarding state
[932683.826004] br-lan: port 2(wlan0) entered forwarding state
[932683.841229] device wlan2 entered promiscuous mode
[932683.857367] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
[932683.863484] br-guest: port 2(wlan2) entered forwarding state
[932683.869386] br-guest: port 2(wlan2) entered forwarding state
[932684.174365] br-guest: port 2(wlan2) entered disabled state
[932684.265577] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
[932684.272265] br-guest: port 2(wlan2) entered forwarding state
[932684.278193] br-guest: port 2(wlan2) entered forwarding state
[932684.868399] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[932684.875079] br-lan: port 3(wlan1) entered forwarding state
[932684.880820] br-lan: port 3(wlan1) entered forwarding state
[932684.905988] device wlan3 entered promiscuous mode
[932684.912111] IPv6: ADDRCONF(NETDEV_UP): wlan3: link is not ready
[932684.918275] br-guest: port 3(wlan3) entered forwarding state
[932684.924142] br-guest: port 3(wlan3) entered forwarding state
[932685.174351] br-guest: port 3(wlan3) entered disabled state
[932685.305978] IPv6: ADDRCONF(NETDEV_CHANGE): wlan3: link becomes ready
[932685.312646] br-guest: port 3(wlan3) entered forwarding state
[932685.318582] br-guest: port 3(wlan3) entered forwarding state
[932685.824311] br-lan: port 2(wlan0) entered forwarding state
[932686.274310] br-guest: port 2(wlan2) entered forwarding state
[932686.874321] br-lan: port 3(wlan1) entered forwarding state
[932687.314318] br-guest: port 3(wlan3) entered forwarding state


After running wifi, I am able to connect again.

MAC addresses found in logs:
9c:d6:43:29:cc:18:  DAP-2695, wlan0
9e:d6:43:29:cc:18:  DAP-2695, wlan2

c0:ee:fb:4a:18:b7:  OnePlus 2, Android 6.0.1
b0:df:3a:12:79:80:  Samsung SM-T520, Android 5.1.1

-------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=333


From lede-bugs at lists.infradead.org  Mon Dec 12 04:48:36 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 12 Dec 2016 12:48:36 +0000
Subject: [FS#334] ath5k: kernel warning every 10 minutes
In-Reply-To: <FS334@bugs.lede-project.org>
References: <FS334@bugs.lede-project.org>
Message-ID: <mailman.73542.1481546942.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Stijn Tintel (stintel) 

Attached to Project - LEDE Project
Summary - ath5k: kernel warning every 10 minutes
Task Type - Bug Report
Category - Kernel
Status - New
Assigned To - 
Operating System - All
Severity - Low
Priority - Medium
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Device: Ubiquiti Routerstation Pro, 1x Mikrotik R52n, 1x Ubiquiti SR71-A, 1x Ubiquiti XR2
LEDE r2473-b305b8c 

While testing 802.11w on ath5k, I noticed that a kernel warning occurs every 10 minutes, or when running "wifi". This happens even when no clients are associated.

Wireless config:

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '11'
        option country 'BE'
        option hwmode '11g'
        option txpower '10'
        option path 'pci0000:00/0000:00:12.0'
        option disabled '0'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'LEDE'
        option encryption 'psk2'
        option key 'edellede'
        option ieee80211w '2'

config wifi-device 'radio1'
        option type 'mac80211'
        option channel '11'
        option country 'BE'
        option hwmode '11g'
        option txpower '13'
        option path 'pci0000:00/0000:00:11.0'
        option htmode 'HT20'
        option disabled '1'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'LEDE'
        option encryption 'psk2'
        option key 'edellede'
        option ieee80211w '2'

config wifi-device 'radio2'
        option type 'mac80211'
        option channel '11'
        option country 'BE'
        option hwmode '11g'
        option path 'pci0000:00/0000:00:13.0'
        option htmode 'HT20'
        option disabled '1'

config wifi-iface 'default_radio2'
        option device 'radio2'
        option network 'lan'
        option mode 'ap'
        option ssid 'LEDE'
        option encryption 'psk2'
        option key 'edellede'
        option ieee80211w '2'


Kernel log:

[   32.052530] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   32.074984] device wlan0 entered promiscuous mode
[   32.079780] br-lan: port 2(wlan0) entered forwarding state
[   32.085357] br-lan: port 2(wlan0) entered forwarding state
[   32.451638] br-lan: port 2(wlan0) entered disabled state
[   33.749319] ------------[ cut here ]------------
[   33.754055] WARNING: CPU: 0 PID: 1780 at compat-wireless-2016-10-08/drivers/net/wireless/ath/ath5k/mac80211-ops.c:500 ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]()
[   33.768752] Modules linked in: ath9k ath9k_common pppoe ppp_async iptable_nat ath9k_hw ath5k ath pppox ppp_generic nf_nat_pptp nf_nat_ipv4 nf_nat_amanda nf_conntrack_pptp nf_conntrack_ipv6 nf_conntrack_ipv4 nf_conntrack_amanda mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_quota xt_policy xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_id xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_NFQUEUE xt_NFLOG xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc nfnetlink_queue nfnetlink_log nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_rtsp nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtsp nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables crc7 crc_itu_t crc_ccitt compat br_netfilter sch_cake sch_teql em_nbyte sch_codel sch_prio sch_pie act_ipt sch_tbf sch_gred sch_dsmark cls_basic em_text em_meta sch_htb sch_sfq act_police sch_fq em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ifb ip6_vti ip_vti sit ipcomp6 xfrm6_tunnel xfrm6_mode_tunnel xfrm6_mode_transport xfrm6_mode_beet esp6 ah6 ipcomp xfrm4_tunnel xfrm4_mode_tunnel xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 ip6_tunnel tunnel6 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo nls_utf8 nls_iso8859_15 nls_iso8859_1 vxlan udp_tunnel ip6_udp_tunnel sha512_generic sha256_generic sha1_generic seqiv jitterentropy_rng drbg md5 hmac ghash_generic gf128mul gcm echainiv des_generic deflate zlib_inflate zlib_deflate ctr cbc authenc mmc_block usb_storage mmc_core ohci_platform ohci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache button_hotplug input_core usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[   34.009197] CPU: 0 PID: 1780 Comm: hostapd Not tainted 4.4.36 #0
[   34.015227] Stack : 00000000 00000000 804a6542 00000034 803d7380 00000000 00000001 80450000
[   34.015227]    80430000 8043ae43 803d3a34 000006f4 804a379c 00000000 00000000 00000004
[   34.015227]    00000000 800a92a4 803d90a0 80430000 00000003 00000000 803d74ac 86b8ba54
[   34.015227]    804a379c 800a7140 80430000 00000000 00000001 80201800 00000000 00000000
[   34.015227]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   34.015227]    ...
[   34.051247] Call Trace:
[   34.053707] [] show_stack+0x64/0xb0
[   34.058088] [] warn_slowpath_common+0xa0/0xd0
[   34.063344] [] warn_slowpath_null+0x18/0x24
[   34.068432] [] ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]
[   34.074819] 
[   34.076310] ---[ end trace 0dabd211d3d954a3 ]---
[   34.080958] wlan0: failed to set key (4, ff:ff:ff:ff:ff:ff) to hardware (-22)
[   34.088794] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   34.095365] br-lan: port 2(wlan0) entered forwarding state
[   34.100958] br-lan: port 2(wlan0) entered forwarding state
[  633.718441] ------------[ cut here ]------------
[  633.723190] WARNING: CPU: 0 PID: 2155 at compat-wireless-2016-10-08/drivers/net/wireless/ath/ath5k/mac80211-ops.c:500 ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]()
[  633.737896] Modules linked in: ath9k ath9k_common pppoe ppp_async iptable_nat ath9k_hw ath5k ath pppox ppp_generic nf_nat_pptp nf_nat_ipv4 nf_nat_amanda nf_conntrack_pptp nf_conntrack_ipv6 nf_conntrack_ipv4 nf_conntrack_amanda mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_quota xt_policy xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_id xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_NFQUEUE xt_NFLOG xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc nfnetlink_queue nfnetlink_log nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_rtsp nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtsp nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables crc7 crc_itu_t crc_ccitt compat br_netfilter sch_cake sch_teql em_nbyte sch_codel sch_prio sch_pie act_ipt sch_tbf sch_gred sch_dsmark cls_basic em_text em_meta sch_htb sch_sfq act_police sch_fq em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ifb ip6_vti ip_vti sit ipcomp6 xfrm6_tunnel xfrm6_mode_tunnel xfrm6_mode_transport xfrm6_mode_beet esp6 ah6 ipcomp xfrm4_tunnel xfrm4_mode_tunnel xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 ip6_tunnel tunnel6 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo nls_utf8 nls_iso8859_15 nls_iso8859_1 vxlan udp_tunnel ip6_udp_tunnel sha512_generic sha256_generic sha1_generic seqiv jitterentropy_rng drbg md5 hmac ghash_generic gf128mul gcm echainiv des_generic deflate zlib_inflate zlib_deflate ctr cbc authenc mmc_block usb_storage mmc_core ohci_platform ohci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache button_hotplug input_core usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[  633.978364] CPU: 0 PID: 2155 Comm: hostapd Tainted: G        W       4.4.36 #0
[  633.985621] Stack : 00000000 00000000 804a6542 00000042 803d7380 00000000 00000001 80450000
[  633.985621]    80430000 8043ae43 803d3a34 0000086b 804a379c 00000000 00000000 00000005
[  633.985621]    00000000 800a92a4 803d90a0 80430000 00000003 00000000 803d74ac 86b89a54
[  633.985621]    804a379c 800a7140 80430000 00000000 80439f50 80201800 00000000 00000000
[  633.985621]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[  633.985621]    ...
[  634.021615] Call Trace:
[  634.024083] [] show_stack+0x64/0xb0
[  634.028465] [] warn_slowpath_common+0xa0/0xd0
[  634.033721] [] warn_slowpath_null+0x18/0x24
[  634.038810] [] ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]
[  634.045208] 
[  634.046704] ---[ end trace 0dabd211d3d954a4 ]---
[  634.051353] wlan0: failed to set key (5, ff:ff:ff:ff:ff:ff) to hardware (-22)
[ 1234.068642] ------------[ cut here ]------------
[ 1234.073426] WARNING: CPU: 0 PID: 2155 at compat-wireless-2016-10-08/drivers/net/wireless/ath/ath5k/mac80211-ops.c:500 ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]()
[ 1234.088094] Modules linked in: ath9k ath9k_common pppoe ppp_async iptable_nat ath9k_hw ath5k ath pppox ppp_generic nf_nat_pptp nf_nat_ipv4 nf_nat_amanda nf_conntrack_pptp nf_conntrack_ipv6 nf_conntrack_ipv4 nf_conntrack_amanda mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_quota xt_policy xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_id xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_NFQUEUE xt_NFLOG xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc nfnetlink_queue nfnetlink_log nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_rtsp nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtsp nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables crc7 crc_itu_t crc_ccitt compat br_netfilter sch_cake sch_teql em_nbyte sch_codel sch_prio sch_pie act_ipt sch_tbf sch_gred sch_dsmark cls_basic em_text em_meta sch_htb sch_sfq act_police sch_fq em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ifb ip6_vti ip_vti sit ipcomp6 xfrm6_tunnel xfrm6_mode_tunnel xfrm6_mode_transport xfrm6_mode_beet esp6 ah6 ipcomp xfrm4_tunnel xfrm4_mode_tunnel xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 ip6_tunnel tunnel6 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo nls_utf8 nls_iso8859_15 nls_iso8859_1 vxlan udp_tunnel ip6_udp_tunnel sha512_generic sha256_generic sha1_generic seqiv jitterentropy_rng drbg md5 hmac ghash_generic gf128mul gcm echainiv des_generic deflate zlib_inflate zlib_deflate ctr cbc authenc mmc_block usb_storage mmc_core ohci_platform ohci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache button_hotplug input_core usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[ 1234.328545] CPU: 0 PID: 2155 Comm: hostapd Tainted: G        W       4.4.36 #0
[ 1234.335802] Stack : 00000000 00000000 804a6542 00000042 803d7380 00000000 00000001 80450000
[ 1234.335802]    80430000 8043ae43 803d3a34 0000086b 804a379c 00000000 00000000 00000004
[ 1234.335802]    00000000 800a92a4 803d90a0 80430000 00000003 00000000 803d74ac 86b89a54
[ 1234.335802]    804a379c 800a7140 80430000 00000000 80439f50 80201800 00000000 00000000
[ 1234.335802]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1234.335802]    ...
[ 1234.371822] Call Trace:
[ 1234.374290] [] show_stack+0x64/0xb0
[ 1234.378671] [] warn_slowpath_common+0xa0/0xd0
[ 1234.383928] [] warn_slowpath_null+0x18/0x24
[ 1234.389014] [] ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]
[ 1234.395403]
[ 1234.396903] ---[ end trace 0dabd211d3d954a5 ]---
[ 1234.401550] wlan0: failed to set key (4, ff:ff:ff:ff:ff:ff) to hardware (-22)
[ 1834.417579] ------------[ cut here ]------------
[ 1834.422314] WARNING: CPU: 0 PID: 2155 at compat-wireless-2016-10-08/drivers/net/wireless/ath/ath5k/mac80211-ops.c:500 ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]()
[ 1834.436999] Modules linked in: ath9k ath9k_common pppoe ppp_async iptable_nat ath9k_hw ath5k ath pppox ppp_generic nf_nat_pptp nf_nat_ipv4 nf_nat_amanda nf_conntrack_pptp nf_conntrack_ipv6 nf_conntrack_ipv4 nf_conntrack_amanda mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_quota xt_policy xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_id xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_NFQUEUE xt_NFLOG xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc nfnetlink_queue nfnetlink_log nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_rtsp nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtsp nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables crc7 crc_itu_t crc_ccitt compat br_netfilter sch_cake sch_teql em_nbyte sch_codel sch_prio sch_pie act_ipt sch_tbf sch_gred sch_dsmark cls_basic em_text em_meta sch_htb sch_sfq act_police sch_fq em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ifb ip6_vti ip_vti sit ipcomp6 xfrm6_tunnel xfrm6_mode_tunnel xfrm6_mode_transport xfrm6_mode_beet esp6 ah6 ipcomp xfrm4_tunnel xfrm4_mode_tunnel xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 ip6_tunnel tunnel6 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo nls_utf8 nls_iso8859_15 nls_iso8859_1 vxlan udp_tunnel ip6_udp_tunnel sha512_generic sha256_generic sha1_generic seqiv jitterentropy_rng drbg md5 hmac ghash_generic gf128mul gcm echainiv des_generic deflate zlib_inflate zlib_deflate ctr cbc authenc mmc_block usb_storage mmc_core ohci_platform ohci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache button_hotplug input_core usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[ 1834.677481] CPU: 0 PID: 2155 Comm: hostapd Tainted: G        W       4.4.36 #0
[ 1834.684738] Stack : 00000000 00000000 804a6542 00000042 803d7380 00000000 00000001 80450000
[ 1834.684738]    80430000 8043ae43 803d3a34 0000086b 804a379c 00000000 00000000 00000005
[ 1834.684738]    00000000 800a92a4 803d90a0 80430000 00000003 00000000 803d74ac 86b89a54
[ 1834.684738]    804a379c 800a7140 80430000 00000000 80439f50 80201800 00000000 00000000
[ 1834.684738]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1834.684738]    ...
[ 1834.720749] Call Trace:
[ 1834.723226] [] show_stack+0x64/0xb0
[ 1834.727607] [] warn_slowpath_common+0xa0/0xd0
[ 1834.732863] [] warn_slowpath_null+0x18/0x24
[ 1834.737951] [] ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]
[ 1834.744338]
[ 1834.745838] ---[ end trace 0dabd211d3d954a6 ]---
[ 1834.750476] wlan0: failed to set key (5, ff:ff:ff:ff:ff:ff) to hardware (-22)


More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=334


From lede-bugs at lists.infradead.org  Mon Dec 12 04:55:34 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 12 Dec 2016 12:55:34 +0000
Subject: [FS#334] ath5k: kernel warning every 10 minutes
In-Reply-To: <FS334@bugs.lede-project.org>
References: <FS334@bugs.lede-project.org>
Message-ID: <mailman.73545.1481547361.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#334 - ath5k: kernel warning every 10 minutes
User who did this: Stijn Tintel (stintel)
Task details edited:
-------
Device: Ubiquiti Routerstation Pro, 1x Mikrotik R52n, 1x Ubiquiti SR71-A, 1x Ubiquiti XR2
LEDE r2473-b305b8c 

While testing 802.11w on ath5k, I noticed that a kernel warning occurs every 10 minutes, or when running "wifi". This happens even when no clients are associated. To make sure it is unrelated to my 802.11w changes, I tested with unmodified LEDE r2473-b305b8c.

Wireless config:

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '11'
        option country 'BE'
        option hwmode '11g'
        option txpower '10'
        option path 'pci0000:00/0000:00:12.0'
        option disabled '0'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'LEDE'
        option encryption 'psk2'
        option key 'edellede'
        option ieee80211w '2'

config wifi-device 'radio1'
        option type 'mac80211'
        option channel '11'
        option country 'BE'
        option hwmode '11g'
        option txpower '13'
        option path 'pci0000:00/0000:00:11.0'
        option htmode 'HT20'
        option disabled '1'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'LEDE'
        option encryption 'psk2'
        option key 'edellede'
        option ieee80211w '2'

config wifi-device 'radio2'
        option type 'mac80211'
        option channel '11'
        option country 'BE'
        option hwmode '11g'
        option path 'pci0000:00/0000:00:13.0'
        option htmode 'HT20'
        option disabled '1'

config wifi-iface 'default_radio2'
        option device 'radio2'
        option network 'lan'
        option mode 'ap'
        option ssid 'LEDE'
        option encryption 'psk2'
        option key 'edellede'
        option ieee80211w '2'


Kernel log:

[   32.052530] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   32.074984] device wlan0 entered promiscuous mode
[   32.079780] br-lan: port 2(wlan0) entered forwarding state
[   32.085357] br-lan: port 2(wlan0) entered forwarding state
[   32.451638] br-lan: port 2(wlan0) entered disabled state
[   33.749319] ------------[ cut here ]------------
[   33.754055] WARNING: CPU: 0 PID: 1780 at compat-wireless-2016-10-08/drivers/net/wireless/ath/ath5k/mac80211-ops.c:500 ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]()
[   33.768752] Modules linked in: ath9k ath9k_common pppoe ppp_async iptable_nat ath9k_hw ath5k ath pppox ppp_generic nf_nat_pptp nf_nat_ipv4 nf_nat_amanda nf_conntrack_pptp nf_conntrack_ipv6 nf_conntrack_ipv4 nf_conntrack_amanda mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_quota xt_policy xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_id xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_NFQUEUE xt_NFLOG xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc nfnetlink_queue nfnetlink_log nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_rtsp nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtsp nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables crc7 crc_itu_t crc_ccitt compat br_netfilter sch_cake sch_teql em_nbyte sch_codel sch_prio sch_pie act_ipt sch_tbf sch_gred sch_dsmark cls_basic em_text em_meta sch_htb sch_sfq act_police sch_fq em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ifb ip6_vti ip_vti sit ipcomp6 xfrm6_tunnel xfrm6_mode_tunnel xfrm6_mode_transport xfrm6_mode_beet esp6 ah6 ipcomp xfrm4_tunnel xfrm4_mode_tunnel xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 ip6_tunnel tunnel6 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo nls_utf8 nls_iso8859_15 nls_iso8859_1 vxlan udp_tunnel ip6_udp_tunnel sha512_generic sha256_generic sha1_generic seqiv jitterentropy_rng drbg md5 hmac ghash_generic gf128mul gcm echainiv des_generic deflate zlib_inflate zlib_deflate ctr cbc authenc mmc_block usb_storage mmc_core ohci_platform ohci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache button_hotplug input_core usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[   34.009197] CPU: 0 PID: 1780 Comm: hostapd Not tainted 4.4.36 #0
[   34.015227] Stack : 00000000 00000000 804a6542 00000034 803d7380 00000000 00000001 80450000
[   34.015227]    80430000 8043ae43 803d3a34 000006f4 804a379c 00000000 00000000 00000004
[   34.015227]    00000000 800a92a4 803d90a0 80430000 00000003 00000000 803d74ac 86b8ba54
[   34.015227]    804a379c 800a7140 80430000 00000000 00000001 80201800 00000000 00000000
[   34.015227]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   34.015227]    ...
[   34.051247] Call Trace:
[   34.053707] [] show_stack+0x64/0xb0
[   34.058088] [] warn_slowpath_common+0xa0/0xd0
[   34.063344] [] warn_slowpath_null+0x18/0x24
[   34.068432] [] ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]
[   34.074819] 
[   34.076310] ---[ end trace 0dabd211d3d954a3 ]---
[   34.080958] wlan0: failed to set key (4, ff:ff:ff:ff:ff:ff) to hardware (-22)
[   34.088794] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   34.095365] br-lan: port 2(wlan0) entered forwarding state
[   34.100958] br-lan: port 2(wlan0) entered forwarding state
[  633.718441] ------------[ cut here ]------------
[  633.723190] WARNING: CPU: 0 PID: 2155 at compat-wireless-2016-10-08/drivers/net/wireless/ath/ath5k/mac80211-ops.c:500 ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]()
[  633.737896] Modules linked in: ath9k ath9k_common pppoe ppp_async iptable_nat ath9k_hw ath5k ath pppox ppp_generic nf_nat_pptp nf_nat_ipv4 nf_nat_amanda nf_conntrack_pptp nf_conntrack_ipv6 nf_conntrack_ipv4 nf_conntrack_amanda mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_quota xt_policy xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_id xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_NFQUEUE xt_NFLOG xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc nfnetlink_queue nfnetlink_log nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_rtsp nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtsp nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables crc7 crc_itu_t crc_ccitt compat br_netfilter sch_cake sch_teql em_nbyte sch_codel sch_prio sch_pie act_ipt sch_tbf sch_gred sch_dsmark cls_basic em_text em_meta sch_htb sch_sfq act_police sch_fq em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ifb ip6_vti ip_vti sit ipcomp6 xfrm6_tunnel xfrm6_mode_tunnel xfrm6_mode_transport xfrm6_mode_beet esp6 ah6 ipcomp xfrm4_tunnel xfrm4_mode_tunnel xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 ip6_tunnel tunnel6 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo nls_utf8 nls_iso8859_15 nls_iso8859_1 vxlan udp_tunnel ip6_udp_tunnel sha512_generic sha256_generic sha1_generic seqiv jitterentropy_rng drbg md5 hmac ghash_generic gf128mul gcm echainiv des_generic deflate zlib_inflate zlib_deflate ctr cbc authenc mmc_block usb_storage mmc_core ohci_platform ohci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache button_hotplug input_core usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[  633.978364] CPU: 0 PID: 2155 Comm: hostapd Tainted: G        W       4.4.36 #0
[  633.985621] Stack : 00000000 00000000 804a6542 00000042 803d7380 00000000 00000001 80450000
[  633.985621]    80430000 8043ae43 803d3a34 0000086b 804a379c 00000000 00000000 00000005
[  633.985621]    00000000 800a92a4 803d90a0 80430000 00000003 00000000 803d74ac 86b89a54
[  633.985621]    804a379c 800a7140 80430000 00000000 80439f50 80201800 00000000 00000000
[  633.985621]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[  633.985621]    ...
[  634.021615] Call Trace:
[  634.024083] [] show_stack+0x64/0xb0
[  634.028465] [] warn_slowpath_common+0xa0/0xd0
[  634.033721] [] warn_slowpath_null+0x18/0x24
[  634.038810] [] ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]
[  634.045208] 
[  634.046704] ---[ end trace 0dabd211d3d954a4 ]---
[  634.051353] wlan0: failed to set key (5, ff:ff:ff:ff:ff:ff) to hardware (-22)
[ 1234.068642] ------------[ cut here ]------------
[ 1234.073426] WARNING: CPU: 0 PID: 2155 at compat-wireless-2016-10-08/drivers/net/wireless/ath/ath5k/mac80211-ops.c:500 ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]()
[ 1234.088094] Modules linked in: ath9k ath9k_common pppoe ppp_async iptable_nat ath9k_hw ath5k ath pppox ppp_generic nf_nat_pptp nf_nat_ipv4 nf_nat_amanda nf_conntrack_pptp nf_conntrack_ipv6 nf_conntrack_ipv4 nf_conntrack_amanda mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_quota xt_policy xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_id xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_NFQUEUE xt_NFLOG xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc nfnetlink_queue nfnetlink_log nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_rtsp nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtsp nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables crc7 crc_itu_t crc_ccitt compat br_netfilter sch_cake sch_teql em_nbyte sch_codel sch_prio sch_pie act_ipt sch_tbf sch_gred sch_dsmark cls_basic em_text em_meta sch_htb sch_sfq act_police sch_fq em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ifb ip6_vti ip_vti sit ipcomp6 xfrm6_tunnel xfrm6_mode_tunnel xfrm6_mode_transport xfrm6_mode_beet esp6 ah6 ipcomp xfrm4_tunnel xfrm4_mode_tunnel xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 ip6_tunnel tunnel6 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo nls_utf8 nls_iso8859_15 nls_iso8859_1 vxlan udp_tunnel ip6_udp_tunnel sha512_generic sha256_generic sha1_generic seqiv jitterentropy_rng drbg md5 hmac ghash_generic gf128mul gcm echainiv des_generic deflate zlib_inflate zlib_deflate ctr cbc authenc mmc_block usb_storage mmc_core ohci_platform ohci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache button_hotplug input_core usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[ 1234.328545] CPU: 0 PID: 2155 Comm: hostapd Tainted: G        W       4.4.36 #0
[ 1234.335802] Stack : 00000000 00000000 804a6542 00000042 803d7380 00000000 00000001 80450000
[ 1234.335802]    80430000 8043ae43 803d3a34 0000086b 804a379c 00000000 00000000 00000004
[ 1234.335802]    00000000 800a92a4 803d90a0 80430000 00000003 00000000 803d74ac 86b89a54
[ 1234.335802]    804a379c 800a7140 80430000 00000000 80439f50 80201800 00000000 00000000
[ 1234.335802]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1234.335802]    ...
[ 1234.371822] Call Trace:
[ 1234.374290] [] show_stack+0x64/0xb0
[ 1234.378671] [] warn_slowpath_common+0xa0/0xd0
[ 1234.383928] [] warn_slowpath_null+0x18/0x24
[ 1234.389014] [] ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]
[ 1234.395403]
[ 1234.396903] ---[ end trace 0dabd211d3d954a5 ]---
[ 1234.401550] wlan0: failed to set key (4, ff:ff:ff:ff:ff:ff) to hardware (-22)
[ 1834.417579] ------------[ cut here ]------------
[ 1834.422314] WARNING: CPU: 0 PID: 2155 at compat-wireless-2016-10-08/drivers/net/wireless/ath/ath5k/mac80211-ops.c:500 ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]()
[ 1834.436999] Modules linked in: ath9k ath9k_common pppoe ppp_async iptable_nat ath9k_hw ath5k ath pppox ppp_generic nf_nat_pptp nf_nat_ipv4 nf_nat_amanda nf_conntrack_pptp nf_conntrack_ipv6 nf_conntrack_ipv4 nf_conntrack_amanda mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_quota xt_policy xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_id xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_NFQUEUE xt_NFLOG xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc nfnetlink_queue nfnetlink_log nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_rtsp nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtsp nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables crc7 crc_itu_t crc_ccitt compat br_netfilter sch_cake sch_teql em_nbyte sch_codel sch_prio sch_pie act_ipt sch_tbf sch_gred sch_dsmark cls_basic em_text em_meta sch_htb sch_sfq act_police sch_fq em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ifb ip6_vti ip_vti sit ipcomp6 xfrm6_tunnel xfrm6_mode_tunnel xfrm6_mode_transport xfrm6_mode_beet esp6 ah6 ipcomp xfrm4_tunnel xfrm4_mode_tunnel xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 ip6_tunnel tunnel6 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo nls_utf8 nls_iso8859_15 nls_iso8859_1 vxlan udp_tunnel ip6_udp_tunnel sha512_generic sha256_generic sha1_generic seqiv jitterentropy_rng drbg md5 hmac ghash_generic gf128mul gcm echainiv des_generic deflate zlib_inflate zlib_deflate ctr cbc authenc mmc_block usb_storage mmc_core ohci_platform ohci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache button_hotplug input_core usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[ 1834.677481] CPU: 0 PID: 2155 Comm: hostapd Tainted: G        W       4.4.36 #0
[ 1834.684738] Stack : 00000000 00000000 804a6542 00000042 803d7380 00000000 00000001 80450000
[ 1834.684738]    80430000 8043ae43 803d3a34 0000086b 804a379c 00000000 00000000 00000005
[ 1834.684738]    00000000 800a92a4 803d90a0 80430000 00000003 00000000 803d74ac 86b89a54
[ 1834.684738]    804a379c 800a7140 80430000 00000000 80439f50 80201800 00000000 00000000
[ 1834.684738]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1834.684738]    ...
[ 1834.720749] Call Trace:
[ 1834.723226] [] show_stack+0x64/0xb0
[ 1834.727607] [] warn_slowpath_common+0xa0/0xd0
[ 1834.732863] [] warn_slowpath_null+0x18/0x24
[ 1834.737951] [] ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]
[ 1834.744338]
[ 1834.745838] ---[ end trace 0dabd211d3d954a6 ]---
[ 1834.750476] wlan0: failed to set key (5, ff:ff:ff:ff:ff:ff) to hardware (-22)

-------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=334


From lede-bugs at lists.infradead.org  Mon Dec 12 05:00:45 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 12 Dec 2016 13:00:45 +0000
Subject: [FS#334] ath5k: kernel warning every 10 minutes
In-Reply-To: <FS334@bugs.lede-project.org>
References: <FS334@bugs.lede-project.org>
Message-ID: <mailman.73548.1481547671.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#334 - ath5k: kernel warning every 10 minutes
User who did this: Stijn Tintel (stintel)
Task details edited:
-------
Device: Ubiquiti Routerstation Pro, 1x Mikrotik R52n, 1x Ubiquiti SR71-A, 1x Ubiquiti XR2
LEDE r2473-b305b8c 

While testing 802.11w on ath5k, I noticed that a kernel warning occurs every 10 minutes, or when running "wifi". This happens even when no clients are associated. To make sure it is unrelated to my 802.11w changes, I tested with unmodified LEDE r2473-b305b8c.

As this image is built with ath9k enabled, hostapd is compiled with 802.11w support, and the config below works with 802.11w enabled for the ath5k interface. When 802.11w is disabled for the ath5k interface, the kernel warning doesn't occur. As soon as I enable it (optional or required), the kernel warning starts appearing every 10 minutes.

Wireless config:

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '11'
        option country 'BE'
        option hwmode '11g'
        option txpower '10'
        option path 'pci0000:00/0000:00:12.0'
        option disabled '0'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'LEDE'
        option encryption 'psk2'
        option key 'edellede'
        option ieee80211w '2'

config wifi-device 'radio1'
        option type 'mac80211'
        option channel '11'
        option country 'BE'
        option hwmode '11g'
        option txpower '13'
        option path 'pci0000:00/0000:00:11.0'
        option htmode 'HT20'
        option disabled '1'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'LEDE'
        option encryption 'psk2'
        option key 'edellede'
        option ieee80211w '2'

config wifi-device 'radio2'
        option type 'mac80211'
        option channel '11'
        option country 'BE'
        option hwmode '11g'
        option path 'pci0000:00/0000:00:13.0'
        option htmode 'HT20'
        option disabled '1'

config wifi-iface 'default_radio2'
        option device 'radio2'
        option network 'lan'
        option mode 'ap'
        option ssid 'LEDE'
        option encryption 'psk2'
        option key 'edellede'
        option ieee80211w '2'


Kernel log:

[   32.052530] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   32.074984] device wlan0 entered promiscuous mode
[   32.079780] br-lan: port 2(wlan0) entered forwarding state
[   32.085357] br-lan: port 2(wlan0) entered forwarding state
[   32.451638] br-lan: port 2(wlan0) entered disabled state
[   33.749319] ------------[ cut here ]------------
[   33.754055] WARNING: CPU: 0 PID: 1780 at compat-wireless-2016-10-08/drivers/net/wireless/ath/ath5k/mac80211-ops.c:500 ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]()
[   33.768752] Modules linked in: ath9k ath9k_common pppoe ppp_async iptable_nat ath9k_hw ath5k ath pppox ppp_generic nf_nat_pptp nf_nat_ipv4 nf_nat_amanda nf_conntrack_pptp nf_conntrack_ipv6 nf_conntrack_ipv4 nf_conntrack_amanda mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_quota xt_policy xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_id xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_NFQUEUE xt_NFLOG xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc nfnetlink_queue nfnetlink_log nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_rtsp nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtsp nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables crc7 crc_itu_t crc_ccitt compat br_netfilter sch_cake sch_teql em_nbyte sch_codel sch_prio sch_pie act_ipt sch_tbf sch_gred sch_dsmark cls_basic em_text em_meta sch_htb sch_sfq act_police sch_fq em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ifb ip6_vti ip_vti sit ipcomp6 xfrm6_tunnel xfrm6_mode_tunnel xfrm6_mode_transport xfrm6_mode_beet esp6 ah6 ipcomp xfrm4_tunnel xfrm4_mode_tunnel xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 ip6_tunnel tunnel6 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo nls_utf8 nls_iso8859_15 nls_iso8859_1 vxlan udp_tunnel ip6_udp_tunnel sha512_generic sha256_generic sha1_generic seqiv jitterentropy_rng drbg md5 hmac ghash_generic gf128mul gcm echainiv des_generic deflate zlib_inflate zlib_deflate ctr cbc authenc mmc_block usb_storage mmc_core ohci_platform ohci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache button_hotplug input_core usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[   34.009197] CPU: 0 PID: 1780 Comm: hostapd Not tainted 4.4.36 #0
[   34.015227] Stack : 00000000 00000000 804a6542 00000034 803d7380 00000000 00000001 80450000
[   34.015227]    80430000 8043ae43 803d3a34 000006f4 804a379c 00000000 00000000 00000004
[   34.015227]    00000000 800a92a4 803d90a0 80430000 00000003 00000000 803d74ac 86b8ba54
[   34.015227]    804a379c 800a7140 80430000 00000000 00000001 80201800 00000000 00000000
[   34.015227]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   34.015227]    ...
[   34.051247] Call Trace:
[   34.053707] [] show_stack+0x64/0xb0
[   34.058088] [] warn_slowpath_common+0xa0/0xd0
[   34.063344] [] warn_slowpath_null+0x18/0x24
[   34.068432] [] ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]
[   34.074819] 
[   34.076310] ---[ end trace 0dabd211d3d954a3 ]---
[   34.080958] wlan0: failed to set key (4, ff:ff:ff:ff:ff:ff) to hardware (-22)
[   34.088794] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   34.095365] br-lan: port 2(wlan0) entered forwarding state
[   34.100958] br-lan: port 2(wlan0) entered forwarding state
[  633.718441] ------------[ cut here ]------------
[  633.723190] WARNING: CPU: 0 PID: 2155 at compat-wireless-2016-10-08/drivers/net/wireless/ath/ath5k/mac80211-ops.c:500 ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]()
[  633.737896] Modules linked in: ath9k ath9k_common pppoe ppp_async iptable_nat ath9k_hw ath5k ath pppox ppp_generic nf_nat_pptp nf_nat_ipv4 nf_nat_amanda nf_conntrack_pptp nf_conntrack_ipv6 nf_conntrack_ipv4 nf_conntrack_amanda mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_quota xt_policy xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_id xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_NFQUEUE xt_NFLOG xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc nfnetlink_queue nfnetlink_log nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_rtsp nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtsp nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables crc7 crc_itu_t crc_ccitt compat br_netfilter sch_cake sch_teql em_nbyte sch_codel sch_prio sch_pie act_ipt sch_tbf sch_gred sch_dsmark cls_basic em_text em_meta sch_htb sch_sfq act_police sch_fq em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ifb ip6_vti ip_vti sit ipcomp6 xfrm6_tunnel xfrm6_mode_tunnel xfrm6_mode_transport xfrm6_mode_beet esp6 ah6 ipcomp xfrm4_tunnel xfrm4_mode_tunnel xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 ip6_tunnel tunnel6 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo nls_utf8 nls_iso8859_15 nls_iso8859_1 vxlan udp_tunnel ip6_udp_tunnel sha512_generic sha256_generic sha1_generic seqiv jitterentropy_rng drbg md5 hmac ghash_generic gf128mul gcm echainiv des_generic deflate zlib_inflate zlib_deflate ctr cbc authenc mmc_block usb_storage mmc_core ohci_platform ohci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache button_hotplug input_core usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[  633.978364] CPU: 0 PID: 2155 Comm: hostapd Tainted: G        W       4.4.36 #0
[  633.985621] Stack : 00000000 00000000 804a6542 00000042 803d7380 00000000 00000001 80450000
[  633.985621]    80430000 8043ae43 803d3a34 0000086b 804a379c 00000000 00000000 00000005
[  633.985621]    00000000 800a92a4 803d90a0 80430000 00000003 00000000 803d74ac 86b89a54
[  633.985621]    804a379c 800a7140 80430000 00000000 80439f50 80201800 00000000 00000000
[  633.985621]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[  633.985621]    ...
[  634.021615] Call Trace:
[  634.024083] [] show_stack+0x64/0xb0
[  634.028465] [] warn_slowpath_common+0xa0/0xd0
[  634.033721] [] warn_slowpath_null+0x18/0x24
[  634.038810] [] ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]
[  634.045208] 
[  634.046704] ---[ end trace 0dabd211d3d954a4 ]---
[  634.051353] wlan0: failed to set key (5, ff:ff:ff:ff:ff:ff) to hardware (-22)
[ 1234.068642] ------------[ cut here ]------------
[ 1234.073426] WARNING: CPU: 0 PID: 2155 at compat-wireless-2016-10-08/drivers/net/wireless/ath/ath5k/mac80211-ops.c:500 ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]()
[ 1234.088094] Modules linked in: ath9k ath9k_common pppoe ppp_async iptable_nat ath9k_hw ath5k ath pppox ppp_generic nf_nat_pptp nf_nat_ipv4 nf_nat_amanda nf_conntrack_pptp nf_conntrack_ipv6 nf_conntrack_ipv4 nf_conntrack_amanda mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_quota xt_policy xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_id xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_NFQUEUE xt_NFLOG xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc nfnetlink_queue nfnetlink_log nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_rtsp nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtsp nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables crc7 crc_itu_t crc_ccitt compat br_netfilter sch_cake sch_teql em_nbyte sch_codel sch_prio sch_pie act_ipt sch_tbf sch_gred sch_dsmark cls_basic em_text em_meta sch_htb sch_sfq act_police sch_fq em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ifb ip6_vti ip_vti sit ipcomp6 xfrm6_tunnel xfrm6_mode_tunnel xfrm6_mode_transport xfrm6_mode_beet esp6 ah6 ipcomp xfrm4_tunnel xfrm4_mode_tunnel xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 ip6_tunnel tunnel6 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo nls_utf8 nls_iso8859_15 nls_iso8859_1 vxlan udp_tunnel ip6_udp_tunnel sha512_generic sha256_generic sha1_generic seqiv jitterentropy_rng drbg md5 hmac ghash_generic gf128mul gcm echainiv des_generic deflate zlib_inflate zlib_deflate ctr cbc authenc mmc_block usb_storage mmc_core ohci_platform ohci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache button_hotplug input_core usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[ 1234.328545] CPU: 0 PID: 2155 Comm: hostapd Tainted: G        W       4.4.36 #0
[ 1234.335802] Stack : 00000000 00000000 804a6542 00000042 803d7380 00000000 00000001 80450000
[ 1234.335802]    80430000 8043ae43 803d3a34 0000086b 804a379c 00000000 00000000 00000004
[ 1234.335802]    00000000 800a92a4 803d90a0 80430000 00000003 00000000 803d74ac 86b89a54
[ 1234.335802]    804a379c 800a7140 80430000 00000000 80439f50 80201800 00000000 00000000
[ 1234.335802]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1234.335802]    ...
[ 1234.371822] Call Trace:
[ 1234.374290] [] show_stack+0x64/0xb0
[ 1234.378671] [] warn_slowpath_common+0xa0/0xd0
[ 1234.383928] [] warn_slowpath_null+0x18/0x24
[ 1234.389014] [] ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]
[ 1234.395403]
[ 1234.396903] ---[ end trace 0dabd211d3d954a5 ]---
[ 1234.401550] wlan0: failed to set key (4, ff:ff:ff:ff:ff:ff) to hardware (-22)
[ 1834.417579] ------------[ cut here ]------------
[ 1834.422314] WARNING: CPU: 0 PID: 2155 at compat-wireless-2016-10-08/drivers/net/wireless/ath/ath5k/mac80211-ops.c:500 ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]()
[ 1834.436999] Modules linked in: ath9k ath9k_common pppoe ppp_async iptable_nat ath9k_hw ath5k ath pppox ppp_generic nf_nat_pptp nf_nat_ipv4 nf_nat_amanda nf_conntrack_pptp nf_conntrack_ipv6 nf_conntrack_ipv4 nf_conntrack_amanda mac80211 ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_quota xt_policy xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_id xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_NFQUEUE xt_NFLOG xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ts_kmp ts_fsm ts_bm slhc nfnetlink_queue nfnetlink_log nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_rtsp nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtsp nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_broadcast iptable_raw iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables crc7 crc_itu_t crc_ccitt compat br_netfilter sch_cake sch_teql em_nbyte sch_codel sch_prio sch_pie act_ipt sch_tbf sch_gred sch_dsmark cls_basic em_text em_meta sch_htb sch_sfq act_police sch_fq em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables ifb ip6_vti ip_vti sit ipcomp6 xfrm6_tunnel xfrm6_mode_tunnel xfrm6_mode_transport xfrm6_mode_beet esp6 ah6 ipcomp xfrm4_tunnel xfrm4_mode_tunnel xfrm4_mode_transport xfrm4_mode_beet esp4 ah4 ip6_tunnel tunnel6 tunnel4 ip_tunnel tun af_key xfrm_user xfrm_ipcomp xfrm_algo nls_utf8 nls_iso8859_15 nls_iso8859_1 vxlan udp_tunnel ip6_udp_tunnel sha512_generic sha256_generic sha1_generic seqiv jitterentropy_rng drbg md5 hmac ghash_generic gf128mul gcm echainiv des_generic deflate zlib_inflate zlib_deflate ctr cbc authenc mmc_block usb_storage mmc_core ohci_platform ohci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache button_hotplug input_core usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[ 1834.677481] CPU: 0 PID: 2155 Comm: hostapd Tainted: G        W       4.4.36 #0
[ 1834.684738] Stack : 00000000 00000000 804a6542 00000042 803d7380 00000000 00000001 80450000
[ 1834.684738]    80430000 8043ae43 803d3a34 0000086b 804a379c 00000000 00000000 00000005
[ 1834.684738]    00000000 800a92a4 803d90a0 80430000 00000003 00000000 803d74ac 86b89a54
[ 1834.684738]    804a379c 800a7140 80430000 00000000 80439f50 80201800 00000000 00000000
[ 1834.684738]    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1834.684738]    ...
[ 1834.720749] Call Trace:
[ 1834.723226] [] show_stack+0x64/0xb0
[ 1834.727607] [] warn_slowpath_common+0xa0/0xd0
[ 1834.732863] [] warn_slowpath_null+0x18/0x24
[ 1834.737951] [] ath5k_sysfs_unregister+0x78c/0x3bb8 [ath5k]
[ 1834.744338]
[ 1834.745838] ---[ end trace 0dabd211d3d954a6 ]---
[ 1834.750476] wlan0: failed to set key (5, ff:ff:ff:ff:ff:ff) to hardware (-22)

-------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=334


From lede-bugs at lists.infradead.org  Mon Dec 12 05:58:20 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 12 Dec 2016 13:58:20 +0000
Subject: [FS#335] mac80211 : Warning prints in RX_NAPI
In-Reply-To: <FS335@bugs.lede-project.org>
References: <FS335@bugs.lede-project.org>
Message-ID: <mailman.73569.1481551131.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Koen Vandeputte (xback) 

Attached to Project - LEDE Project
Summary - mac80211 : Warning prints in RX_NAPI
Task Type - Bug Report
Category - Kernel
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Hardware:
- Multiple cns3xxx Gateworks Laguna boards in IBSS config
- 4x UBNT SR-71 per device (802.11n 2x2)
- LEDE r2114

No idea how to repro it properly ...


During a check of a device in the field, I noticed lots of these warnings:

[38467.750000] WARNING: CPU: 0 PID: 0 at compat-wireless-2016-10-08/net/mac80211/rx.c:4180 ieee80211_rx_napi+0xe4/0x934 [mac80211]()
[38467.760000] Rate marked as an HT rate but passed status->rate_idx is not an MCS index [0-76]: 126 (0x7e)


Full log:

http://pastebin.com/raw/rzF0XKyy

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=335


From lede-bugs at lists.infradead.org  Mon Dec 12 18:49:50 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 13 Dec 2016 02:49:50 +0000
Subject: [FS#336] ramips: DIR-610 A1 (F25L32PA ROM) stops persisting on cold
 boot
In-Reply-To: <FS336@bugs.lede-project.org>
References: <FS336@bugs.lede-project.org>
Message-ID: <mailman.73649.1481597543.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Victor Shyba (shyba) 

Attached to Project - LEDE Project
Summary - ramips: DIR-610 A1 (F25L32PA ROM) stops persisting on cold boot
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Hi, I am using a DIR-610 A1 with LEDE, but it isn't persisting new data after cold reboots.

LEDE_from_http_recovery.log -- shows it persisting data across reboots while recently flashed
LEDE_from_working_warm_to_cold_boot.log -- shows what happens when power and all cables are reconnected and a cold boot starts. It remembers old data, but doesn't save new data.

Also note that even sysupgrade to another OWRT distro or 'mtd -r erase rootfs_data' does nothing.
LEDE_failsafe_mtd_erase_rootfs_data_does_nothing.log
LEDE_failsafe_sysupgrade_to_OWRT_does_nothing.log

OEM.log and OEM_cold_boot.log -- Shows OEM persisting on cold and warm reboots.

15.01.log -- gkgw asked to add a 15.01 log. It never worked, this is a kernel panic on first boot.

Thank you for this amazing project.
 

One or more files have been attached.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=336


From lede-bugs at lists.infradead.org  Mon Dec 12 19:00:00 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 13 Dec 2016 03:00:00 +0000
Subject: [FS#337] ramips: Review DIR-610 A1 .dts partitions
In-Reply-To: <FS337@bugs.lede-project.org>
References: <FS337@bugs.lede-project.org>
Message-ID: <mailman.73650.1481598024.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Victor Shyba (shyba) 

Attached to Project - LEDE Project
Summary - ramips: Review DIR-610 A1 .dts partitions
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Very Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - **maybe** related: https://bugs.lede-project.org/index.php?do=details&task_id=336

While showing my OEM logs to gkgw on IRC we saw that some partitions are preserved but could be used.
* does 'devconf' needs to be there? (devdata seems to be used: "[   12.413503] rt2800_wmac 10180000.wmac: loaded eeprom from mtd device "devdata")
Also note that while flashing back to OEM I had all my settings recovered. So "devconf" looks like a dlink conf partition.
* What about langpack?
* What's "boot env" and why don't we declare it?

OEM partition table:

F25L32PA(8c 20168c20) (4096 Kbytes)
mtd .name = raspi, .size = 0x00400000 (4M) .erasesize = 0x00010000 (64K) .numeraseregions = 0
seama skip the header
xxxxxxxx: squashfs filesystem found at offset 1376320, magic 73717368 
Creating 8 MTD partitions on "raspi":
0x000000150060-0x0000003cc060 : "rootfs"
0x000000050000-0x0000003e0000 : "upgrade"
0x000000040000-0x000000050000 : "devconf"
0x000000030000-0x000000040000 : "devdata"
0x0000003e0000-0x000000400000 : "langpack"
0x000000000000-0x000000400000 : "flash"
0x000000000000-0x000000030000 : "u-boot"
0x000000030000-0x000000038000 : "boot env"


LEDE partition table:

[    0.591730] m25p80 spi0.0: f25l32pa (4096 Kbytes)
[    0.601305] 4 ofpart partitions found on MTD device spi0.0
[    0.612294] Creating 4 MTD partitions on "spi0.0":
[    0.621908] 0x000000000000-0x000000030000 : "u-boot"
[    0.635583] 0x000000030000-0x000000040000 : "devdata"
[    0.649748] 0x000000040000-0x000000050000 : "factory"
[    0.663859] 0x000000050000-0x000000400000 : "firmware"
[    1.118452] 2 seama-fw partitions found on MTD device firmware
[    1.130191] 0x000000050040-0x000000181000 : "kernel"
[    1.143445] 0x000000181000-0x000000400000 : "rootfs"
[    1.157362] mtd: device 5 (rootfs) set to be root filesystem
[    1.168959] 1 squashfs-split partitions found on MTD device rootfs
[    1.181383] 0x000000335000-0x000000400000 : "rootfs_data"


More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=337


From lede-bugs at lists.infradead.org  Tue Dec 13 00:24:00 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 13 Dec 2016 08:24:00 +0000
Subject: [FS#337] ramips: Review DIR-610 A1 .dts partitions
In-Reply-To: <FS337@bugs.lede-project.org>
References: <FS337@bugs.lede-project.org>
Message-ID: <mailman.73690.1481617464.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#337 - ramips: Review DIR-610 A1 .dts partitions
User who did this - Mathias Kresin (mkresin)

----------
> * does ?devconf? needs to be there? (devdata seems to be used: ?[ 12.413503] rt2800_wmac 10180000.wmac: loaded eeprom from mtd device ?devdata?)

LEDE loads something from this partition. Therefore it is required.

> Also note that while flashing back to OEM I had all my settings recovered. So ?devconf? looks like a dlink conf partition.
> * What about langpack?

Well, none of the partitions exist in LEDE, they are only required by the D-Link firmware. LEDE uses this portion of the flash for kernel+rootfs. I'm not really sure what you asking here.

> * What?s ?boot env? and why don?t we declare it? 

boot env is usually the partition where u-boot stores it's settings. But the whole partitioning scheme of the D-Link firmware is broken.

The wireless calibration data are stored at 0x34000, which is in the u-boot env **and** devdata partition of the OEM firmware. That doesn't make any sense since the wireless data are unrelated to the u-boot env.

It's just the usual hacked/broken OEM firmware thing. Bits are shifted by the OEM till it somehow works. Regardless whether it makes sense or not.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=337#comment1036


From lede-bugs at lists.infradead.org  Tue Dec 13 00:24:08 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 13 Dec 2016 08:24:08 +0000
Subject: [FS#337] ramips: Review DIR-610 A1 .dts partitions
In-Reply-To: <FS337@bugs.lede-project.org>
References: <FS337@bugs.lede-project.org>
Message-ID: <mailman.73691.1481617468.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#337 - ramips: Review DIR-610 A1 .dts partitions
User who did this - Mathias Kresin (mkresin)

Reason for closing: Not a bug
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=337


From lede-bugs at lists.infradead.org  Wed Dec 14 02:19:38 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 14 Dec 2016 10:19:38 +0000
Subject: [FS#338] mt76-2016-11-05 does not compiled
In-Reply-To: <FS338@bugs.lede-project.org>
References: <FS338@bugs.lede-project.org>
Message-ID: <mailman.73962.1481710810.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - George Ivanov (givanov) 

Attached to Project - LEDE Project
Summary - mt76-2016-11-05 does not compiled
Task Type - Bug Report
Category - Kernel
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - High
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - There occurred a compilation error after adding new mt76 support:

some lines from compilation output:

Makefile:1402: recipe for target '_module_/home/development/linux/openwrt/lede_trunk/lede-dvb-ar71xx/build_dir/target-mips_24kc_musl-1.1.15/linux-ar71xx_generic/mt76-2016-11-05' failed
make[4]: *** [_module_/home/development/linux/openwrt/lede_trunk/lede-dvb-ar71xx/build_dir/target-mips_24kc_musl-1.1.15/linux-ar71xx_generic/mt76-2016-11-05] Error 2
make[4]: Leaving directory '/home/development/linux/openwrt/lede_trunk/lede-dvb-ar71xx/build_dir/target-mips_24kc_musl-1.1.15/linux-ar71xx_generic/linux-4.4.38'
Makefile:71: recipe for target '/home/development/linux/openwrt/lede_trunk/lede-dvb-ar71xx/build_dir/target-mips_24kc_musl-1.1.15/linux-ar71xx_generic/mt76-2016-11-05/.built' failed
make[3]: *** [/home/development/linux/openwrt/lede_trunk/lede-dvb-ar71xx/build_dir/target-mips_24kc_musl-1.1.15/linux-ar71xx_generic/mt76-2016-11-05/.built] Error 2

make[3]: Target 'compile' not remade because of errors.
make[3]: Leaving directory '/home/development/linux/openwrt/lede_trunk/lede-dvb-ar71xx/package/kernel/mt76'
package/Makefile:127: recipe for target 'package/kernel/mt76/compile' failed
make[2]: *** [package/kernel/mt76/compile] Error 2

Base compilation platform - Ubuntu 16.04

Best regards,
George Ivanov


More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=338


From lede-bugs at lists.infradead.org  Wed Dec 14 04:03:26 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 14 Dec 2016 12:03:26 +0000
Subject: [FS#338] mt76-2016-11-05 does not compiled
In-Reply-To: <FS338@bugs.lede-project.org>
References: <FS338@bugs.lede-project.org>
Message-ID: <mailman.73982.1481717031.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#338 - mt76-2016-11-05 does not compiled
User who did this - Mathias Kresin (mkresin)

----------
Please provide a full compile log. The few lines you have pasted do not include the real build error.

Please provide the output of:


./scripts/diffconfig.sh


Please show us the commandline you are using for compiling LEDE!

Do you have any local changes in your tree?
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=338#comment1037


From lede-bugs at lists.infradead.org  Wed Dec 14 11:22:01 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 14 Dec 2016 19:22:01 +0000
Subject: [FS#336] ramips: DIR-610 A1 (F25L32PA ROM) stops persisting on cold
 boot
In-Reply-To: <FS336@bugs.lede-project.org>
References: <FS336@bugs.lede-project.org>
Message-ID: <mailman.74035.1481743345.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#336 - ramips: DIR-610 A1 (F25L32PA ROM) stops persisting on cold boot
User who did this - Victor Shyba (shyba)

----------
Better explanation:
LEDE stops writing to flash after a cold reboot.
Steps to reproduce:
(this works)
1. Flash LEDE using uboot HTTP.
2. write to /
3. Reboot. Writing works.
See: LEDE_from_http_recovery.log
(bug is here)
4. Unplug all cables and power. Wait. Plug it all again.
5. Writing fails (LEDE_from_working_warm_to_cold_boot.log)
6. 'mtd -r erase rootfs_data' fails. (LEDE_failsafe_mtd_erase_rootfs_data_does_nothing.log)
7. 'sysupgrade' fails. (LEDE_failsafe_sysupgrade_to_OWRT_does_nothing.log)

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=336#comment1038


From lede-bugs at lists.infradead.org  Wed Dec 14 12:40:35 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 14 Dec 2016 20:40:35 +0000
Subject: [FS#40] lede-ar71xx-generic-uImage-lzma.bin (from trunk de165b66be4)
 for a WNR2000v1 is too big
In-Reply-To: <FS40@bugs.lede-project.org>
References: <FS40@bugs.lede-project.org>
Message-ID: <mailman.74077.1481748061.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#40 - lede-ar71xx-generic-uImage-lzma.bin (from trunk de165b66be4) for a WNR2000v1 is too big
User who did this - Huan Truong (htruong)

----------
wnr2000v1 is now supported in mainline LEDE. Please follow the directions on 

http://www.tnhh.net/mobile/posts/lede-on-wnr2000v1-unsupported-hardware.html

and on my commit 

https://github.com/lede-project/source/pull/611

to get it installed.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=40#comment1039


From lede-bugs at lists.infradead.org  Thu Dec 15 08:16:23 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 15 Dec 2016 16:16:23 +0000
Subject: [FS#339] jool push be breaking ar71xx build
In-Reply-To: <FS339@bugs.lede-project.org>
References: <FS339@bugs.lede-project.org>
Message-ID: <mailman.74231.1481818656.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Kabuli Chana (anomeome) 

Attached to Project - LEDE Project
Summary - jool push be breaking ar71xx build
Task Type - Build Failure
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - [[http://ix.io/1MxL|log]]

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=339


From lede-bugs at lists.infradead.org  Thu Dec 15 08:56:04 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 15 Dec 2016 16:56:04 +0000
Subject: [FS#339] jool push be breaking ar71xx build
In-Reply-To: <FS339@bugs.lede-project.org>
References: <FS339@bugs.lede-project.org>
Message-ID: <mailman.74237.1481821116.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#339 - jool push be breaking ar71xx build
User who did this - Mathias Kresin (mkresin)

Reason for closing: Different project
Additional comments about closing: jool is not part of the LEDE base system. It is maintained as part of the (external/additional) [[https://github.com/openwrt/packages/tree/master/net/jool|packages feed]] which has its own bugtracker.

Would you please open a bug report at https://github.com/openwrt/packages/issues to make sure that the appropriate people get aware of the issue.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=339


From lede-bugs at lists.infradead.org  Thu Dec 15 09:01:57 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 15 Dec 2016 17:01:57 +0000
Subject: [FS#320] relayd feature request
In-Reply-To: <FS320@bugs.lede-project.org>
References: <FS320@bugs.lede-project.org>
Message-ID: <mailman.74238.1481821340.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#320 - relayd feature request
User who did this - Pedro (finas)

----------
cool. extending the init script seems easier.

Thanks for the input. hoping someone will pick this down the road, I had to resort to gargoyle for a specific case where I really needed this functionality and it kills me really.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=320#comment1040


From lede-bugs at lists.infradead.org  Thu Dec 15 13:21:04 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 15 Dec 2016 21:21:04 +0000
Subject: [FS#305] firewall3: when OUTPUT policy != ACCEPT, drops SYN-ACK and
 ICMP responses; locks me out
In-Reply-To: <FS305@bugs.lede-project.org>
References: <FS305@bugs.lede-project.org>
Message-ID: <mailman.74249.1481836889.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#305 - firewall3: when OUTPUT policy != ACCEPT, drops SYN-ACK and ICMP responses; locks me out
User who did this - Stephan G?nther (stephg)

----------
Solved with recent commit:
https://git.lede-project.org/?p=source.git;a=commit;h=2daab45cae3cfc09bae96f4326a3963a7504e86d
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=305#comment1041


From lede-bugs at lists.infradead.org  Fri Dec 16 00:31:02 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 16 Dec 2016 08:31:02 +0000
Subject: [FS#305] firewall3: when OUTPUT policy != ACCEPT, drops SYN-ACK and
 ICMP responses; locks me out
In-Reply-To: <FS305@bugs.lede-project.org>
References: <FS305@bugs.lede-project.org>
Message-ID: <mailman.74297.1481877087.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#305 - firewall3: when OUTPUT policy != ACCEPT, drops SYN-ACK and ICMP responses; locks me out
User who did this - Mathias Kresin (mkresin)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=305


From lede-bugs at lists.infradead.org  Fri Dec 16 00:31:59 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 16 Dec 2016 08:31:59 +0000
Subject: [FS#338] mt76-2016-11-05 does not compiled
In-Reply-To: <FS338@bugs.lede-project.org>
References: <FS338@bugs.lede-project.org>
Message-ID: <mailman.74298.1481877142.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#338 - mt76-2016-11-05 does not compiled
User who did this - Mathias Kresin (mkresin)

Reason for closing: Fixed
Additional comments about closing: Most likely fixed with https://git.lede-project.org/fb237477fd1e7801e4877f9fe1ea7bc1ec16dd99. If it's still an issue, please reopen the ticket.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=338


From lede-bugs at lists.infradead.org  Fri Dec 16 00:50:03 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 16 Dec 2016 08:50:03 +0000
Subject: [FS#330] xrx200-net: kenrel panic
In-Reply-To: <FS330@bugs.lede-project.org>
References: <FS330@bugs.lede-project.org>
Message-ID: <mailman.74301.1481878226.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#330 - xrx200-net: kenrel panic
User who did this: Mathias Kresin (mkresin)
Summary: From Lede 2443 ownwards on WND3700v4 causes panic on BT Home Hub 5 on boot -> xrx200-net: kenrel panic
Task details edited:
-------
Supply the following if possible:
 - Device problem occurs on Bt Home Hub 5 Type A (caused by WNDR3700v4)
 - Software versions of LEDE release from 2395 on BT Home Hub 5, from 2443 on WNDR3700v4
 - Steps to reproduce
   
Bt Home Hub 5 is connected to the internet via ADSL and acquires a subnet.
The 4 ports Switch is on the fixed public IP Internet subnet, 1 port connected to WNDR3700v4 WAN port and the others to servers on fixed public IP subnet.
The red Ethernet is not connected.
Masquerading is not configured, used as proper router.
WiFi Disabled

WNDR3700v4 WAN port connected to BT Home Hub 5 Switch and assigned 1 IP in the public subnet
WNDR3700v4 4 port switch connected to local switch and other devices on local private lan.
Configured for Masquerading from LAN and WiFi to WAN.

Bt Home Hub 5 panics at boot only if:
1) the 4 port switch is connected to the WNDR3700v4 WAN port
2) WNDR3700v4 runs LEDE > r2393. I have no releases between r2393 and r2443, thus it begins to happen if I upgrade WNDR3700v4 to 2443.

It is really peculiar because a firmware upgrade on one router, WNDR3700v4, causes a panic on a Home Hub 5 type!

If I downgrade WNDR3700v4 to r2393, I can reboot the Home Hub as many times as I want and there is no panic.

Attached is the boot console log from Home Hub 5


[    3.877651] init: - preinit -
[    4.072951] Reserved instruction in kernel code[#1]:
[    4.076461] CPU: 0 PID: 391 Comm: ip Not tainted 4.4.36 #0
[    4.081940] task: 87d20f00 ti: 87f9c000 task.ti: 87f9c000
[    4.087330] $ 0   : 00000000 00000000 97ff97ff 00000000
[    4.092552] $ 4   : afffffdf 87c0f6c0 00000020 00000000
[    4.097774] $ 8   : 00000040 87e17962 00000000 00000000
[    4.102996] $12   : 10032094 7737d2b0 00000000 00400bd4
[    4.108219] $16   : 87c0f6c0 afffffdf 87c0f6c0 afffffdf
[    4.113441] $20   : 00000000 c0000000 00000020 87d14800
[    4.118664] $24   : 00000000 800285d0                  
[    4.123886] $28   : 87f9c000 87f9db68 8066c878 802e76bc
[    4.129109] Hi    : 000001cb
[    4.131981] Lo    : 00001e75
[    4.134861] epc   : 97ff97ff 0x97ff97ff
[    4.138708] ra    : 802e76bc eth_type_trans+0x30/0x210
[    4.143819] Status: 1100fc03	KERNEL EXL IE 
[    4.147999] Cause : 10800028 (ExcCode 0a)
[    4.152002] PrId  : 00019556 (MIPS 34Kc)
[    4.155916] Modules linked in: usb_storage dwc2 ledtrig_transient ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug xfs libcrc32c ext4 jbd2 mbcache exportfs cryptomgr aead crypto_null crc32c_generic
[    4.174377] Process ip (pid: 391, threadinfo=87f9c000, task=87d20f00, tls=7737ee50)
[    4.182028] Stack : 87f9c000 87f9db90 8066c878 802c8904 8066cca8 71000040 87c0f6c0 8066cca8
	  00000040 80277ad8 87f380a7 00000b0e 00000000 00000000 8000003f 8049d0ac
	  8066cca8 00000020 00000008 0000012c 804e8960 87f9dbf0 fffedee6 804e0000
	  804f0000 802c8904 00001000 00000003 00000001 8048944c 804f0000 804b350c
	  804e0000 804b3898 87f9dbf0 87f9dbf0 87f9dbf8 87f9dbf8 80643f24 00000004
	  ...
[    4.217542] Call Trace:
[    4.220013] [] net_rx_action+0x118/0x2e0
[    4.224781] [] xrx200_poll_rx+0x134/0x1d8
[    4.229653] [] net_rx_action+0x118/0x2e0
[    4.234456] [] __do_softirq+0x2a0/0x2b8
[    4.239135] [] handle_level_irq+0x100/0x170
[    4.244185] [] xrx200_open+0x128/0x1e8
[    4.248808] [] ltq_hw_irqdispatch+0xa8/0xe4
[    4.253854] [] do_readpage+0x438/0x6a0
[    4.258458] [] ret_from_irq+0x0/0x4
[    4.262815] [] xrx200_open+0x128/0x1e8
[    4.267427] [] xrx200_open+0x128/0x1e8
[    4.272039] [] xrx200_open+0x144/0x1e8
[    4.276649] [] xrx200_open+0x54/0x1e8
[    4.281189] [] __dev_open+0xf0/0x1ac
[    4.285633] [] filemap_map_pages+0x250/0x2f4
[    4.290755] [] __dev_change_flags+0xc0/0x17c
[    4.295901] [] do_set_pte+0x180/0x1d4
[    4.300416] [] dev_change_flags+0x28/0x70
[    4.305286] [] dev_load+0x18/0x8c
[    4.309475] [] devinet_ioctl+0x2b4/0x8a8
[    4.314273] [] sock_ioctl+0x294/0x2f0
[    4.318788] [] do_vfs_ioctl+0x584/0x5ec
[    4.323480] [] d_instantiate+0x24/0x38
[    4.328093] [] sock_alloc_file+0xb8/0x118
[    4.332970] [] __alloc_fd+0xb0/0x208
[    4.337411] [] SyS_ioctl+0x50/0x94
[    4.341676] [] syscall_common+0x30/0x54
[    4.346373] [] __bzero+0xc4/0x164
[    4.350543] 
[    4.352017] 
Code: ffff  ffff  ffff  ffff  ffff  ffff  ffff  ffff 
[    4.358872] ---[ end trace 248345993f4ae135 ]---
[    4.365919] Kernel panic - not syncing: Fatal exception in interrupt
[    4.372104] Rebooting in 1 seconds..

 
-------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=330


From lede-bugs at lists.infradead.org  Fri Dec 16 00:55:21 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 16 Dec 2016 08:55:21 +0000
Subject: [FS#330] xrx200-net: kenrel panic
In-Reply-To: <FS330@bugs.lede-project.org>
References: <FS330@bugs.lede-project.org>
Message-ID: <mailman.74306.1481878546.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#330 - xrx200-net: kenrel panic
User who did this - Mathias Kresin (mkresin)

----------
It is most likely not fixed and unrelated to the WNDR3700v4.

It seams to me some timing related bug. As soon as something changes in the boot timing the issue is either triggered or gone.

I'm aware of two other people who managed to trigger the bug. All of them are using a BT HomeHub 5A. Another report of the panic can be found at http://openwrt.ebilan.co.uk/viewtopic.php?f=7&t=182&p=1461#p1441.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=330#comment1042


From lede-bugs at lists.infradead.org  Fri Dec 16 11:40:59 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 16 Dec 2016 19:40:59 +0000
Subject: [FS#340] brcm63xx: faulty ethernet link detection
In-Reply-To: <FS340@bugs.lede-project.org>
References: <FS340@bugs.lede-project.org>
Message-ID: <mailman.74407.1481917288.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Daniel Gonz?lez Cabanelas (danitool) 

Attached to Project - LEDE Project
Summary - brcm63xx: faulty ethernet link detection
Task Type - Bug Report
Category - Kernel
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Device: Inventel Livebox 1
  * BCM6348 SoC
  * Two ethernet ports:
     * 1 internal phy
     * 1 external phy, Altima AC101 phy

Looks like there is a bug at the ethernet phy driver in the kernel:

  * The eth0 (internal phy) interface doesn't detect LINK activity when connecting/disconnecting the ethernet cable, it's always UP

  * The eth1 (external phy) interface  detects LINK activity when connecting/disconnecting the ethernet cable, but always with **HALF** speed when the cable is connected

[   33.630022] device eth0 entered promiscuous mode
[   33.658602] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[   33.778651] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   35.601615] eth1: link UP - 100/half - flow control off
[   35.617617] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready



With an old Openwrt version (Attitude Adjustment), the LINK detection works perfect on both interfaces
[  140.208000] eth0: link DOWN
[  146.896000] eth1: link UP - 100/full - flow control off
[  146.900000] br-lan: port 1(eth1) entered forwarding state
[  146.908000] br-lan: port 1(eth1) entered forwarding state
[  148.912000] br-lan: port 1(eth1) entered forwarding state
[  204.900000] eth1: link DOWN
[  204.900000] br-lan: port 1(eth1) entered disabled state
[  206.308000] eth0: link UP - 100/full - flow control off



More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=340


From lede-bugs at lists.infradead.org  Sat Dec 17 10:55:55 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 17 Dec 2016 18:55:55 +0000
Subject: [FS#341] ath10k-firmware Makefile references non-existent
 QCA9887_BOARD_FILE_MD5 and QCA9887_FIRMWARE_FILE_MD
In-Reply-To: <FS341@bugs.lede-project.org>
References: <FS341@bugs.lede-project.org>
Message-ID: <mailman.74476.1482001109.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Hannu Nyman (hnyman) 

Attached to Project - LEDE Project
Summary - ath10k-firmware Makefile references non-existent QCA9887_BOARD_FILE_MD5 and QCA9887_FIRMWARE_FILE_MD
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - I noticed today a strangely named downloaded file "board.bin." in /dl after an update, and that made me to investigate a bit.

The commit "treewide: clean up download hashes" eliminated all MD5 hashes from the core Makefiles and replaced the _MD5 hash definitions with _HASH definitions:
https://git.lede-project.org/?p=source.git;a=commitdiff;h=720b99215da295a2e7b4acdef30b58bec6acedc2#patch33

But at least two instances of filenames in ath10k-firmware Makefile were left with references to the deleted _MD5 definition, which leads to hash being absent from the filename.

The block with the wrong references is:

https://git.lede-project.org/?p=source.git;a=blob;f=package/firmware/ath10k-firmware/Makefile;h=a0056547485477b71e39860fbe00ee03205147c2;hb=720b99215da295a2e7b4acdef30b58bec6acedc2#l37

QCA9887_FIRMWARE_FILE:=firmware-5.bin_10.2.4-1.0-00013
QCA9887_FIRMWARE_FILE_HASH:=5966408bd41f309edb595344b8dd088c0fed212debfd91e5f3e8a55ea119c16d
QCA9887_FIRMWARE_FILE_DL:=$(QCA9887_FIRMWARE_FILE).$(QCA9887_FIRMWARE_FILE_MD5)
QCA9887_BOARD_FILE:=board.bin
QCA9887_BOARD_FILE_HASH:=cf4df099f6ee05c181f55ce17297a1d32c61d725eb96246fd315ad5587c42426
QCA9887_BOARD_FILE_DL:=$(QCA9887_BOARD_FILE).$(QCA9887_BOARD_FILE_MD5)


Both filenames are intended to include the hash, but due to the wrong variable, hash gets left out.

I am not sure if that causes any actual damage right now, but at least the file name is not like it is intended to be.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=341


From lede-bugs at lists.infradead.org  Sat Dec 17 11:55:09 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 17 Dec 2016 19:55:09 +0000
Subject: [FS#34] WRT160NL wireless issues
In-Reply-To: <FS34@bugs.lede-project.org>
References: <FS34@bugs.lede-project.org>
Message-ID: <mailman.74482.1482004535.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#34 - WRT160NL wireless issues
User who did this - grega (gregecslo)

----------
Come on guys, no progress?
Archer C7 V2 2.4ghz wifi stops responding after few hours (5ghz works ok), wrt160nl wifi stops immediatley after load is applied...
This is affecting A LOT of devices and no fix or workaround after 6 months...
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=34#comment1043


From lede-bugs at lists.infradead.org  Sat Dec 17 13:13:43 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 17 Dec 2016 21:13:43 +0000
Subject: [FS#340] brcm63xx: faulty ethernet link detection
In-Reply-To: <FS340@bugs.lede-project.org>
References: <FS340@bugs.lede-project.org>
Message-ID: <mailman.74483.1482009246.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#340 - brcm63xx: faulty ethernet link detection
User who did this - Daniel Gonz?lez Cabanelas (danitool)

----------

  * As commented elsewhere the problem with //eth1// can be solved by patching the file bcm63xx_enet.c     memcpy(bcm_enet_shared_base, p, sizeof(bcm_enet_shared_base));
 
-   if (ephy_reset)
-       gpiod_direction_output(ephy_reset, 0);
-
+   if (ephy_reset){
+       gpiod_direction_output(ephy_reset, 1);
+       msleep(50);
+       gpiod_set_value(ephy_reset, 0);
+   }


  * With //eth0// (internal phy) if I boot with the ethernet cable disconnected, the link remains **down forever** even if plug the the ethernet cable. It seems that the link is only detected when the phy is initialized.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=340#comment1044


From lede-bugs at lists.infradead.org  Sat Dec 17 13:29:07 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 17 Dec 2016 21:29:07 +0000
Subject: [FS#317] Archer C7 v2 -> net/core/dev.c:4839 net_rx_action+0x138/0x2c8
In-Reply-To: <FS317@bugs.lede-project.org>
References: <FS317@bugs.lede-project.org>
Message-ID: <mailman.74485.1482010170.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#317 - Archer C7 v2 -> net/core/dev.c:4839 net_rx_action+0x138/0x2c8
User who did this - JD (DoubleQ)

----------
And again with the latest version....

[    0.000000] Linux version 4.4.38 (buildbot at builds) (gcc version 5.4.0 (LEDE GCC 5.4.0 r2400-abedd71) ) #0 Fri Dec 16 10:12:46 2016
[    0.000000] MyLoader: sysp=696b6997, boardp=6969a996, parts=696d6997
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019750 (MIPS 74Kc)


[   75.086188] br-lan: port 3(wlan1) entered forwarding state
[28585.424288] ------------[ cut here ]------------
[28585.429018] WARNING: CPU: 0 PID: 0 at net/core/dev.c:4839 net_rx_action+0x138/0x2c8()
[28585.437008] Modules linked in: pppoe ppp_async iptable_nat ath9k pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 ipt_REJECT ipt_MASQUERADE ath9k_common xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG 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_mangle iptable_filter ip_tables crc_ccitt ath9k_hw ath10k_pci ath10k_core ath mac80211 cfg80211 compat ledtrig_usbport ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables ehci_platform ehci_hcd gpio_button_hotplug usbcore nls_base usb_common
[28585.503550] CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.38 #0
[28585.509377] Stack : 803e1fc4 00000000 00000001 80440000 8042d1d8 8042ce63 803c35f0 00000000
[28585.509377] 	  804a3788 00000040 00000042 0000012c 00000001 800a7268 803c8ce0 80430000
[28585.509377] 	  00000003 00000040 803c70ec 80427c6c 00000001 800a51e4 00000000 00000000
[28585.509377] 	  00000001 801f4b00 00000000 00000000 00000000 00000000 00000000 00000000
[28585.509377] 	  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[28585.509377] 	  ...
[28585.545730] Call Trace:
[28585.548224] [] show_stack+0x50/0x84
[28585.552658] [] warn_slowpath_common+0xa0/0xd0
[28585.557961] [] warn_slowpath_null+0x18/0x24
[28585.563092] [] net_rx_action+0x138/0x2c8
[28585.567960] [] __do_softirq+0x250/0x298
[28585.572757] [] plat_irq_dispatch+0xd4/0x10c
[28585.577882] [] ret_from_irq+0x0/0x4
[28585.582317] [] r4k_wait_irqoff+0x18/0x20
[28585.587177] [] cpu_startup_entry+0x9c/0xe8
[28585.592223] [] start_kernel+0x470/0x490
[28585.596989] 
[28585.598505] ---[ end trace 4c11387fd26fbce7 ]---
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=317#comment1045


From lede-bugs at lists.infradead.org  Mon Dec 19 08:23:19 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 19 Dec 2016 16:23:19 +0000
Subject: [FS#342] iptables v1.4.21: can't initialize iptables table raw
In-Reply-To: <FS342@bugs.lede-project.org>
References: <FS342@bugs.lede-project.org>
Message-ID: <mailman.74627.1482164625.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Hannu Nyman (hnyman) 

Attached to Project - LEDE Project
Summary - iptables v1.4.21: can't initialize iptables table raw
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - I noticed forum discussion about this and then found the error message also in my own system log:
Mon Dec 19 18:07:33 2016 user.notice : iptables v1.4.21: can't initialize iptables table `raw': Table does not exist (do you need to insmod?)
Mon Dec 19 18:07:33 2016 user.notice : Perhaps iptables or your kernel needs to be upgraded.

This is likely due to the recent commit 970dd4dd58 that split out iptable_raw into a separate package. Apparently something still wants to initialise the "raw" table. This error message in the system log may be pure cosmetics, but it looks strange for users.

Commit:
  "kernel: netfilter: split out iptable_raw into a separate package
https://git.lede-project.org/?p=source.git;a=commit;h=970dd4dd58c1f1c1b4cde69a732483aacdc0236a

Present at version: LEDE Reboot SNAPSHOT r2540-6f77b8d510

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=342


From lede-bugs at lists.infradead.org  Mon Dec 19 14:34:20 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 19 Dec 2016 22:34:20 +0000
Subject: [FS#317] Archer C7 v2 -> net/core/dev.c:4839 net_rx_action+0x138/0x2c8
In-Reply-To: <FS317@bugs.lede-project.org>
References: <FS317@bugs.lede-project.org>
Message-ID: <mailman.74666.1482186884.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#317 - Archer C7 v2 -> net/core/dev.c:4839 net_rx_action+0x138/0x2c8
User who did this - Ted Hess (thess)

Reason for closing: Not a bug
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=317


From lede-bugs at lists.infradead.org  Mon Dec 19 14:35:05 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 19 Dec 2016 22:35:05 +0000
Subject: [FS#306] 2.4 GHz WiFi does not work on wndr3700v5
In-Reply-To: <FS306@bugs.lede-project.org>
References: <FS306@bugs.lede-project.org>
Message-ID: <mailman.74667.1482186928.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#306 - 2.4 GHz WiFi does not work on wndr3700v5
User who did this - Ted Hess (thess)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=306


From lede-bugs at lists.infradead.org  Mon Dec 19 14:39:41 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 19 Dec 2016 22:39:41 +0000
Subject: [FS#321] BTHomeHub5 Type A dsl_notify.sh fails to set LED
In-Reply-To: <FS321@bugs.lede-project.org>
References: <FS321@bugs.lede-project.org>
Message-ID: <mailman.74668.1482187205.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#321 - BTHomeHub5 Type A dsl_notify.sh fails to set LED
User who did this - Ted Hess (thess)

----------
@Mathias - please comment so I can accept/deny re-open request.

TIA
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=321#comment1046


From lede-bugs at lists.infradead.org  Mon Dec 19 15:23:47 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 19 Dec 2016 23:23:47 +0000
Subject: [FS#321] BTHomeHub5 Type A dsl_notify.sh fails to set LED
In-Reply-To: <FS321@bugs.lede-project.org>
References: <FS321@bugs.lede-project.org>
Message-ID: <mailman.74671.1482189851.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#321 - BTHomeHub5 Type A dsl_notify.sh fails to set LED
User who did this - Mathias Kresin (mkresin)

----------
Hey Ted,

my opinion on this hasn't changed and I don't see that any further discussion on this would lead to something useful (all caps demand). The change was intentionally and is not a bug.

The "workaround" provided by the reporter doesn't really work as outlined in my first response.

In the end it is a matter of personal preference and I provided everything that is required to restore the old LED behavior. The default for the whole Lantiq target is to indicate the ppp status in case only one LED for xdsl line state and internet connection exists.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=321#comment1047


From lede-bugs at lists.infradead.org  Mon Dec 19 17:46:17 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 20 Dec 2016 01:46:17 +0000
Subject: [FS#321] BTHomeHub5 Type A dsl_notify.sh fails to set LED
In-Reply-To: <FS321@bugs.lede-project.org>
References: <FS321@bugs.lede-project.org>
Message-ID: <mailman.74674.1482198403.1639.lede-bugs@lists.infradead.org>

A Project Manager has denied the request pending for the following task:

FS#321 - BTHomeHub5 Type A dsl_notify.sh fails to set LED
User who did this - Ted Hess (thess)

Reason for denial:
See comments

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=321


From lede-bugs at lists.infradead.org  Tue Dec 20 03:24:21 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 20 Dec 2016 11:24:21 +0000
Subject: [FS#343] [lantig-xrx200] FB7360SL - Link problems on Switch ports
 (2,3,4)
In-Reply-To: <FS343@bugs.lede-project.org>
References: <FS343@bugs.lede-project.org>
Message-ID: <mailman.74752.1482233085.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Guido L. (LipkeGu) 

Attached to Project - LEDE Project
Summary - [lantig-xrx200] FB7360SL - Link problems on Switch ports (2,3,4)
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Supply the following if possible:
 - Fritzbox 7360SL
 - LEDE Reboot CURRENT r2449-7c47f43
 - Plugin a device on the Ports 2,3 or 4. After a while the ports have Link Problems. (sometimes No DHCP, or no link)
   

 

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=343


From lede-bugs at lists.infradead.org  Tue Dec 20 03:43:06 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 20 Dec 2016 11:43:06 +0000
Subject: [FS#94] netifd: PPPoE MTU problem
In-Reply-To: <FS94@bugs.lede-project.org>
References: <FS94@bugs.lede-project.org>
Message-ID: <mailman.74755.1482234211.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#94 - netifd: PPPoE MTU problem
User who did this - Hamy (Hamy)

----------
OpenWrt had this problem for as long as i remember. as a workaround, you can use pppd_options like this:

config interface 'wan'
        option ifname 'ptm0.7'
        option proto 'pppoe'
        ...
        option pppd_options 'mtu 1448'

do NOT change the mtu of the underlying interface and let it be the default of 1500
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=94#comment1048


From lede-bugs at lists.infradead.org  Tue Dec 20 04:07:38 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 20 Dec 2016 12:07:38 +0000
Subject: [FS#343] [lantig-xrx200] FB7360SL - Link problems on Switch ports
 (2,3,4)
In-Reply-To: <FS343@bugs.lede-project.org>
References: <FS343@bugs.lede-project.org>
Message-ID: <mailman.74756.1482235681.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#343 - [lantig-xrx200] FB7360SL - Link problems on Switch ports (2,3,4)
User who did this - Guido L. (LipkeGu)

----------
The Driver for the Switch ATH8030 seems to have problems with handling the ports.

http://www.wehavemorefun.de/fbwiki/images/e/e1/FRITZ%21Box_Fon_WLAN_7360_SL-Bild3.jpg

[    1.085252] eth0: attached PHY [Atheros 8030 ethernet] (phy_addr=0:00, irq=-1)
[    1.153227] eth0: attached PHY [Atheros 8030 ethernet] (phy_addr=0:01, irq=-1)
[    1.221724] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.4] (phy_addr=0:11, irq=-1)
[    1.289721] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.4] (phy_addr=0:13, irq=-1)

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=343#comment1049


From lede-bugs at lists.infradead.org  Tue Dec 20 13:17:21 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 20 Dec 2016 21:17:21 +0000
Subject: [FS#336] ramips: DIR-610 A1 (F25L32PA ROM) stops persisting on cold
 boot
In-Reply-To: <FS336@bugs.lede-project.org>
References: <FS336@bugs.lede-project.org>
Message-ID: <mailman.74877.1482268667.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#336 - ramips: DIR-610 A1 (F25L32PA ROM) stops persisting on cold boot
User who did this - Victor Shyba (shyba)

----------
Working with this kernel patch: https://github.com/shyba/lede-source/commit/caf5e70c97e297903aec56e3ca70ed7035cb587b

PR soon.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=336#comment1050


From lede-bugs at lists.infradead.org  Tue Dec 20 15:03:09 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 20 Dec 2016 23:03:09 +0000
Subject: [FS#257] Xiaomi MiWiFi Mini - unstable 2.4G
In-Reply-To: <FS257@bugs.lede-project.org>
References: <FS257@bugs.lede-project.org>
Message-ID: <mailman.74888.1482275141.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#257 - Xiaomi MiWiFi Mini - unstable 2.4G
User who did this - tom psyborg (psyborg)

----------
it will most likely be a problem with vanilla kernel: https://github.com/openwrt/openwrt/issues/146
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=257#comment1051


From lede-bugs at lists.infradead.org  Tue Dec 20 17:56:33 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 21 Dec 2016 01:56:33 +0000
Subject: [FS#304] ZBT-WG3526 - kernel crash on multiple SSID Wifi  -
 mt7603_mac.c:1205 mt7603_mac_work+0x1bc/0x27
In-Reply-To: <FS304@bugs.lede-project.org>
References: <FS304@bugs.lede-project.org>
Message-ID: <mailman.74889.1482285422.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#304 - ZBT-WG3526 - kernel crash on multiple SSID Wifi  - mt7603_mac.c:1205 mt7603_mac_work+0x1bc/0x27
User who did this - tom psyborg (psyborg)

----------
there was a similar bug on MT7620A maybe the cause is same.. https://dev.openwrt.org/ticket/20338
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=304#comment1052


From lede-bugs at lists.infradead.org  Wed Dec 21 03:36:07 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 21 Dec 2016 11:36:07 +0000
Subject: [FS#304] ZBT-WG3526 - kernel crash on multiple SSID Wifi  -
 mt7603_mac.c:1205 mt7603_mac_work+0x1bc/0x27
In-Reply-To: <FS304@bugs.lede-project.org>
References: <FS304@bugs.lede-project.org>
Message-ID: <mailman.74976.1482320323.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#304 - ZBT-WG3526 - kernel crash on multiple SSID Wifi  - mt7603_mac.c:1205 mt7603_mac_work+0x1bc/0x27
User who did this - camel (camel)

----------
maybe ... but we need someone from the devels to look into. my knowledge is not enough for it.
i guess, that is 1 of the highest prior on the MT76 
:(
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=304#comment1053


From lede-bugs at lists.infradead.org  Wed Dec 21 04:45:18 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 21 Dec 2016 12:45:18 +0000
Subject: [FS#158] AP+STA on MT7620A/N unusable
In-Reply-To: <FS158@bugs.lede-project.org>
References: <FS158@bugs.lede-project.org>
Message-ID: <mailman.74983.1482324342.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#158 - AP+STA on MT7620A/N unusable
User who did this - tom psyborg (psyborg)

----------
it is on 2.4 obviously, since MT7620A is a 2.4 only wisoc.

checked with openwrt, AP+STA works fine on xiaomi mini r49946
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=158#comment1054


From lede-bugs at lists.infradead.org  Wed Dec 21 05:01:11 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 21 Dec 2016 13:01:11 +0000
Subject: [FS#344] UCI Compile error when build with O2
In-Reply-To: <FS344@bugs.lede-project.org>
References: <FS344@bugs.lede-project.org>
Message-ID: <mailman.74984.1482325294.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - gwlim (gwlim) 

Attached to Project - LEDE Project
Summary - UCI Compile error when build with O2
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - On LEDE Latest Tree UCI compiles with Error on O2 I know LEDE by default builds with Os but it doesn't make sense the compile does not pass with O2

make[4]: Entering directory `/home/lede/beta/build_dir/target-mips_74kc+dsp2_musl-1.1.15/uci-2016-07-04.1'
make[5]: Entering directory `/home/lede/beta/build_dir/target-mips_74kc+dsp2_musl-1.1.15/uci-2016-07-04.1'
make[6]: Entering directory `/home/lede/beta/build_dir/target-mips_74kc+dsp2_musl-1.1.15/uci-2016-07-04.1'
make[6]: Leaving directory `/home/lede/beta/build_dir/target-mips_74kc+dsp2_musl-1.1.15/uci-2016-07-04.1'
[ 15%] Built target ucimap
make[6]: Entering directory `/home/lede/beta/build_dir/target-mips_74kc+dsp2_musl-1.1.15/uci-2016-07-04.1'
make[6]: Leaving directory `/home/lede/beta/build_dir/target-mips_74kc+dsp2_musl-1.1.15/uci-2016-07-04.1'
make[6]: Entering directory `/home/lede/beta/build_dir/target-mips_74kc+dsp2_musl-1.1.15/uci-2016-07-04.1'
[ 23%] Building C object CMakeFiles/uci.dir/file.c.o
/home/lede/beta/build_dir/target-mips_74kc+dsp2_musl-1.1.15/uci-2016-07-04.1/file.c: In function 'uci_import':
/home/lede/beta/build_dir/target-mips_74kc+dsp2_musl-1.1.15/uci-2016-07-04.1/file.c:654:28: error: 'pctx' may be used uninitialized in this function [-Werror=maybe-uninitialized]
  struct uci_parse_context *pctx;
                            ^
cc1: all warnings being treated as errors
make[6]: *** [CMakeFiles/uci.dir/file.c.o] Error 1
make[6]: Leaving directory `/home/lede/beta/build_dir/target-mips_74kc+dsp2_musl-1.1.15/uci-2016-07-04.1'
make[5]: *** [CMakeFiles/uci.dir/all] Error 2
make[5]: Leaving directory `/home/lede/beta/build_dir/target-mips_74kc+dsp2_musl-1.1.15/uci-2016-07-04.1'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/home/lede/beta/build_dir/target-mips_74kc+dsp2_musl-1.1.15/uci-2016-07-04.1'
make[3]: *** [/home/lede/beta/build_dir/target-mips_74kc+dsp2_musl-1.1.15/uci-2016-07-04.1/.built] Error 2
make[3]: Leaving directory `/home/lede/beta/package/system/uci'
make[2]: *** [package/system/uci/compile] Error 2
make[2]: Leaving directory `/home/lede/beta'
make[1]: *** [/home/lede/beta/staging_dir/target-mips_74kc+dsp2_musl-1.1.15/stamp/.package_compile] Error 2
make[1]: Leaving directory `/home/lede/beta'


More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=344


From lede-bugs at lists.infradead.org  Wed Dec 21 07:18:19 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 21 Dec 2016 15:18:19 +0000
Subject: [FS#342] iptables v1.4.21: can't initialize iptables table raw
In-Reply-To: <FS342@bugs.lede-project.org>
References: <FS342@bugs.lede-project.org>
Message-ID: <mailman.74989.1482333524.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#342 - iptables v1.4.21: can't initialize iptables table raw
User who did this - Jo-Philipp Wich (jow-)

----------
Can you provide a list of installed packages on your system? firewall3 should not touch raw anymore since http://git.lede-project.org/2daab45
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=342#comment1055


From lede-bugs at lists.infradead.org  Wed Dec 21 07:38:33 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 21 Dec 2016 15:38:33 +0000
Subject: [FS#342] iptables v1.4.21: can't initialize iptables table raw
In-Reply-To: <FS342@bugs.lede-project.org>
References: <FS342@bugs.lede-project.org>
Message-ID: <mailman.74992.1482334737.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#342 - iptables v1.4.21: can't initialize iptables table raw
User who did this - dissent1 (dissent1)

----------
I suspect it's luci-app-firewall that touches it. This msg appears right after opening firewall tab in luci.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=342#comment1056


From lede-bugs at lists.infradead.org  Wed Dec 21 08:11:06 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 21 Dec 2016 16:11:06 +0000
Subject: [FS#342] iptables v1.4.21: can't initialize iptables table raw
In-Reply-To: <FS342@bugs.lede-project.org>
References: <FS342@bugs.lede-project.org>
Message-ID: <mailman.74993.1482336689.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#342 - iptables v1.4.21: can't initialize iptables table raw
User who did this - Jo-Philipp Wich (jow-)

----------
Ah yes. Seems like it requires a LuCI side fix then.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=342#comment1057


From lede-bugs at lists.infradead.org  Wed Dec 21 08:15:11 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 21 Dec 2016 16:15:11 +0000
Subject: [FS#342] iptables v1.4.21: can't initialize iptables table raw
In-Reply-To: <FS342@bugs.lede-project.org>
References: <FS342@bugs.lede-project.org>
Message-ID: <mailman.74994.1482336935.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#342 - iptables v1.4.21: can't initialize iptables table raw
User who did this - Hannu Nyman (hnyman)

----------
> I suspect it's luci-app-firewall that touches it. This msg appears right after opening firewall tab in luci.

Possible. I tested and the error appears after each visit to Status/Firewall ipv4/ipv6 tab.
That luci part is likely coming from this:
https://github.com/openwrt/luci/blob/master/modules/luci-base/luasrc/sys/iptparser.lua#L30

Maybe those three "raw" items should be eliminated from iptparser.lua.


But Luci is not related to boot. And the log message appears at boot, too. So something in the core system tries to access "raw", too.

More context when it comes at boot time:
Wed Dec 21 10:23:01 2016 kern.info kernel: [   40.268370] br-lan: port 1(eth1) entered forwarding state
Wed Dec 21 10:23:01 2016 daemon.notice netifd: Network device 'wlan1' link is up
Wed Dec 21 10:23:01 2016 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Wed Dec 21 10:23:02 2016 user.notice SQM: Starting SQM script: default_cake.qos on eth0, in: 85000 Kbps, out: 10000 Kbps
Wed Dec 21 10:23:02 2016 user.notice : SQM: Starting SQM script: default_cake.qos on eth0, in: 85000 Kbps, out: 10000 Kbps
Wed Dec 21 10:23:02 2016 daemon.err insmod: module is already loaded - act_ipt
Wed Dec 21 10:23:02 2016 daemon.err insmod: module is already loaded - sch_cake
Wed Dec 21 10:23:02 2016 daemon.err insmod: module is already loaded - sch_ingress
Wed Dec 21 10:23:02 2016 daemon.err insmod: module is already loaded - act_mirred
Wed Dec 21 10:23:02 2016 daemon.err insmod: module is already loaded - cls_fw
Wed Dec 21 10:23:02 2016 daemon.err insmod: module is already loaded - cls_flow
Wed Dec 21 10:23:02 2016 daemon.err insmod: module is already loaded - cls_u32
Wed Dec 21 10:23:02 2016 daemon.err insmod: module is already loaded - sch_htb
Wed Dec 21 10:23:02 2016 daemon.err insmod: module is already loaded - sch_hfsc
Wed Dec 21 10:23:02 2016 daemon.notice netifd: radio0 (1038): Using interface wlan0 with hwaddr dc:ef:09:ef:f3:e6 and ssid "HN5WLAN"
Wed Dec 21 10:23:02 2016 user.notice SQM: default_cake.qos was started on eth0 successfully
Wed Dec 21 10:23:02 2016 user.notice : SQM: default_cake.qos was started on eth0 successfully
Wed Dec 21 10:23:02 2016 kern.info kernel: [   40.748526] br-lan: port 2(wlan1) entered forwarding state
Wed Dec 21 10:23:02 2016 kern.info kernel: [   40.950177] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Wed Dec 21 10:23:02 2016 kern.info kernel: [   40.950336] br-lan: port 3(wlan0) entered forwarding state
Wed Dec 21 10:23:02 2016 kern.info kernel: [   40.955652] br-lan: port 3(wlan0) entered forwarding state
Wed Dec 21 10:23:02 2016 daemon.notice netifd: Network device 'wlan0' link is up
Wed Dec 21 10:23:02 2016 daemon.err miniupnpd[1833]: could not open lease file: /var/upnp.leases
Wed Dec 21 10:23:02 2016 daemon.err miniupnpd[1833]: Why did you run me anyway?
Wed Dec 21 10:23:03 2016 user.notice : iptables v1.4.21: can't initialize iptables table `raw': Table does not exist (do you need to insmod?)
Wed Dec 21 10:23:03 2016 user.notice : Perhaps iptables or your kernel needs to be upgraded.
Wed Dec 21 10:23:03 2016 user.notice travelmate-0.2.7[1907] info: travelmate is currently disabled, please set 'trm_enabled' to '1' to use this service
Wed Dec 21 10:23:03 2016 daemon.notice netifd: Interface 'wan6' is now up


List of packages from the manifest:
6in4 - 24-1
6rd - 9-2
6to4 - 12-2
adblock - 2.0.0-1
aiccu - 20070115-16
ath10k-firmware-qca988x - 2016-12-15-fead2ed867af4e107265059b9f578179d7409867-1
ath10k-firmware-qca9984 - 2016-12-15-fead2ed867af4e107265059b9f578179d7409867-1
base-files - 171-r2608-05abcf518d
bcp38 - 5-1
block-mount - 2016-09-31-94a5b0ad8d53f024f036c3526b48c34ebbd66a2f
busybox - 1.25.1-2
ca-certificates - 20161130
ccrypt - 1.10-3
chat - 2.4.7-10
collectd - 5.5.2-4
collectd-mod-conntrack - 5.5.2-4
collectd-mod-cpu - 5.5.2-4
collectd-mod-cpufreq - 5.5.2-4
collectd-mod-entropy - 5.5.2-4
collectd-mod-interface - 5.5.2-4
collectd-mod-iwinfo - 5.5.2-4
collectd-mod-load - 5.5.2-4
collectd-mod-memory - 5.5.2-4
collectd-mod-network - 5.5.2-4
collectd-mod-ping - 5.5.2-4
collectd-mod-rrdtool - 5.5.2-4
collectd-mod-thermal - 5.5.2-4
collectd-mod-uptime - 5.5.2-4
comgt - 0.32-28
curl - 7.51.0-1
ddns-scripts - 2.7.6-7
dnsmasq - 2.76-6
dropbear - 2016.74-1
etherwake - 1.09-4
firewall - 2016-11-29
fstools - 2016-09-31-94a5b0ad8d53f024f036c3526b48c34ebbd66a2f
fwtool - 1
hostapd-common - 2016-12-19-1
hostapd-utils - 2016-12-19-1
htop - 2.0.2-1
ip-tiny - 4.4.0-6
ip6tables - 1.4.21-2
ip6tables-mod-nat - 1.4.21-2
ipset - 6.30-1
iptables - 1.4.21-2
iptables-mod-conntrack-extra - 1.4.21-2
iptables-mod-ipopt - 1.4.21-2
iptables-mod-ipsec - 1.4.21-2
iw - 4.9-1
iwinfo - 2016-09-21-fd9e17be0c43bd6b8df5371f0b353747bc563874
jshn - 2016-11-29-77a629375d7387a33a59509d9d751a8798134cab
jsonfilter - 2016-07-02-dea067ad67d977c247c300c06676a06adf21e0c7
kernel - 4.4.39-1-ed49036a1092dfb4781d02010c12f576
kmod-ata-ahci - 4.4.39-1
kmod-ata-ahci-platform - 4.4.39-1
kmod-ata-core - 4.4.39-1
kmod-ath - 4.4.39+2016-10-08-1
kmod-ath10k - 4.4.39+2016-10-08-1
kmod-cfg80211 - 4.4.39+2016-10-08-1
kmod-crypto-aead - 4.4.39-1
kmod-crypto-crc32c - 4.4.39-1
kmod-crypto-des - 4.4.39-1
kmod-crypto-ecb - 4.4.39-1
kmod-crypto-hash - 4.4.39-1
kmod-crypto-hmac - 4.4.39-1
kmod-crypto-manager - 4.4.39-1
kmod-crypto-md4 - 4.4.39-1
kmod-crypto-md5 - 4.4.39-1
kmod-crypto-null - 4.4.39-1
kmod-crypto-pcompress - 4.4.39-1
kmod-crypto-sha1 - 4.4.39-1
kmod-crypto-sha256 - 4.4.39-1
kmod-fs-cifs - 4.4.39-1
kmod-fs-exfat - 4.4.39+2016-09-26-051167ceccbe75d9d77fc4f5356f5a39a01779e8-1
kmod-fs-ext4 - 4.4.39-1
kmod-fs-hfsplus - 4.4.39-1
kmod-fs-msdos - 4.4.39-1
kmod-fs-ntfs - 4.4.39-1
kmod-fs-vfat - 4.4.39-1
kmod-gpio-button-hotplug - 4.4.39-2
kmod-gre - 4.4.39-1
kmod-ifb - 4.4.39-1
kmod-ip6tables - 4.4.39-1
kmod-ipt-conntrack - 4.4.39-1
kmod-ipt-conntrack-extra - 4.4.39-1
kmod-ipt-core - 4.4.39-1
kmod-ipt-ipopt - 4.4.39-1
kmod-ipt-ipsec - 4.4.39-1
kmod-ipt-ipset - 4.4.39-1
kmod-ipt-nat - 4.4.39-1
kmod-ipt-nat6 - 4.4.39-1
kmod-ipt-nathelper-rtsp - 4.4.39+2.11-1
kmod-iptunnel - 4.4.39-1
kmod-iptunnel4 - 4.4.39-1
kmod-leds-gpio - 4.4.39-1
kmod-lib-crc-ccitt - 4.4.39-1
kmod-lib-crc16 - 4.4.39-1
kmod-mac80211 - 4.4.39+2016-10-08-1
kmod-mppe - 4.4.39-1
kmod-nf-conntrack - 4.4.39-1
kmod-nf-conntrack6 - 4.4.39-1
kmod-nf-ipt - 4.4.39-1
kmod-nf-ipt6 - 4.4.39-1
kmod-nf-nat - 4.4.39-1
kmod-nf-nat6 - 4.4.39-1
kmod-nfnetlink - 4.4.39-1
kmod-nls-base - 4.4.39-1
kmod-nls-cp1250 - 4.4.39-1
kmod-nls-cp437 - 4.4.39-1
kmod-nls-cp850 - 4.4.39-1
kmod-nls-iso8859-1 - 4.4.39-1
kmod-nls-iso8859-15 - 4.4.39-1
kmod-nls-utf8 - 4.4.39-1
kmod-ppp - 4.4.39-1
kmod-pppoe - 4.4.39-1
kmod-pppox - 4.4.39-1
kmod-pptp - 4.4.39-1
kmod-sched - 4.4.39-1
kmod-sched-cake - 4.4.39+2016-12-19-70c8eb766d5afcf3cf187594b7cd776da92bee3c-1
kmod-sched-core - 4.4.39-1
kmod-scsi-core - 4.4.39-1
kmod-sit - 4.4.39-1
kmod-slhc - 4.4.39-1
kmod-tun - 4.4.39-1
kmod-usb-core - 4.4.39-1
kmod-usb-dwc3 - 4.4.39-1
kmod-usb-dwc3-of-simple - 4.4.39-1
kmod-usb-ledtrig-usbport - 4.4.39-1
kmod-usb-ohci - 4.4.39-1
kmod-usb-phy-qcom-dwc3 - 4.4.39-1
kmod-usb-serial - 4.4.39-1
kmod-usb-serial-wwan - 4.4.39-1
kmod-usb-storage - 4.4.39-1
kmod-usb2 - 4.4.39-1
kmod-usb3 - 4.4.39-1
lede-keyring - 2016-04-30-5c7857eed3fa06a9005f96b9b029388c7f316e83
libblobmsg-json - 2016-11-29-77a629375d7387a33a59509d9d751a8798134cab
libc - 1.1.15-1
libcurl - 7.51.0-1
libgcc - 5.4.0-1
libip4tc - 1.4.21-2
libip6tc - 1.4.21-2
libiwinfo - 2016-09-21-fd9e17be0c43bd6b8df5371f0b353747bc563874
libiwinfo-lua - 2016-09-21-fd9e17be0c43bd6b8df5371f0b353747bc563874
libjson-c - 0.12.1-1
libjson-script - 2016-11-29-77a629375d7387a33a59509d9d751a8798134cab
libltdl - 2.4-1
liblua - 5.1.5-1
libmnl - 1.0.4-1
libncursesw - 6.0-1
libnl-tiny - 0.1-5
libopenssl - 1.0.2j-1
liboping - 1.6.2-1
libpcre - 8.39-1
libpthread - 1.1.15-1
librrd1 - 1.0.50-2
librt - 1.1.15-1
libubox - 2016-11-29-77a629375d7387a33a59509d9d751a8798134cab
libubus - 2016-10-12-312448a5b147c221836827a7a641e76a4514db44
libubus-lua - 2016-10-12-312448a5b147c221836827a7a641e76a4514db44
libuci - 2016-07-04.1-1
libuci-lua - 2016-07-04.1-1
libuclient - 2016-07-30-ccb314db2e99463de15eed9d7626360d82aec4d2
libusb-1.0 - 1.0.20-1
libustream-openssl - 2016-07-02-ec80adaa1b47f28d426fa19c692011ce60b992d6
libuuid - 2.28-1
libxtables - 1.4.21-2
lua - 5.1.5-1
luci - git-16.356.28888-08f955d62-1
luci-app-adblock - git-16.356.28888-08f955d62-1
luci-app-bcp38 - 2-1
luci-app-commands - git-16.356.28888-08f955d62-1
luci-app-ddns - 2.4.8-1
luci-app-firewall - git-16.356.28888-08f955d62-1
luci-app-sqm - 1.0.9-1
luci-app-statistics - git-16.356.28888-08f955d62-1
luci-app-travelmate - git-16.356.28888-08f955d62-1
luci-app-upnp - git-16.356.28888-08f955d62-1
luci-app-wol - git-16.356.28888-08f955d62-1
luci-base - git-16.356.28888-08f955d62-1
luci-lib-ip - git-16.356.28888-08f955d62-1
luci-lib-jsonc - git-16.356.28888-08f955d62-1
luci-lib-nixio - git-16.356.28888-08f955d62-1
luci-mod-admin-full - git-16.356.28888-08f955d62-1
luci-proto-3g - git-16.356.28888-08f955d62-1
luci-proto-ipv6 - git-16.356.28888-08f955d62-1
luci-proto-ppp - git-16.356.28888-08f955d62-1
luci-ssl-openssl - git-16.356.28888-08f955d62-1
luci-theme-bootstrap - git-16.356.28888-08f955d62-1
luci-theme-material - git-16.356.28888-08f955d62-1
miniupnpd - 2.0-3
mtd - 21
nano - 2.7.1-1
netifd - 2016-11-21-153a12143b9fef4b5d3c3a6597f6fe967a17c9d7
odhcp6c - 2016-12-16-7533a6243dc3ac5a747cf6ccbc4d0539dafd3e07
odhcpd - 2016-12-17-e05553099c47b92420c21ff30b07709dfa40a84a
openssl-util - 1.0.2j-1
opkg - 9c97d5ecd795709c8584e972bfdf3aee3a5b846d-15
patch - 2.7.5-1
ppp - 2.4.7-10
ppp-mod-pppoe - 2.4.7-10
ppp-mod-pptp - 2.4.7-10
procd - 2016-12-13-f800ecf860addd4fc7f1acde76a9adbd4b1f50e7
procd-nand - 2016-12-13-f800ecf860addd4fc7f1acde76a9adbd4b1f50e7
resolveip - 2
rpcd - 2016-06-30-23417e94d25570e6d62542bac46edd51e8e0243a
rrdtool1 - 1.0.50-2
sqm-scripts - 1.0.9-1
sqm-scripts-extra - 2016-06-08-1
swconfig - 11
tc - 4.4.0-6
terminfo - 6.0-1
travelmate - 0.2.7-1
ubi-utils - 1.5.2-1
uboot-envtools - 2015.10-1
ubox - 2016-09-26-5649c028c426060616e2bd4e7ea83271cd333d21
ubus - 2016-10-12-312448a5b147c221836827a7a641e76a4514db44
ubusd - 2016-10-12-312448a5b147c221836827a7a641e76a4514db44
uci - 2016-07-04.1-1
uclient-fetch - 2016-07-30-ccb314db2e99463de15eed9d7626360d82aec4d2
uhttpd - 2016-10-25-1628fa4b34aa143187353f81e8001b9a15286bda
uhttpd-mod-ubus - 2016-10-25-1628fa4b34aa143187353f81e8001b9a15286bda
usb-modeswitch - 2014-08-26-993a9a542791953c4804f7ddbb3a07756738e37a
usign - 2015-07-04-ef6419142a3b0fbcddcccf536e3c1880302c6f89
vsftpd-tls - 3.0.3-1
wget - 1.18-2
wpad - 2016-12-19-1
zlib - 1.2.8-1

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=342#comment1058


From lede-bugs at lists.infradead.org  Wed Dec 21 08:36:37 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 21 Dec 2016 16:36:37 +0000
Subject: [FS#342] iptables v1.4.21: can't initialize iptables table raw
In-Reply-To: <FS342@bugs.lede-project.org>
References: <FS342@bugs.lede-project.org>
Message-ID: <mailman.74999.1482338221.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#342 - iptables v1.4.21: can't initialize iptables table raw
User who did this - Hannu Nyman (hnyman)

----------
The boot time log item is coming from Luci statistics. And that be triggered from console, too:

root at lede:~# /etc/init.d/luci_statistics restart
iptables v1.4.21: can't initialize iptables table `raw': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.


Sounds strange, but I will look into that more closely.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=342#comment1059


From lede-bugs at lists.infradead.org  Wed Dec 21 08:42:02 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 21 Dec 2016 16:42:02 +0000
Subject: [FS#342] iptables v1.4.21: can't initialize iptables table raw
In-Reply-To: <FS342@bugs.lede-project.org>
References: <FS342@bugs.lede-project.org>
Message-ID: <mailman.75000.1482338545.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#342 - iptables v1.4.21: can't initialize iptables table raw
User who did this - Hannu Nyman (hnyman)

----------
It is caused by the Luci statistics config generation code:
root at lede:~#  /usr/bin/stat-genconfig
iptables v1.4.21: can't initialize iptables table `raw': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.

It accesses the same iptparser.lua as the firewall status page.

https://github.com/openwrt/luci/blob/master/applications/luci-app-statistics/root/usr/bin/stat-genconfig#L120

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=342#comment1060


From lede-bugs at lists.infradead.org  Wed Dec 21 08:44:25 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 21 Dec 2016 16:44:25 +0000
Subject: [FS#342] iptables v1.4.21: can't initialize iptables table raw
In-Reply-To: <FS342@bugs.lede-project.org>
References: <FS342@bugs.lede-project.org>
Message-ID: <mailman.75001.1482338688.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#342 - iptables v1.4.21: can't initialize iptables table raw
User who did this - Hannu Nyman (hnyman)

----------
@jow

Is it ok to just delete the "raw" items fromthe iptparser.lua table lists?

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=342#comment1061


From lede-bugs at lists.infradead.org  Wed Dec 21 08:45:47 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 21 Dec 2016 16:45:47 +0000
Subject: [FS#342] iptables v1.4.21: can't initialize iptables table raw
In-Reply-To: <FS342@bugs.lede-project.org>
References: <FS342@bugs.lede-project.org>
Message-ID: <mailman.75002.1482338769.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#342 - iptables v1.4.21: can't initialize iptables table raw
User who did this - Jo-Philipp Wich (jow-)

----------
Ideally we should check `/proc/net/ip_tables_names` and `/proc/net/ip6_tables_names`
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=342#comment1062


From lede-bugs at lists.infradead.org  Wed Dec 21 09:08:06 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 21 Dec 2016 17:08:06 +0000
Subject: [FS#342] iptables v1.4.21: can't initialize iptables table raw
In-Reply-To: <FS342@bugs.lede-project.org>
References: <FS342@bugs.lede-project.org>
Message-ID: <mailman.75007.1482340110.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#342 - iptables v1.4.21: can't initialize iptables table raw
User who did this - Jo-Philipp Wich (jow-)

----------
I added a fix to LuCI - https://github.com/openwrt/luci/commit/b56d1a85e2fa2ba50b2253e07e41b421a2c20fca
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=342#comment1063


From lede-bugs at lists.infradead.org  Wed Dec 21 23:54:36 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 07:54:36 +0000
Subject: [FS#343] [lantig-xrx200] FB7360SL - Link problems on Switch ports
 (2,3,4)
In-Reply-To: <FS343@bugs.lede-project.org>
References: <FS343@bugs.lede-project.org>
Message-ID: <mailman.75122.1482393429.1639.lede-bugs@lists.infradead.org>

Mathias Kresin has taken ownership of the following task:

FS#343 - [lantig-xrx200] FB7360SL - Link problems on Switch ports (2,3,4)

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=343


From lede-bugs at lists.infradead.org  Wed Dec 21 23:55:22 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 07:55:22 +0000
Subject: [FS#177] ipq806x: USB3 ports fail if booted when USB3 flash drives
 inserted during boot time
In-Reply-To: <FS177@bugs.lede-project.org>
References: <FS177@bugs.lede-project.org>
Message-ID: <mailman.75123.1482393473.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#177 - ipq806x: USB3 ports fail if booted when USB3 flash drives inserted during boot time
User who did this: Mathias Kresin (mkresin)
Status: Waiting on reporter -> New

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=177


From lede-bugs at lists.infradead.org  Wed Dec 21 23:57:41 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 07:57:41 +0000
Subject: [FS#294] linksys 1200ac (and most likely other mvneta) has a
 multi-flow lockout problem
In-Reply-To: <FS294@bugs.lede-project.org>
References: <FS294@bugs.lede-project.org>
Message-ID: <mailman.75124.1482393488.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#294 - linksys 1200ac (and most likely other mvneta) has a multi-flow lockout problem
User who did this - Mathias Kresin (mkresin)

Reason for closing: Fixed
Additional comments about closing: One report that it works again and no response from the original reporter. I assume this one is fixed. If I'm wrong, please reopen the ticket.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=294


From lede-bugs at lists.infradead.org  Wed Dec 21 23:59:47 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 07:59:47 +0000
Subject: [FS#280] iptables kerneltz an hour off from displayed time after DST
In-Reply-To: <FS280@bugs.lede-project.org>
References: <FS280@bugs.lede-project.org>
Message-ID: <mailman.75125.1482393611.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#280 - iptables kerneltz an hour off from displayed time after DST
User who did this - Mathias Kresin (mkresin)

Reason for closing: Deferred
Additional comments about closing: No response from the reporter within more than a month. Please reopen the ticket if you have time to provide the requested output.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=280


From lede-bugs at lists.infradead.org  Thu Dec 22 00:01:48 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 08:01:48 +0000
Subject: [FS#205] Cannot install LEDE on Ubiquiti PicoStation M2
In-Reply-To: <FS205@bugs.lede-project.org>
References: <FS205@bugs.lede-project.org>
Message-ID: <mailman.75126.1482393859.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#205 - Cannot install LEDE on Ubiquiti PicoStation M2
User who did this: Mathias Kresin (mkresin)
Status: Waiting on reporter -> New

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=205


From lede-bugs at lists.infradead.org  Thu Dec 22 00:06:36 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 08:06:36 +0000
Subject: [FS#253] Multicast over wireless ceases to work properly after a
 while on ath9k with many clients connected
In-Reply-To: <FS253@bugs.lede-project.org>
References: <FS253@bugs.lede-project.org>
Message-ID: <mailman.75127.1482394151.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#253 - Multicast over wireless ceases to work properly after a while on ath9k with many clients connected
User who did this - Mathias Kresin (mkresin)

----------
Michael, would you please test again! According to Neils edit, this one should be fixed in the meantime.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=253#comment1064


From lede-bugs at lists.infradead.org  Thu Dec 22 00:06:51 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 08:06:51 +0000
Subject: [FS#253] Multicast over wireless ceases to work properly after a
 while on ath9k with many clients connected
In-Reply-To: <FS253@bugs.lede-project.org>
References: <FS253@bugs.lede-project.org>
Message-ID: <mailman.75128.1482394158.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#253 - Multicast over wireless ceases to work properly after a while on ath9k with many clients connected
User who did this: Mathias Kresin (mkresin)
Status: Unconfirmed -> Waiting on reporter

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=253


From lede-bugs at lists.infradead.org  Thu Dec 22 00:34:11 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 08:34:11 +0000
Subject: [FS#303] ZBT-WG3526 - SQM - kernel error - rcu_sched detected stalls
 on
In-Reply-To: <FS303@bugs.lede-project.org>
References: <FS303@bugs.lede-project.org>
Message-ID: <mailman.75131.1482395676.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#303 - ZBT-WG3526 - SQM - kernel error - rcu_sched detected stalls on
User who did this - Mathias Kresin (mkresin)

Reason for closing: Invalid report
Additional comments about closing: Closed on request of reporter.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=303


From lede-bugs at lists.infradead.org  Thu Dec 22 00:52:43 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 08:52:43 +0000
Subject: [FS#345] Fan script not necessary for WRT1900ACS
In-Reply-To: <FS345@bugs.lede-project.org>
References: <FS345@bugs.lede-project.org>
Message-ID: <mailman.75134.1482396787.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - dkadioglu (dkadioglu) 

Attached to Project - LEDE Project
Summary - Fan script not necessary for WRT1900ACS
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - The fan script /sbin/fan_ctrl.sh for mvebu is not necessary on the WRT1900ACS as it has no fan builtin. So the crontab entry which calls it every 5 minutes could be removed, I think. This would avoid those 'cron.info crond[1564]: USER root pid 10023 cmd /sbin/fan_ctrl.sh' entries in syslog, too.
I'm sorry but, I've got no idea, what an easy fix could look like.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=345


From lede-bugs at lists.infradead.org  Thu Dec 22 04:42:50 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 12:42:50 +0000
Subject: [FS#346] libpcap: error: 'compiler_state_t {aka struct
 _compiler_state}' has no member named 'ai'
In-Reply-To: <FS346@bugs.lede-project.org>
References: <FS346@bugs.lede-project.org>
Message-ID: <mailman.75150.1482410595.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Konstantin Shalygin (k0ste) 

Attached to Project - LEDE Project
Summary - libpcap: error: 'compiler_state_t {aka struct _compiler_state}' has no member named 'ai'
Task Type - Build Failure
Category - Packages
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - High
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - make[4]: Entering directory '/srv/raid/filez/builder/lede/build_dir/target-mips_24kc_musl-1.1.15/libpcap-1.8.1'
mips-openwrt-linux-musl-gcc -Os -pipe -mno-branch-likely -mips32r2 -mtune=24kc -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-var
iable -Wno-error=unused-result -msoft-float -mips16 -minterlink-mips16 -iremap /srv/raid/filez/builder/lede/build_dir/target-mips_24kc_musl-1.1.15/lib
pcap-1.8.1:libpcap-1.8.1 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro -ffunction-sections -fdata-sec
tions -I/srv/raid/filez/builder/lede/build_dir/target-mips_24kc_musl-1.1.15/linux/include -I.  -DBUILDING_PCAP -D_BSD_SOURCE -DHAVE_CONFIG_H  -D_U_="_
_attribute__((unused))" -Os -pipe -mno-branch-likely -mips32r2 -mtune=24kc -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variabl
e -Wno-error=unused-result -msoft-float -mips16 -minterlink-mips16 -iremap /srv/raid/filez/builder/lede/build_dir/target-mips_24kc_musl-1.1.15/libpcap
-1.8.1:libpcap-1.8.1 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro -ffunction-sections -fdata-section
s      -c ./gencode.c
./gencode.c: In function 'pcap_compile':
./gencode.c:693:8: error: 'compiler_state_t {aka struct _compiler_state}' has no member named 'ai'
  cstate.ai = NULL;
        ^
./gencode.c: In function 'gen_gateway':
./gencode.c:4914:13: error: 'cstate' undeclared (first use in this function)
   bpf_error(cstate, "direction applied to 'gateway'");
             ^
./gencode.c:4914:13: note: each undeclared identifier is reported only once for each function it appears in
make[4]: *** [Makefile:495: gencode.o] Error 1
make[4]: Leaving directory '/srv/raid/filez/builder/lede/build_dir/target-mips_24kc_musl-1.1.15/libpcap-1.8.1'
make[3]: *** [Makefile:98: /srv/raid/filez/builder/lede/build_dir/target-mips_24kc_musl-1.1.15/libpcap-1.8.1/.built] Error 2
make[3]: Leaving directory '/srv/raid/filez/builder/lede/package/libs/libpcap'
make[2]: *** [package/Makefile:133: package/libs/libpcap/compile] Error 2
make[2]: Leaving directory '/srv/raid/filez/builder/lede'
make[1]: *** [package/Makefile:128: /srv/raid/filez/builder/lede/staging_dir/target-mips_24kc_musl-1.1.15/stamp/.package_compile] Error 2
make[1]: Leaving directory '/srv/raid/filez/builder/lede'
make: *** [/srv/raid/filez/builder/lede/include/toplevel.mk:199: world] Error 2


More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=346


From lede-bugs at lists.infradead.org  Thu Dec 22 05:31:07 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 13:31:07 +0000
Subject: [FS#341] ath10k-firmware Makefile references non-existent
 QCA9887_BOARD_FILE_MD5 and QCA9887_FIRMWARE_FILE_MD
In-Reply-To: <FS341@bugs.lede-project.org>
References: <FS341@bugs.lede-project.org>
Message-ID: <mailman.75166.1482413491.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#341 - ath10k-firmware Makefile references non-existent QCA9887_BOARD_FILE_MD5 and QCA9887_FIRMWARE_FILE_MD
User who did this - Felix Fietkau (nbd)

----------
Fix pushed in 87b074726, thanks.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=341#comment1065


From lede-bugs at lists.infradead.org  Thu Dec 22 05:31:31 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 13:31:31 +0000
Subject: [FS#341] ath10k-firmware Makefile references non-existent
 QCA9887_BOARD_FILE_MD5 and QCA9887_FIRMWARE_FILE_MD
In-Reply-To: <FS341@bugs.lede-project.org>
References: <FS341@bugs.lede-project.org>
Message-ID: <mailman.75167.1482413515.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#341 - ath10k-firmware Makefile references non-existent QCA9887_BOARD_FILE_MD5 and QCA9887_FIRMWARE_FILE_MD
User who did this - Felix Fietkau (nbd)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=341


From lede-bugs at lists.infradead.org  Thu Dec 22 07:39:08 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 15:39:08 +0000
Subject: [FS#347] VLANs with number > 7 broken after changes to ar8216.c
In-Reply-To: <FS347@bugs.lede-project.org>
References: <FS347@bugs.lede-project.org>
Message-ID: <mailman.75202.1482421173.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Andr? Paul (flux) 

Attached to Project - LEDE Project
Summary - VLANs with number > 7 broken after changes to ar8216.c
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - High
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - A VLAN configuration in /etc/config/network that formerly worked on TP-Link WDR4300 devices does not work anymore with the current trunk version:


config switch_vlan 'VLAN_TEST1'
        option vlan '127'
        option vid '100'
        option device 'switch0'
        option ports '0t 2t 3t 4t 5t'



The issue is caused by high VLAN numbers (127 in this case) as the following swconfig command shows:


root at lede:~# swconfig dev switch0 vlan 127 set vid 100
Failed to set attribute: Invalid input data or parameter


Only VLAN numbers (not VLAN IDs!!) below 8 are accepted by swconfig, while the command

root at lede:~# swconfig dev switch0 help

still outputs the correct maximum number of VLANs, which is 128.

This config


config switch_vlan 'VLAN_TEST1'
        option vlan '7'
        option vid '100'
        option device 'switch0'
        option ports '0t 2t 3t 4t 5t'


_does_ work with the modifications made in commit 5a69f596027ff45d9daf7c6584a8a9d4f7ea0770 and the VLANs are configured correctly, but any VLAN number higher than 7 does _not_ work, so the number of VLANs is limited to 8 which is a bit low compared to the 128 supported by hardware.

The issue can be fixed by replacing AR8X16_MAX_PORTS with AR8X16_MAX_VLANS in line 978 of ar8216.c (commit 5a69f596027ff45d9daf7c6584a8a9d4f7ea0770) so that it looks like this:


if (val->port_vlan >= AR8X16_MAX_VLANS)



More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=347


From lede-bugs at lists.infradead.org  Thu Dec 22 08:09:54 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 16:09:54 +0000
Subject: [FS#284] WRT1900acs, wifi stops workign under havy load
In-Reply-To: <FS284@bugs.lede-project.org>
References: <FS284@bugs.lede-project.org>
Message-ID: <mailman.75224.1482423018.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#284 - WRT1900acs, wifi stops workign under havy load
User who did this - Mathias Kresin (mkresin)

Reason for closing: Fixed
Additional comments about closing: mwlwifi was updated to 10.3.2.0-20161220 with https://git.lede-project.org/24e58c3f72a94ebf659586eb876b06b59adb2bb2

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=284


From lede-bugs at lists.infradead.org  Thu Dec 22 09:55:25 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 17:55:25 +0000
Subject: [FS#348] Dependency issue breaks what was a valid config
In-Reply-To: <FS348@bugs.lede-project.org>
References: <FS348@bugs.lede-project.org>
Message-ID: <mailman.75252.1482429349.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Kabuli Chana (anomeome) 

Attached to Project - LEDE Project
Summary - Dependency issue breaks what was a valid config
Task Type - Build Failure
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Very Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Dependency issue on build packaging, unset libustream-polarssl to resolve.

Configuring dnsmasq-full.
Collected errors:
 * check_data_file_clashes: Package libustream-polarssl wants to install file /home/0util/br/wrtv1/source/build_dir/target-arm_cortex-a9+vfpv3_musl-1.1.15_eabi/root-mvebu/lib/libustream-ssl.so
        But that file is already provided by package  * libustream-mbedtls
 * opkg_install_cmd: Cannot install package libustream-polarssl.
package/Makefile:60: recipe for target 'package/install' failed
make[2]: *** [package/install] Error 255
make[2]: Leaving directory '/home/0util/br/wrtv1/source'
package/Makefile:129: recipe for target '/home/0util/br/wrtv1/source/staging_dir/target-arm_cortex-a9+vfpv3_musl-1.1.15_eabi/stamp/.package_install' failed




More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=348


From lede-bugs at lists.infradead.org  Thu Dec 22 13:33:26 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 21:33:26 +0000
Subject: [FS#347] VLANs with number > 7 broken after changes to ar8216.c
In-Reply-To: <FS347@bugs.lede-project.org>
References: <FS347@bugs.lede-project.org>
Message-ID: <mailman.75273.1482442559.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#347 - VLANs with number > 7 broken after changes to ar8216.c
User who did this - dissent1 (dissent1)

----------
May be lines 978 and 1011 should be swapped?
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=347#comment1066


From lede-bugs at lists.infradead.org  Thu Dec 22 14:51:37 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 22 Dec 2016 22:51:37 +0000
Subject: [FS#348] Dependency issue breaks what was a valid config
In-Reply-To: <FS348@bugs.lede-project.org>
References: <FS348@bugs.lede-project.org>
Message-ID: <mailman.75276.1482447121.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#348 - Dependency issue breaks what was a valid config
User who did this - Jeff (northbound)

----------
Same here.

Collected errors:
 * check_data_file_clashes: Package libustream-polarssl wants to install file /home/jeff/lede3/source/build_dir/target-arm_cortex-a9+vfpv3_musl-1.1.15_eabi/root-mvebu/lib/libustream-ssl.so
	But that file is already provided by package  * libustream-mbedtls
 * opkg_install_cmd: Cannot install package libustream-polarssl.
package/Makefile:60: recipe for target 'package/install' failed
make[2]: *** [package/install] Error 255
make[2]: Leaving directory '/home/jeff/lede3/source'
package/Makefile:129: recipe for target '/home/jeff/lede3/source/staging_dir/target-arm_cortex-a9+vfpv3_musl-1.1.15_eabi/stamp/.package_install' failed
make[1]: *** [/home/jeff/lede3/source/staging_dir/target-arm_cortex-a9+vfpv3_musl-1.1.15_eabi/stamp/.package_install] Error 2
make[1]: Leaving directory '/home/jeff/lede3/source'
Build failed - please re-run with -j1 to see the real error message
/home/jeff/lede3/source/include/toplevel.mk:197: recipe for target 'world' failed
make: *** [world] Error 1
jeff at jeff-VM:~/lede3/source$ 




----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=348#comment1067


From lede-bugs at lists.infradead.org  Thu Dec 22 23:44:35 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 07:44:35 +0000
Subject: [FS#348] Dependency issue breaks what was a valid config
In-Reply-To: <FS348@bugs.lede-project.org>
References: <FS348@bugs.lede-project.org>
Message-ID: <mailman.75304.1482479231.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#348 - Dependency issue breaks what was a valid config
User who did this - Hannu Nyman (hnyman)

----------
You have to de-select libustream-polarssl from your .config (e.g. via menuconfig). 

luci-ssl was changed yesterday to depend on libustream-mbedtls instead of libustream--polarssl. Your old .config likely includes libustream-polarssl, and you need to remove that selection.

https://github.com/openwrt/luci/commit/974194b440572e56d645f148316d53d65fd0a782
> LEDE uses mbedTLS as default SSL provider now and PolarSSL becomes EOL at the end of 2016.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=348#comment1068


From lede-bugs at lists.infradead.org  Fri Dec 23 03:04:27 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 11:04:27 +0000
Subject: [FS#253] Multicast over wireless ceases to work properly after a
 while on ath9k with many clients connected
In-Reply-To: <FS253@bugs.lede-project.org>
References: <FS253@bugs.lede-project.org>
Message-ID: <mailman.75331.1482491223.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#253 - Multicast over wireless ceases to work properly after a while on ath9k with many clients connected
User who did this - Michael Marley (mamarley)

----------
I just tested again with the latest LEDE nightly.  It took about a day this time, but it still stopped passing multicasted RAs over wireless, causing IPv6 to stop working.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=253#comment1069


From lede-bugs at lists.infradead.org  Fri Dec 23 03:15:36 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 11:15:36 +0000
Subject: [FS#253] Multicast over wireless ceases to work properly after a
 while on ath9k with many clients connected
In-Reply-To: <FS253@bugs.lede-project.org>
References: <FS253@bugs.lede-project.org>
Message-ID: <mailman.75332.1482491892.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#253 - Multicast over wireless ceases to work properly after a while on ath9k with many clients connected
User who did this - Mathias Kresin (mkresin)

----------
And the RAs are still broadcasted via wired ethernet? Just to make sure that you don't see a different bug now.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=253#comment1070


From lede-bugs at lists.infradead.org  Fri Dec 23 03:22:01 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 11:22:01 +0000
Subject: [FS#253] Multicast over wireless ceases to work properly after a
 while on ath9k with many clients connected
In-Reply-To: <FS253@bugs.lede-project.org>
References: <FS253@bugs.lede-project.org>
Message-ID: <mailman.75335.1482492273.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#253 - Multicast over wireless ceases to work properly after a while on ath9k with many clients connected
User who did this - Michael Marley (mamarley)

----------
They are indeed.  I can even see the RAs multicasted in response to the RSs I am sending from the wireless PC on the wired PCs, I just can't see any of the RAs from the wireless PCs.  They are still disappearing somewhere inside the wireless subsystem on the WAP because I can see them (with tcpdump) coming in on the WAP's wired interface and leaving through its wireless interface, but they never arrive at the clients.

And you still can't reproduce this with LEDE/OpenWRT and odhcpd sending the RAs because that program unicasts RAs in response to RSs, while radvd multicasts them.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=253#comment1071


From lede-bugs at lists.infradead.org  Fri Dec 23 04:00:27 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 12:00:27 +0000
Subject: [FS#347] VLANs with number > 7 broken after changes to ar8216.c
In-Reply-To: <FS347@bugs.lede-project.org>
References: <FS347@bugs.lede-project.org>
Message-ID: <mailman.75338.1482494451.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#347 - VLANs with number > 7 broken after changes to ar8216.c
User who did this - Andr? Paul (flux)

----------
Could be, but that would mean that val->port_vlan contains the VLAN in one case and the port in the other case.

For my purposes, changing line 978 to AR8X16_MAX_VLANS was sufficient and restored the expected behaviour. So **at least** this line needs to be fixed.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=347#comment1072


From lede-bugs at lists.infradead.org  Fri Dec 23 04:07:35 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 12:07:35 +0000
Subject: [FS#348] Dependency issue breaks what was a valid config
In-Reply-To: <FS348@bugs.lede-project.org>
References: <FS348@bugs.lede-project.org>
Message-ID: <mailman.75342.1482494884.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#348 - Dependency issue breaks what was a valid config
User who did this - Jeff (northbound)

----------
I had read that and I did try to untag but can not untag. Looks like this may be why. Openssl is tagged in luci and there is no longer a choice for polarssl

Symbol: PACKAGE_px5g-polarssl [=y]                                                                               
   Type  : tristate                                                                                                 
   Prompt: px5g-polarssl............... X.509 certificate generator (using polarssl)                                
     Location:                                                                                                      
       -> Utilities                                                                                                 
   (3)   -> Encryption                                                                                              
     Defined at tmp/.config-package.in:77654                                                                        
     Selects: PACKAGE_libpthread [=y] && PACKAGE_libpolarssl [=y] && PACKAGE_libssp [=n] && PACKAGE_librt [=y] &&   
     Selected by: PACKAGE_luci-ssl [=n] && !PACKAGE_px5g-mbedtls [=n] || PACKAGE_luci-ssl-openssl [=y] && !PACKAG    
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=348#comment1073


From lede-bugs at lists.infradead.org  Fri Dec 23 05:36:17 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 13:36:17 +0000
Subject: [FS#348] Dependency issue breaks what was a valid config
In-Reply-To: <FS348@bugs.lede-project.org>
References: <FS348@bugs.lede-project.org>
Message-ID: <mailman.75388.1482500204.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#348 - Dependency issue breaks what was a valid config
User who did this - Jeff (northbound)

----------
Problem is in /source/feeds/luci/collections/luci-ssl makefile and luci-ssl-openssl makefile
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=348#comment1074


From lede-bugs at lists.infradead.org  Fri Dec 23 05:41:09 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 13:41:09 +0000
Subject: [FS#348] Dependency issue breaks what was a valid config
In-Reply-To: <FS348@bugs.lede-project.org>
References: <FS348@bugs.lede-project.org>
Message-ID: <mailman.75391.1482500495.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#348 - Dependency issue breaks what was a valid config
User who did this - Kevin Darbyshire-Bryant (kdarbyshirebryant)

----------
Select px5g-mbedtls and I suspect you'll then be able to do what you want as you'll then be able to unselect px5g-polarssl.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=348#comment1075


From lede-bugs at lists.infradead.org  Fri Dec 23 06:02:39 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 14:02:39 +0000
Subject: [FS#312] GRE tunnel fail to up if df option set to 0
In-Reply-To: <FS312@bugs.lede-project.org>
References: <FS312@bugs.lede-project.org>
Message-ID: <mailman.75392.1482501910.1639.lede-bugs@lists.infradead.org>

Hans Dedecker has taken ownership of the following task:

FS#312 - GRE tunnel fail to up if df option set to 0

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=312


From lede-bugs at lists.infradead.org  Fri Dec 23 06:03:07 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 14:03:07 +0000
Subject: [FS#312] GRE tunnel fail to up if df option set to 0
In-Reply-To: <FS312@bugs.lede-project.org>
References: <FS312@bugs.lede-project.org>
Message-ID: <mailman.75393.1482501939.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#312 - GRE tunnel fail to up if df option set to 0
User who did this: Hans Dedecker (dedeckeh)
Percent Complete: 0% -> 40%

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=312


From lede-bugs at lists.infradead.org  Fri Dec 23 07:12:09 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 15:12:09 +0000
Subject: [FS#253] Multicast over wireless ceases to work properly after a
 while on ath9k with many clients connected
In-Reply-To: <FS253@bugs.lede-project.org>
References: <FS253@bugs.lede-project.org>
Message-ID: <mailman.75394.1482505954.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#253 - Multicast over wireless ceases to work properly after a while on ath9k with many clients connected
User who did this: Mathias Kresin (mkresin)
Status: Waiting on reporter -> New

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=253


From lede-bugs at lists.infradead.org  Fri Dec 23 09:06:04 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 17:06:04 +0000
Subject: [FS#348] Dependency issue breaks what was a valid config
In-Reply-To: <FS348@bugs.lede-project.org>
References: <FS348@bugs.lede-project.org>
Message-ID: <mailman.75399.1482512793.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#348 - Dependency issue breaks what was a valid config
User who did this - Jeff (northbound)

----------
It is compiling again. Thank you @Kevin Darbyshire-Bryant
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=348#comment1076


From lede-bugs at lists.infradead.org  Fri Dec 23 10:25:32 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 18:25:32 +0000
Subject: [FS#347] VLANs with number > 7 broken after changes to ar8216.c
In-Reply-To: <FS347@bugs.lede-project.org>
References: <FS347@bugs.lede-project.org>
Message-ID: <mailman.75403.1482517555.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#347 - VLANs with number > 7 broken after changes to ar8216.c
User who did this - Jo-Philipp Wich (jow-)

Reason for closing: Fixed
Additional comments about closing: http://git.lede-project.org/29cc927

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=347


From lede-bugs at lists.infradead.org  Fri Dec 23 11:29:19 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 19:29:19 +0000
Subject: [FS#349] mwan3 is broken with virtual ifaces
In-Reply-To: <FS349@bugs.lede-project.org>
References: <FS349@bugs.lede-project.org>
Message-ID: <mailman.75431.1482521383.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Kyle Sanderson (KyleSanderson) 

Attached to Project - LEDE Project
Summary - mwan3 is broken with virtual ifaces
Task Type - Bug Report
Category - Packages
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - High
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Supply the following if possible:
 - Device problem occurs on
All
 - Software versions of LEDE release, packages, etc.
Trunk
 - Steps to reproduce
Create a tun iface, use mwan3.
 - When did it last work?
Chaos Calmer.

Asked by Rich B to file here https://forum.lede-project.org/t/criteria-for-first-lede-stable-release/552/33

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=349


From lede-bugs at lists.infradead.org  Fri Dec 23 12:14:18 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 20:14:18 +0000
Subject: [FS#350] Lantiq: ARV4518pw and ARV7518pw both are stuck in endless
 reboots
In-Reply-To: <FS350@bugs.lede-project.org>
References: <FS350@bugs.lede-project.org>
Message-ID: <mailman.75432.1482524210.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Mohammed Berdai (medber) 

Attached to Project - LEDE Project
Summary - Lantiq: ARV4518pw and ARV7518pw both are stuck in endless reboots
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - High
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Both ARV4518pw and ARV7518pw are stuck in endless reboots.

Both can't go beyond this message at boot:
[    0.888130] bootconsole [early0] disabled

This issue appeared in this week's commits.

I included both of their boot logs.



One or more files have been attached.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=350


From lede-bugs at lists.infradead.org  Fri Dec 23 12:22:26 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 20:22:26 +0000
Subject: [FS#351] Lantiq: ARV7510PW22 kernel panic
In-Reply-To: <FS351@bugs.lede-project.org>
References: <FS351@bugs.lede-project.org>
Message-ID: <mailman.75433.1482524570.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Mohammed Berdai (medber) 

Attached to Project - LEDE Project
Summary - Lantiq: ARV7510PW22 kernel panic
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - ARV7510PW22 gets a kernel panic probably due to the switch to dwc2 on danube.

I included the boot log.


One or more files have been attached.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=351


From lede-bugs at lists.infradead.org  Fri Dec 23 12:46:02 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 20:46:02 +0000
Subject: [FS#350] Lantiq: ARV4518pw and ARV7518pw both are stuck in endless
 reboots
In-Reply-To: <FS350@bugs.lede-project.org>
References: <FS350@bugs.lede-project.org>
Message-ID: <mailman.75434.1482525986.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#350 - Lantiq: ARV4518pw and ARV7518pw both are stuck in endless reboots
User who did this - Mathias Kresin (mkresin)

----------
Hey Mohammed,

would you please give the attached patch a try!

Mathias
----------

One or more files have been attached.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=350#comment1077


From lede-bugs at lists.infradead.org  Fri Dec 23 14:52:50 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 22:52:50 +0000
Subject: [FS#177] ipq806x: USB3 ports fail if booted when USB3 flash drives
 inserted during boot time
In-Reply-To: <FS177@bugs.lede-project.org>
References: <FS177@bugs.lede-project.org>
Message-ID: <mailman.75441.1482533597.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#177 - ipq806x: USB3 ports fail if booted when USB3 flash drives inserted during boot time
User who did this - dissent1 (dissent1)

----------
Could you try to apply this patch and check how it goes
https://github.com/dissent1/r7800/commit/398eb31b09c7bb627ab8972cbe79015fedf16ff9.patch
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=177#comment1078


From lede-bugs at lists.infradead.org  Fri Dec 23 14:57:01 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 23 Dec 2016 22:57:01 +0000
Subject: [FS#352] Failed to build Python 3
In-Reply-To: <FS352@bugs.lede-project.org>
References: <FS352@bugs.lede-project.org>
Message-ID: <mailman.75442.1482533843.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Chang Yu-heng (changyuheng) 

Attached to Project - LEDE Project
Summary - Failed to build Python 3
Task Type - Bug Report
Category - Packages
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Supply the following if possible:
 - Device problem occurs on
 - Software versions of LEDE release, packages, etc.
 - Steps to reproduce
   

I just git pull latest LEDE repo and tried to build a image for MT7620A.
Seemed like the just changed curse library (December 20th) isn't compatible with Python 3.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=352


From lede-bugs at lists.infradead.org  Fri Dec 23 19:22:12 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 24 Dec 2016 03:22:12 +0000
Subject: [FS#294] linksys 1200ac (and most likely other mvneta) has a
 multi-flow lockout problem
In-Reply-To: <FS294@bugs.lede-project.org>
References: <FS294@bugs.lede-project.org>
Message-ID: <mailman.75449.1482549889.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#294 - linksys 1200ac (and most likely other mvneta) has a multi-flow lockout problem
User who did this - Dave T?ht (dtaht)

----------
Nope. Not fixed. Tried the Dec 23 build just now. I hit it with > 4 flows, it locks out everything else.

(The way I was dealing with it was with running cake at 900mbit on the
internal ethernet using sqm - which works great, aside from burning a ton of cpu). 

I guess it's one way around bugs like this....

Example test using 12 flows from flent and netperf on the router:

root at apu2:~/t# flent -H 172.26.64.1 -t 'isitfixed'
--te=download_streams=12 tcp_ndown

Warning: Program exited non-zero (1).
Command: /usr/bin/netperf -P 0 -v 0 -D -0.20 -4  -H 172.26.64.1 -t
TCP_MAERTS -l 60 -f m   --   -H 172.26.64.1
Program output:
  netperf: send_omni: connect_data_socket failed: No route to host

Warning: Command produced no valid data.
Data series: TCP download::5
Runner: NetperfDemoRunner
Command: /usr/bin/netperf -P 0 -v 0 -D -0.20 -4  -H 172.26.64.1 -t
TCP_MAERTS -l 60 -f m   --   -H 172.26.64.1
Standard error output:
  netperf: send_omni: connect_data_socket failed: No route to host



----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=294#comment1079


From lede-bugs at lists.infradead.org  Fri Dec 23 20:36:45 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 24 Dec 2016 04:36:45 +0000
Subject: [FS#353] [lantiq-xrx200] ifx-vmmc fails to compile
In-Reply-To: <FS353@bugs.lede-project.org>
References: <FS353@bugs.lede-project.org>
Message-ID: <mailman.75452.1482554229.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Guido L. (LipkeGu) 

Attached to Project - LEDE Project
Summary - [lantiq-xrx200] ifx-vmmc fails to compile
Task Type - Bug Report
Category - Kernel
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - 
 In file included from /home/guido/source/build_dir/target-mips_24kc_musl-1.1.15/linux-lantiq_xrx200/drv_vmmc-1.9.0/src/drv_vmmc_res.h:20:0,
                 from /home/guido/source/build_dir/target-mips_24kc_musl-1.1.15/linux-lantiq_xrx200/drv_vmmc-1.9.0/src/drv_vmmc_alm_priv.h:20,
                 from /home/guido/source/build_dir/target-mips_24kc_musl-1.1.15/linux-lantiq_xrx200/drv_vmmc-1.9.0/src/drv_vmmc_alm.c:20:
/home/guido/source/build_dir/target-mips_24kc_musl-1.1.15/linux-lantiq_xrx200/drv_vmmc-1.9.0/src/drv_vmmc_api.h:35:59: fatal error: ifx_pmcu.h: No such file or directory
compilation terminated.


More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=353


From lede-bugs at lists.infradead.org  Fri Dec 23 21:17:37 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 24 Dec 2016 05:17:37 +0000
Subject: [FS#353] [lantiq-xrx200] ifx-vmmc fails to compile
In-Reply-To: <FS353@bugs.lede-project.org>
References: <FS353@bugs.lede-project.org>
Message-ID: <mailman.75453.1482556681.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#353 - [lantiq-xrx200] ifx-vmmc fails to compile
User who did this - Guido L. (LipkeGu)

----------
As far i found out this error happens when "Power Management is selected"
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=353#comment1080


From lede-bugs at lists.infradead.org  Sat Dec 24 01:49:11 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 24 Dec 2016 09:49:11 +0000
Subject: [FS#353] [lantiq-xrx200] ifx-vmmc fails to compile
In-Reply-To: <FS353@bugs.lede-project.org>
References: <FS353@bugs.lede-project.org>
Message-ID: <mailman.75490.1482573103.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#353 - [lantiq-xrx200] ifx-vmmc fails to compile
User who did this - Mathias Kresin (mkresin)

----------
Please provide the output of:


./scripts/diffconfig.sh

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=353#comment1081


From lede-bugs at lists.infradead.org  Sat Dec 24 04:02:54 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 24 Dec 2016 12:02:54 +0000
Subject: [FS#350] Lantiq: ARV4518pw and ARV7518pw both are stuck in endless
 reboots
In-Reply-To: <FS350@bugs.lede-project.org>
References: <FS350@bugs.lede-project.org>
Message-ID: <mailman.75501.1482580999.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#350 - Lantiq: ARV4518pw and ARV7518pw both are stuck in endless reboots
User who did this - Mohammed Berdai (medber)

----------
Hi Mathias,

I tested your patch today. arv4518pw is still stuck in endless reboots while arv7518pw only finished booting up the first time I flashed the patched firmware. Reflashing didn't resolve the issue. So both are still stuck in endless reboots.

Mohammed
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=350#comment1082


From lede-bugs at lists.infradead.org  Sat Dec 24 04:24:05 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 24 Dec 2016 12:24:05 +0000
Subject: [FS#350] Lantiq: ARV4518pw and ARV7518pw both are stuck in endless
 reboots
In-Reply-To: <FS350@bugs.lede-project.org>
References: <FS350@bugs.lede-project.org>
Message-ID: <mailman.75502.1482582268.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#350 - Lantiq: ARV4518pw and ARV7518pw both are stuck in endless reboots
User who did this - Mathias Kresin (mkresin)

----------
Hey Mohammed,

there are two issues with your devices. The first one is that the serial console doesn't work any longer due to a recent patch. That is what my patch tries to fix.

The second and real problem should be visible as soon as the serial console works again.

Would you please give the attached patch a try. The first one didn't worked the way as I expected.
----------

One or more files have been attached.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=350#comment1083


From lede-bugs at lists.infradead.org  Sat Dec 24 06:52:25 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 24 Dec 2016 14:52:25 +0000
Subject: [FS#294] linksys 1200ac (and most likely other mvneta) has a
 multi-flow lockout problem
In-Reply-To: <FS294@bugs.lede-project.org>
References: <FS294@bugs.lede-project.org>
Message-ID: <mailman.75511.1482591171.1639.lede-bugs@lists.infradead.org>

The following task has been re-opened:

FS#294 - linksys 1200ac (and most likely other mvneta) has a multi-flow lockout problem
User who did this - Mathias Kresin (mkresin)

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=294


From lede-bugs at lists.infradead.org  Sat Dec 24 06:52:41 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 24 Dec 2016 14:52:41 +0000
Subject: [FS#294] linksys 1200ac (and most likely other mvneta) has a
 multi-flow lockout problem
In-Reply-To: <FS294@bugs.lede-project.org>
References: <FS294@bugs.lede-project.org>
Message-ID: <mailman.75512.1482591180.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#294 - linksys 1200ac (and most likely other mvneta) has a multi-flow lockout problem
User who did this: Mathias Kresin (mkresin)
Status: Waiting on reporter -> New

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=294


From lede-bugs at lists.infradead.org  Sat Dec 24 07:00:49 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 24 Dec 2016 15:00:49 +0000
Subject: [FS#343] [lantig-xrx200] FB7360SL - Link problems on Switch ports
 (2,3,4)
In-Reply-To: <FS343@bugs.lede-project.org>
References: <FS343@bugs.lede-project.org>
Message-ID: <mailman.75513.1482591673.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#343 - [lantig-xrx200] FB7360SL - Link problems on Switch ports (2,3,4)
User who did this - Mathias Kresin (mkresin)

Reason for closing: Fixed
Additional comments about closing: https://git.lede-project.org/7dd42d610dcd6f9271d5d44edff52caf633b8abf

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=343


From lede-bugs at lists.infradead.org  Sat Dec 24 07:02:16 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 24 Dec 2016 15:02:16 +0000
Subject: [FS#287] Missing crosscompiler in imagebuilder? (ramips - A5-V11
 platform)
In-Reply-To: <FS287@bugs.lede-project.org>
References: <FS287@bugs.lede-project.org>
Message-ID: <mailman.75516.1482591759.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#287 - Missing crosscompiler in imagebuilder? (ramips - A5-V11 platform)
User who did this - Mathias Kresin (mkresin)

Reason for closing: Fixed
Additional comments about closing: Fixed with the switch to new image build code. (https://git.lede-project.org/0cf581ca3a2a692938003a7038d93f2e24d9125a)

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=287


From lede-bugs at lists.infradead.org  Sat Dec 24 07:46:04 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 24 Dec 2016 15:46:04 +0000
Subject: [FS#354] Error using last source
In-Reply-To: <FS354@bugs.lede-project.org>
References: <FS354@bugs.lede-project.org>
Message-ID: <mailman.75517.1482594387.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - ezar (ezar) 

Attached to Project - LEDE Project
Summary - Error using last source
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - I try to build using latest source, and this error occurs:

Collected errors:
 * check_data_file_clashes: Package libustream-polarssl wants to install file /home/ezarlive/lede/source/build_dir/target-mips_24kc_musl-1.1.15/root-ar71xx/lib/libustream-ssl.so
    But that file is already provided by package  * libustream-mbedtls
 * opkg_install_cmd: Cannot install package libustream-polarssl.
package/Makefile:60: recipe for target 'package/install' failed
make[2]: *** [package/install] Error 255
make[2]: Leaving directory '/home/ezarlive/lede/source'
package/Makefile:129: recipe for target '/home/ezarlive/lede/source/staging_dir/target-mips_24kc_musl-1.1.15/stamp/.package_install' failed
make[1]: *** [/home/ezarlive/lede/source/staging_dir/target-mips_24kc_musl-1.1.15/stamp/.package_install] Error 2
make[1]: Leaving directory '/home/ezarlive/lede/source'
/home/ezarlive/lede/source/include/toplevel.mk:197: recipe for target 'world' failed
make: *** [world] Error 2

 

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=354


From lede-bugs at lists.infradead.org  Sat Dec 24 09:15:26 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 24 Dec 2016 17:15:26 +0000
Subject: [FS#350] Lantiq: ARV4518pw and ARV7518pw both are stuck in endless
 reboots
In-Reply-To: <FS350@bugs.lede-project.org>
References: <FS350@bugs.lede-project.org>
Message-ID: <mailman.75522.1482599879.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#350 - Lantiq: ARV4518pw and ARV7518pw both are stuck in endless reboots
User who did this - Hauke Mehrtens (Hauke)

----------
The normal console does not work on the TP-Link VR200. It has the same first problem as described here.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=350#comment1084


From lede-bugs at lists.infradead.org  Sat Dec 24 10:35:47 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 24 Dec 2016 18:35:47 +0000
Subject: [FS#350] Lantiq: ARV4518pw and ARV7518pw both are stuck in endless
 reboots
In-Reply-To: <FS350@bugs.lede-project.org>
References: <FS350@bugs.lede-project.org>
Message-ID: <mailman.75527.1482604699.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#350 - Lantiq: ARV4518pw and ARV7518pw both are stuck in endless reboots
User who did this - Mohammed Berdai (medber)

----------
Thank you Mathias. It seems related to dwc2 module. I've seen a recent commit that switched the usb module to dwc2 in danube. Maybe that's the cause.

On the other hand I'm going back in time testing older commits for arv4518pw in order to locate the cause of the problem.

I attached the boot log for arv7518pw



----------

One or more files have been attached.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=350#comment1085


From lede-bugs at lists.infradead.org  Sat Dec 24 11:54:27 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 24 Dec 2016 19:54:27 +0000
Subject: [FS#353] [lantiq-xrx200] ifx-vmmc fails to compile
In-Reply-To: <FS353@bugs.lede-project.org>
References: <FS353@bugs.lede-project.org>
Message-ID: <mailman.75534.1482609291.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#353 - [lantiq-xrx200] ifx-vmmc fails to compile
User who did this - Guido L. (LipkeGu)

----------
id did:

  * make distclean
  * git fetch upstream
  * git rebase upstream/master
  * rm .config
  * make menuconfig
  * make -j5


CONFIG_TARGET_lantiq=y
CONFIG_TARGET_lantiq_xrx200=y
CONFIG_TARGET_lantiq_xrx200_DEVICE_FRITZ7360SL=y
CONFIG_PACKAGE_6in4=y
CONFIG_PACKAGE_SAMBA_MAX_DEBUG_LEVEL=-1
CONFIG_PACKAGE_ipset=y
CONFIG_PACKAGE_kmod-crypto-crc32c=y
CONFIG_PACKAGE_kmod-fs-ext4=y
CONFIG_PACKAGE_kmod-fs-vfat=y
CONFIG_PACKAGE_kmod-i2c-algo-bit=y
CONFIG_PACKAGE_kmod-i2c-core=y
CONFIG_PACKAGE_kmod-i2c-gpio=y
CONFIG_PACKAGE_kmod-ipt-ipset=y
CONFIG_PACKAGE_kmod-iptunnel=y
CONFIG_PACKAGE_kmod-iptunnel4=y
CONFIG_PACKAGE_kmod-lib-crc16=y
CONFIG_PACKAGE_kmod-lib-lz4=y
CONFIG_PACKAGE_kmod-lib-lzo=y
CONFIG_PACKAGE_kmod-ltq-tapi=y
CONFIG_PACKAGE_kmod-ltq-vmmc=y
CONFIG_PACKAGE_kmod-nfnetlink=y
CONFIG_PACKAGE_kmod-nls-cp437=y
CONFIG_PACKAGE_kmod-nls-iso8859-1=y
CONFIG_PACKAGE_kmod-nls-utf8=y
CONFIG_PACKAGE_kmod-scsi-core=y
CONFIG_PACKAGE_kmod-sit=y
CONFIG_PACKAGE_kmod-spi-bitbang=y
CONFIG_PACKAGE_kmod-spi-dev=y
CONFIG_PACKAGE_kmod-spi-gpio=y
CONFIG_PACKAGE_kmod-spi-gpio-old=y
CONFIG_PACKAGE_kmod-usb-storage=y
CONFIG_PACKAGE_kmod-zram=y
CONFIG_PACKAGE_libiwinfo=y
CONFIG_PACKAGE_libiwinfo-lua=y
CONFIG_PACKAGE_liblua=y
CONFIG_PACKAGE_libmnl=y
CONFIG_PACKAGE_libncurses=y
CONFIG_PACKAGE_libubus-lua=y
CONFIG_PACKAGE_libuci-lua=y
CONFIG_PACKAGE_lua=y
CONFIG_PACKAGE_luci=y
CONFIG_PACKAGE_luci-app-firewall=y
CONFIG_PACKAGE_luci-base=y
CONFIG_PACKAGE_luci-lib-ip=y
CONFIG_PACKAGE_luci-lib-jsonc=y
CONFIG_PACKAGE_luci-lib-nixio=y
CONFIG_PACKAGE_luci-mod-admin-full=y
CONFIG_PACKAGE_luci-proto-ipv6=y
CONFIG_PACKAGE_luci-proto-ppp=y
CONFIG_PACKAGE_luci-theme-bootstrap=y
CONFIG_PACKAGE_luci-theme-openwrt=y
CONFIG_PACKAGE_nano=y
# CONFIG_PACKAGE_ppp is not set
CONFIG_PACKAGE_ppp-multilink=y
CONFIG_PACKAGE_rpcd=y
CONFIG_PACKAGE_samba36-server=y
CONFIG_PACKAGE_terminfo=y
CONFIG_PACKAGE_uhttpd=y
CONFIG_PACKAGE_uhttpd-mod-ubus=y
CONFIG_PACKAGE_zoneinfo-europe=y
# CONFIG_TARGET_ROOTFS_UBIFS is not set
CONFIG_VOICE_CPE_TAPI_CID=y
CONFIG_VOICE_CPE_TAPI_DECT=y
CONFIG_VOICE_CPE_TAPI_FAX=y
CONFIG_VOICE_CPE_TAPI_HDLC=y
CONFIG_VOICE_CPE_TAPI_KPI=y
CONFIG_VOICE_CPE_TAPI_LINUX_HOTPLUG=y
CONFIG_VOICE_CPE_TAPI_LT_GR909=y
CONFIG_VOICE_CPE_TAPI_METERING=y
CONFIG_VOICE_CPE_TAPI_QOS=y
CONFIG_VOICE_CPE_TAPI_STATISTICS=y
CONFIG_VOICE_CPE_TAPI_TRACES=y
CONFIG_VOICE_CPE_VMMC_DISABLE_DECT_NIBBLE_SWAP=y
CONFIG_VOICE_CPE_VMMC_MPS_HISTORY_SIZE=128
CONFIG_VOICE_CPE_VMMC_PMC=y
CONFIG_VOICE_CPE_VMMC_WITH_DEVICE_VR9=y

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=353#comment1086


From lede-bugs at lists.infradead.org  Sun Dec 25 06:26:00 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 25 Dec 2016 14:26:00 +0000
Subject: [FS#351] Lantiq: ARV7510PW22 kernel panic
In-Reply-To: <FS351@bugs.lede-project.org>
References: <FS351@bugs.lede-project.org>
Message-ID: <mailman.75540.1482675985.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#351 - Lantiq: ARV7510PW22 kernel panic
User who did this - Andreas Gnau (Rondom)

----------
I could reproduce this using the official snapshot cbca3ae92e28432cc311ef11b3b94b894f7e60de, but interestingly it was working fine straight after flashing and only after the first reboot (after configuring everything) it panicked reproducibly on every reboot.

Indeed the dwc2-driver is the culprit. I reverted "lantiq: use dwc2 by default on danube" ffd7c155008bff4b08197dfd710d7a1386313f98 and it works fine.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=351#comment1087


From lede-bugs at lists.infradead.org  Sun Dec 25 07:19:25 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 25 Dec 2016 15:19:25 +0000
Subject: [FS#355] PPPoE kernel panic
In-Reply-To: <FS355@bugs.lede-project.org>
References: <FS355@bugs.lede-project.org>
Message-ID: <mailman.75541.1482679316.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - lucize (lucize) 

Attached to Project - LEDE Project
Summary - PPPoE kernel panic
Task Type - Bug Report
Category - Kernel
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Critical
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - 
x86/64
r2671-f922615

setup pppoe with rp-pppoe-server and devices will crash either the server or the client
it will not crash with my ISP pppoe server


[ 1714.848832] ------------[ cut here ]------------
[ 1714.849621] Kernel BUG at ffffffffa04ebc2c [verbose debug info unavailable]
[ 1714.850717] invalid opcode: 0000 [#1] SMP 
[ 1714.851853] Modules linked in: ath9k ath9k_htc ath9k_common rt2800usb rt2800lib pppoe ppp_async option iptable_nat brcmsmac ath9k_hw ath usb_wwan rt2x00usb rt2x00lib qmi_wwan pppox ppp_mppe ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 mac80211 ipt_REJECT ipt_MASQUERADE huawei_cdc_ncm cfg80211 cdc_ncm cdc_ether xt_time xt_tcpudp xt_tcpmss xt_string xt_statistic xt_state xt_recent xt_quota xt_pkttype xt_physdev xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_hashlimit xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_addrtype xt_TCPMSS xt_REDIRECT xt_NETMAP xt_LOG xt_IPMARK xt_HL xt_DSCP xt_CT xt_CLASSIFY via_rhine usbserial usbnet usbhid ts_kmp ts_fsm ts_bm slhc rfcomm r8169 r8152 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_netlink lib80211_crypt_wep lib80211_crypt_tkip lib80211_crypt_ccmp lib80211 iptable_raw iptable_mangle iptable_filter ipt_ECN ip_tables ip6table_raw hidp hci_uart e1000e e100 crc8 crc_itu_t crc_ccitt cordic compat_xtables compat cdc_wdm btusb btintel brcmutil br_netfilter bnep bluetooth 8139too 8139cp act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_hfsc sch_ingress evdev k10temp hwmon i2c_piix4 i2c_dev xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables ip_gre gre e1000 ifb ipip tunnel4 ip_tunnel tun vfat fat bcma nls_utf8 nls_iso8859_1 nls_cp437 regmap_spi regmap_mmio regmap_i2c i2c_core regmap_core lzo_decompress lzo_compress sha1_generic ecb cmac exfat button_hotplug ptp pps_core mii
[ 1714.885155] CPU: 1 PID: 11230 Comm: pppd Not tainted 4.4.39 #0
[ 1714.886092] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 05/20/2014
[ 1714.887888] task: ffff88003ba8a040 ti: ffff88003b880000 task.ti: ffff88003b880000
[ 1714.889131] RIP: 0010:[]  [] ppp_output_wakeup+0xb4c/0xeac [ppp_generic]
[ 1714.890753] RSP: 0018:ffff88003b883e58  EFLAGS: 00010246
[ 1714.891623] RAX: 0000000000000000 RBX: ffff88003b86ee00 RCX: 00000000006403a8
[ 1714.892736] RDX: 0000000000000000 RSI: 000000004004743a RDI: ffffffffa04ec9e0
[ 1714.893853] RBP: 00000000006403a8 R08: 0000000000000000 R09: 0000000000000000
[ 1714.894950] R10: 0000000000008802 R11: 0000000000000206 R12: 0000000000000000
[ 1714.896078] R13: ffff88003b86e100 R14: 00000000006403a8 R15: 0000000000000000
[ 1714.897297] FS:  00007fce166d8c48(0000) GS:ffff88003fd00000(0000) knlGS:0000000000000000
[ 1714.898620] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1714.899486] CR2: 000000000063ef80 CR3: 000000003b90d000 CR4: 00000000001406e0
[ 1714.900680] Stack:
[ 1714.901023]  ffffffff810cc8ec 8000000039bdc065 0000000000000008 ffff88003c25b740
[ 1714.902295]  8000000000000065 ffff8800000001f0 0000000000000055 ffff88003b86ee00
[ 1714.903607]  00000000006403a8 ffff88003c64c750 000000004004743a 00000000006403a8
[ 1714.904916] Call Trace:
[ 1714.905321]  [] ? handle_mm_fault+0x9fc/0x1270
[ 1714.906270]  [] ? do_vfs_ioctl+0x299/0x470
[ 1714.907205]  [] ? __do_page_fault+0x14e/0x3a0
[ 1714.908156]  [] ? SyS_ioctl+0x32/0x60
[ 1714.909031]  [] ? entry_SYSCALL_64_fastpath+0x12/0x71
[ 1714.910056] Code: 44 89 e6 4c 89 ef e8 14 ca ff ff 48 85 c0 74 0e f0 ff 40 50 45 31 f6 48 89 83 c8 00 00 00 48 89 ef e8 39 e0 f5 e0 e9 62 f6 ff ff  0b 49 8d 9d 80 00 00 00 49 8d 6d 7c 48 89 df e8 0f f7 f5 e0 
[ 1714.914509] RIP  [] ppp_output_wakeup+0xb4c/0xeac [ppp_generic]
[ 1714.915749]  RSP 
[ 1714.916464] ---[ end trace 14c23a04fe795c7b ]---
[ 1714.917580] Kernel panic - not syncing: Fatal exception
[ 1714.918481] Kernel Offset: disabled
[ 1714.922733] Rebooting in 3 seconds..


More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=355


From lede-bugs at lists.infradead.org  Sun Dec 25 09:13:37 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 25 Dec 2016 17:13:37 +0000
Subject: [FS#346] libpcap: error: 'compiler_state_t {aka struct
 _compiler_state}' has no member named 'ai'
In-Reply-To: <FS346@bugs.lede-project.org>
References: <FS346@bugs.lede-project.org>
Message-ID: <mailman.75544.1482686041.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#346 - libpcap: error: 'compiler_state_t {aka struct _compiler_state}' has no member named 'ai'
User who did this - Hauke Mehrtens (Hauke)

----------
This is already fixed in this commit:
https://git.lede-project.org/16725e2db0a4fbf72e05443049df3f0cfa2ad86b
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=346#comment1088


From lede-bugs at lists.infradead.org  Sun Dec 25 09:14:09 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 25 Dec 2016 17:14:09 +0000
Subject: [FS#346] libpcap: error: 'compiler_state_t {aka struct
 _compiler_state}' has no member named 'ai'
In-Reply-To: <FS346@bugs.lede-project.org>
References: <FS346@bugs.lede-project.org>
Message-ID: <mailman.75545.1482686073.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#346 - libpcap: error: 'compiler_state_t {aka struct _compiler_state}' has no member named 'ai'
User who did this - Hauke Mehrtens (Hauke)

Reason for closing: Fixed
Additional comments about closing: https://git.lede-project.org/16725e2db0a4fbf72e05443049df3f0cfa2ad86b

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=346


From lede-bugs at lists.infradead.org  Sun Dec 25 09:32:08 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 25 Dec 2016 17:32:08 +0000
Subject: [FS#285] Kernel panic on ebox-3300 (Vortex86DX CPU)
In-Reply-To: <FS285@bugs.lede-project.org>
References: <FS285@bugs.lede-project.org>
Message-ID: <mailman.75546.1482687153.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#285 - Kernel panic on ebox-3300 (Vortex86DX CPU)
User who did this - Hauke Mehrtens (Hauke)

----------
This problem is probably caused by this change in upstream Linux kernel:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d524165cb8dbb2ce5916cd7682236b9324ae2644

it is not possible to activate x2apic support in a 32 bit kernel.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=285#comment1089


From lede-bugs at lists.infradead.org  Sun Dec 25 09:51:50 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 25 Dec 2016 17:51:50 +0000
Subject: [FS#353] [lantiq-xrx200] ifx-vmmc fails to compile
In-Reply-To: <FS353@bugs.lede-project.org>
References: <FS353@bugs.lede-project.org>
Message-ID: <mailman.75548.1482688334.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#353 - [lantiq-xrx200] ifx-vmmc fails to compile
User who did this - Hauke Mehrtens (Hauke)

----------
CONFIG_VOICE_CPE_VMMC_PMC is not supported in LEDE, I just marked it as broken here:
https://git.lede-project.org/4af4f214926b3e8ebdd1830010ccdc8d0fb6c3ff

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=353#comment1090


From lede-bugs at lists.infradead.org  Sun Dec 25 09:52:28 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 25 Dec 2016 17:52:28 +0000
Subject: [FS#353] [lantiq-xrx200] ifx-vmmc fails to compile
In-Reply-To: <FS353@bugs.lede-project.org>
References: <FS353@bugs.lede-project.org>
Message-ID: <mailman.75549.1482688371.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#353 - [lantiq-xrx200] ifx-vmmc fails to compile
User who did this - Hauke Mehrtens (Hauke)

Reason for closing: Fixed
Additional comments about closing: CONFIG_VOICE_CPE_VMMC_PMC is not supported in LEDE, I just marked it as broken here:
https://git.lede-project.org/4af4f214926b3e8ebdd1830010ccdc8d0fb6c3ff

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=353


From lede-bugs at lists.infradead.org  Sun Dec 25 12:04:06 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 25 Dec 2016 20:04:06 +0000
Subject: [FS#312] GRE tunnel fail to up if df option set to 0
In-Reply-To: <FS312@bugs.lede-project.org>
References: <FS312@bugs.lede-project.org>
Message-ID: <mailman.75556.1482696269.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#312 - GRE tunnel fail to up if df option set to 0
User who did this: Hans Dedecker (dedeckeh)
Percent Complete: 40% -> 100%

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=312


From lede-bugs at lists.infradead.org  Sun Dec 25 12:05:31 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 25 Dec 2016 20:05:31 +0000
Subject: [FS#312] GRE tunnel fail to up if df option set to 0
In-Reply-To: <FS312@bugs.lede-project.org>
References: <FS312@bugs.lede-project.org>
Message-ID: <mailman.75557.1482696355.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#312 - GRE tunnel fail to up if df option set to 0
User who did this - Hans Dedecker (dedeckeh)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=312


From lede-bugs at lists.infradead.org  Sun Dec 25 18:15:18 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 26 Dec 2016 02:15:18 +0000
Subject: [FS#356] linksys wrt3200acm vlan bug
In-Reply-To: <FS356@bugs.lede-project.org>
References: <FS356@bugs.lede-project.org>
Message-ID: <mailman.75560.1482718670.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - qqlove (qqlove) 

Attached to Project - LEDE Project
Summary - linksys wrt3200acm vlan bug
Task Type - Bug Report
Category - Packages
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - All
Due in Version - Undecided
Due Date - Undecided
Details - 
 - Can not vlan information, we can not create vlan
 - SNAPSHOT of LEDE release, packages, etc.

   

 

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=356


From lede-bugs at lists.infradead.org  Mon Dec 26 00:43:38 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 26 Dec 2016 08:43:38 +0000
Subject: [FS#357] [pptpd] Cant use Package "pppd-multilink" when pptpd is
 selected
In-Reply-To: <FS357@bugs.lede-project.org>
References: <FS357@bugs.lede-project.org>
Message-ID: <mailman.75571.1482741970.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Guido L. (LipkeGu) 

Attached to Project - LEDE Project
Summary - [pptpd] Cant use Package "pppd-multilink" when pptpd is selected
Task Type - Bug Report
Category - Packages
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - This Patch fixes a problem when pptpd is selected. pptpd depends on pppd which forces users to use pppd instead of pppd-multilink.


diff --git a/net/pptpd/Makefile b/net/pptpd/Makefile
index f188cc0..bce0df8 100644
--- a/net/pptpd/Makefile
+++ b/net/pptpd/Makefile
@@ -25,7 +25,7 @@ include $(INCLUDE_DIR)/package.mk
 define Package/pptpd
   SECTION:=net
   CATEGORY:=Network
-  DEPENDS:=+kmod-ppp +kmod-gre +kmod-mppe +ppp
+  DEPENDS:=@(PACKAGE_ppp||PACKAGE_ppp-multilink) +kmod-ppp +kmod-gre +kmod-mppe
   TITLE:=PopTop pptp server
   URL:=http://poptop.sourceforge.net/
   SUBMENU:=VPN


Signed-off-by: Guido Lipke 

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=357


From lede-bugs at lists.infradead.org  Mon Dec 26 01:38:03 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 26 Dec 2016 09:38:03 +0000
Subject: [FS#357] [pptpd] Cant use Package "pppd-multilink" when pptpd is
 selected
In-Reply-To: <FS357@bugs.lede-project.org>
References: <FS357@bugs.lede-project.org>
Message-ID: <mailman.75578.1482745108.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#357 - [pptpd] Cant use Package "pppd-multilink" when pptpd is selected
User who did this - Mathias Kresin (mkresin)

Reason for closing: Different project
Additional comments about closing: Additional comments about closing: The pptpd scripts package is not part of the LEDE base system. It is maintained as part of the (external/additional) [[https://github.com/openwrt/packages/tree/master/net/pptpd|packages feed]] which has its own bugtracker.

Would you please open a bug report at https://github.com/openwrt/packages/issues to make sure that the appropriate people get aware of the issue.

Please don't attach/paste patches to the bugtracker. If you already have a patch, submit this patch as pull request.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=357


From lede-bugs at lists.infradead.org  Mon Dec 26 10:29:38 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 26 Dec 2016 18:29:38 +0000
Subject: [FS#350] Lantiq: ARV4518pw and ARV7518pw both are stuck in endless
 reboots
In-Reply-To: <FS350@bugs.lede-project.org>
References: <FS350@bugs.lede-project.org>
Message-ID: <mailman.75620.1482777007.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#350 - Lantiq: ARV4518pw and ARV7518pw both are stuck in endless reboots
User who did this - Mohammed Berdai (medber)

----------
I can confirm that reverting this commit solved the problem :

lantiq: use dwc2 by default on danube
ffd7c155008bff4b08197dfd710d7a1386313f98


AND these three also were committed right before the one that caused the kernel panic

lantiq: dwc2 parameters for danube
6f60926babe50cd1aa24fb849577fff9fe7f46b4

lantiq: device tree bindings for dwc2 on danube
5c06a31e23b9cc1b8c8a1a8e0ab58353fc925865

lantiq: initialise dwc2 on danube
c82d5b30e10e6987bb73119c2c08ec9ff4a504dd


and the kernel panic ins FS#351 is related to it.



----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=350#comment1091


From lede-bugs at lists.infradead.org  Mon Dec 26 10:32:11 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 26 Dec 2016 18:32:11 +0000
Subject: [FS#351] Lantiq: ARV7510PW22 kernel panic
In-Reply-To: <FS351@bugs.lede-project.org>
References: <FS351@bugs.lede-project.org>
Message-ID: <mailman.75621.1482777154.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#351 - Lantiq: ARV7510PW22 kernel panic
User who did this - Mohammed Berdai (medber)

----------
indeed the switch to dwc2 is the cause for this router (arv7510pw22), arv4518pw and arv7518pw.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=351#comment1092


From lede-bugs at lists.infradead.org  Mon Dec 26 13:04:55 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 26 Dec 2016 21:04:55 +0000
Subject: [FS#358] commit 0090ad breaks opkg update
In-Reply-To: <FS358@bugs.lede-project.org>
References: <FS358@bugs.lede-project.org>
Message-ID: <mailman.75638.1482786448.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - gamanakis (gamanakis) 

Attached to Project - LEDE Project
Summary - commit 0090ad breaks opkg update
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details -  - Device problem occurs on Linksys WRT1900ACS
 - LEDE nightly 26/12/2016
 - Steps to reproduce:
1) run opkg update
2) run opkg list
3) what happens: only the installed packages are listed.
expected: all the packages in the repository should be listed.

Reverting to release 15 of opkg resolves the problem. Culprit is probably commit 0090adcd5c94adad2168cd9b338f45827533c81d.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=358


From lede-bugs at lists.infradead.org  Tue Dec 27 01:21:50 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 09:21:50 +0000
Subject: [FS#358] commit 0090ad breaks opkg update
In-Reply-To: <FS358@bugs.lede-project.org>
References: <FS358@bugs.lede-project.org>
Message-ID: <mailman.75682.1482830534.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#358 - commit 0090ad breaks opkg update
User who did this - Felix Fietkau (nbd)

----------
Fixed in the latest version
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=358#comment1093


From lede-bugs at lists.infradead.org  Tue Dec 27 01:21:58 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 09:21:58 +0000
Subject: [FS#358] commit 0090ad breaks opkg update
In-Reply-To: <FS358@bugs.lede-project.org>
References: <FS358@bugs.lede-project.org>
Message-ID: <mailman.75683.1482830539.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#358 - commit 0090ad breaks opkg update
User who did this - Felix Fietkau (nbd)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=358


From lede-bugs at lists.infradead.org  Tue Dec 27 01:22:31 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 09:22:31 +0000
Subject: [FS#120] opkg fails with Out of memory on a device with 32 MB of RAM
In-Reply-To: <FS120@bugs.lede-project.org>
References: <FS120@bugs.lede-project.org>
Message-ID: <mailman.75684.1482830577.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#120 - opkg fails with Out of memory on a device with 32 MB of RAM
User who did this - Felix Fietkau (nbd)

----------
Please test the latest version
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=120#comment1094


From lede-bugs at lists.infradead.org  Tue Dec 27 01:35:14 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 09:35:14 +0000
Subject: [FS#242] userspace apps should run as unprivileged user
In-Reply-To: <FS242@bugs.lede-project.org>
References: <FS242@bugs.lede-project.org>
Message-ID: <mailman.75685.1482831338.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#242 - userspace apps should run as unprivileged user
User who did this - Felix Fietkau (nbd)

----------
Please don't open bug reports like this one.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=242#comment1095


From lede-bugs at lists.infradead.org  Tue Dec 27 01:35:29 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 09:35:29 +0000
Subject: [FS#242] userspace apps should run as unprivileged user
In-Reply-To: <FS242@bugs.lede-project.org>
References: <FS242@bugs.lede-project.org>
Message-ID: <mailman.75686.1482831348.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#242 - userspace apps should run as unprivileged user
User who did this - Felix Fietkau (nbd)

Reason for closing: Invalid report
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=242


From lede-bugs at lists.infradead.org  Tue Dec 27 01:36:05 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 09:36:05 +0000
Subject: [FS#290] procd strips away double quotes required in OpenVPN
 configuration file
In-Reply-To: <FS290@bugs.lede-project.org>
References: <FS290@bugs.lede-project.org>
Message-ID: <mailman.75687.1482831388.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#290 - procd strips away double quotes required in OpenVPN configuration file
User who did this - Felix Fietkau (nbd)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=290


From lede-bugs at lists.infradead.org  Tue Dec 27 01:39:03 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 09:39:03 +0000
Subject: [FS#286] ath9k / stations early drop with 'max_inactivity=30'
In-Reply-To: <FS286@bugs.lede-project.org>
References: <FS286@bugs.lede-project.org>
Message-ID: <mailman.75688.1482831569.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#286 - ath9k / stations early drop with 'max_inactivity=30'
User who did this - Felix Fietkau (nbd)

----------
Please try the latest version
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=286#comment1096


From lede-bugs at lists.infradead.org  Tue Dec 27 01:39:36 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 09:39:36 +0000
Subject: [FS#348] Dependency issue breaks what was a valid config
In-Reply-To: <FS348@bugs.lede-project.org>
References: <FS348@bugs.lede-project.org>
Message-ID: <mailman.75689.1482831607.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#348 - Dependency issue breaks what was a valid config
User who did this - Felix Fietkau (nbd)

Reason for closing: Not a bug
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=348


From lede-bugs at lists.infradead.org  Tue Dec 27 01:40:52 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 09:40:52 +0000
Subject: [FS#356] linksys wrt3200acm vlan bug
In-Reply-To: <FS356@bugs.lede-project.org>
References: <FS356@bugs.lede-project.org>
Message-ID: <mailman.75690.1482831679.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#356 - linksys wrt3200acm vlan bug
User who did this - Felix Fietkau (nbd)

----------
This bug report is hard to understand. Please provide a better and more detailed description, including steps to reproduce
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=356#comment1097


From lede-bugs at lists.infradead.org  Tue Dec 27 03:04:07 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 11:04:07 +0000
Subject: [FS#342] iptables v1.4.21: can't initialize iptables table raw
In-Reply-To: <FS342@bugs.lede-project.org>
References: <FS342@bugs.lede-project.org>
Message-ID: <mailman.75711.1482836797.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#342 - iptables v1.4.21: can't initialize iptables table raw
User who did this - Felix Fietkau (nbd)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=342


From lede-bugs at lists.infradead.org  Tue Dec 27 03:14:08 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 11:14:08 +0000
Subject: [FS#354] Error using last source
In-Reply-To: <FS354@bugs.lede-project.org>
References: <FS354@bugs.lede-project.org>
Message-ID: <mailman.75712.1482837272.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#354 - Error using last source
User who did this - Felix Fietkau (nbd)

----------
In your configuration, disable px5g-polarssl, libutream-polarssl and libpolarssl, then enable px5g-mbedtls instead
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=354#comment1098


From lede-bugs at lists.infradead.org  Tue Dec 27 03:14:16 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 11:14:16 +0000
Subject: [FS#354] Error using last source
In-Reply-To: <FS354@bugs.lede-project.org>
References: <FS354@bugs.lede-project.org>
Message-ID: <mailman.75713.1482837276.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#354 - Error using last source
User who did this - Felix Fietkau (nbd)

Reason for closing: Not a bug
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=354


From lede-bugs at lists.infradead.org  Tue Dec 27 03:19:16 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 11:19:16 +0000
Subject: [FS#334] ath5k: kernel warning every 10 minutes
In-Reply-To: <FS334@bugs.lede-project.org>
References: <FS334@bugs.lede-project.org>
Message-ID: <mailman.75716.1482837580.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#334 - ath5k: kernel warning every 10 minutes
User who did this - Felix Fietkau (nbd)

Reason for closing: Fixed
Additional comments about closing: Fixed in r2691-f04b651453

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=334


From lede-bugs at lists.infradead.org  Tue Dec 27 03:21:21 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 11:21:21 +0000
Subject: [FS#352] Failed to build Python 3
In-Reply-To: <FS352@bugs.lede-project.org>
References: <FS352@bugs.lede-project.org>
Message-ID: <mailman.75717.1482837704.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#352 - Failed to build Python 3
User who did this - Felix Fietkau (nbd)

----------
Please report the issue here: https://github.com/openwrt/packages
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=352#comment1099


From lede-bugs at lists.infradead.org  Tue Dec 27 03:21:28 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 11:21:28 +0000
Subject: [FS#352] Failed to build Python 3
In-Reply-To: <FS352@bugs.lede-project.org>
References: <FS352@bugs.lede-project.org>
Message-ID: <mailman.75718.1482837709.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#352 - Failed to build Python 3
User who did this - Felix Fietkau (nbd)

Reason for closing: Different project
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=352


From lede-bugs at lists.infradead.org  Tue Dec 27 04:01:13 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 12:01:13 +0000
Subject: [FS#295] ath10k_pci 0001:01:00.0: SWBA overrun on vdev
In-Reply-To: <FS295@bugs.lede-project.org>
References: <FS295@bugs.lede-project.org>
Message-ID: <mailman.75724.1482840097.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#295 - ath10k_pci 0001:01:00.0: SWBA overrun on vdev
User who did this - Felix Fietkau (nbd)

----------
Please try the latest version
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=295#comment1100


From lede-bugs at lists.infradead.org  Tue Dec 27 04:01:27 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 12:01:27 +0000
Subject: [FS#295] ath10k_pci 0001:01:00.0: SWBA overrun on vdev
In-Reply-To: <FS295@bugs.lede-project.org>
References: <FS295@bugs.lede-project.org>
Message-ID: <mailman.75725.1482840107.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#295 - ath10k_pci 0001:01:00.0: SWBA overrun on vdev
User who did this: Felix Fietkau (nbd)
Status: Unconfirmed -> Waiting on reporter

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=295


From lede-bugs at lists.infradead.org  Tue Dec 27 04:02:13 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 12:02:13 +0000
Subject: [FS#349] mwan3 is broken with virtual ifaces
In-Reply-To: <FS349@bugs.lede-project.org>
References: <FS349@bugs.lede-project.org>
Message-ID: <mailman.75726.1482840156.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#349 - mwan3 is broken with virtual ifaces
User who did this - Felix Fietkau (nbd)

----------
Please report it here: https://github.com/openwrt/packages
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=349#comment1101


From lede-bugs at lists.infradead.org  Tue Dec 27 04:02:26 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 12:02:26 +0000
Subject: [FS#349] mwan3 is broken with virtual ifaces
In-Reply-To: <FS349@bugs.lede-project.org>
References: <FS349@bugs.lede-project.org>
Message-ID: <mailman.75727.1482840166.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#349 - mwan3 is broken with virtual ifaces
User who did this - Felix Fietkau (nbd)

Reason for closing: Different project
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=349


From lede-bugs at lists.infradead.org  Tue Dec 27 04:20:47 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 12:20:47 +0000
Subject: [FS#319] Relayd based bridge bugs. bug in luci not reloading relayd
 on configuration changes
In-Reply-To: <FS319@bugs.lede-project.org>
References: <FS319@bugs.lede-project.org>
Message-ID: <mailman.75729.1482841273.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#319 - Relayd based bridge bugs. bug in luci not reloading relayd on configuration changes
User who did this - Felix Fietkau (nbd)

----------
Please try the latest version
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=319#comment1102


From lede-bugs at lists.infradead.org  Tue Dec 27 04:20:55 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 12:20:55 +0000
Subject: [FS#319] Relayd based bridge bugs. bug in luci not reloading relayd
 on configuration changes
In-Reply-To: <FS319@bugs.lede-project.org>
References: <FS319@bugs.lede-project.org>
Message-ID: <mailman.75730.1482841278.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#319 - Relayd based bridge bugs. bug in luci not reloading relayd on configuration changes
User who did this: Felix Fietkau (nbd)
Status: Unconfirmed -> Waiting on reporter

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=319


From lede-bugs at lists.infradead.org  Tue Dec 27 04:20:56 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 12:20:56 +0000
Subject: [FS#319] Relayd based bridge bugs. bug in luci not reloading relayd
 on configuration changes
In-Reply-To: <FS319@bugs.lede-project.org>
References: <FS319@bugs.lede-project.org>
Message-ID: <mailman.75731.1482841278.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#319 - Relayd based bridge bugs. bug in luci not reloading relayd on configuration changes
User who did this: Felix Fietkau (nbd)
Percent Complete: 0% -> 90%

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=319


From lede-bugs at lists.infradead.org  Tue Dec 27 04:22:21 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 12:22:21 +0000
Subject: [FS#318] Relayd based bridge bugs. bug in init.d file
In-Reply-To: <FS318@bugs.lede-project.org>
References: <FS318@bugs.lede-project.org>
Message-ID: <mailman.75733.1482841362.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#318 - Relayd based bridge bugs. bug in init.d file
User who did this - Felix Fietkau (nbd)

----------
Fixed in the latest version
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=318#comment1103


From lede-bugs at lists.infradead.org  Tue Dec 27 04:22:29 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 12:22:29 +0000
Subject: [FS#318] Relayd based bridge bugs. bug in init.d file
In-Reply-To: <FS318@bugs.lede-project.org>
References: <FS318@bugs.lede-project.org>
Message-ID: <mailman.75734.1482841371.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#318 - Relayd based bridge bugs. bug in init.d file
User who did this - Felix Fietkau (nbd)

Reason for closing: Fixed
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=318


From lede-bugs at lists.infradead.org  Tue Dec 27 09:39:38 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 17:39:38 +0000
Subject: [FS#319] Relayd based bridge bugs. bug in luci not reloading relayd
 on configuration changes
In-Reply-To: <FS319@bugs.lede-project.org>
References: <FS319@bugs.lede-project.org>
Message-ID: <mailman.75768.1482860532.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#319 - Relayd based bridge bugs. bug in luci not reloading relayd on configuration changes
User who did this - Pedro (finas)

----------
tried a new git clone today, the bug with the parameter not being appended to the value is fixed but any*** change I make  on the luci web interface does not reload relayd

***
any change that sets these parameters:
        option expiry '30'
        option retry '5'
        option ipaddr '172.16.1.75'

also it's still not possible to automatically set the option ipaddr to whatever is assigned by dhcp. ( I know, it's not a bug :)  )






----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=319#comment1106


From lede-bugs at lists.infradead.org  Tue Dec 27 12:05:32 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 20:05:32 +0000
Subject: [FS#251] sending SIGSEGV to dnsmasq for invalid read access from
 00000000
In-Reply-To: <FS251@bugs.lede-project.org>
References: <FS251@bugs.lede-project.org>
Message-ID: <mailman.75778.1482869412.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#251 - sending SIGSEGV to dnsmasq for invalid read access from 00000000
User who did this - Felix Fietkau (nbd)

----------
Please test the latest version
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=251#comment1108


From lede-bugs at lists.infradead.org  Tue Dec 27 13:02:19 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 21:02:19 +0000
Subject: [FS#359] kirkwood: kernel does not recognize rootfs in ubi
In-Reply-To: <FS359@bugs.lede-project.org>
References: <FS359@bugs.lede-project.org>
Message-ID: <mailman.75779.1482872564.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Alberto Bursi (bobafetthotmail1) 

Attached to Project - LEDE Project
Summary - kirkwood: kernel does not recognize rootfs in ubi
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - I'm trying to add support for a ZyXEL NSA310 (kirkwood-based NAS), but the kernel does not find the rootfs in the ubi.

The image has kernel+rootfs+rootfs_data in ubi, built with
FILESYSTEMS := squashfs
IMAGES += factory.bin
IMAGE/factory.bin := append-ubi
KERNEL_IN_UBI := 1

If I boot the initramfs (ramdisk) system image while there is a ubi image flashed to nand, it gives this error while booting

[ 1.070706] UBI: auto-attach mtd2
[ 1.073868] ubi0: attaching mtd2
[ 1.083812] UBI: EOF marker found, PEBs from 28 will be erased
[ 1.089971] ubi0: scanning is finished
[ 1.093994] ubi0 error: ubi_read_volume_table: the layout volume was not found
[ 1.101458] ubi0 error: ubi_attach_mtd_dev: failed to attach mtd2, error -22
[ 1.108559] UBI error: cannot attach mtd2

but since ubi isn't necessary for the initramfs image, it works fine and I get to system console.

If I boot the firmware image from nand (and set uboot for booting from ubi, with NO bootargs passed to the kernel), the kernel boots until it finds the same error above, and then it posts this

[ 1.605331] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[ 1.612865] Please append a correct "root=" boot option; here are the available partitions:
[ 1.621268] 1f00 1024 mtdblock0 (driver?)
[ 1.626346] 1f01 512 mtdblock1 (driver?)
[ 1.631439] 1f02 129024 mtdblock2 (driver?)
[ 1.636521] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

And auto-reboots.

I've tried with bootargs like ubi.mtd=2 but with any bootarg about root= or ubi it simply hangs and does not even start the kernel (shortly after uboot executes the kernel the device restarts).

the ubi partition seems to be OK according to uboot (see output of various uboot commands). Any help appreciated. 

NSA310> ubi part ubi
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: attached mtd1 (name "mtd=2", size 126 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 1008, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1235565284
ubi0: available PEBs: 0, total reserved PEBs: 1008, PEBs reserved for bad PEB handling: 20

NSA310> ubi info
UBI: MTD device name: "mtd=2"
UBI: MTD device size: 126 MiB
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: number of good PEBs: 1008
UBI: number of bad PEBs: 0
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 3
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 1008
UBI: number of PEBs reserved for bad PEB handling: 20
UBI: max/mean erase counter: 1/0

NSA310> ubi info l
Volume information dump:
        vol_id          0
        reserved_pebs   16
        alignment       1
        data_pad        0
        vol_type        3
        name_len        6
        usable_leb_size 129024
        used_ebs        16
        used_bytes      2064384
        last_eb_bytes   129024
        corrupted       0
        upd_marker      0
        name            kernel
Volume information dump:
        vol_id          1
        reserved_pebs   10
        alignment       1
        data_pad        0
        vol_type        3
        name_len        6
        usable_leb_size 129024
        used_ebs        10
        used_bytes      1290240
        last_eb_bytes   129024
        corrupted       0
        upd_marker      0
        name            rootfs
Volume information dump:
        vol_id          2
        reserved_pebs   958
        alignment       1
        data_pad        0
        vol_type        3
        name_len        11
        usable_leb_size 129024
        used_ebs        958
        used_bytes      123604992
        last_eb_bytes   129024
        corrupted       0
        upd_marker      0
        name            rootfs_data
Volume information dump:
        vol_id          2147479551
        reserved_pebs   2
        alignment       1
        data_pad        0
        vol_type        3
        name_len        13
        usable_leb_size 129024
        used_ebs        2
        used_bytes      258048
        last_eb_bytes   2
        corrupted       0
        upd_marker      0
        name            layout volume

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=359


From lede-bugs at lists.infradead.org  Tue Dec 27 13:04:19 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 21:04:19 +0000
Subject: [FS#359] kirkwood: kernel does not recognize rootfs in ubi
In-Reply-To: <FS359@bugs.lede-project.org>
References: <FS359@bugs.lede-project.org>
Message-ID: <mailman.75780.1482872683.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#359 - kirkwood: kernel does not recognize rootfs in ubi
User who did this - Alberto Bursi (bobafetthotmail1)

----------
Btw, I'm using the same dtb I use to boot Debian on it.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=359#comment1109


From lede-bugs at lists.infradead.org  Tue Dec 27 14:03:51 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 22:03:51 +0000
Subject: [FS#251] sending SIGSEGV to dnsmasq for invalid read access from
 00000000
In-Reply-To: <FS251@bugs.lede-project.org>
References: <FS251@bugs.lede-project.org>
Message-ID: <mailman.75788.1482876261.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#251 - sending SIGSEGV to dnsmasq for invalid read access from 00000000
User who did this - IronicSven (IronicSven)

----------
I've tested a few versions since last weekend and couldn't reproduce this issue on my 1043nd v1 anymore. I think it's fixed.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=251#comment1111


From lede-bugs at lists.infradead.org  Tue Dec 27 14:26:48 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 22:26:48 +0000
Subject: [FS#251] sending SIGSEGV to dnsmasq for invalid read access from
 00000000
In-Reply-To: <FS251@bugs.lede-project.org>
References: <FS251@bugs.lede-project.org>
Message-ID: <mailman.75794.1482877762.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#251 - sending SIGSEGV to dnsmasq for invalid read access from 00000000
User who did this - Matthias Schiffer (NeoRaider)

----------
Still reproducible with current master (r2695-c9c68c71776).
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=251#comment1112


From lede-bugs at lists.infradead.org  Wed Dec 28 06:10:04 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 28 Dec 2016 14:10:04 +0000
Subject: [FS#360] Regression: no ipv6 with multiple interface
In-Reply-To: <FS360@bugs.lede-project.org>
References: <FS360@bugs.lede-project.org>
Message-ID: <mailman.75827.1482934233.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - bastien-roucaries (bastien-roucaries) 

Attached to Project - LEDE Project
Summary - Regression: no ipv6 with multiple interface
Task Type - Bug Report
Category - Packages
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Hi,

I used something like this in order to have multiple ip adress:
/etc/config/network
config interface 'A_MAIN'
        option ifname 'br-BRIDGE_V20'
        option _orig_ifname 'br-BRIDGE_V20'
        option _orig_bridge 'false'
        option proto 'none'

config interface 'LAN_V20'
        option proto 'static'
        option ifname 'br-BRIDGE_V20'
        option netmask '255.255.255.0'
        option ipaddr '192.168.20.1'

config interface 'LAN_V20_6'
        option proto 'static'
        option ifname 'br-BRIDGE_V20'
        option ip6addr '2a01:e35:2f01:a61::1/64'

config interface 'LAN_V20_6L'
        option proto 'static'
        option ifname 'br-BRIDGE_V20'
        option ip6addr 'fd02:15b3:9237:20::1/64'

   
and /etc/config/dhcp something like:

config dhcp 'LAN_V20'
        option interface 'LAN_V20'
        option start '100'
        option limit '150'
        option leasetime '12h'

config dhcp 'LAN_V20_6'
        option interface 'LAN_V20_6'
        option ra 'server'
        option dhcpv6 'server'
        option ra_management '1'
        option ra_default '1'
        option master '1'
        option ignore '1'
config dhcp 'LAN_V20_6L'
        option interface 'LAN_V20_6L'
        option ra 'server'
        option dhcpv6 'server'
        option ra_management '1'
        option ra_default '1'
        option ignore '1'

Now it does not define ipv6 adress

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=360


From lede-bugs at lists.infradead.org  Wed Dec 28 06:33:48 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 28 Dec 2016 14:33:48 +0000
Subject: [FS#361] git: add pre-receive hook to reject commits without SoB line
In-Reply-To: <FS361@bugs.lede-project.org>
References: <FS361@bugs.lede-project.org>
Message-ID: <mailman.75828.1482935653.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - Stijn Tintel (stintel) 

Attached to Project - LEDE Project
Summary - git: add pre-receive hook to reject commits without SoB line
Task Type - Feature Request
Category - Other
Status - New
Assigned To - Ted Hess
Operating System - All
Severity - Medium
Priority - Medium
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - I recently pushed a commit without Signed-off-by. Looking at the git history, this happened before.
To avoid this in the future, add a pre-receive that checks for signed-off-by line, and rejects the push when it's not found.

Here is some (ugly) example python code that does this, and even goes 1 step further: it rejects the push if there is any commit that does not contain a SoB for the commit author. I think it makes sense to enforce this, it came up in https://github.com/lede-project/source/pull/592#issuecomment-265760007 .

author = ""
for line in sys.stdin:
    (base, commit, ref) = line.strip().split()
    diff = subprocess.Popen(['git', 'log', '-n 1', commit],stdout=subprocess.PIPE)
    for line in iter(diff.stdout.readline, ''):
        if line.startswith('Author: '):
            author = re.sub('^Author: ', '', line)
            print('Found author: {}').format(author)
            continue
        if line.find('Signed-off-by: '):
            sob = re.sub('.*Signed-off-by: ', '', line)
            if sob == author:
                print('Found SoB line for author')
                return True

sys.exit(1)


More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=361


From lede-bugs at lists.infradead.org  Wed Dec 28 06:34:07 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 28 Dec 2016 14:34:07 +0000
Subject: [FS#361] git: add pre-receive hook to reject commits without SoB line
In-Reply-To: <FS361@bugs.lede-project.org>
References: <FS361@bugs.lede-project.org>
Message-ID: <mailman.75829.1482935667.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#361 - git: add pre-receive hook to reject commits without SoB line
User who did this: Stijn Tintel (stintel)
Task details edited:
-------
I recently pushed a commit without Signed-off-by. Looking at the git history, this happened before.
To avoid this in the future, add a pre-receive that checks for signed-off-by line, and rejects the push when it's not found.

Here is some (ugly) example python code that does this, and even goes 1 step further: it rejects the push if there is any commit that does not contain a SoB for the commit author. I think it makes sense to enforce this, it came up in https://github.com/lede-project/source/pull/592#issuecomment-265760007 .


author = ""
for line in sys.stdin:
    (base, commit, ref) = line.strip().split()
    diff = subprocess.Popen(['git', 'log', '-n 1', commit],stdout=subprocess.PIPE)
    for line in iter(diff.stdout.readline, ''):
        if line.startswith('Author: '):
            author = re.sub('^Author: ', '', line)
            print('Found author: {}').format(author)
            continue
        if line.find('Signed-off-by: '):
            sob = re.sub('.*Signed-off-by: ', '', line)
            if sob == author:
                print('Found SoB line for author')
                return True

sys.exit(1)

-------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=361


From lede-bugs at lists.infradead.org  Wed Dec 28 06:34:32 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 28 Dec 2016 14:34:32 +0000
Subject: [FS#361] git: add pre-receive hook to reject commits without SoB line
In-Reply-To: <FS361@bugs.lede-project.org>
References: <FS361@bugs.lede-project.org>
Message-ID: <mailman.75830.1482935695.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#361 - git: add pre-receive hook to reject commits without SoB line
User who did this: Stijn Tintel (stintel)
Task details edited:
-------
I recently pushed a commit without Signed-off-by. Looking at the git history, this happened before.
To avoid this in the future, add a pre-receive that checks for signed-off-by line, and rejects the push when it's not found.

Here is some (ugly) example python code that does this, and even goes 1 step further: it rejects the push if there is any commit that does not contain a SoB for the commit author. I think it makes sense to enforce this, it came up in https://github.com/lede-project/source/pull/592#issuecomment-265760007 .


author = ""
for line in sys.stdin:
    (base, commit, ref) = line.strip().split()
    diff = subprocess.Popen(['git', 'log', '-n 1', commit],stdout=subprocess.PIPE)
    for line in iter(diff.stdout.readline, ''):
        if line.startswith('Author: '):
            author = re.sub('^Author: ', '', line)
            print('Found author: {}').format(author)
            continue
        if line.find('Signed-off-by: '):
            sob = re.sub('.*Signed-off-by: ', '', line)
            if sob == author:
                print('Found SoB line for author')
                sys.exit(0)

sys.exit(1)

-------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=361


From lede-bugs at lists.infradead.org  Wed Dec 28 06:37:37 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 28 Dec 2016 14:37:37 +0000
Subject: [FS#361] git: add pre-receive hook to reject commits without SoB line
In-Reply-To: <FS361@bugs.lede-project.org>
References: <FS361@bugs.lede-project.org>
Message-ID: <mailman.75831.1482935880.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#361 - git: add pre-receive hook to reject commits without SoB line
User who did this: Stijn Tintel (stintel)
Task details edited:
-------
I recently pushed a commit without Signed-off-by. Looking at the git history, this happened before.
To avoid this in the future, add a pre-receive that checks for signed-off-by line, and rejects the push when it's not found.

Here is some (ugly) example python code that does this, and even goes 1 step further: it rejects the push if there is any commit that does not contain a SoB for the commit author. I think it makes sense to enforce this, it came up in https://github.com/lede-project/source/pull/592#issuecomment-265760007 .


#!/usr/bin/env python

import os, re, subprocess, sys

author = ""
for line in sys.stdin:
    (base, commit, ref) = line.strip().split()
    diff = subprocess.Popen(['git', 'log', '-n 1', commit],stdout=subprocess.PIPE)
    for line in iter(diff.stdout.readline, ''):
        if line.startswith('Author: '):
            author = re.sub('^Author: ', '', line)
            print('Found author: {}').format(author)
            continue
        if line.find('Signed-off-by: '):
            sob = re.sub('.*Signed-off-by: ', '', line)
            if sob == author:
                print('Found SoB line for author')
                sys.exit(0)

sys.exit(1)

-------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=361


From lede-bugs at lists.infradead.org  Wed Dec 28 06:49:34 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 28 Dec 2016 14:49:34 +0000
Subject: [FS#361] git: add pre-receive hook to reject commits without SoB line
In-Reply-To: <FS361@bugs.lede-project.org>
References: <FS361@bugs.lede-project.org>
Message-ID: <mailman.75834.1482936598.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#361 - git: add pre-receive hook to reject commits without SoB line
User who did this: Stijn Tintel (stintel)
Task details edited:
-------
I recently pushed a commit without Signed-off-by. Looking at the git history, this happened before.
To avoid this in the future, add a pre-receive that checks for signed-off-by line, and rejects the push when it's not found.

Here is some (ugly) example python code that does this, and even goes 1 step further: it rejects the push if there is any commit that does not contain a SoB for the commit author. I think it makes sense to enforce this, it came up in https://github.com/lede-project/source/pull/592#issuecomment-265760007 .


#!/usr/bin/env python

import os, re, subprocess, sys

author = ""
for line in sys.stdin:
    (base, commit, ref) = line.strip().split()
    diff = subprocess.Popen(['git', 'log', '-n 1', commit],stdout=subprocess.PIPE)
    for line in iter(diff.stdout.readline, ''):
        if line.startswith('Author: '):
            author = re.sub('^Author: ', '', line)
            print('Found author: {}').format(author)
            continue
        if line.find('Signed-off-by: '):
            sob = re.sub('.*Signed-off-by: ', '', line)
            if sob == author:
                print('Found SoB line for author')
                sys.exit(0)

sys.exit(1)


EDIT: Seems the above code only checks the last commit, let me play with this a bit longer
-------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=361


From lede-bugs at lists.infradead.org  Wed Dec 28 07:05:12 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 28 Dec 2016 15:05:12 +0000
Subject: [FS#361] git: add pre-receive hook to reject commits without SoB line
In-Reply-To: <FS361@bugs.lede-project.org>
References: <FS361@bugs.lede-project.org>
Message-ID: <mailman.75835.1482937537.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#361 - git: add pre-receive hook to reject commits without SoB line
User who did this - Rafa? Mi?ecki (rmilecki)

----------
Ack from me for such an improvement!
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=361#comment1114


From lede-bugs at lists.infradead.org  Wed Dec 28 07:26:40 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 28 Dec 2016 15:26:40 +0000
Subject: [FS#361] git: add pre-receive hook to reject commits without SoB line
In-Reply-To: <FS361@bugs.lede-project.org>
References: <FS361@bugs.lede-project.org>
Message-ID: <mailman.75836.1482938825.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#361 - git: add pre-receive hook to reject commits without SoB line
User who did this: Stijn Tintel (stintel)
Task details edited:
-------
I recently pushed a commit without Signed-off-by. Looking at the git history, this happened before.
To avoid this in the future, add a pre-receive that checks for signed-off-by line, and rejects the push when it's not found.

Here is some (ugly) example python code that does this, and even goes 1 step further: it rejects the push if there is any commit that does not contain a SoB for the commit author. I think it makes sense to enforce this, it came up in https://github.com/lede-project/source/pull/592#issuecomment-265760007 .


#!/usr/bin/env python

import os, re, subprocess, sys

author = ""
for line in sys.stdin:
    (base, commit, ref) = line.strip().split()
    crange = '{}..{}'.format(base, commit)
    commits = subprocess.Popen(['git', 'log', '--format=%H', crange],stdout=subprocess.PIPE)
    for commit in iter(commits.stdout.readline, ''):
        msg = subprocess.Popen(['git', 'log', '-n 1', commit.strip()],stdout=subprocess.PIPE)
        found_sob = False
        for line in iter(msg.stdout.readline, ''):
            if line.startswith('Author: '):
                author = re.sub('^Author: ', '', line)
                continue
            if line.find('Signed-off-by: '):
                sob = re.sub('.*Signed-off-by: ', '', line)
                if sob == author:
                    found_sob = True
        if found_sob:
            continue
        else:
            print('No SoB line for author in commit {}'.format(commit))
            sys.exit(1)


-------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=361


From lede-bugs at lists.infradead.org  Wed Dec 28 13:29:17 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 28 Dec 2016 21:29:17 +0000
Subject: [FS#362] WR1043ND v4 Slow WAN -> LAN Whilst Synced @100Mbps
In-Reply-To: <FS362@bugs.lede-project.org>
References: <FS362@bugs.lede-project.org>
Message-ID: <mailman.75889.1482960582.1639.lede-bugs@lists.infradead.org>

A new Flyspray task has been opened.  Details are below. 

User who did this - SpiderVice (Spider-Vice) 

Attached to Project - LEDE Project
Summary - WR1043ND v4 Slow WAN -> LAN Whilst Synced @100Mbps
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Recently, builds for this device have started to be made, but there's a very peculiar issue I've found. Any client that is synced to 100 Mbps (and not 1 Gbps, in my case due to incapacity of the cable used) gets their speed seemingly throttled to 20-30 Mbps. My connection is a 100 Mbps connection, and I get full 95 Mbps (Hardware NAT disabled) on the stock firmware, and I also get this speed on LEDE __only if I use a 1 Gbps link__.

Speedtest on the stock firmware with the 100 Mbps link: http://www.speedtest.net/result/5904234776.png
Speedtest on the  latest LEDE with the 100 Mbps link: http://www.speedtest.net/result/5915271748.png
1 Gbps links get full speed, as expected.

If I perform a transfer from LAN to LAN, I get full speed on the 100 Mbps link. The resulting speed graph is not a hard-cap, but seemingly some kind of throttle/flow control being applied. I cannot change any settings with ethtool as it throws 'not supported' errors.

Only happens WAN > LAN connections.
Nothing of interest in the logs, unless I can somehow get a more verbose log of the connection status.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=362


From lede-bugs at lists.infradead.org  Wed Dec 28 23:59:47 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 29 Dec 2016 07:59:47 +0000
Subject: [FS#177] ipq806x: USB3 ports fail if booted when USB3 flash drives
 inserted during boot time
In-Reply-To: <FS177@bugs.lede-project.org>
References: <FS177@bugs.lede-project.org>
Message-ID: <mailman.75926.1482998542.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#177 - ipq806x: USB3 ports fail if booted when USB3 flash drives inserted during boot time
User who did this - dissent1 (dissent1)

----------
V2 patch here, please test who faces this problem
----------

One or more files have been attached.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=177#comment1116


From lede-bugs at lists.infradead.org  Thu Dec 29 01:17:14 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 29 Dec 2016 09:17:14 +0000
Subject: [FS#356] linksys wrt3200acm vlan bug
In-Reply-To: <FS356@bugs.lede-project.org>
References: <FS356@bugs.lede-project.org>
Message-ID: <mailman.75932.1483003060.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#356 - linksys wrt3200acm vlan bug
User who did this - ?lvaro Fern?ndez Rojas (Noltari)

----------
I just bought a Linksys WRT3200ACM and I can confirm that VLANs are only working for eth0 (WAN) and not for eth1 (LAN), since the switch isn't properly detected:
root at lede:~# swconfig list
root at lede:~#

There might be other issues with this router, like no LEDs for WiFi (both 2.4GHz and 5GHz).

I will try to look into this as soon as possible.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=356#comment1117


From lede-bugs at lists.infradead.org  Fri Dec 30 01:44:53 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 30 Dec 2016 09:44:53 +0000
Subject: [FS#360] Regression: no ipv6 with multiple interface
In-Reply-To: <FS360@bugs.lede-project.org>
References: <FS360@bugs.lede-project.org>
Message-ID: <mailman.76043.1483091118.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#360 - Regression: no ipv6 with multiple interface
User who did this: Hans Dedecker (dedeckeh)
Assigned To: [-] -> Hans Dedecker

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=360


From lede-bugs at lists.infradead.org  Fri Dec 30 02:03:31 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 30 Dec 2016 10:03:31 +0000
Subject: [FS#360] Regression: no ipv6 with multiple interface
In-Reply-To: <FS360@bugs.lede-project.org>
References: <FS360@bugs.lede-project.org>
Message-ID: <mailman.76046.1483092235.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#360 - Regression: no ipv6 with multiple interface
User who did this - Hans Dedecker (dedeckeh)

----------
The used network config to create multiple IP(v6) addresses is not correct as aliased interfaces needs to be used.
Typically the following config will be used to configure multiple IP addresses assuming BRIGDE_V20 is defined as a logical interface

config interface 'A_MAIN'
        option ifname '@BRIDGE_V20' 
        option proto 'none'

config interface 'LAN_V20'
        option proto 'static'
        option ifname '@BRIDGE_V20'
        option netmask '255.255.255.0'
        option ipaddr '192.168.20.1'

config interface 'LAN_V20_6'
        option proto 'static'
        option ifname '@BRIDGE_V20'
        option ip6addr '2a01:e35:2f01:a61::1/64'

config interface 'LAN_V20_6L'
        option proto 'static'
        option ifname '@BRIDGE_V20'
        option ip6addr 'fd02:15b3:9237:20::1/64'

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=360#comment1119


From lede-bugs at lists.infradead.org  Fri Dec 30 02:03:42 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 30 Dec 2016 10:03:42 +0000
Subject: [FS#360] Regression: no ipv6 with multiple interface
In-Reply-To: <FS360@bugs.lede-project.org>
References: <FS360@bugs.lede-project.org>
Message-ID: <mailman.76047.1483092244.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#360 - Regression: no ipv6 with multiple interface
User who did this - Hans Dedecker (dedeckeh)

Reason for closing: Not a bug
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=360


From lede-bugs at lists.infradead.org  Fri Dec 30 07:35:55 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 30 Dec 2016 15:35:55 +0000
Subject: [FS#361] git: add pre-receive hook to reject commits without SoB line
In-Reply-To: <FS361@bugs.lede-project.org>
References: <FS361@bugs.lede-project.org>
Message-ID: <mailman.76089.1483112309.1639.lede-bugs@lists.infradead.org>

For full information about what has changed in this task, visit the URL below and click the History tab.

FS#361 - git: add pre-receive hook to reject commits without SoB line
User who did this: Ted Hess (thess)
Status: New -> Researching

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=361


From lede-bugs at lists.infradead.org  Fri Dec 30 13:49:04 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 30 Dec 2016 21:49:04 +0000
Subject: [FS#286] ath9k / stations early drop with 'max_inactivity=30'
In-Reply-To: <FS286@bugs.lede-project.org>
References: <FS286@bugs.lede-project.org>
Message-ID: <mailman.76100.1483134697.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#286 - ath9k / stations early drop with 'max_inactivity=30'
User who did this - Bastian Bittorf (bittorf)

----------
i can not see this issue anymore with r2709 - thank you!
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=286#comment1120


From lede-bugs at lists.infradead.org  Fri Dec 30 14:16:38 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 30 Dec 2016 22:16:38 +0000
Subject: [FS#362] WR1043ND v4 Slow WAN -> LAN Whilst Synced @100Mbps
In-Reply-To: <FS362@bugs.lede-project.org>
References: <FS362@bugs.lede-project.org>
Message-ID: <mailman.76101.1483136222.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#362 - WR1043ND v4 Slow WAN -> LAN Whilst Synced @100Mbps
User who did this - diizzyy (diizzyy)

----------
Speedtest is a very bad way of measuring performance, does iperf show anything strange between your clients?
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=362#comment1121


From lede-bugs at lists.infradead.org  Fri Dec 30 14:18:22 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 30 Dec 2016 22:18:22 +0000
Subject: [FS#359] kirkwood: kernel does not recognize rootfs in ubi
In-Reply-To: <FS359@bugs.lede-project.org>
References: <FS359@bugs.lede-project.org>
Message-ID: <mailman.76102.1483136325.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#359 - kirkwood: kernel does not recognize rootfs in ubi
User who did this - diizzyy (diizzyy)

----------
nbd kindly committed fixes recently which might be of interest, this makes my iomega iconnect device boot and flash properly.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=359#comment1122


From lede-bugs at lists.infradead.org  Fri Dec 30 15:29:11 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 30 Dec 2016 23:29:11 +0000
Subject: [FS#362] WR1043ND v4 Slow WAN -> LAN Whilst Synced @100Mbps
In-Reply-To: <FS362@bugs.lede-project.org>
References: <FS362@bugs.lede-project.org>
Message-ID: <mailman.76103.1483140576.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#362 - WR1043ND v4 Slow WAN -> LAN Whilst Synced @100Mbps
User who did this - SpiderVice (Spider-Vice)

----------
LAN to LAN is normal. Any WAN to LAN activity on a 100 Mbps link is affected. Not just SpeedTest. Any download, any interaction.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=362#comment1123


From lede-bugs at lists.infradead.org  Sat Dec 31 03:31:56 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 31 Dec 2016 11:31:56 +0000
Subject: [FS#359] kirkwood: kernel does not recognize rootfs in ubi
In-Reply-To: <FS359@bugs.lede-project.org>
References: <FS359@bugs.lede-project.org>
Message-ID: <mailman.76111.1483184071.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#359 - kirkwood: kernel does not recognize rootfs in ubi
User who did this - Alberto Bursi (bobafetthotmail1)

----------
Sadly, that patch is unrelated (he changes the nand partition names of some kirkwood devices from "root" to "ubi"). My nand partitions already had the right names.

I just built an image with kernel outside of ubi (using same sources as I used for the bug report) and everything works fine. 

These are the partitions I have on flash now (before there was only ubi after the uboot stuff).

[    0.870019] 0x000000000000-0x000000100000 : "uboot"
[    0.876440] 0x000000100000-0x000000180000 : "uboot_env"
[    0.882786] 0x000000180000-0x000000680000 : "kernel"
[    0.888807] 0x000000680000-0x000008000000 : "ubi"

this is the part about ubi not failing like before and actually doing its job.

[    1.030586] UBI: auto-attach mtd3
[    1.033752] ubi0: attaching mtd3
[    1.040249] UBI: EOF marker found, PEBs from 12 will be erased
[    1.046376] ubi0: scanning is finished
[    1.081030] ubi0: volume 1 ("rootfs_data") re-sized from 9 to 938 LEBs
[    1.088278] ubi0: attached mtd3 (name "ubi", size 121 MiB)
[    1.093820] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[    1.100741] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[    1.107473] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[    1.114305] ubi0: good PEBs: 972, bad PEBs: 0, corrupted PEBs: 0
[    1.120348] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[    1.127600] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 120222938
[    1.136699] ubi0: available PEBs: 0, total reserved PEBs: 972, PEBs reserved for bad PEB handling: 20
[    1.146319] ubi0: background thread "ubi_bgt0d" started, PID 903
[    1.210154] block ubiblock0_0: created from ubi0:0(rootfs)
[    1.215682] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem


And I get to serial console afterwards.

So, there are either issues with the kernel patch that detects multiple partitions in ubi when there is also the kernel in it, or I did something wrong. 
I did copycat the goflexnet that is working fine here, so I'm a bit puzzled about this.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=359#comment1124


From lede-bugs at lists.infradead.org  Sat Dec 31 09:12:46 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 31 Dec 2016 17:12:46 +0000
Subject: [FS#356] linksys wrt3200acm vlan bug
In-Reply-To: <FS356@bugs.lede-project.org>
References: <FS356@bugs.lede-project.org>
Message-ID: <mailman.76120.1483204393.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#356 - linksys wrt3200acm vlan bug
User who did this - ?lvaro Fern?ndez Rojas (Noltari)

----------
BTW, I was trying to find out the LEDs of the Linksys WRT3200ACM and apparently I bricked my device (I guess that some GPIOs are connected to the NAND but still can be manually exported).
However, I was able to obtain the following GPIOs:
GPIO#26: ETH Switch On/Off
GPIO#45: WLAN 2.4GHz LED
GPIO#46: WLAN 5GHz LED

Regards,
?lvaro.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=356#comment1125


From lede-bugs at lists.infradead.org  Sat Dec 31 10:57:24 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 31 Dec 2016 18:57:24 +0000
Subject: [FS#120] opkg fails with Out of memory on a device with 32 MB of RAM
In-Reply-To: <FS120@bugs.lede-project.org>
References: <FS120@bugs.lede-project.org>
Message-ID: <mailman.76131.1483210673.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#120 - opkg fails with Out of memory on a device with 32 MB of RAM
User who did this - Alberto Bursi (bobafetthotmail1)

----------
Still fails when it really shouldn't. it seems wget fails to download a 4kib package while I have 8 MiB of free RAM + 12 MiB of caches.

root at lede:/# opkg install luci-app-minidlna
Installing luci-app-minidlna (git-16.365.41161-ca79611-1) to root...
Downloading http://downloads.lede-project.org/snapshots/packages/mips_24kc/luci/luci-app-minidlna_git-16.365.41161-ca79611-1_all.ipk.
Collected errors:
 * xsystem: wget: vfork: Out of memory.
 * opkg_download: Failed to download http://downloads.lede-project.org/snapshots/packages/mips_24kc/luci/luci-app-minidlna_git-16.365.41161-ca79611-1_all.ipk, wget returned -1.
 * opkg_install_pkg: Failed to download luci-app-minidlna. Perhaps you need to run 'opkg update'?
 * opkg_install_cmd: Cannot install package luci-app-minidlna.

root at lede:/# free
             total       used       free     shared    buffers     cached
Mem:         27940      19156       8784        560       1044       3704
-/+ buffers/cache:      14408      13532
Swap:            0          0          0

root at lede:/# cat /proc/meminfo
MemTotal:          27940 kB
MemFree:            7996 kB
MemAvailable:      10660 kB
Buffers:            1120 kB
Cached:             3716 kB
SwapCached:            0 kB
Active:             3840 kB
Inactive:           2172 kB
Active(anon):       1704 kB
Inactive(anon):       32 kB
Active(file):       2136 kB
Inactive(file):     2140 kB
Unevictable:           0 kB
Mlocked:               0 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:          1184 kB
Mapped:             1644 kB
Shmem:               560 kB
Slab:               7068 kB
SReclaimable:       1892 kB
SUnreclaim:         5176 kB
KernelStack:         328 kB
PageTables:          216 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:       13968 kB
Committed_AS:       4312 kB
VmallocTotal:    1048372 kB
VmallocUsed:           0 kB
VmallocChunk:          0 kB
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=120#comment1127


From lede-bugs at lists.infradead.org  Tue Dec 27 04:23:56 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 12:23:56 +0000
Subject: [FS#13] Ath9k AP stays up for connected clients but doesn't show in
 scan on new ones
In-Reply-To: <FS13@bugs.lede-project.org>
References: <FS13@bugs.lede-project.org>
Message-ID: <mailman.76238.1483351999.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#13 - Ath9k AP stays up for connected clients but doesn't show in scan on new ones
User who did this - Felix Fietkau (nbd)

----------
Please try the latest version
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=13#comment1104


From lede-bugs at lists.infradead.org  Tue Dec 27 08:44:10 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 16:44:10 +0000
Subject: [FS#13] Ath9k AP stays up for connected clients but doesn't show in
 scan on new ones
In-Reply-To: <FS13@bugs.lede-project.org>
References: <FS13@bugs.lede-project.org>
Message-ID: <mailman.76239.1483351999.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#13 - Ath9k AP stays up for connected clients but doesn't show in scan on new ones
User who did this - IronicSven (IronicSven)

----------
Hi Felix,

the wifi still stops working and disappears on my 1043nd with the latest snapshot.

I tried to debug it last weekend and discovered it only happens under a few seconds of high load. Therefore I can trigger it with iperf.

I just build an image from https://git.lede-project.org/source.git with ath debugging enabled and this is what I captured:


root at FlensNet:~# uci set wireless.radio0.log_level=0
root at FlensNet:~# uci commit wireless
root at FlensNet:~# wifi up
root at FlensNet:~# echo 0x00000409 > /sys/kernel/debug/ieee80211/phy0/ath9k/debug
root at FlensNet:~# logread -f

# now I start iperf

Tue Dec 27 17:15:39 2016 kern.debug kernel: [  113.787634] ath: phy0: NF calibrated [ctl] [chain 0] is -90
Tue Dec 27 17:15:39 2016 kern.debug kernel: [  113.793249] ath: phy0: NF calibrated [ctl] [chain 1] is -87
Tue Dec 27 17:15:39 2016 kern.debug kernel: [  113.798867] ath: phy0: NF calibrated [ctl] [chain 2] is -86
Tue Dec 27 17:16:09 2016 kern.debug kernel: [  143.797558] ath: phy0: NF calibrated [ctl] [chain 0] is -89
Tue Dec 27 17:16:09 2016 kern.debug kernel: [  143.803192] ath: phy0: NF calibrated [ctl] [chain 1] is -88
Tue Dec 27 17:16:09 2016 kern.debug kernel: [  143.808830] ath: phy0: NF calibrated [ctl] [chain 2] is -85
Tue Dec 27 17:16:26 2016 kern.debug kernel: [  159.807130] ath: phy0: tx hung, resetting the chip
Tue Dec 27 17:16:26 2016 kern.debug kernel: [  159.818006] ath: phy0: Failed to stop TX DMA, queues=0x002!
Tue Dec 27 17:16:26 2016 kern.debug kernel: [  159.830165] ath: phy0: NF calibrated [ctl] [chain 0] is -90
Tue Dec 27 17:16:26 2016 kern.debug kernel: [  159.835773] ath: phy0: NF calibrated [ctl] [chain 1] is -86
Tue Dec 27 17:16:26 2016 kern.debug kernel: [  159.841418] ath: phy0: NF calibrated [ctl] [chain 2] is -87
Tue Dec 27 17:16:26 2016 kern.debug kernel: [  159.847021] ath: phy0: reset MAC via external reset
Tue Dec 27 17:16:26 2016 kern.debug kernel: [  159.902661] ath: phy0: ah->misc_mode 0xc
Tue Dec 27 17:16:26 2016 kern.debug kernel: [  159.909136] ath: phy0: enabling IQ Calibration
Tue Dec 27 17:16:26 2016 kern.debug kernel: [  159.913602] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 17:16:26 2016 kern.debug kernel: [  159.918872] ath: phy0: Setting CFG 0x10a
Tue Dec 27 17:16:27 2016 kern.debug kernel: [  160.937114] ath: phy0: tx hung, resetting the chip
Tue Dec 27 17:16:27 2016 kern.debug kernel: [  160.948101] ath: phy0: NF calibrated [ctl] [chain 0] is -87
Tue Dec 27 17:16:27 2016 kern.debug kernel: [  160.953716] ath: phy0: NF calibrated [ctl] [chain 1] is -87
Tue Dec 27 17:16:27 2016 kern.debug kernel: [  160.959372] ath: phy0: NF calibrated [ctl] [chain 2] is -84
Tue Dec 27 17:16:27 2016 kern.debug kernel: [  160.995701] ath: phy0: ah->misc_mode 0xc
Tue Dec 27 17:16:27 2016 kern.debug kernel: [  161.002169] ath: phy0: enabling IQ Calibration
Tue Dec 27 17:16:27 2016 kern.debug kernel: [  161.006631] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 17:16:27 2016 kern.debug kernel: [  161.011903] ath: phy0: Setting CFG 0x10a
Tue Dec 27 17:16:28 2016 kern.debug kernel: [  162.027114] ath: phy0: tx hung, resetting the chip
Tue Dec 27 17:16:28 2016 kern.debug kernel: [  162.032452] ath: phy0: NF calibrated [ctl] [chain 0] is -89
Tue Dec 27 17:16:28 2016 kern.debug kernel: [  162.038108] ath: phy0: NF calibrated [ctl] [chain 1] is -86
Tue Dec 27 17:16:28 2016 kern.debug kernel: [  162.043708] ath: phy0: NF calibrated [ctl] [chain 2] is -85
Tue Dec 27 17:16:28 2016 kern.debug kernel: [  162.080043] ath: phy0: ah->misc_mode 0xc
Tue Dec 27 17:16:28 2016 kern.debug kernel: [  162.086484] ath: phy0: enabling IQ Calibration
Tue Dec 27 17:16:28 2016 kern.debug kernel: [  162.090978] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 17:16:28 2016 kern.debug kernel: [  162.096225] ath: phy0: Setting CFG 0x10a

# about now iperf hangs and the wifi symbol on my android device disappears

Tue Dec 27 17:16:58 2016 kern.debug kernel: [  192.096793] ath: phy0: 0: Chn 0 pmi=0x000c8415;pmq=0x000a4731;iqcm=0x00002272;
Tue Dec 27 17:16:58 2016 kern.debug kernel: [  192.104070] ath: phy0: 0: Chn 1 pmi=0x000a4d43;pmq=0x0009537b;iqcm=0x00006dfd;
Tue Dec 27 17:16:58 2016 kern.debug kernel: [  192.111352] ath: phy0: 0: Chn 2 pmi=0x0009cd18;pmq=0x00090419;iqcm=0xffff8061;
Tue Dec 27 17:16:58 2016 kern.debug kernel: [  192.118615] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 17:16:59 2016 kern.debug kernel: [  193.116761] ath: phy0: 1: Chn 0 pmi=0x002bc89c;pmq=0x001a2fdf;iqcm=0xfffe3b89;
Tue Dec 27 17:16:59 2016 kern.debug kernel: [  193.124030] ath: phy0: 1: Chn 1 pmi=0x0020d8ad;pmq=0x001f60fd;iqcm=0x000658ad;
Tue Dec 27 17:16:59 2016 kern.debug kernel: [  193.131310] ath: phy0: 1: Chn 2 pmi=0x00162d15;pmq=0x001f0b19;iqcm=0xfffe1ff1;
Tue Dec 27 17:16:59 2016 kern.debug kernel: [  193.138578] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 17:17:04 2016 kern.debug kernel: [  198.436702] ath: phy0: 2: Chn 0 pmi=0x003587c7;pmq=0x002390be;iqcm=0xfffe079e;
Tue Dec 27 17:17:04 2016 kern.debug kernel: [  198.443976] ath: phy0: 2: Chn 1 pmi=0x002afd77;pmq=0x00289f9a;iqcm=0x00066de2;
Tue Dec 27 17:17:04 2016 kern.debug kernel: [  198.451265] ath: phy0: 2: Chn 2 pmi=0x003633fd;pmq=0x003e9e1f;iqcm=0xfffda432;
Tue Dec 27 17:17:04 2016 kern.debug kernel: [  198.458533] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 17:17:07 2016 kern.debug kernel: [  201.056653] ath: phy0: 3: Chn 0 pmi=0x0040e147;pmq=0x002b71ed;iqcm=0xfffd09c2;
Tue Dec 27 17:17:07 2016 kern.debug kernel: [  201.063932] ath: phy0: 3: Chn 1 pmi=0x002c7c11;pmq=0x002a384d;iqcm=0x0006e5b0;
Tue Dec 27 17:17:07 2016 kern.debug kernel: [  201.071211] ath: phy0: 3: Chn 2 pmi=0x00376cae;pmq=0x004011a0;iqcm=0xfffdccab;
Tue Dec 27 17:17:07 2016 kern.debug kernel: [  201.078476] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 17:17:08 2016 kern.debug kernel: [  201.876642] ath: phy0: 4: Chn 0 pmi=0x004acdd9;pmq=0x00345105;iqcm=0xfffcde5a;
Tue Dec 27 17:17:08 2016 kern.debug kernel: [  201.883919] ath: phy0: 4: Chn 1 pmi=0x0035ff9c;pmq=0x00325ce8;iqcm=0x0006fda4;
Tue Dec 27 17:17:08 2016 kern.debug kernel: [  201.891208] ath: phy0: 4: Chn 2 pmi=0x003ccf87;pmq=0x0045b01c;iqcm=0xfffda1a7;


I hope this helps.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=13#comment1105


From lede-bugs at lists.infradead.org  Tue Dec 27 11:57:42 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 19:57:42 +0000
Subject: [FS#13] Ath9k AP stays up for connected clients but doesn't show in
 scan on new ones
In-Reply-To: <FS13@bugs.lede-project.org>
References: <FS13@bugs.lede-project.org>
Message-ID: <mailman.76240.1483351999.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#13 - Ath9k AP stays up for connected clients but doesn't show in scan on new ones
User who did this - Felix Fietkau (nbd)

----------
Does the disconnect happen around the time right before or after your "about now" line?

By the way, I pushed another AR913x specific stability fix, so please test the latest version.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=13#comment1107


From lede-bugs at lists.infradead.org  Tue Dec 27 13:55:55 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 21:55:55 +0000
Subject: [FS#13] Ath9k AP stays up for connected clients but doesn't show in
 scan on new ones
In-Reply-To: <FS13@bugs.lede-project.org>
References: <FS13@bugs.lede-project.org>
Message-ID: <mailman.76241.1483351999.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#13 - Ath9k AP stays up for connected clients but doesn't show in scan on new ones
User who did this - IronicSven (IronicSven)

----------
Hi Felix,

wifi disappears before the "about now" line.

I tested your fix but it still happens.


root at FlensNet:~# cat /etc/os-release | grep BUILD
BUILD_ID="r2695-c9c68c7"
root at FlensNet:~# echo 0x00000409 > /sys/kernel/debug/ieee80211/phy0/ath9k/debug
root at FlensNet:~# logread -f
Tue Dec 27 22:36:39 2016 kern.debug kernel: [  109.597074] ath: phy0: 48: Chn 0 pmi=0x00cc6dd7;pmq=0x00d047cf;iqcm=0xffff1388;
Tue Dec 27 22:36:39 2016 kern.debug kernel: [  109.604442] ath: phy0: 48: Chn 1 pmi=0x0104228c;pmq=0x00eb9d9a;iqcm=0xfffdae7c;
Tue Dec 27 22:36:39 2016 kern.debug kernel: [  109.611815] ath: phy0: 48: Chn 2 pmi=0x013c3eec;pmq=0x0142fe99;iqcm=0xfffeef20;
Tue Dec 27 22:36:39 2016 kern.debug kernel: [  109.619168] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:39 2016 kern.debug kernel: [  109.717104] ath: phy0: 49: Chn 0 pmi=0x00d865b0;pmq=0x00dad7e4;iqcm=0xfffe5f35;
Tue Dec 27 22:36:39 2016 kern.debug kernel: [  109.724481] ath: phy0: 49: Chn 1 pmi=0x010d176a;pmq=0x00f369c5;iqcm=0xfffd61ac;
Tue Dec 27 22:36:39 2016 kern.debug kernel: [  109.731856] ath: phy0: 49: Chn 2 pmi=0x01451c01;pmq=0x014d25f9;iqcm=0xfffee38d;
Tue Dec 27 22:36:39 2016 kern.debug kernel: [  109.739210] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  110.637059] ath: phy0: 50: Chn 0 pmi=0x00e3188f;pmq=0x00e4edc4;iqcm=0xfffd27d3;
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  110.644426] ath: phy0: 50: Chn 1 pmi=0x0113424e;pmq=0x00f92d68;iqcm=0xfffd8139;
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  110.651794] ath: phy0: 50: Chn 2 pmi=0x015af9d5;pmq=0x015cc847;iqcm=0xfffe245f;
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  110.659149] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  110.757047] ath: phy0: 51: Chn 0 pmi=0x00e661cc;pmq=0x00e8701c;iqcm=0xfffc6071;
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  110.764408] ath: phy0: 51: Chn 1 pmi=0x01165e0d;pmq=0x00fc7ba3;iqcm=0xfffdb8ea;
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  110.771779] ath: phy0: 51: Chn 2 pmi=0x015e6f6a;pmq=0x0160ab0c;iqcm=0xfffdcf18;
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  110.779137] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  111.377047] ath: phy0: 52: Chn 0 pmi=0x00e6b8e9;pmq=0x00e8ddf0;iqcm=0xfffc6d10;
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  111.384413] ath: phy0: 52: Chn 1 pmi=0x01170c3b;pmq=0x00fd05e1;iqcm=0xfffdc01a;
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  111.391782] ath: phy0: 52: Chn 2 pmi=0x015f3c24;pmq=0x01615d16;iqcm=0xfffdd31e;
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  111.399140] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  111.497086] ath: phy0: 53: Chn 0 pmi=0x00f7b8af;pmq=0x00f84a3d;iqcm=0xfffd841d;
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  111.504467] ath: phy0: 53: Chn 1 pmi=0x01205f65;pmq=0x0104a77a;iqcm=0xfffe5277;
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  111.511835] ath: phy0: 53: Chn 2 pmi=0x016bbd3b;pmq=0x016d8fbd;iqcm=0xfffee59d;
Tue Dec 27 22:36:40 2016 kern.debug kernel: [  111.519185] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.617103] ath: phy0: 54: Chn 0 pmi=0x01042b62;pmq=0x01065bce;iqcm=0xfffc28af;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.624479] ath: phy0: 54: Chn 1 pmi=0x012a3599;pmq=0x01103fa7;iqcm=0xfffdfe14;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.631843] ath: phy0: 54: Chn 2 pmi=0x0174f322;pmq=0x0178e0f5;iqcm=0xfffdd605;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.639194] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.737089] ath: phy0: 55: Chn 0 pmi=0x01081c98;pmq=0x010b0ea0;iqcm=0xfffc07ce;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.744455] ath: phy0: 55: Chn 1 pmi=0x0133cc97;pmq=0x011ab0ce;iqcm=0xfffe1832;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.751825] ath: phy0: 55: Chn 2 pmi=0x017d2d36;pmq=0x01827e6a;iqcm=0xfffd8223;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.759176] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.857085] ath: phy0: 56: Chn 0 pmi=0x012b4707;pmq=0x012955f2;iqcm=0x000307d0;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.864461] ath: phy0: 56: Chn 1 pmi=0x013fb24d;pmq=0x01242b63;iqcm=0xfffe5282;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.871825] ath: phy0: 56: Chn 2 pmi=0x0187e0f7;pmq=0x018ab1a2;iqcm=0xfffe1af8;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.879175] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.977102] ath: phy0: 57: Chn 0 pmi=0x01393f73;pmq=0x013520a5;iqcm=0x0002342e;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.984480] ath: phy0: 57: Chn 1 pmi=0x01492abb;pmq=0x012d9a75;iqcm=0xfffd6bb3;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.991851] ath: phy0: 57: Chn 2 pmi=0x0190b9a4;pmq=0x0193d2d1;iqcm=0xfffd9fa1;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  111.999204] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.097087] ath: phy0: 58: Chn 0 pmi=0x0143f966;pmq=0x013e01f8;iqcm=0x00002161;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.104463] ath: phy0: 58: Chn 1 pmi=0x0150a73c;pmq=0x0138518b;iqcm=0xfffe3bca;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.111832] ath: phy0: 58: Chn 2 pmi=0x0199b058;pmq=0x019fcfe2;iqcm=0xfffb4efb;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.119184] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.217087] ath: phy0: 59: Chn 0 pmi=0x014bd240;pmq=0x014a1bf3;iqcm=0x00015ef4;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.224465] ath: phy0: 59: Chn 1 pmi=0x015cc1c1;pmq=0x013e8a34;iqcm=0xfffd658a;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.231833] ath: phy0: 59: Chn 2 pmi=0x01a35247;pmq=0x01a8048f;iqcm=0xfffd6ee5;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.239183] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.337224] ath: phy0: 60: Chn 0 pmi=0x0154a60b;pmq=0x01544796;iqcm=0x0002c438;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.344604] ath: phy0: 60: Chn 1 pmi=0x0167db5e;pmq=0x01473471;iqcm=0xfffca7bd;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.351994] ath: phy0: 60: Chn 2 pmi=0x01ae755b;pmq=0x01b2375b;iqcm=0xfffe4400;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.359349] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.457148] ath: phy0: 61: Chn 0 pmi=0x01602116;pmq=0x015daf22;iqcm=0x00025bf5;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.464523] ath: phy0: 61: Chn 1 pmi=0x01733d4f;pmq=0x0152b57e;iqcm=0xfffb6196;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.471908] ath: phy0: 61: Chn 2 pmi=0x01bb810f;pmq=0x01bbfa79;iqcm=0xfffe26bb;
Tue Dec 27 22:36:41 2016 kern.debug kernel: [  112.479262] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.577086] ath: phy0: 62: Chn 0 pmi=0x016b1081;pmq=0x016654ca;iqcm=0x00034dc6;
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.584461] ath: phy0: 62: Chn 1 pmi=0x017da552;pmq=0x015c0920;iqcm=0xfffa1ee3;
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.591833] ath: phy0: 62: Chn 2 pmi=0x01c63645;pmq=0x01c4d422;iqcm=0xfffe74fc;
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.599183] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.697090] ath: phy0: 63: Chn 0 pmi=0x01793ca3;pmq=0x017345f7;iqcm=0x0002a10b;
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.704466] ath: phy0: 63: Chn 1 pmi=0x018a045c;pmq=0x016946f8;iqcm=0xfff9e48c;
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.711841] ath: phy0: 63: Chn 2 pmi=0x01d3a5d5;pmq=0x01d02e62;iqcm=0xfffd969d;
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.719191] ath: phy0: Starting IQ Cal and Correction for Chain 0
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.725315] ath: phy0: Original: Chn 0 iq_corr_meas = 0x0002a10b
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.731363] ath: phy0: Chn 0 pwr_meas_i = 0x01793ca3
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.736346] ath: phy0: Chn 0 pwr_meas_q = 0x017345f7
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.741347] ath: phy0: iqCorrNeg is 0x00000000
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.745811] ath: phy0: Chn 0 iCoff = 0x00000000
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.750378] ath: phy0: Chn 0 qCoff = 0x00000001
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.754927] ath: phy0: New: Chn 0 iCoff = 0x00000000
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.759931] ath: phy0: Chn 0 : iCoff = 0x40  qCoff = 0x1
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.765272] ath: phy0: IQ Cal and Correction done for Chain 0
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.771055] ath: phy0: Starting IQ Cal and Correction for Chain 1
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.777188] ath: phy0: Original: Chn 1 iq_corr_meas = 0xfff9e48c
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.783215] ath: phy0: Chn 1 pwr_meas_i = 0x018a045c
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.788219] ath: phy0: Chn 1 pwr_meas_q = 0x016946f8
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.793201] ath: phy0: iqCorrNeg is 0x00000001
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.797674] ath: phy0: Chn 1 iCoff = 0x00000002
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.802222] ath: phy0: Chn 1 qCoff = 0x00000005
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.806777] ath: phy0: New: Chn 1 iCoff = 0x00000002
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.811780] ath: phy0: Chn 1 : iCoff = 0x2  qCoff = 0x5
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.817039] ath: phy0: IQ Cal and Correction done for Chain 1
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.822805] ath: phy0: Starting IQ Cal and Correction for Chain 2
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.828941] ath: phy0: Original: Chn 2 iq_corr_meas = 0xfffd969d
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.834970] ath: phy0: Chn 2 pwr_meas_i = 0x01d3a5d5
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.839973] ath: phy0: Chn 2 pwr_meas_q = 0x01d02e62
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.844955] ath: phy0: iqCorrNeg is 0x00000001
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.849437] ath: phy0: Chn 2 iCoff = 0x00000000
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.853985] ath: phy0: Chn 2 qCoff = 0x00000000
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.858553] ath: phy0: New: Chn 2 iCoff = 0x00000000
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.863538] ath: phy0: Chn 2 : iCoff = 0x0  qCoff = 0x0
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.868802] ath: phy0: IQ Cal and Correction done for Chain 2
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.874576] ath: phy0: NF calibrated [ctl] [chain 0] is -92
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.880183] ath: phy0: NF calibrated [ctl] [chain 1] is -90
Tue Dec 27 22:36:42 2016 kern.debug kernel: [  112.885785] ath: phy0: NF calibrated [ctl] [chain 2] is -89
Tue Dec 27 22:36:51 2016 kern.debug kernel: [  121.517029] ath: phy0: tx hung, resetting the chip
Tue Dec 27 22:36:51 2016 kern.debug kernel: [  121.527947] ath: phy0: Failed to stop TX DMA, queues=0x002!
Tue Dec 27 22:36:51 2016 kern.debug kernel: [  121.540425] ath: phy0: NF calibrated [ctl] [chain 0] is -92
Tue Dec 27 22:36:51 2016 kern.debug kernel: [  121.546033] ath: phy0: NF calibrated [ctl] [chain 1] is -90
Tue Dec 27 22:36:51 2016 kern.debug kernel: [  121.551678] ath: phy0: NF calibrated [ctl] [chain 2] is -89
Tue Dec 27 22:36:51 2016 kern.debug kernel: [  121.588036] ath: phy0: ah->misc_mode 0xc
Tue Dec 27 22:36:51 2016 kern.debug kernel: [  121.594481] ath: phy0: enabling IQ Calibration
Tue Dec 27 22:36:51 2016 kern.debug kernel: [  121.598973] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:51 2016 kern.debug kernel: [  121.604221] ath: phy0: Setting CFG 0x10a
Tue Dec 27 22:36:52 2016 kern.debug kernel: [  122.617023] ath: phy0: tx hung, resetting the chip
Tue Dec 27 22:36:52 2016 kern.debug kernel: [  122.628055] ath: phy0: NF calibrated [ctl] [chain 0] is -92
Tue Dec 27 22:36:52 2016 kern.debug kernel: [  122.633666] ath: phy0: NF calibrated [ctl] [chain 1] is -91
Tue Dec 27 22:36:52 2016 kern.debug kernel: [  122.639323] ath: phy0: NF calibrated [ctl] [chain 2] is -90
Tue Dec 27 22:36:52 2016 kern.debug kernel: [  122.675653] ath: phy0: ah->misc_mode 0xc
Tue Dec 27 22:36:52 2016 kern.debug kernel: [  122.682119] ath: phy0: enabling IQ Calibration
Tue Dec 27 22:36:52 2016 kern.debug kernel: [  122.686582] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:52 2016 kern.debug kernel: [  122.691855] ath: phy0: Setting CFG 0x10a
Tue Dec 27 22:36:53 2016 kern.debug kernel: [  123.707020] ath: phy0: tx hung, resetting the chip
Tue Dec 27 22:36:53 2016 kern.debug kernel: [  123.716234] ath: phy0: NF calibrated [ctl] [chain 0] is -109
Tue Dec 27 22:36:53 2016 kern.debug kernel: [  123.722003] ath: phy0: NF[0] (-109) < MIN (-100), correcting to NOM
Tue Dec 27 22:36:53 2016 kern.debug kernel: [  123.728311] ath: phy0: NF calibrated [ctl] [chain 1] is -108
Tue Dec 27 22:36:53 2016 kern.debug kernel: [  123.733999] ath: phy0: NF[1] (-108) < MIN (-100), correcting to NOM
Tue Dec 27 22:36:53 2016 kern.debug kernel: [  123.740308] ath: phy0: NF calibrated [ctl] [chain 2] is -90
Tue Dec 27 22:36:53 2016 kern.debug kernel: [  123.776641] ath: phy0: ah->misc_mode 0xc
Tue Dec 27 22:36:53 2016 kern.debug kernel: [  123.783109] ath: phy0: enabling IQ Calibration
Tue Dec 27 22:36:53 2016 kern.debug kernel: [  123.787589] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:53 2016 kern.debug kernel: [  123.792842] ath: phy0: Setting CFG 0x10a
Tue Dec 27 22:36:54 2016 kern.debug kernel: [  124.797028] ath: phy0: tx hung, resetting the chip
Tue Dec 27 22:36:54 2016 kern.debug kernel: [  124.803197] ath: phy0: NF calibrated [ctl] [chain 0] is -93
Tue Dec 27 22:36:54 2016 kern.debug kernel: [  124.808879] ath: phy0: NF calibrated [ctl] [chain 1] is -91
Tue Dec 27 22:36:54 2016 kern.debug kernel: [  124.814473] ath: phy0: NF calibrated [ctl] [chain 2] is -90
Tue Dec 27 22:36:54 2016 kern.debug kernel: [  124.850816] ath: phy0: ah->misc_mode 0xc
Tue Dec 27 22:36:54 2016 kern.debug kernel: [  124.857253] ath: phy0: enabling IQ Calibration
Tue Dec 27 22:36:54 2016 kern.debug kernel: [  124.861715] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:54 2016 kern.debug kernel: [  124.866969] ath: phy0: Setting CFG 0x10a
Tue Dec 27 22:36:55 2016 kern.debug kernel: [  125.877052] ath: phy0: tx hung, resetting the chip
Tue Dec 27 22:36:55 2016 kern.debug kernel: [  125.883003] ath: phy0: NF calibrated [ctl] [chain 0] is -109
Tue Dec 27 22:36:55 2016 kern.debug kernel: [  125.888767] ath: phy0: NF[0] (-109) < MIN (-100), correcting to NOM
Tue Dec 27 22:36:55 2016 kern.debug kernel: [  125.895069] ath: phy0: NF calibrated [ctl] [chain 1] is -108
Tue Dec 27 22:36:55 2016 kern.debug kernel: [  125.900772] ath: phy0: NF[1] (-108) < MIN (-100), correcting to NOM
Tue Dec 27 22:36:55 2016 kern.debug kernel: [  125.907083] ath: phy0: NF calibrated [ctl] [chain 2] is -89
Tue Dec 27 22:36:55 2016 kern.debug kernel: [  125.943417] ath: phy0: ah->misc_mode 0xc
Tue Dec 27 22:36:55 2016 kern.debug kernel: [  125.949883] ath: phy0: enabling IQ Calibration
Tue Dec 27 22:36:55 2016 kern.debug kernel: [  125.954345] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:55 2016 kern.debug kernel: [  125.959618] ath: phy0: Setting CFG 0x10a
Tue Dec 27 22:36:56 2016 kern.debug kernel: [  126.967021] ath: phy0: tx hung, resetting the chip
Tue Dec 27 22:36:56 2016 kern.debug kernel: [  126.973556] ath: phy0: NF calibrated [ctl] [chain 0] is -92
Tue Dec 27 22:36:56 2016 kern.debug kernel: [  126.979239] ath: phy0: NF calibrated [ctl] [chain 1] is -92
Tue Dec 27 22:36:56 2016 kern.debug kernel: [  126.984835] ath: phy0: NF calibrated [ctl] [chain 2] is -90
Tue Dec 27 22:36:56 2016 kern.debug kernel: [  127.021180] ath: phy0: ah->misc_mode 0xc
Tue Dec 27 22:36:56 2016 kern.debug kernel: [  127.027624] ath: phy0: enabling IQ Calibration
Tue Dec 27 22:36:56 2016 kern.debug kernel: [  127.032086] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:56 2016 kern.debug kernel: [  127.037356] ath: phy0: Setting CFG 0x10a
Tue Dec 27 22:36:57 2016 kern.debug kernel: [  128.047028] ath: phy0: tx hung, resetting the chip
Tue Dec 27 22:36:57 2016 kern.debug kernel: [  128.052847] ath: phy0: NF calibrated [ctl] [chain 0] is -92
Tue Dec 27 22:36:57 2016 kern.debug kernel: [  128.058522] ath: phy0: NF calibrated [ctl] [chain 1] is -90
Tue Dec 27 22:36:57 2016 kern.debug kernel: [  128.064116] ath: phy0: NF calibrated [ctl] [chain 2] is -90
Tue Dec 27 22:36:57 2016 kern.debug kernel: [  128.100460] ath: phy0: ah->misc_mode 0xc
Tue Dec 27 22:36:57 2016 kern.debug kernel: [  128.106898] ath: phy0: enabling IQ Calibration
Tue Dec 27 22:36:57 2016 kern.debug kernel: [  128.111392] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:57 2016 kern.debug kernel: [  128.116638] ath: phy0: Setting CFG 0x10a
Tue Dec 27 22:36:58 2016 kern.debug kernel: [  129.127041] ath: phy0: tx hung, resetting the chip
Tue Dec 27 22:36:58 2016 kern.debug kernel: [  129.132607] ath: phy0: NF calibrated [ctl] [chain 0] is -93
Tue Dec 27 22:36:58 2016 kern.debug kernel: [  129.138272] ath: phy0: NF calibrated [ctl] [chain 1] is -92
Tue Dec 27 22:36:58 2016 kern.debug kernel: [  129.143868] ath: phy0: NF calibrated [ctl] [chain 2] is -90
Tue Dec 27 22:36:58 2016 kern.debug kernel: [  129.180211] ath: phy0: ah->misc_mode 0xc
Tue Dec 27 22:36:58 2016 kern.debug kernel: [  129.186649] ath: phy0: enabling IQ Calibration
Tue Dec 27 22:36:58 2016 kern.debug kernel: [  129.191143] ath: phy0: starting IQ Mismatch Calibration
Tue Dec 27 22:36:58 2016 kern.debug kernel: [  129.196391] ath: phy0: Setting CFG 0x10a

# wifi is gone

Tue Dec 27 22:37:28 2016 kern.debug kernel: [  159.197039] ath: phy0: 0: Chn 0 pmi=0x00012439;pmq=0x00017528;iqcm=0x0000049c;
Tue Dec 27 22:37:28 2016 kern.debug kernel: [  159.204318] ath: phy0: 0: Chn 1 pmi=0x0003bf6f;pmq=0x000534c7;iqcm=0x0000499f;
Tue Dec 27 22:37:28 2016 kern.debug kernel: [  159.211593] ath: phy0: 0: Chn 2 pmi=0x00024e7d;pmq=0x0002af25;iqcm=0xffffe40c;
Tue Dec 27 22:37:28 2016 kern.debug kernel: [  159.218858] ath: phy0: starting IQ Mismatch Calibration



This it how it looks in the iperf client:


Client connecting to sven-virtualbox, TCP port 5001
TCP window size:  512 KByte (default)
------------------------------------------------------------
[  3] local 192.168.1.155 port 45565 connected with 192.168.1.223 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec  4.25 MBytes  35.7 Mbits/sec
[  3]  1.0- 2.0 sec  3.00 MBytes  25.2 Mbits/sec
[  3]  2.0- 3.0 sec  4.50 MBytes  37.7 Mbits/sec
[  3]  3.0- 4.0 sec  5.00 MBytes  41.9 Mbits/sec
[  3]  4.0- 5.0 sec  4.38 MBytes  36.7 Mbits/sec
[  3]  5.0- 6.0 sec  4.75 MBytes  39.8 Mbits/sec
[  3]  6.0- 7.0 sec  4.75 MBytes  39.8 Mbits/sec
[  3]  7.0- 8.0 sec  3.88 MBytes  32.5 Mbits/sec
[  3]  8.0- 9.0 sec  2.25 MBytes  18.9 Mbits/sec
[  3]  9.0-10.0 sec  0.00 Bytes  0.00 bits/sec
[  3] 10.0-11.0 sec  0.00 Bytes  0.00 bits/sec

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=13#comment1110


From lede-bugs at lists.infradead.org  Tue Dec 27 14:58:18 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 27 Dec 2016 22:58:18 +0000
Subject: [FS#13] Ath9k AP stays up for connected clients but doesn't show in
 scan on new ones
In-Reply-To: <FS13@bugs.lede-project.org>
References: <FS13@bugs.lede-project.org>
Message-ID: <mailman.76244.1483351999.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#13 - Ath9k AP stays up for connected clients but doesn't show in scan on new ones
User who did this - Felix Fietkau (nbd)

----------
I pushed another fix you can test to my staging tree. It fixes some issues with calibration (which might play a role in these hangs).
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=13#comment1113


From lede-bugs at lists.infradead.org  Wed Dec 28 10:45:41 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 28 Dec 2016 18:45:41 +0000
Subject: [FS#13] Ath9k AP stays up for connected clients but doesn't show in
 scan on new ones
In-Reply-To: <FS13@bugs.lede-project.org>
References: <FS13@bugs.lede-project.org>
Message-ID: <mailman.76245.1483351999.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#13 - Ath9k AP stays up for connected clients but doesn't show in scan on new ones
User who did this - IronicSven (IronicSven)

----------
Hi Felix,

building from your staging tree fails with:


mkimage -A mips -O linux -T kernel -a 0x80060000 -C lzma  -e 0x80060000 -n 'MIPS OpenWrt Linux-4.4.39' -d /home/sven/openwrt/staging/build_dir/target-mips_24kc_musl-1.1.15/linux-ar71xx_generic/vmlinux.bin.lzma /home/sven/openwrt/staging/bin/targets/ar71xx/generic/lede-ar71xx-generic-uImage-lzma.bin
mkimage: error while loading shared libraries: libssl.so.39: cannot open shared object file: No such file or directory
Makefile:97: recipe for target 'kernel_prepare' failed


But I copied package/kernel/mac80211/patches/347-ath9k-don-t-run-periodic-and-nf-calibation-at-the-sa.patch to the source tree and build.

Wifi still disconnects and disappears:


root at FlensNet:~# cat /etc/os-release | grep BUILD
BUILD_ID="r2697-19059d8"
root at FlensNet:~# logread -f
Wed Dec 28 19:33:43 2016 kern.debug kernel: [  332.937592] ath: phy0: 25: Chn 0 pmi=0x0116f140;pmq=0x00f32914;iqcm=0xfffbe571;
Wed Dec 28 19:33:43 2016 kern.debug kernel: [  332.944984] ath: phy0: 25: Chn 1 pmi=0x01056afb;pmq=0x00e676de;iqcm=0xffed8386;
Wed Dec 28 19:33:43 2016 kern.debug kernel: [  332.952353] ath: phy0: 25: Chn 2 pmi=0x012f4ac0;pmq=0x014e9e63;iqcm=0xfffb4073;
Wed Dec 28 19:33:43 2016 kern.debug kernel: [  332.959703] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:43 2016 kern.debug kernel: [  333.057560] ath: phy0: 26: Chn 0 pmi=0x011f2bb3;pmq=0x00fd3564;iqcm=0xfffdc475;
Wed Dec 28 19:33:43 2016 kern.debug kernel: [  333.064935] ath: phy0: 26: Chn 1 pmi=0x0112454a;pmq=0x00edba2e;iqcm=0xffeef206;
Wed Dec 28 19:33:43 2016 kern.debug kernel: [  333.072305] ath: phy0: 26: Chn 2 pmi=0x0135cf0b;pmq=0x0153a3c2;iqcm=0xfff9da25;
Wed Dec 28 19:33:43 2016 kern.debug kernel: [  333.079659] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:43 2016 kern.debug kernel: [  333.177571] ath: phy0: 27: Chn 0 pmi=0x012ac42e;pmq=0x010e011e;iqcm=0xfffc3314;
Wed Dec 28 19:33:43 2016 kern.debug kernel: [  333.184949] ath: phy0: 27: Chn 1 pmi=0x012781ff;pmq=0x0104af28;iqcm=0xfff0f89e;
Wed Dec 28 19:33:43 2016 kern.debug kernel: [  333.192316] ath: phy0: 27: Chn 2 pmi=0x014e6c33;pmq=0x016504ef;iqcm=0xfffc548f;
Wed Dec 28 19:33:43 2016 kern.debug kernel: [  333.199668] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.297593] ath: phy0: 28: Chn 0 pmi=0x01355eed;pmq=0x011733fe;iqcm=0xfffdea77;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.304975] ath: phy0: 28: Chn 1 pmi=0x01311926;pmq=0x010a570d;iqcm=0xfff14206;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.312344] ath: phy0: 28: Chn 2 pmi=0x01570f73;pmq=0x016e1511;iqcm=0xfffa5981;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.319694] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.417566] ath: phy0: 29: Chn 0 pmi=0x01402caf;pmq=0x011fcbb1;iqcm=0xfffd02fb;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.424940] ath: phy0: 29: Chn 1 pmi=0x013985c5;pmq=0x01123421;iqcm=0xfff03570;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.432313] ath: phy0: 29: Chn 2 pmi=0x01670d69;pmq=0x018201a0;iqcm=0xfffb32f1;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.439668] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.537551] ath: phy0: 30: Chn 0 pmi=0x0147317b;pmq=0x01282f28;iqcm=0xfffdbff9;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.544928] ath: phy0: 30: Chn 1 pmi=0x01420b08;pmq=0x0119af07;iqcm=0xfff13dde;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.552301] ath: phy0: 30: Chn 2 pmi=0x016c766a;pmq=0x01860125;iqcm=0xfffac293;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.559657] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.657570] ath: phy0: 31: Chn 0 pmi=0x0151bda6;pmq=0x0131d4df;iqcm=0xfffdf6f8;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.664944] ath: phy0: 31: Chn 1 pmi=0x014d18d2;pmq=0x0122d665;iqcm=0xfff153b3;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.672321] ath: phy0: 31: Chn 2 pmi=0x01727185;pmq=0x018bd0f8;iqcm=0xfffa83e7;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.679678] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.777546] ath: phy0: 32: Chn 0 pmi=0x015b2b23;pmq=0x0138ab95;iqcm=0xfffd4a37;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.784923] ath: phy0: 32: Chn 1 pmi=0x0156c208;pmq=0x012cd0a7;iqcm=0xfff05bcd;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.792291] ath: phy0: 32: Chn 2 pmi=0x017c5a64;pmq=0x01989722;iqcm=0xfffb141b;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.799648] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.897546] ath: phy0: 33: Chn 0 pmi=0x0163f2c5;pmq=0x01401afd;iqcm=0xfffbfa15;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.904939] ath: phy0: 33: Chn 1 pmi=0x015ff174;pmq=0x01384d0e;iqcm=0xffeeccf1;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.912308] ath: phy0: 33: Chn 2 pmi=0x018615fe;pmq=0x01a44025;iqcm=0xfffce338;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  333.919665] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  334.017562] ath: phy0: 34: Chn 0 pmi=0x016da0da;pmq=0x01485903;iqcm=0xfffaa932;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  334.024937] ath: phy0: 34: Chn 1 pmi=0x016a9902;pmq=0x014422fa;iqcm=0xffed3b55;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  334.032309] ath: phy0: 34: Chn 2 pmi=0x018f4083;pmq=0x01aef418;iqcm=0xfffe5490;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  334.039665] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  334.137539] ath: phy0: 35: Chn 0 pmi=0x017789d5;pmq=0x01514934;iqcm=0xfff97113;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  334.144911] ath: phy0: 35: Chn 1 pmi=0x0174bf29;pmq=0x014f5d06;iqcm=0xffecbec8;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  334.152285] ath: phy0: 35: Chn 2 pmi=0x0199f5f6;pmq=0x01ba1def;iqcm=0xffff6a2b;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  334.159639] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  334.257717] ath: phy0: 36: Chn 0 pmi=0x01807374;pmq=0x015eb9f7;iqcm=0xfff9bf54;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  334.265092] ath: phy0: 36: Chn 1 pmi=0x017d81a0;pmq=0x0157f619;iqcm=0xffef1ec2;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  334.272483] ath: phy0: 36: Chn 2 pmi=0x01a40a6c;pmq=0x01bfab17;iqcm=0xffff53dc;
Wed Dec 28 19:33:44 2016 kern.debug kernel: [  334.279840] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.377564] ath: phy0: 37: Chn 0 pmi=0x018a4ad3;pmq=0x0167fbfd;iqcm=0xfffa49d4;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.384943] ath: phy0: 37: Chn 1 pmi=0x018a9594;pmq=0x01621407;iqcm=0xffef15f8;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.392313] ath: phy0: 37: Chn 2 pmi=0x01ad41bf;pmq=0x01c8be59;iqcm=0xfffe82c3;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.399663] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.497630] ath: phy0: 38: Chn 0 pmi=0x0193464e;pmq=0x0173da21;iqcm=0xfff8e0ac;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.504987] ath: phy0: 38: Chn 1 pmi=0x019008ba;pmq=0x0167d364;iqcm=0xfff02cad;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.512377] ath: phy0: 38: Chn 2 pmi=0x01b6e605;pmq=0x01cee40e;iqcm=0xffff3f9c;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.519735] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.617539] ath: phy0: 39: Chn 0 pmi=0x019dd381;pmq=0x017d221e;iqcm=0xfff8c726;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.624915] ath: phy0: 39: Chn 1 pmi=0x0198d820;pmq=0x016f3fd5;iqcm=0xffefa65a;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.632288] ath: phy0: 39: Chn 2 pmi=0x01bda8bd;pmq=0x01d60409;iqcm=0xffff20ed;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.639644] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.737564] ath: phy0: 40: Chn 0 pmi=0x01a7bde5;pmq=0x01882adf;iqcm=0xfff7defd;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.744926] ath: phy0: 40: Chn 1 pmi=0x01a1cfc6;pmq=0x0178bb60;iqcm=0xfff06da1;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.752298] ath: phy0: 40: Chn 2 pmi=0x01c86ebb;pmq=0x01de27a1;iqcm=0xffffc46f;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.759653] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.857529] ath: phy0: 41: Chn 0 pmi=0x01b102c5;pmq=0x019371f6;iqcm=0xfffa1cc2;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.864907] ath: phy0: 41: Chn 1 pmi=0x01aeb5d0;pmq=0x01804a5e;iqcm=0xfff2aa14;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.872275] ath: phy0: 41: Chn 2 pmi=0x01d3e2df;pmq=0x01e68df5;iqcm=0xfffcfc29;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.879626] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.977619] ath: phy0: 42: Chn 0 pmi=0x01b944cd;pmq=0x019e8ac5;iqcm=0xfff9316a;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.984995] ath: phy0: 42: Chn 1 pmi=0x01b76489;pmq=0x018ab76f;iqcm=0xfff3d927;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.992385] ath: phy0: 42: Chn 2 pmi=0x01dbf56c;pmq=0x01ebf3a0;iqcm=0xfffd734a;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  334.999741] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  335.097553] ath: phy0: 43: Chn 0 pmi=0x01c34ac3;pmq=0x01aa00be;iqcm=0xfff892f6;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  335.104934] ath: phy0: 43: Chn 1 pmi=0x01bebc50;pmq=0x0192b661;iqcm=0xfff42338;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  335.112303] ath: phy0: 43: Chn 2 pmi=0x01e4ec6e;pmq=0x01f30175;iqcm=0xfffdc199;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  335.119660] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  335.217513] ath: phy0: 44: Chn 0 pmi=0x01d15b03;pmq=0x01b729b2;iqcm=0xfff46905;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  335.224883] ath: phy0: 44: Chn 1 pmi=0x01c6f998;pmq=0x01a39d73;iqcm=0xfff35674;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  335.232253] ath: phy0: 44: Chn 2 pmi=0x01f9d4cf;pmq=0x0208c083;iqcm=0x0005882d;
Wed Dec 28 19:33:45 2016 kern.debug kernel: [  335.239608] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.337523] ath: phy0: 45: Chn 0 pmi=0x01d85c21;pmq=0x01c29fda;iqcm=0xfff5a2b4;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.344897] ath: phy0: 45: Chn 1 pmi=0x01d0cbb4;pmq=0x01ab0a6b;iqcm=0xfff64a70;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.352266] ath: phy0: 45: Chn 2 pmi=0x02021680;pmq=0x020ce1f6;iqcm=0x0004562a;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.359617] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.457530] ath: phy0: 46: Chn 0 pmi=0x01e19df9;pmq=0x01cb5bf6;iqcm=0xfff5aad8;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.464898] ath: phy0: 46: Chn 1 pmi=0x01d93c3b;pmq=0x01b26da1;iqcm=0xfff6177c;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.472272] ath: phy0: 46: Chn 2 pmi=0x020b5e73;pmq=0x02162990;iqcm=0x00043038;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.479624] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.577508] ath: phy0: 47: Chn 0 pmi=0x01f03c7f;pmq=0x01d38382;iqcm=0xfff5181a;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.584884] ath: phy0: 47: Chn 1 pmi=0x01e38332;pmq=0x01bbf95d;iqcm=0xfff301da;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.592258] ath: phy0: 47: Chn 2 pmi=0x0212641e;pmq=0x0222a50f;iqcm=0x0004f55c;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.599615] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.697641] ath: phy0: 48: Chn 0 pmi=0x01fd8e31;pmq=0x01de8504;iqcm=0xfff500cb;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.705000] ath: phy0: 48: Chn 1 pmi=0x01e9d357;pmq=0x01c1670b;iqcm=0xfff2715c;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.712385] ath: phy0: 48: Chn 2 pmi=0x0217ec1e;pmq=0x0228fecf;iqcm=0x0004e370;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.719737] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.817611] ath: phy0: 49: Chn 0 pmi=0x020ad6fd;pmq=0x01ee992a;iqcm=0xfff3274d;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.824979] ath: phy0: 49: Chn 1 pmi=0x01f011b3;pmq=0x01c75f1a;iqcm=0xfff35da0;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.832372] ath: phy0: 49: Chn 2 pmi=0x021f9e68;pmq=0x022e9ab8;iqcm=0x00058169;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.839728] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.937498] ath: phy0: 50: Chn 0 pmi=0x0215889d;pmq=0x01fda9ca;iqcm=0xfff51152;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.944874] ath: phy0: 50: Chn 1 pmi=0x01f5d92e;pmq=0x01ca71e5;iqcm=0xfff2f8ec;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.952250] ath: phy0: 50: Chn 2 pmi=0x0234b32d;pmq=0x023b9a8b;iqcm=0x000342d8;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  335.959604] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  336.057495] ath: phy0: 51: Chn 0 pmi=0x0220a63b;pmq=0x02059ff2;iqcm=0xfff3e155;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  336.064869] ath: phy0: 51: Chn 1 pmi=0x01fe988c;pmq=0x01d44f5a;iqcm=0xfff41ca4;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  336.072239] ath: phy0: 51: Chn 2 pmi=0x023da714;pmq=0x0247ca67;iqcm=0x0003f6ad;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  336.079595] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  336.177562] ath: phy0: 52: Chn 0 pmi=0x022a0eee;pmq=0x0211638e;iqcm=0xfff3e75c;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  336.184935] ath: phy0: 52: Chn 1 pmi=0x020c0962;pmq=0x01ddd569;iqcm=0xfff2c3ab;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  336.192317] ath: phy0: 52: Chn 2 pmi=0x02483de0;pmq=0x024f7b57;iqcm=0x00040ea8;
Wed Dec 28 19:33:46 2016 kern.debug kernel: [  336.199674] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.297503] ath: phy0: 53: Chn 0 pmi=0x02336c3b;pmq=0x0218dc3f;iqcm=0xfff3c0e1;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.304886] ath: phy0: 53: Chn 1 pmi=0x021a3d08;pmq=0x01eb0560;iqcm=0xfff389c0;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.312253] ath: phy0: 53: Chn 2 pmi=0x025276a9;pmq=0x025bceca;iqcm=0x0003d898;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.319603] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.417564] ath: phy0: 54: Chn 0 pmi=0x0243e28d;pmq=0x022c6b19;iqcm=0xfff42088;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.424936] ath: phy0: 54: Chn 1 pmi=0x02248379;pmq=0x01f3a18c;iqcm=0xfff22cae;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.432320] ath: phy0: 54: Chn 2 pmi=0x02635a56;pmq=0x02683507;iqcm=0x0003abf0;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.439674] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.537515] ath: phy0: 55: Chn 0 pmi=0x0251f5a4;pmq=0x023a574a;iqcm=0xfff6b414;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.544892] ath: phy0: 55: Chn 1 pmi=0x022d9c06;pmq=0x01ff1ddc;iqcm=0xfff12df4;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.552261] ath: phy0: 55: Chn 2 pmi=0x02713c07;pmq=0x0275e19f;iqcm=0x0000c3fc;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.559611] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.657481] ath: phy0: 56: Chn 0 pmi=0x025f7d7e;pmq=0x0245c662;iqcm=0xfff64bb1;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.664854] ath: phy0: 56: Chn 1 pmi=0x02398bea;pmq=0x02099301;iqcm=0xfff1b39d;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.672228] ath: phy0: 56: Chn 2 pmi=0x027c097d;pmq=0x0281ddfa;iqcm=0x00013fed;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.679585] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.777486] ath: phy0: 57: Chn 0 pmi=0x026c5069;pmq=0x0254530c;iqcm=0xfff992b3;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.784862] ath: phy0: 57: Chn 1 pmi=0x0243c684;pmq=0x02179456;iqcm=0xffefc684;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.792237] ath: phy0: 57: Chn 2 pmi=0x02895b30;pmq=0x028c13a3;iqcm=0xfffe6330;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.799593] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.897493] ath: phy0: 58: Chn 0 pmi=0x027dde59;pmq=0x025c8b6a;iqcm=0xfffb1364;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.904869] ath: phy0: 58: Chn 1 pmi=0x024d5634;pmq=0x0225f9a1;iqcm=0xfff29be3;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.912240] ath: phy0: 58: Chn 2 pmi=0x029a8cf6;pmq=0x02a0110d;iqcm=0xfff8ae9e;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  336.919593] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  337.017480] ath: phy0: 59: Chn 0 pmi=0x028b3819;pmq=0x02662e62;iqcm=0xfffe5568;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  337.024853] ath: phy0: 59: Chn 1 pmi=0x025604ac;pmq=0x02352338;iqcm=0xfff24c83;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  337.032228] ath: phy0: 59: Chn 2 pmi=0x02a5ddba;pmq=0x02abe70b;iqcm=0xfff52164;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  337.039584] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  337.137484] ath: phy0: 60: Chn 0 pmi=0x029720ee;pmq=0x02775499;iqcm=0xffffa522;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  337.144864] ath: phy0: 60: Chn 1 pmi=0x02699f8d;pmq=0x0243e5a8;iqcm=0xffee440a;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  337.152232] ath: phy0: 60: Chn 2 pmi=0x02b1d96d;pmq=0x02b3c431;iqcm=0xfff4a65d;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  337.159583] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  337.257505] ath: phy0: 61: Chn 0 pmi=0x02a0b78d;pmq=0x028266d6;iqcm=0xffff209f;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  337.264879] ath: phy0: 61: Chn 1 pmi=0x0274b078;pmq=0x024c2c48;iqcm=0xffed96d5;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  337.272251] ath: phy0: 61: Chn 2 pmi=0x02bd3cef;pmq=0x02bcbb86;iqcm=0xfff53806;
Wed Dec 28 19:33:47 2016 kern.debug kernel: [  337.279599] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.377586] ath: phy0: 62: Chn 0 pmi=0x02ac5ea5;pmq=0x028c20f6;iqcm=0xfffe252e;
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.384951] ath: phy0: 62: Chn 1 pmi=0x027dc97e;pmq=0x025384ed;iqcm=0xffee3c20;
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.392341] ath: phy0: 62: Chn 2 pmi=0x02c7607d;pmq=0x02c7a4b5;iqcm=0xfff654c6;
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.399697] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.497488] ath: phy0: 63: Chn 0 pmi=0x02ba601b;pmq=0x0299f561;iqcm=0xfffe0184;
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.504854] ath: phy0: 63: Chn 1 pmi=0x0290c94c;pmq=0x0263df4c;iqcm=0xffedb708;
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.512229] ath: phy0: 63: Chn 2 pmi=0x02d159f2;pmq=0x02d015d1;iqcm=0xfff634ef;
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.519584] ath: phy0: Starting IQ Cal and Correction for Chain 0
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.525706] ath: phy0: Original: Chn 0 iq_corr_meas = 0xfffe0184
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.531756] ath: phy0: Chn 0 pwr_meas_i = 0x02ba601b
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.536746] ath: phy0: Chn 0 pwr_meas_q = 0x0299f561
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.541749] ath: phy0: iqCorrNeg is 0x00000001
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.546210] ath: phy0: Chn 0 iCoff = 0x00000000
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.550779] ath: phy0: Chn 0 qCoff = 0x00000003
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.555326] ath: phy0: New: Chn 0 iCoff = 0x00000000
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.560332] ath: phy0: Chn 0 : iCoff = 0x0  qCoff = 0x3
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.565585] ath: phy0: IQ Cal and Correction done for Chain 0
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.571371] ath: phy0: Starting IQ Cal and Correction for Chain 1
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.577503] ath: phy0: Original: Chn 1 iq_corr_meas = 0xffedb708
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.583538] ath: phy0: Chn 1 pwr_meas_i = 0x0290c94c
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.588542] ath: phy0: Chn 1 pwr_meas_q = 0x0263df4c
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.593531] ath: phy0: iqCorrNeg is 0x00000001
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.598006] ath: phy0: Chn 1 iCoff = 0x00000003
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.602561] ath: phy0: Chn 1 qCoff = 0x00000004
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.607116] ath: phy0: New: Chn 1 iCoff = 0x00000003
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.612124] ath: phy0: Chn 1 : iCoff = 0x3  qCoff = 0x4
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.617373] ath: phy0: IQ Cal and Correction done for Chain 1
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.623169] ath: phy0: Starting IQ Cal and Correction for Chain 2
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.629309] ath: phy0: Original: Chn 2 iq_corr_meas = 0xfff634ef
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.635344] ath: phy0: Chn 2 pwr_meas_i = 0x02d159f2
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.640349] ath: phy0: Chn 2 pwr_meas_q = 0x02d015d1
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.645338] ath: phy0: iqCorrNeg is 0x00000001
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.649821] ath: phy0: Chn 2 iCoff = 0x00000001
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.654376] ath: phy0: Chn 2 qCoff = 0x00000000
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.658946] ath: phy0: New: Chn 2 iCoff = 0x00000001
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.663939] ath: phy0: Chn 2 : iCoff = 0x1  qCoff = 0x0
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.669203] ath: phy0: IQ Cal and Correction done for Chain 2
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.767480] ath: phy0: NF calibrated [ctl] [chain 0] is -92
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.773093] ath: phy0: NF calibrated [ctl] [chain 1] is -91
Wed Dec 28 19:33:48 2016 kern.debug kernel: [  337.778717] ath: phy0: NF calibrated [ctl] [chain 2] is -89
Wed Dec 28 19:33:58 2016 kern.debug kernel: [  347.757307] ath: phy0: tx hung, resetting the chip
Wed Dec 28 19:33:58 2016 kern.debug kernel: [  347.769086] ath: phy0: NF calibrated [ctl] [chain 0] is -92
Wed Dec 28 19:33:58 2016 kern.debug kernel: [  347.774701] ath: phy0: NF calibrated [ctl] [chain 1] is -91
Wed Dec 28 19:33:58 2016 kern.debug kernel: [  347.780342] ath: phy0: NF calibrated [ctl] [chain 2] is -89
Wed Dec 28 19:33:58 2016 kern.debug kernel: [  347.816668] ath: phy0: ah->misc_mode 0xc
Wed Dec 28 19:33:58 2016 kern.debug kernel: [  347.823137] ath: phy0: enabling IQ Calibration
Wed Dec 28 19:33:58 2016 kern.debug kernel: [  347.827618] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:58 2016 kern.debug kernel: [  347.832870] ath: phy0: Setting CFG 0x10a
Wed Dec 28 19:33:59 2016 kern.debug kernel: [  348.837255] ath: phy0: tx hung, resetting the chip
Wed Dec 28 19:33:59 2016 kern.debug kernel: [  348.848300] ath: phy0: NF calibrated [ctl] [chain 0] is -93
Wed Dec 28 19:33:59 2016 kern.debug kernel: [  348.853913] ath: phy0: NF calibrated [ctl] [chain 1] is -91
Wed Dec 28 19:33:59 2016 kern.debug kernel: [  348.859569] ath: phy0: NF calibrated [ctl] [chain 2] is -90
Wed Dec 28 19:33:59 2016 kern.debug kernel: [  348.895898] ath: phy0: ah->misc_mode 0xc
Wed Dec 28 19:33:59 2016 kern.debug kernel: [  348.902366] ath: phy0: enabling IQ Calibration
Wed Dec 28 19:33:59 2016 kern.debug kernel: [  348.906829] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:33:59 2016 kern.debug kernel: [  348.912103] ath: phy0: Setting CFG 0x10a
Wed Dec 28 19:34:00 2016 kern.debug kernel: [  349.927241] ath: phy0: tx hung, resetting the chip
Wed Dec 28 19:34:00 2016 kern.debug kernel: [  349.934038] ath: phy0: NF calibrated [ctl] [chain 0] is -93
Wed Dec 28 19:34:00 2016 kern.debug kernel: [  349.939727] ath: phy0: NF calibrated [ctl] [chain 1] is -91
Wed Dec 28 19:34:00 2016 kern.debug kernel: [  349.945337] ath: phy0: NF calibrated [ctl] [chain 2] is -90
Wed Dec 28 19:34:00 2016 kern.debug kernel: [  349.981677] ath: phy0: ah->misc_mode 0xc
Wed Dec 28 19:34:00 2016 kern.debug kernel: [  349.988118] ath: phy0: enabling IQ Calibration
Wed Dec 28 19:34:00 2016 kern.debug kernel: [  349.992580] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:34:00 2016 kern.debug kernel: [  349.997851] ath: phy0: Setting CFG 0x10a
Wed Dec 28 19:34:01 2016 kern.debug kernel: [  351.007247] ath: phy0: tx hung, resetting the chip
Wed Dec 28 19:34:01 2016 kern.debug kernel: [  351.013115] ath: phy0: NF calibrated [ctl] [chain 0] is -92
Wed Dec 28 19:34:01 2016 kern.debug kernel: [  351.018798] ath: phy0: NF calibrated [ctl] [chain 1] is -91
Wed Dec 28 19:34:01 2016 kern.debug kernel: [  351.024393] ath: phy0: NF calibrated [ctl] [chain 2] is -90
Wed Dec 28 19:34:01 2016 kern.debug kernel: [  351.060733] ath: phy0: ah->misc_mode 0xc
Wed Dec 28 19:34:01 2016 kern.debug kernel: [  351.067174] ath: phy0: enabling IQ Calibration
Wed Dec 28 19:34:01 2016 kern.debug kernel: [  351.071669] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:34:01 2016 kern.debug kernel: [  351.076925] ath: phy0: Setting CFG 0x10a
Wed Dec 28 19:34:02 2016 kern.debug kernel: [  352.087210] ath: phy0: tx hung, resetting the chip
Wed Dec 28 19:34:02 2016 kern.debug kernel: [  352.093158] ath: phy0: NF calibrated [ctl] [chain 0] is -93
Wed Dec 28 19:34:02 2016 kern.debug kernel: [  352.098827] ath: phy0: NF calibrated [ctl] [chain 1] is -92
Wed Dec 28 19:34:02 2016 kern.debug kernel: [  352.104424] ath: phy0: NF calibrated [ctl] [chain 2] is -90
Wed Dec 28 19:34:02 2016 kern.debug kernel: [  352.140764] ath: phy0: ah->misc_mode 0xc
Wed Dec 28 19:34:02 2016 kern.debug kernel: [  352.147225] ath: phy0: enabling IQ Calibration
Wed Dec 28 19:34:02 2016 kern.debug kernel: [  352.151693] ath: phy0: starting IQ Mismatch Calibration
Wed Dec 28 19:34:02 2016 kern.debug kernel: [  352.156947] ath: phy0: Setting CFG 0x10a

# wifi is gone

Wed Dec 28 19:34:32 2016 kern.debug kernel: [  382.156821] ath: phy0: 0: Chn 0 pmi=0x000b728f;pmq=0x000a0cbc;iqcm=0xffff9285;
Wed Dec 28 19:34:32 2016 kern.debug kernel: [  382.164094] ath: phy0: 0: Chn 1 pmi=0x000aebea;pmq=0x000966be;iqcm=0x00004c6e;
Wed Dec 28 19:34:32 2016 kern.debug kernel: [  382.171375] ath: phy0: 0: Chn 2 pmi=0x0009e251;pmq=0x000aeefd;iqcm=0xffffc9ed;
Wed Dec 28 19:34:32 2016 kern.debug kernel: [  382.178638] ath: phy0: starting IQ Mismatch Calibration

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=13#comment1115


From lede-bugs at lists.infradead.org  Thu Dec 29 05:22:53 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 29 Dec 2016 13:22:53 +0000
Subject: [FS#13] Ath9k AP stays up for connected clients but doesn't show in
 scan on new ones
In-Reply-To: <FS13@bugs.lede-project.org>
References: <FS13@bugs.lede-project.org>
Message-ID: <mailman.76248.1483351999.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#13 - Ath9k AP stays up for connected clients but doesn't show in scan on new ones
User who did this - Johan van Zoomeren (amain)

----------
Hi Felix,

Thanks for the patch, but it does not seem to work. I compiled an image using your staging area, up to commit 2782d36a4053b9879ea84b9e29c347eb4471c639, and the problem is still there.

ath9k debug level:

# echo 0x00000409 > /sys/kernel/debug/ieee80211/phy0/ath9k/debug


iperf:

...
2016-12-29 11:34:49 [ 4] 286.5-287.0 sec 1.41 MBytes 23.7 Mbits/sec
2016-12-29 11:34:50 [ 4] 287.0-287.5 sec 1.21 MBytes 20.3 Mbits/sec
2016-12-29 11:34:50 [ 4] 287.5-288.0 sec 1.19 MBytes 19.9 Mbits/sec
2016-12-29 11:34:51 [ 4] 288.0-288.5 sec 1.34 MBytes 22.4 Mbits/sec
(connection lost)


router log:

..
Dec 29 11:33:22 debwrt kernel: [ 1383.295518] ath: phy0: NF calibrated [ctl] [chain 0] is -89
Dec 29 11:33:22 debwrt kernel: [ 1383.295555] ath: phy0: NF calibrated [ctl] [chain 1] is -88
Dec 29 11:33:22 debwrt kernel: [ 1383.295576] ath: phy0: NF calibrated [ctl] [chain 2] is -87
Dec 29 11:33:52 debwrt kernel: [ 1413.559811] ath: phy0: NF calibrated [ctl] [chain 0] is -88
Dec 29 11:33:52 debwrt kernel: [ 1413.559847] ath: phy0: NF calibrated [ctl] [chain 1] is -88
Dec 29 11:33:52 debwrt kernel: [ 1413.559869] ath: phy0: NF calibrated [ctl] [chain 2] is -87
Dec 29 11:34:22 debwrt kernel: [ 1443.626346] ath: phy0: NF calibrated [ctl] [chain 0] is -88
Dec 29 11:34:22 debwrt kernel: [ 1443.626382] ath: phy0: NF calibrated [ctl] [chain 1] is -89
Dec 29 11:34:22 debwrt kernel: [ 1443.626404] ath: phy0: NF calibrated [ctl] [chain 2] is -88
Dec 29 11:34:52 debwrt kernel: [ 1473.699523] ath: phy0: NF calibrated [ctl] [chain 0] is -89
Dec 29 11:34:52 debwrt kernel: [ 1473.699558] ath: phy0: NF calibrated [ctl] [chain 1] is -89
Dec 29 11:34:52 debwrt kernel: [ 1473.699580] ath: phy0: NF calibrated [ctl] [chain 2] is -89
Dec 29 11:34:52 debwrt kernel: [ 1473.799518] ath: phy0: tx hung, resetting the chip
Dec 29 11:34:52 debwrt kernel: [ 1473.830307] ath: phy0: NF calibrated [ctl] [chain 0] is -89
Dec 29 11:34:52 debwrt kernel: [ 1473.830340] ath: phy0: NF calibrated [ctl] [chain 1] is -89
Dec 29 11:34:52 debwrt kernel: [ 1473.830362] ath: phy0: NF calibrated [ctl] [chain 2] is -89
Dec 29 11:34:52 debwrt kernel: [ 1473.861072] ath: phy0: ah->misc_mode 0xc
Dec 29 11:34:52 debwrt kernel: [ 1473.863588] ath: phy0: enabling IQ Calibration
Dec 29 11:34:52 debwrt kernel: [ 1473.863608] ath: phy0: starting IQ Mismatch Calibration
Dec 29 11:34:52 debwrt kernel: [ 1473.863631] ath: phy0: Setting CFG 0x10a
...


After the connections gets lost, the log starts to show the "resetting the chip" message about every second for a while. See attached a larger syslog.

If there is anything a can do to help to debug or test, please let me know.

A way to get past the compile error already reported by Sven:

$ # revert commit: https://git.lede-project.org/?p=source.git;a=commit;h=2fd5ce9488d11c7e6eee7dc30f128bd12be889f5
$ make tools/libressl/clean
$ make tools/libressl/install
$ export LD_LIBRARY_PATH=$(readlink -f build_dir/host/libressl-2.5.0/ssl/.libs):$(readlink -f build_dir/host/libressl-2.5.0/crypto/.libs)
$ make -j4

----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=13#comment1118


From lede-bugs at lists.infradead.org  Sat Dec 31 10:18:29 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 31 Dec 2016 18:18:29 +0000
Subject: [FS#13] Ath9k AP stays up for connected clients but doesn't show in
 scan on new ones
In-Reply-To: <FS13@bugs.lede-project.org>
References: <FS13@bugs.lede-project.org>
Message-ID: <mailman.76249.1483351999.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#13 - Ath9k AP stays up for connected clients but doesn't show in scan on new ones
User who did this - IronicSven (IronicSven)

----------
Hi Felix,

I've spend some time today to understand tiny parts of the ath9k code and got better debugging results with this debugging level:

root at FlensNet:~# echo 0x00266665 > /sys/kernel/debug/ieee80211/phy0/ath9k/debug


It shows that there are recurring beacon problems before multiple calibrations and the tx hung:


...
Sat Dec 31 18:07:32 2016 kern.debug kernel: [ 1187.102795] ath: phy0: resume beacon xmit after 1 misses
Sat Dec 31 18:07:32 2016 kern.debug kernel: [ 1187.115571] ath: phy0: missed 1 consecutive beacons
...


The missing beacons might be the root cause.

You can find the complete syslog here: http://pastebin.com/8rcr3Gq1

PS: Building from your staging tree works now for me.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=13#comment1126


