From lede-bugs at lists.infradead.org  Tue May  1 00:25:16 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 01 May 2018 07:25:16 +0000
Subject: [FS#1046] LED lights functionality brokes WiFi connection, switch
 LEDS without controls on Linksys 3200ACM
In-Reply-To: <FS1046@bugs.openwrt.org>
References: <FS1046@bugs.openwrt.org>
Message-ID: <mailman.6426.1525159662.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1046 - LED lights functionality brokes WiFi connection, switch LEDS without controls on Linksys 3200ACM
User who did this - fbafkis (fbafkis)

----------
I confirm that the problem is still present today, with new stable versions of mwlwifi drivers and LEDE 17.0.1.4 and firmware 4.4.92. 
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1046#comment4678


From lede-bugs at lists.infradead.org  Tue May  1 02:21:40 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 01 May 2018 09:21:40 +0000
Subject: [FS#1501] DS-Lite is broken on snapshot with some models
In-Reply-To: <FS1501@bugs.openwrt.org>
References: <FS1501@bugs.openwrt.org>
Message-ID: <mailman.6447.1525166546.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1501 - DS-Lite is broken on snapshot with some models
User who did this - Tim Biermann (TimB87)

----------
Hey Hans,

I am sorry, I didn't commit the changes with uci.
This is the syslog with debug info: https://pastebin.com/qBZfeiTw

Best regards,
Tim
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1501#comment4679


From lede-bugs at lists.infradead.org  Tue May  1 02:38:26 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 01 May 2018 09:38:26 +0000
Subject: [FS#1501] DS-Lite is broken on snapshot with some models
In-Reply-To: <FS1501@bugs.openwrt.org>
References: <FS1501@bugs.openwrt.org>
Message-ID: <mailman.6448.1525167521.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1501 - DS-Lite is broken on snapshot with some models
User who did this - jpdribbler (jpdribbler)

----------
I just tried dslite again using the latest build from https://forum.lede-project.org/t/build-for-netgear-r7800/316 and beside dslite i was not able to get an ipv6 at all (DHCPv6). Probably not helpful without logs but fyi :)

Thanks Hans for checking.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1501#comment4680


From lede-bugs at lists.infradead.org  Tue May  1 05:20:16 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 01 May 2018 12:20:16 +0000
Subject: [FS#1526] rpcd: memory leak in the current package version
In-Reply-To: <FS1526@bugs.openwrt.org>
References: <FS1526@bugs.openwrt.org>
Message-ID: <mailman.6501.1525177237.2282.lede-bugs@lists.infradead.org>

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

User who did this - Yuubari (Yuubari) 

Attached to Project - OpenWrt/LEDE Project
Summary - rpcd: memory leak in the current package version
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 -  - Device problem occurs on

Netgear WNDR3800.

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

OpenWrt SNAPSHOT r6775-afdca53 / LuCI Master (git-18.118.21533-00d2429)
rpcd - 2018-04-20-66a9bad1-1 (https://git.openwrt.org/?p=project/rpcd.git;a=commit;h=66a9bad1a73bc33c4c5a9a00de8dc8ad35bdfaf1) ? after the supposed memory leak fix.

 - Steps to reproduce

Leaving the router running normally is enough.

After about 3 days rpcd was consuming 40% of RAM and the OOM killer was wreaking mayhem in the system. Restarting rpcd solved the issue for now, but it already went from 0.7 to 4.2% memory usage. Accessing a luci page increases its RES by 4 KB every time. It looks like JS-based access (like leaving the interface overview page open) also produces these increases.

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1526


From lede-bugs at lists.infradead.org  Tue May  1 06:14:34 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 01 May 2018 13:14:34 +0000
Subject: [FS#854] Unstable Internet caused by frequent PPPoE reconnect,
 network.wan.keepalive=0 has no effect
In-Reply-To: <FS854@bugs.openwrt.org>
References: <FS854@bugs.openwrt.org>
Message-ID: <mailman.6519.1525180497.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#854 - Unstable Internet caused by frequent PPPoE reconnect, network.wan.keepalive=0 has no effect
User who did this - kochstefan (kochstefan)

----------
I have noticed this issue the first time at the begin of the year 2016 with OpenWRT. The issue occurs for me every time when connecting to my SSH-server behind the OpenWRT router and load (SSH/SCP server uploads to SSH/SCP downloading remote client) a big file.

So the SSH/SCP client does this:
scp domainname.of.server:/path/to/big/file bigfile
bigfile                                                                                                                                                                                                                          0% 3712KB   0.0KB/s - stalled -

To reproduce: The SSH server behind OpenWRT router needs a slower internet connection as the remote client (server's upload speed is slower than client's download speed). So the upload speed of the SSH servers internet connection is fully exhausted.

I assume that the keepalive message does not get transmitted properly because of exhausted internet connection. The question is, why there is no prioritization or balancing.

The workaround for me was to add "option keepalive '100 30'" to the WAN interface within /etc/config/network.

Recently, I noticed a similar failure again. The issue occurs every time when loading a big file via SCP, too. So I have tried your suggestion of '1024 86400', too. But it seems to be another error (not the keepalive issue):
Tue May  1 14:32:32 2018 daemon.notice pppd[1905]: Modem hangup
Tue May  1 14:32:32 2018 daemon.info pppd[1905]: Connect time 9.8 minutes.
Tue May  1 14:32:32 2018 daemon.info pppd[1905]: Sent 114234224 bytes, received 2755645 bytes.

If no keepalive option is set I get the log messages:
Tue May  1 14:54:03 2018 daemon.info pppd[1874]: No response to 5 echo-requests
Tue May  1 14:54:03 2018 daemon.notice pppd[1874]: Serial link appears to be disconnected.
Tue May  1 14:54:03 2018 daemon.info pppd[1874]: Connect time 5.8 minutes.
Tue May  1 14:54:03 2018 daemon.info pppd[1874]: Sent 4718939 bytes, received 539442 bytes.

With both options '100 30' and '1024 86400' there is no "No response to X echo-requests" message within the log.

pppd was started with:
/usr/sbin/pppd nodetach ipparam wan ifname pppoe-wan lcp-echo-interval 86400 lcp-echo-failure 1024 lcp-echo-adaptive +ipv6 set AUTOIPV6=1 nodefaultroute usepeerdns maxfail 1 [...]

----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=854#comment4681


From lede-bugs at lists.infradead.org  Tue May  1 14:51:26 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 01 May 2018 21:51:26 +0000
Subject: [FS#1527] AR8327 low throughput
In-Reply-To: <FS1527@bugs.openwrt.org>
References: <FS1527@bugs.openwrt.org>
Message-ID: <mailman.6579.1525211631.2282.lede-bugs@lists.infradead.org>

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

User who did this - eripek (eripek) 

Attached to Project - OpenWrt/LEDE Project
Summary - AR8327 low throughput
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - mittel
Priority - gering
Reported Version - All
Due in Version - Undecided
Due Date - Undecided
Details - Affected devices and versions of LEDE/OpenWRT:
1x TL-WR1043NDv2 - OpenWrt SNAPSHOT, r6800-52ba576
3x TL-WR1043NDv2 - LEDE 17.01.4 (stable)
1x TL-WDR3600 - LEDE 17.01.4 (stable)

All of the above devices use AR8327 rev as their switch:
[    0.881815] switch0: Atheros AR8327 rev. 4 switch registered on ag71xx-mdio.0

Steps to reproduce:
A) iperf clients
3x TL-WR1043NDv2 connected by their WAN port, that is configured to act as vlan trunk port only.
1x TL-WDR3600 connected by it's WAN port, that is configured to act as vlan trunk port only.
1x TL-WR1043NDv2 connected by it's port no 4, that is configured to act as vlan trunk port only.
B) iperf server 1 (192.168.0.1)
C) iperf server 2 (192.168.0.11)
D) four gigabit ethernet easysmart/websmart switches with 1,5GB+ throughput, each, in between A,B,C.

1. Any A against B over cable - as an example:
Client connecting to 192.168.0.1, TCP port 5001
TCP window size: 43.8 KByte (default)
------------------------------------------------------------
[  3] local 192.168.0.75 port 35102 connected with 192.168.0.1 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec   179 MBytes   150 Mbits/sec


2. C against B over each of the 4 devices in D:
Client connecting to 192.168.0.1, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[  3] local 192.168.0.11 port 56228 connected with 192.168.0.1 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  1.09 GBytes   938 Mbits/sec

Each of the TP-Links is using switch-only, no WAN, no NAT, but INPUT-iptables for their respective vlans, so another test of one of the A-devices against B w/o iptables:
------------------------------------------------------------
Client connecting to 192.168.0.1, TCP port 5001
TCP window size: 43.8 KByte (default)
------------------------------------------------------------
[  3] local 192.168.0.242 port 45976 connected with 192.168.0.1 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec   213 MBytes   179 Mbits/sec

It seems, that devices containing AR8327 rev4 wont achieve more than 1/5 of the specified nominal LAN speeds, when acting as an endpoint.

Further observations: WLAN clients won't exceed 25-30 Mbit/s, when using one of the trunked vlans. (WLAN client iwlwifi, Centrino N 2230, e.g. in either 40 or 20 MHz against A-devices in 802.11n WDS AP mode).

Since this is no WAN to LAN scenario, (missing) HWNAT cannot be involved.
Why is the switch performance below expectations? Is this a hw issue or a driver problem?



More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1527


From lede-bugs at lists.infradead.org  Tue May  1 15:22:10 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 01 May 2018 22:22:10 +0000
Subject: [FS#1528] Archer C7 v2 cannot 
In-Reply-To: <FS1528@bugs.openwrt.org>
References: <FS1528@bugs.openwrt.org>
Message-ID: <mailman.6580.1525213344.2282.lede-bugs@lists.infradead.org>

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

User who did this - Curtis Hacker (hakcenter) 

Attached to Project - OpenWrt/LEDE Project
Summary - Archer C7 v2 cannot 
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Critical
Priority - Very Low
Reported Version - lede-17.01
Due in Version - Undecided
Due Date - Undecided
Details - Supply the following if possible:
 - Device problem occurs on
 - Software versions of OpenWrt/LEDE release, packages, etc.
 - Steps to reproduce
   

 

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1528


From lede-bugs at lists.infradead.org  Tue May  1 15:25:40 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 01 May 2018 22:25:40 +0000
Subject: [FS#1528] Archer C7 v2 cannot 
In-Reply-To: <FS1528@bugs.openwrt.org>
References: <FS1528@bugs.openwrt.org>
Message-ID: <mailman.6583.1525213556.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1528 - Archer C7 v2 cannot 
User who did this - Curtis Hacker (hakcenter)

----------
Wow I totally hit enter waaaaaaaay too soon, super sorry.


There is a long standing bug apparently over 3 years old, from even the openwrt on this device.

I am able to confirm that the fix from comment #8 @ on the old openwrt ticket 18680 does indeed solve the issue.

The issue is pretty painful, upon rebooting, or loss of power just on the LEDE device, it is unable to acquire a new/same ip from dhcp. Restarting the modem alleviates this issue but is obviously a total walk around the actual issue.

Moving the ports and swapping the wan/lan ifnames across completely solves this issue. The device reboots, grabs its old IP and all is well in the world
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1528#comment4682


From lede-bugs at lists.infradead.org  Tue May  1 19:37:14 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 02 May 2018 02:37:14 +0000
Subject: [FS#1529] Feature request: preserve official firmware in spare
 partition
In-Reply-To: <FS1529@bugs.openwrt.org>
References: <FS1529@bugs.openwrt.org>
Message-ID: <mailman.6602.1525228649.2282.lede-bugs@lists.infradead.org>

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

User who did this - Matthew Exon (mexon) 

Attached to Project - OpenWrt/LEDE Project
Summary - Feature request: preserve official firmware in spare partition
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've been having lots of problems with my WRT1200AC router.  The 2.4GHz wifi and ethernet are not working, and no amount of reflashing or resetting seems to help.  I'd like to try reverting to the Linksys firmware, but I'm finding that's not working either (https://community.linksys.com/t5/Wireless-Routers/WRT1200AC-flashing-to-Linksys-firmware-from-OpenWRT-kernel-panic/td-p/1307907).

On the DD-WRT forum I've learned that a common "trick" is to keep the official firmware on the spare partition permanently, so that it's always possible to get back to a clean slate.  I definitely regret not doing that.  But OpenWRT automatically flashes to the opposite partition.

Could this be changed so that LuCI allows the option of choosing which partition gets written to?  It could be an "advanced" option.  Perhaps with language like:

* Flash to CURRENT partition ("linux2"), leaving existing alternate partition ("linux1") as recovery partition
* Flash to ALTERNATE partition ("linux1"), and make current OpenWRT partition ("linux2") the recovery partition

It would be extra nifty to display what's on the partitions already as well.

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1529


From lede-bugs at lists.infradead.org  Wed May  2 02:48:47 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 02 May 2018 09:48:47 +0000
Subject: [FS#723] ath10k fails station mode for QCA986x/988x
In-Reply-To: <FS723@bugs.openwrt.org>
References: <FS723@bugs.openwrt.org>
Message-ID: <mailman.6655.1525254550.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#723 - ath10k fails station mode for QCA986x/988x
User who did this - duc (duc)

----------
I have a similar problem with version 17.01.4. (BUILD_ID="r3560-79f57e422d")
Hardware: TP-LINK Archer C5 v1 (system type Qualcomm Atheros QCA9558 ver 1 rev 0 with a qca988x chip)

The 5G WLAN has worked correctly with version 15.05, but after the upgrade 5G WLAN station don't work. Even the downgrade don't change anything. 'iw dev' don't show any 5G device.

I have also:
[   10.408822] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-0000:01:00.0.bin failed with error -2
...
[   17.170222] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2

These files are not present in the /lib/firmware directory tree. I have only ath10k/cal-pci-0000:01:00.0.bin and ath10k/QCA988X/hw2.0/board.bin on the file system.

I don't know if it's normal. 

Is there any way to trace all executed wireless related commands to get the command which don't work?
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=723#comment4683


From lede-bugs at lists.infradead.org  Wed May  2 06:30:04 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 02 May 2018 13:30:04 +0000
Subject: [FS#1299] Build system can't build target-specific packages depending
 on generic packages
In-Reply-To: <FS1299@bugs.openwrt.org>
References: <FS1299@bugs.openwrt.org>
Message-ID: <mailman.6704.1525267947.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1299 - Build system can't build target-specific packages depending on generic packages
User who did this - Sebastian (sebastian-de)

----------
seems to be fixed with commit 8dd7721 in the telephony feed, chan-lantiq packages appear in
https://downloads.openwrt.org/snapshots/targets/lantiq/xrx200/packages/
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1299#comment4684


From lede-bugs at lists.infradead.org  Wed May  2 17:01:32 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 03 May 2018 00:01:32 +0000
Subject: [FS#1530] r6755: tl-841n-v8 problems: ath: phy0: DMA failed to stop
 in 10 ms AR_CR=0x00000024 ...
In-Reply-To: <FS1530@bugs.openwrt.org>
References: <FS1530@bugs.openwrt.org>
Message-ID: <mailman.6787.1525305836.2282.lede-bugs@lists.infradead.org>

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

User who did this - Martin Tippmann (glycoknob) 

Attached to Project - OpenWrt/LEDE Project
Summary - r6755: tl-841n-v8 problems: ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 ...
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 - revision: trunk - r6755-d089a5d773
hardware: tp-link 841n-v8 
build-configs: 
https://github.com/weimarnetz/firmware/blob/master/configs/ar71xx_tiny.config
https://github.com/weimarnetz/firmware/blob/master/configs/common.config


Started to see these errors in crash-reports - seems to happen multiple times per day. 



crashlog fh461-TP-Link TL-WR841N/ND v8
beta-113-g9c709a2+openwrt-r6755-d089a5d773
Linux fh461 4.9.91 #0 Mon Apr 23 20:07:22 2018 mips GNU/Linux
69:24:7d:f0:91:12:fa:32:92:55:08:69:f3:4a:27:09:d4:4a:f9:05
TP-Link TL-WR841N/ND v8
Time: 1525266772.173517
Modules:	ath9k at 80ee0000+15db0	ath9k_common at 80e34000+2a80	ath9k_hw at 80f00000+51020	ath at 80e38000+41c0	mac80211 at 80e80000+5faa0	iptable_nat at 80e31000+2c0	ipt_REJECT at 80ce2000+360	ipt_MASQUERADE at 80d85000+260	cfg80211 at 80e00000+30d50	xt_time at 80da3000+620	xt_tcpudp at 80da1000+680	xt_state at 80d9e000+280	xt_nat at 80da2000+440	xt_multiport at 80da0000+480	xt_mark at 80d9d000+260	xt_mac at 80d9a000+240	xt_limit at 80d98000+3c0	xt_conntrack at 80d95000+860	xt_comment at 80d87000+1c0	xt_TCPMSS at 80d90000+a40	xt_REDIRECT at 80d84000+260	xt_LOG at 80d80000+2c0	nf_reject_ipv4 at 80ce8000+7a0	nf_nat_redirect at 80ceb000+360	nf_nat_masquerade_ipv4 at 80cfc000+4f0	nf_conntrack_ipv4 at 80d82000+1240	nf_nat_ipv4 at 80ce0000+c50	nf_nat at 80ce4000+2010	nf_log_ipv4 at 80d13000+c20	nf_defrag_ipv4 at 80d1a000+2c0	nf_conntrack_rtcache at 80d1b000+960	nf_conntrack at 80cf0000+b2c0	iptable_mangle at 80d0e000+380	iptable_filter at 80d10000+2a0	ip_tables at 80d14000+2490	compat at 80cda000+1260	ip6t_REJECT at 80d07000+380	nf_reject_ipv6 at 80cd9000+840	nf_log_ipv6 at 80d05000+cc0	nf_log_common at 80d0c000+840	ip6table_mangle at 80cdf000+460	ip6table_filter at 80d35000+260	ip6_tables at 80d08000+2400	x_tables at 80cdc000+2b30	tun at 80d00000+4360	gpio_button_hotplug at 80c8c000+11c0
[    0.000000] Linux version 4.9.91 (buildbot at weimarnetz) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r6556-d7ca4c6d3e) ) #0 Mon Apr 23 20:07:22 2018
[    0.000000] MyLoader: sysp=8b8b81ac, boardp=96e34c72, parts=b298aa77
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0001974c (MIPS 74Kc)
[    0.000000] SoC: Atheros AR9341 rev 1
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 02000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] On node 0 totalpages: 8192
[    0.000000] free_area_init_node: node 0, pgdat 803ec8b4, node_mem_map 81000020
[    0.000000]   Normal zone: 64 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 8192 pages, LIFO batch:0
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
[    0.000000] Kernel command line:  board=TL-WR841N-v8  console=ttyS0,115200 rootfstype=squashfs noinitrd
[    0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[    0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 27984K/32768K available (3153K kernel code, 150K rwdata, 332K rodata, 196K init, 212K bss, 4784K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:51
[    0.000000] Clocks: CPU:535.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:25.000MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7144898866 ns
[    0.000011] sched_clock: 32 bits at 267MHz, resolution 3ns, wraps every 8027976190ns
[    0.008248] Calibrating delay loop... 266.64 BogoMIPS (lpj=1333248)
[    0.091064] pid_max: default: 32768 minimum: 301
[    0.096058] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.103051] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.113506] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.123919] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.131034] NET: Registered protocol family 16
[    0.137451] MIPS: machine is TP-LINK TL-WR841N/ND v8
[    0.618054] Can't analyze schedule() prologue at 80370e68
[    0.635480] clocksource: Switched to clocksource MIPS
[    0.642102] NET: Registered protocol family 2
[    0.647714] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.655078] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.661846] TCP: Hash tables configured (established 1024 bind 1024)
[    0.668662] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.674834] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.681773] NET: Registered protocol family 1
[    0.686454] PCI: CLS 0 bytes, default 32
[    0.691104] Crashlog allocated RAM at address 0x1f00000
[    0.698114] workingset: timestamp_bits=30 max_order=13 bucket_order=0
[    0.712737] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.718933] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.739073] io scheduler noop registered
[    0.743211] io scheduler deadline registered (default)
[    0.749106] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[    0.756351] console [ttyS0] disabled
[    0.780246] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 1562500) is a 16550A
[    0.789368] console [ttyS0] enabled
[    0.796935] bootconsole [early0] disabled
[    0.809405] m25p80 spi0.0: found s25sl032p, expected m25p80
[    0.815183] m25p80 spi0.0: s25sl032p (4096 Kbytes)
[    0.821115] 5 tp-link partitions found on MTD device spi0.0
[    0.826931] Creating 5 MTD partitions on "spi0.0":
[    0.831893] 0x000000000000-0x000000020000 : "u-boot"
[    0.838748] 0x000000020000-0x00000015107c : "kernel"
[    0.845853] 0x00000015107c-0x0000003f0000 : "rootfs"
[    0.852824] mtd: device 2 (rootfs) set to be root filesystem
[    0.858792] 1 squashfs-split partitions found on MTD device rootfs
[    0.865191] 0x000000390000-0x0000003f0000 : "rootfs_data"
[    0.872684] 0x0000003f0000-0x000000400000 : "art"
[    0.879534] 0x000000020000-0x0000003f0000 : "firmware"
[    0.887904] libphy: Fixed MDIO Bus: probed
[    0.911041] libphy: ag71xx_mdio: probed
[    1.537571] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.1:00 [uid=004dd042, driver=Generic PHY]
[    1.547876] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
[    2.177362] ag71xx-mdio.1: Found an AR934X built-in switch
[    2.229797] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
[    2.238507] NET: Registered protocol family 10
[    2.247818] NET: Registered protocol family 17
[    2.252602] 8021q: 802.1Q VLAN Support v1.8
[    2.265221] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
[    2.273857] Freeing unused kernel memory: 196K
[    2.278494] This architecture does not have kernel memory protection.
[    2.545497] random: fast init done
[    3.233660] init: Console is alive
[    3.237514] init: - watchdog -
[    3.994732] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    4.146802] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    4.155226] init: - preinit -
[    5.340601] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[    8.562019] jffs2: notice: (366) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[    8.579568] mount_root: switching to jffs2 overlay
[    8.616411] urandom-seed: Seeding with /etc/urandom.seed
[    8.689353] procd: - early -
[    8.692446] procd: - watchdog -
[    9.250783] procd: - watchdog -
[    9.254343] procd: - ubus -
[    9.517271] procd: - init -
[    9.830081] kmodloader: loading kernel modules from /etc/modules.d/*
[    9.840020] tun: Universal TUN/TAP device driver, 1.6
[    9.845248] tun: (C) 1999-2004 Max Krasnyansky 
[    9.856765] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    9.874264] Loading modules backported from Linux version wt-2017-11-01-0-gfe248fc2c180
[    9.882597] Backport generated by backports.git v4.14-rc2-1-31-g86cf0e5d
[    9.891727] ip_tables: (C) 2000-2006 Netfilter Core Team
[    9.906150] nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
[    9.962757] xt_time: kernel timezone is -0000
[   10.071153] ath: EEPROM regdomain: 0x0
[   10.071164] ath: EEPROM indicates default country code should be used
[   10.071168] ath: doing EEPROM country->regdmn map search
[   10.071185] ath: country maps to regdmn code: 0x3a
[   10.071191] ath: Country alpha2 being used: US
[   10.071195] ath: Regpair used: 0x3a
[   10.084756] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   10.089600] ieee80211 phy0: Atheros AR9340 Rev:1 mem=0xb8100000, irq=47
[   10.132795] kmodloader: done loading kernel modules from /etc/modules.d/*
[   21.132399] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   21.159067] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   21.181083] IPv6: ADDRCONF(NETDEV_UP): br-vap: link is not ready
[   21.216086] IPv6: ADDRCONF(NETDEV_UP): br-roam: link is not ready
[   23.217877] eth0: link up (100Mbps/Full duplex)
[   23.222619] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   23.416141] ath: EEPROM regdomain: 0x8114
[   23.420293] ath: EEPROM indicates we should expect a country code
[   23.426643] ath: doing EEPROM country->regdmn map search
[   23.432129] ath: country maps to regdmn code: 0x37
[   23.437092] ath: Country alpha2 being used: DE
[   23.441679] ath: Regpair used: 0x37
[   23.445283] ath: regdomain 0x8114 dynamically updated by user
[   28.082864] IPv6: ADDRCONF(NETDEV_UP): wlan0-1: link is not ready
[   28.377681] br-vap: port 1(wlan0-1) entered blocking state
[   28.383369] br-vap: port 1(wlan0-1) entered disabled state
[   28.389588] device wlan0-1 entered promiscuous mode
[   28.507712] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready
[   28.514627] br-vap: port 1(wlan0-1) entered blocking state
[   28.520388] br-vap: port 1(wlan0-1) entered forwarding state
[   28.582371] IPv6: ADDRCONF(NETDEV_CHANGE): br-vap: link becomes ready
[   28.617361] br-roam: port 1(wlan0-2) entered blocking state
[   28.623278] br-roam: port 1(wlan0-2) entered disabled state
[   28.629546] device wlan0-2 entered promiscuous mode
[   28.696011] IPv6: ADDRCONF(NETDEV_UP): wlan0-2: link is not ready
[   28.702438] br-roam: port 1(wlan0-2) entered blocking state
[   28.708272] br-roam: port 1(wlan0-2) entered forwarding state
[   28.714815] IPv6: ADDRCONF(NETDEV_CHANGE): br-roam: link becomes ready
[   28.826240] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-2: link becomes ready
[   29.344781] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   29.554096] wlan0: Created IBSS using preconfigured BSSID 02:ca:ff:ee:ba:be
[   29.561380] wlan0: Creating new IBSS network, BSSID 02:ca:ff:ee:ba:be
[   29.600876] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   54.884553] random: crng init done
[26187.720165] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00006400
[26729.429478] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00006400
[28439.382610] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00006400
[29941.604627] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00026400
[34096.679390] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00006400
[35348.329357] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02100020 DMADBG_7=0x00006400
[39363.344165] ------------[ cut here ]------------
[39363.348963] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:316 0x802a95c0
[39363.356276] NETDEV WATCHDOG: eth0 (ag71xx): transmit queue 0 timed out
[39363.363033] Kernel panic - not syncing: panic_on_warn set ...
[39363.363033]


More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1530


From lede-bugs at lists.infradead.org  Thu May  3 00:30:14 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 03 May 2018 07:30:14 +0000
Subject: [FS#1299] Build system can't build target-specific packages depending
 on generic packages
In-Reply-To: <FS1299@bugs.openwrt.org>
References: <FS1299@bugs.openwrt.org>
Message-ID: <mailman.6807.1525332764.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1299 - Build system can't build target-specific packages depending on generic packages
User who did this - Carl-Daniel Hailfinger (hailfinger)

----------
Indeed, yesterday it seemed fixed and chan-lantiq packages were available in https://downloads.openwrt.org/snapshots/targets/lantiq/xrx200/packages/

Right now, the chan-lantiq packages have disappeared again. Should I close this bug and open a new one for the disappeared packages?
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1299#comment4685


From lede-bugs at lists.infradead.org  Thu May  3 01:47:59 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 03 May 2018 08:47:59 +0000
Subject: [FS#1501] DS-Lite is broken on snapshot with some models
In-Reply-To: <FS1501@bugs.openwrt.org>
References: <FS1501@bugs.openwrt.org>
Message-ID: <mailman.6818.1525337293.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1501 - DS-Lite is broken on snapshot with some models
User who did this - Hans Dedecker (dedeckeh)

----------
The logs don't show any obvious issue as the wan6_4 dslite interface is coming up and the required IPv4/6 routes are in place.
There's no reason to disable masquerading as it should work even with masquerading in place.

To trouble shoot it further I would like to launch an IPv4 ping to 8.8.8.8 from a lan device.
While the ping is ongoing I would like to see the output of

  * ifconfig

  * ifstatus wan6_4

  * iptables -t filter -L -vn

  * iptables -t nat -L -vn

  * ip6tabes -t filter -L -vn
 
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1501#comment4686


From lede-bugs at lists.infradead.org  Thu May  3 04:23:40 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 03 May 2018 11:23:40 +0000
Subject: [FS#1467] ieee80211_tx_status: headroom too small
In-Reply-To: <FS1467@bugs.openwrt.org>
References: <FS1467@bugs.openwrt.org>
Message-ID: <mailman.6846.1525346637.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1467 - ieee80211_tx_status: headroom too small
User who did this - Enrique Rodriguez (enrique.rodriguez)

----------
I've detected that the error only happens when using 4.14 kernel and an ath10k radio that is part of a bridge. This is an example brctl output where wlan0 and wlan1 are inside br-lan bridge:

root at LEDE:~# brctl show
bridge name	bridge id		STP enabled	interfaces
br-lan		9000.04f021132a4a	no		eth0.1
							eth0.2
							wlan0



If the wireless interface is not part of a bridge, it works correctly and no errors are shown.

Maybe this is a kernel related issue?

----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1467#comment4687


From lede-bugs at lists.infradead.org  Thu May  3 07:05:23 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 03 May 2018 14:05:23 +0000
Subject: [FS#1521] Option persist in /etc/config/network is not working.
In-Reply-To: <FS1521@bugs.openwrt.org>
References: <FS1521@bugs.openwrt.org>
Message-ID: <mailman.6897.1525356478.2282.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#1521 - Option persist in /etc/config/network is not working.
User who did this - Hans Dedecker (dedeckeh)

Reason for closing: Works for me
Additional comments about closing: Setting persist to 1 in uci results into the expected behavior; persist is set as a cmd line argument of pppd :

/usr/sbin/pppd nodetach ipparam wan ifname pppoe-wan +ipv6 nodefaultroute usepeerdns persist

Setting persist to 0 in uci results into nopersist being passed as cmd line argument to pppd and maxfail set to 1 :

/usr/sbin/pppd nodetach ipparam wan ifname pppoe-wan +ipv6 nodefaultroute usepeerdns nopersist maxfail 1

 


More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1521


From lede-bugs at lists.infradead.org  Fri May  4 02:12:12 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 04 May 2018 09:12:12 +0000
Subject: [FS#1510] busybox conflicts with flock
In-Reply-To: <FS1510@bugs.openwrt.org>
References: <FS1510@bugs.openwrt.org>
Message-ID: <mailman.7108.1525425153.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1510 - busybox conflicts with flock
User who did this - Yousong Zhou (yousong)

----------
Please test whether the changes at flock-alt branch of my staging tree [1] can fix the issue.  Thank you

 [1] https://git.openwrt.org/?p=openwrt/staging/yousong.git;a=shortlog;h=refs/heads/flock-alt
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1510#comment4688


From lede-bugs at lists.infradead.org  Fri May  4 02:22:33 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 04 May 2018 09:22:33 +0000
Subject: [FS#1518] kernel error: CPU: 2 PID: 27318 Comm: cat Not tainted
 4.14.34
In-Reply-To: <FS1518@bugs.openwrt.org>
References: <FS1518@bugs.openwrt.org>
Message-ID: <mailman.7111.1525425768.2282.lede-bugs@lists.infradead.org>

The following task has been changed.  The changes are listed below.  For full information about what has changed, visit the URL and click the History tab.

FS#1518 - kernel error: CPU: 2 PID: 27318 Comm: cat Not tainted 4.14.34
User who did this: Yousong Zhou (yousong)
Task details edited:
-------
Model	ZBT-WG3526 (16M)
Firmware Version	OpenWrt SNAPSHOT r6755-d089a5d / LuCI Master (git-18.113.52925-0c30ee0)
Kernel Version	4.14.34

error is comming after a while .. :(


Thu Apr 26 12:59:00 2018 kern.warn kernel: [69277.917386] ------------[ cut here ]------------
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69277.922064] WARNING: CPU: 2 PID: 27318 at lib/iov_iter.c:695 copy_page_to_iter+0xc4/0x508
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69277.930339] Modules linked in: pppoe ppp_async option usb_wwan pptp pppox ppp_mppe ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 mt76x2e mt7603e mt76 mac80211 iptable_nat 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_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_FLOWOFFLOAD xt_DSCP xt_CT xt_CLASSIFY usbserial usb_storage ts_fsm ts_bm slhc nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.001388]  nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda macvlan iptable_mangle iptable_filter ipt_ECN ip_tables crc_ccitt compat br_netfilter fuse sch_cake nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_tbf sch_htb sch_hfsc sch_ingress ledtrig_usbport 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
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.072898]  ip6table_mangle ip6table_filter ip6_tables x_tables ip_gre gre ifb ip_tunnel tun vfat fat f2fs ext4 jbd2 mbcache nls_utf8 nls_iso8859_1 nls_cp437 sha1_generic ecb crc32c_generic crc32_generic mmc_block mtk_sd mmc_core leds_gpio xhci_mtk xhci_plat_hcd xhci_pci xhci_hcd ahci libahci libata sd_mod scsi_mod gpio_button_hotplug usbcore nls_base usb_common
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.105236] CPU: 2 PID: 27318 Comm: cat Not tainted 4.14.34 #0
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.111065] Stack : 00000000 00000000 00000000 00000000 805f7ada 00000032 00000000 00000000
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.119416]         8f0ac1f4 80590927 8051cabc 00000002 00006ab6 00000001 8dca3be8 b3f6da0b
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.127750]         00000000 00000000 805f0000 00008808 00000000 00000199 00000008 00000000
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.136087]         00000000 80590000 00019b14 00000000 80000000 00000000 805b0000 80229950
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.144432]         00000009 000002b7 00000000 8dca3db0 00000001 802911d0 00000008 805f0008
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.152779]         ...
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.155227] Call Trace:
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.157698] [] show_stack+0x58/0x100
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.162148] [] dump_stack+0x9c/0xe0
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.166501] [] __warn+0xe0/0x114
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.170581] [] warn_slowpath_null+0x1c/0x30
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.175621] [] copy_page_to_iter+0xc4/0x508
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.180656] [] shmem_file_read_iter+0x2c0/0x3c0
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.186080] [] generic_file_splice_read+0xec/0x170
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.191721] [] splice_direct_to_actor+0xc8/0x234
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.197187] [] do_splice_direct+0x98/0xd0
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.202061] [] do_sendfile+0x284/0x478
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.206683] [] SyS_sendfile64+0x84/0xd8
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.211399] [] syscall_common+0x34/0x58
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.216566] ---[ end trace b0a90f34a85fa703 ]---

-------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1518


From lede-bugs at lists.infradead.org  Fri May  4 03:13:12 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 04 May 2018 10:13:12 +0000
Subject: [FS#1498] Building gccgo failes
In-Reply-To: <FS1498@bugs.openwrt.org>
References: <FS1498@bugs.openwrt.org>
Message-ID: <mailman.7120.1525428810.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1498 - Building gccgo failes
User who did this - Yousong Zhou (yousong)

----------
Hi,

I have a patch [1] for the missing libgcc_s.so issue.  Please test and see if it works for you

 [1] https://github.com/yousong/build-scripts/blob/master/build-gcc-pass0.sh#L62
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1498#comment4689


From lede-bugs at lists.infradead.org  Fri May  4 03:13:18 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 04 May 2018 10:13:18 +0000
Subject: [FS#1498] Building gccgo failes
In-Reply-To: <FS1498@bugs.openwrt.org>
References: <FS1498@bugs.openwrt.org>
Message-ID: <mailman.7121.1525428810.2282.lede-bugs@lists.infradead.org>

Yousong Zhou has taken ownership of the following task:

FS#1498 - Building gccgo failes

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1498


From lede-bugs at lists.infradead.org  Fri May  4 04:27:32 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 04 May 2018 11:27:32 +0000
Subject: [FS#1498] Building gccgo failes
In-Reply-To: <FS1498@bugs.openwrt.org>
References: <FS1498@bugs.openwrt.org>
Message-ID: <mailman.7126.1525433270.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1498 - Building gccgo failes
User who did this - Dominik Menke (dmke)

----------
So far this looks promising: building the toolchain succeedes without error.

I'll confirm whether the compiler actually works in a moment.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1498#comment4690


From lede-bugs at lists.infradead.org  Fri May  4 06:14:10 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 04 May 2018 13:14:10 +0000
Subject: [FS#1299] Build system can't build target-specific packages depending
 on generic packages
In-Reply-To: <FS1299@bugs.openwrt.org>
References: <FS1299@bugs.openwrt.org>
Message-ID: <mailman.7140.1525439665.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1299 - Build system can't build target-specific packages depending on generic packages
User who did this - Carl-Daniel Hailfinger (hailfinger)

----------
The packages have reappeared again.

Thank you for fixing this!
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1299#comment4691


From lede-bugs at lists.infradead.org  Fri May  4 10:30:56 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 04 May 2018 17:30:56 +0000
Subject: [FS#1531] Table of Packages broken
In-Reply-To: <FS1531@bugs.openwrt.org>
References: <FS1531@bugs.openwrt.org>
Message-ID: <mailman.7225.1525455206.2282.lede-bugs@lists.infradead.org>

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

User who did this - gschaub (gschaub) 

Attached to Project - OpenWrt/LEDE Project
Summary - Table of Packages broken
Task Type - Bug Report
Category - Website
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Clicking the Table of Packages no longer returns any information.  I have tried from iOS and Windows, multiple browsers. 
   

 

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1531


From lede-bugs at lists.infradead.org  Fri May  4 14:39:01 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 04 May 2018 21:39:01 +0000
Subject: [FS#909] runas wrapper executes programs using wrong interpreter
In-Reply-To: <FS909@bugs.openwrt.org>
References: <FS909@bugs.openwrt.org>
Message-ID: <mailman.7269.1525469956.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#909 - runas wrapper executes programs using wrong interpreter
User who did this - Kirill Elagin (kirelagin)

----------
I?m sorry I somehow missed these notifications :/.

I can?t find your commit now, but I?m eager to test it.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=909#comment4692


From lede-bugs at lists.infradead.org  Fri May  4 14:54:10 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 04 May 2018 21:54:10 +0000
Subject: [FS#909] runas wrapper executes programs using wrong interpreter
In-Reply-To: <FS909@bugs.openwrt.org>
References: <FS909@bugs.openwrt.org>
Message-ID: <mailman.7270.1525470868.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#909 - runas wrapper executes programs using wrong interpreter
User who did this - Kirill Elagin (kirelagin)

----------
Actually, now I?ve got a similar issue, but this time with `mksquashfs4`, which needs `zlib`.

[staging_dir/host]$ ./lib/ld-linux-x86-64.so.2 --library-path lib/ ./bin/.mksquashfs4.bin mksquashfs4
(works)

[staging_dir/host]$ ./lib/ld-linux-x86-64.so.2 --library-path lib/ lib/runas ./bin/.mksquashfs4.bin mksquashfs4
mksquashfs4: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory

----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=909#comment4693


From lede-bugs at lists.infradead.org  Fri May  4 15:23:07 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 04 May 2018 22:23:07 +0000
Subject: [FS#909] runas wrapper executes programs using wrong interpreter
In-Reply-To: <FS909@bugs.openwrt.org>
References: <FS909@bugs.openwrt.org>
Message-ID: <mailman.7274.1525472602.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#909 - runas wrapper executes programs using wrong interpreter
User who did this - Jo-Philipp Wich (jow-)

----------
The failing command line looks weird... why two space separated arguments to --library-path ? Also I dropped the runas executable in favor to a shared library opened with LD_PRELOAD.

See http://git.openwrt.org/ef1cafa736679eb035d405bcdf903fd1fb329865
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=909#comment4694


From lede-bugs at lists.infradead.org  Fri May  4 18:07:06 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 05 May 2018 01:07:06 +0000
Subject: [FS#909] runas wrapper executes programs using wrong interpreter
In-Reply-To: <FS909@bugs.openwrt.org>
References: <FS909@bugs.openwrt.org>
Message-ID: <mailman.7280.1525482575.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#909 - runas wrapper executes programs using wrong interpreter
User who did this - Kirill Elagin (kirelagin)

----------
> The failing command line looks weird... why two space separated arguments to ?library-path

Why two arguments? `--library-path lib/` is the library path and then comes the executable that we run and its arguments. The failing line is exactly the one that existing wrappers use (and they are failing for me).

The change you linked did get included into 17.01.4, right? I am trying to generate a 17.01.4 image and it was failing for me with exactly the same `mksquashfs4` error as in my example (not being able to find `libz.so`). I replaced the failing one with the top one (which skips `lib/runas`) and the image was generated successfully. Well, ?successfully? might not be the right word here, because it completely bricked my router and I am still trying to understand what when wrong, because there were no errors from the generation process :(.

Anyway, what I see is that all wrappers in `lede-imagebuilder-17.01.4-ar71xx-generic.Linux-x86_64/staging_dir/host/bin` go through `lib/runas`. I?m sorry if I originally didn?t make it clear enough that I was talking specifically about the image generator all this time.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=909#comment4695


From lede-bugs at lists.infradead.org  Fri May  4 18:14:43 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 05 May 2018 01:14:43 +0000
Subject: [FS#909] runas wrapper executes programs using wrong interpreter
In-Reply-To: <FS909@bugs.openwrt.org>
References: <FS909@bugs.openwrt.org>
Message-ID: <mailman.7281.1525482897.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#909 - runas wrapper executes programs using wrong interpreter
User who did this - Kirill Elagin (kirelagin)

----------
Ah, I see, your commit didn?t make into 17.01.4. Alright, let me try staging (too bad I no longer have a router to try the resulting firmware on :).
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=909#comment4696


From lede-bugs at lists.infradead.org  Fri May  4 18:46:19 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 05 May 2018 01:46:19 +0000
Subject: [FS#909] runas wrapper executes programs using wrong interpreter
In-Reply-To: <FS909@bugs.openwrt.org>
References: <FS909@bugs.openwrt.org>
Message-ID: <mailman.7282.1525484794.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#909 - runas wrapper executes programs using wrong interpreter
User who did this - Kirill Elagin (kirelagin)

----------
Yes, your new way of wrapping executables works wonderfully. The issue is resolved now.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=909#comment4697


From lede-bugs at lists.infradead.org  Sat May  5 06:08:29 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 05 May 2018 13:08:29 +0000
Subject: [FS#1501] DS-Lite is broken on snapshot with some models
In-Reply-To: <FS1501@bugs.openwrt.org>
References: <FS1501@bugs.openwrt.org>
Message-ID: <mailman.7367.1525525727.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1501 - DS-Lite is broken on snapshot with some models
User who did this - Tim Biermann (TimB87)

----------
Hey Hans,

this is from a fresh snapshot (03.05.), firewall untouched, odhcpd loglevel 7 and your edited dslite.sh. I set WAN(4) to unmanaged and rebooted:

Kernel Log https://pastebin.com/0W3SMqqA
System Log https://pastebin.com/fjwuxjVK
Commands https://pastebin.com/2HFxhVsY

On a side note, for what it's worth, my provider switched me to Dual Stack yesterday (I have no idea why they are suddenly able to, but I won't protest). While DHCPv4 and v6 now work flawlessly, it seems that I can still use an AFTR to get another v4 address - I tested that with 17.01.4 - so I will still be able to deliver logs.

Thanks for taking your time and have a great weekend,

Tim
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1501#comment4698


From lede-bugs at lists.infradead.org  Sat May  5 06:53:56 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 05 May 2018 13:53:56 +0000
Subject: [FS#1363] QMI does not use correct APN
In-Reply-To: <FS1363@bugs.openwrt.org>
References: <FS1363@bugs.openwrt.org>
Message-ID: <mailman.7372.1525528578.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1363 - QMI does not use correct APN
User who did this - dchard (dchard)

----------
I can confirm this behavior.

I have a Quectel EC25 modem and in QMI mode it is not applying the APN set in the luci-protocol-qmi app. No matter what APN I set on the webui, the modem sends the default APN it was programmed in the factory ("3gnet" in my case).

I also have a small LTE test network at my disposal, so I also checked the core network, where it is clear that the modem tries to activate the default EPS bearer with APN=3gnet, while I already set "internet", also tried with "static" and "" (empty string where the modem should not send a requested APN during the attach procedure).

Another way to confirm this without a core network:

1. Set whatever APN in the luci-protocol-qmi app.
2. Open minicom and query the PDN profiles with:
AT+CGDCONT?
3. If the APN set on the luci-protocol-qmi is not matching the APN in the above query, the APN will be used is the one seen with AT+CGDCONT?

If I manually set the APN with AT+CGDCONT, then the QMI mode connection will use that APN instead of the one the user gives on the luci interface.

To elaborate why this problem is not so obvious and not affecting a lot of people:

During the default PDN activation - at least on LTE - the core network requests the subscribed profile from the HSS, and if the requested APN is not matching the "subscribed" APN, then the core network will in most cases activate the data connection with the default subscribed APn no matter what the modem requests, therefor the user will have internet.

The problem is visible when an operator allows multiple APNs like in the above example: public IP, NAT-ed, but even corporate can be part of this, so the user must specify the APN for these non-default cases.

I did not tried the above mentioned fix, I will on next monday.

None the less this is a serious issue that in QMI mode the APN setting is not applied.

I am using latest master for ar71xx for GL-MIFI and the kernel is  4.9.96.

I am more than happy to test any future fixes/patches to help fix this as soon as possible. In case needed, I can provide core network traces.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1363#comment4699


From lede-bugs at lists.infradead.org  Sat May  5 07:52:31 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 05 May 2018 14:52:31 +0000
Subject: [FS#1363] QMI does not use correct APN
In-Reply-To: <FS1363@bugs.openwrt.org>
References: <FS1363@bugs.openwrt.org>
Message-ID: <mailman.7381.1525531973.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1363 - QMI does not use correct APN
User who did this - dchard (dchard)

----------
I tested the fix recommended by Evren on my home KPN NL connection and it is a partial success:

1. If I apply the recommended patch and I want to key in specific APN, that is now activated and the connection is set up, and it does not matter what AT+CGDCONT? shows.

2. However when I want to activate the default APN where the APN string is empty, that still does not work. I suspect in this case it is again the AT+CGDCONT value which gets activated (incorrectly), but I can only check this on monday.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1363#comment4700


From lede-bugs at lists.infradead.org  Sat May  5 14:47:49 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 05 May 2018 21:47:49 +0000
Subject: [FS#1299] Build system can't build target-specific packages depending
 on generic packages
In-Reply-To: <FS1299@bugs.openwrt.org>
References: <FS1299@bugs.openwrt.org>
Message-ID: <mailman.7390.1525557014.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1299 - Build system can't build target-specific packages depending on generic packages
User who did this - Carl-Daniel Hailfinger (hailfinger)

----------
And the packages disappeared again.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1299#comment4701


From lede-bugs at lists.infradead.org  Sun May  6 12:08:18 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 06 May 2018 19:08:18 +0000
Subject: [FS#1532] ar71xx - ath9k: probe of ar933x_wmac failed with error -5
In-Reply-To: <FS1532@bugs.openwrt.org>
References: <FS1532@bugs.openwrt.org>
Message-ID: <mailman.7435.1525633850.2282.lede-bugs@lists.infradead.org>

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

User who did this - rceccleston (rceccleston) 

Attached to Project - OpenWrt/LEDE Project
Summary - ar71xx - ath9k: probe of ar933x_wmac failed with error -5
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Critical
Priority - Very Low
Reported Version - lede-17.01
Due in Version - Undecided
Due Date - Undecided
Details - After updating to 17.01.4 from the Alfa 4.12 firmware, the WiFi driver fails to start.

https://downloads.lede-project.org/releases/17.01.4/targets/ar71xx/generic/lede-17.01.4-ar71xx-generic-tube2h-16M-squashfs-sysupgrade.bin

This has affected two brand new ALFA NETWORK Tube2H access points.

[    0.000000] Linux version 4.4.92 (buildbot at builds-02.infra.lede-project.org) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3101-bce140e) ) #0 Tue Oct 17 14:59:45 2017
[    0.000000] MyLoader: sysp=fffeff36, boardp=b7369ffb, parts=d7ffffbc
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019374 (MIPS 24Kc)
[    0.000000] SoC: Atheros AR9330 rev 1
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 04000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] No valid device tree found, continuing without
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000003ffffff]
[    0.000000] On node 0 totalpages: 16384
[    0.000000] free_area_init_node: node 0, pgdat 803d04d0, node_mem_map 81000000
[    0.000000]   Normal zone: 128 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 16384 pages, LIFO batch:3
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
[    0.000000] Kernel command line:  board=TUBE2H console=ttyATH0,115200 mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,15936k(firmware),64k(nvram),64k(art)ro rootfstype=squashfs,jffs2 noinitrd
[    0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 60352K/65536K available (3076K kernel code, 160K rwdata, 412K rodata, 312K init, 205K bss, 5184K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:51
[    0.000000] Clocks: CPU:400.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:25.000MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000013] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.007553] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
[    0.088746] pid_max: default: 32768 minimum: 301
[    0.093353] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.099502] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.109806] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.117847] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.125423] NET: Registered protocol family 16
[    0.130150] MIPS: machine is ALFA NETWORK Tube2H
[    0.364146] Can't analyze schedule() prologue at 800670fc
[    0.380569] clocksource: Switched to clocksource MIPS
[    0.385626] NET: Registered protocol family 2
[    0.389753] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.395155] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.401194] TCP: Hash tables configured (established 1024 bind 1024)
[    0.407366] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.412851] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.419139] NET: Registered protocol family 1
[    0.423029] PCI: CLS 0 bytes, default 32
[    0.428687] Crashlog allocated RAM at address 0x3f00000
[    0.453035] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.457232] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.470249] io scheduler noop registered
[    0.472691] io scheduler deadline registered (default)
[    0.477820] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.487826] ar933x-uart: ttyATH0 at MMIO 0x18020000 (irq = 11, base_baud = 1562500) is a AR933X UART
[    0.495688] console [ttyATH0] enabled
[    0.502470] bootconsole [early0] disabled
[    0.516623] m25p80 spi0.0: found mx25l12805d, expected m25p80
[    0.521036] m25p80 spi0.0: mx25l12805d (16384 Kbytes)
[    0.525987] 5 cmdlinepart partitions found on MTD device spi0.0
[    0.531874] Creating 5 MTD partitions on "spi0.0":
[    0.536638] 0x000000000000-0x000000040000 : "u-boot"
[    0.544636] 0x000000040000-0x000000050000 : "u-boot-env"
[    0.550814] 0x000000050000-0x000000fe0000 : "firmware"
[    0.572389] 2 uimage-fw partitions found on MTD device firmware
[    0.576868] 0x000000050000-0x000000190000 : "kernel"
[    0.583803] 0x000000190000-0x000000fe0000 : "rootfs"
[    0.589560] mtd: device 4 (rootfs) set to be root filesystem
[    0.593886] 1 squashfs-split partitions found on MTD device rootfs
[    0.599940] 0x0000003b0000-0x000000fe0000 : "rootfs_data"
[    0.607674] 0x000000fe0000-0x000000ff0000 : "nvram"
[    0.613493] 0x000000ff0000-0x000001000000 : "art"
[    0.636049] libphy: ag71xx_mdio: probed
[    1.222278] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY]
[    1.230991] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
[    1.238804] NET: Registered protocol family 10
[    1.247011] NET: Registered protocol family 17
[    1.250087] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    1.262831] 8021q: 802.1Q VLAN Support v1.8
[    1.274164] VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
[    1.282268] Freeing unused kernel memory: 312K
[    2.537440] init: Console is alive
[    2.539690] init: - watchdog -
[    3.599703] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    3.697112] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    3.705120] init: - preinit -
[    4.232613] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    4.266572] random: procd: uninitialized urandom read (4 bytes read, 6 bits of entropy available)
[    7.659183] jffs2: notice: (361) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[    7.675112] mount_root: switching to jffs2 overlay
[    7.687121] urandom-seed: Seeding with /etc/urandom.seed
[    7.987822] procd: - early -
[    7.989387] procd: - watchdog -
[    8.679860] procd: - watchdog -
[    8.682044] procd: - ubus -
[    8.810445] random: ubusd: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
[    8.907894] random: ubusd: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
[    8.916112] random: ubusd: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
[    8.924571] random: ubusd: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
[    8.933849] random: ubusd: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
[    8.942414] random: ubusd: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
[    8.951768] random: ubusd: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
[    8.960336] random: ubusd: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
[    8.969689] procd: - init -
[    9.405503] kmodloader: loading kernel modules from /etc/modules.d/*
[    9.416486] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    9.435926] Loading modules backported from Linux version wt-2017-01-31-0-ge882dff19e7f
[    9.442573] Backport generated by backports.git backports-20160324-13-g24da7d3c
[    9.454320] ip_tables: (C) 2000-2006 Netfilter Core Team
[    9.469259] nf_conntrack version 0.5.0 (947 buckets, 3788 max)
[    9.519627] xt_time: kernel timezone is -0000
[    9.596929] PPP generic driver version 2.4.2
[    9.603310] NET: Registered protocol family 24
[    9.662487] ath: phy0: Unable to initialize hardware; initialization status: -5
[    9.668364] ath9k ar933x_wmac: failed to initialize device
[    9.673901] ath9k: probe of ar933x_wmac failed with error -5
[    9.681699] kmodloader: done loading kernel modules from /etc/modules.d/*
[   11.610530] random: jshn: uninitialized urandom read (4 bytes read, 19 bits of entropy available)
[   20.860043] device eth0 entered promiscuous mode
[   20.865427] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[   31.742046] eth0: link up (100Mbps/Full duplex)
[   31.745204] br-lan: port 1(eth0) entered forwarding state
[   31.750630] br-lan: port 1(eth0) entered forwarding state
[   31.758377] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[   33.750711] br-lan: port 1(eth0) entered forwarding state
[   77.030624] random: nonblocking pool is initialized


Capture of log from ALFA NETWORK Tube2H 4.12 prior to flashing OpenWRT


Jan  1 12:00:00 ALFA syslog.info syslogd started: BusyBox v1.19.2
Jan  1 12:00:00 ALFA user.notice kernel: klogd started: BusyBox v1.19.2 (2017-06-07 12:03:11 CST)
Jan  1 12:00:00 ALFA user.notice kernel: Linux version 2.6.31--LSDK-9.2.0_U11.14-dirty (mini at swbuild.alfacloud.tk) (gcc version 4.3.3 (GCC) ) #53 Wed Jun 7 12:05:14 CST 2017
Jan  1 12:00:00 ALFA user.warn kernel: flash_size passed from bootloader = 16
Jan  1 12:00:00 ALFA user.warn kernel: arg 1: console=ttyS0,115200
Jan  1 12:00:00 ALFA user.warn kernel: arg 2: root=31:02
Jan  1 12:00:00 ALFA user.warn kernel: arg 3: init=/sbin/init
Jan  1 12:00:00 ALFA user.warn kernel: arg 4: mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),14336k(rootfs),1600k(uImage),64k(NVRAM),64k(ART)
Jan  1 12:00:00 ALFA user.warn kernel: arg 5: mem=64M
Jan  1 12:00:00 ALFA user.info kernel: CPU revision is: 00019374 (MIPS 24Kc)
Jan  1 12:00:00 ALFA user.info kernel: Determined physical RAM map:
Jan  1 12:00:00 ALFA user.info kernel:  memory: 02000000 @ 00000000 (usable)
Jan  1 12:00:00 ALFA user.info kernel: Readback ErrCtl register=00000000
Jan  1 12:00:00 ALFA user.info kernel: Memory: 61456k/65536k available (2570k kernel code, 4008k reserved, 495k data, 152k init, 0k highmem)
Jan  1 12:00:00 ALFA user.info kernel: NR_IRQS:128
Jan  1 12:00:00 ALFA user.warn kernel: plat_time_init: plat time init done
Jan  1 12:00:00 ALFA user.info kernel: Calibrating delay loop... 266.24 BogoMIPS (lpj=532480)
Jan  1 12:00:00 ALFA user.warn kernel: Mount-cache hash table entries: 512
Jan  1 12:00:00 ALFA user.info kernel: NET: Registered protocol family 16
Jan  1 12:00:00 ALFA user.warn kernel: ===== ar7240_platform_init: 0
Jan  1 12:00:00 ALFA user.warn kernel: bio: create slab  at 0
Jan  1 12:00:00 ALFA user.notice kernel: SCSI subsystem initialized
Jan  1 12:00:00 ALFA user.info kernel: cfg80211: Calling CRDA to update world regulatory domain
Jan  1 12:00:00 ALFA user.info kernel: NET: Registered protocol family 2
Jan  1 12:00:00 ALFA user.info kernel: IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan  1 12:00:00 ALFA user.info kernel: TCP established hash table entries: 2048 (order: 2, 16384 bytes)
Jan  1 12:00:00 ALFA user.info kernel: TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
Jan  1 12:00:00 ALFA user.info kernel: TCP: Hash tables configured (established 2048 bind 2048)
Jan  1 12:00:00 ALFA user.info kernel: TCP reno registered
Jan  1 12:00:00 ALFA user.info kernel: NET: Registered protocol family 1
Jan  1 12:00:00 ALFA user.warn kernel: AR7240 GPIOC major 0
Jan  1 12:00:00 ALFA user.info kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
Jan  1 12:00:00 ALFA user.info kernel: msgmni has been set to 120
Jan  1 12:00:00 ALFA user.info kernel: alg: No test for lzma (lzma-generic)
Jan  1 12:00:00 ALFA user.info kernel: alg: No test for stdrng (krng)
Jan  1 12:00:00 ALFA user.info kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
Jan  1 12:00:00 ALFA user.info kernel: io scheduler noop registered
Jan  1 12:00:00 ALFA user.info kernel: io scheduler deadline registered (default)
Jan  1 12:00:00 ALFA user.info kernel: HDLC line discipline maxframe=4096
Jan  1 12:00:00 ALFA user.info kernel: N_HDLC line discipline registered.
Jan  1 12:00:00 ALFA user.info kernel: Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
Jan  1 12:00:00 ALFA user.warn kernel: ttyS0: detected caps 00000000 should be 00000100
Jan  1 12:00:00 ALFA user.info kernel: serial8250.0: ttyS0 at MMIO 0xb8020000 (irq = 19) is a 16550A
Jan  1 12:00:00 ALFA user.info kernel: console [ttyS0] enabled
Jan  1 12:00:00 ALFA user.info kernel: brd: module loaded
Jan  1 12:00:00 ALFA user.info kernel: PPP generic driver version 2.4.2
Jan  1 12:00:00 ALFA user.info kernel: PPP Deflate Compression module registered
Jan  1 12:00:00 ALFA user.info kernel: PPP BSD Compression module registered
Jan  1 12:00:00 ALFA user.info kernel: PPP MPPE Compression module registered
Jan  1 12:00:00 ALFA user.info kernel: NET: Registered protocol family 24
Jan  1 12:00:00 ALFA user.info kernel: PPPoL2TP kernel driver, V1.0
Jan  1 12:00:00 ALFA user.info kernel: IMQ driver loaded successfully.
Jan  1 12:00:00 ALFA user.info kernel: 	Hooking IMQ before NAT on PREROUTING.
Jan  1 12:00:00 ALFA user.info kernel: 	Hooking IMQ after NAT on POSTROUTING.
Jan  1 12:00:00 ALFA user.warn kernel: No partitions found on flash bank 0, use default mtd partitions tables
Jan  1 12:00:00 ALFA user.notice kernel: Creating 7 MTD partitions on "ar7240-nor0":
Jan  1 12:00:00 ALFA user.notice kernel: 0x000000000000-0x000000040000 : "u-boot"
Jan  1 12:00:00 ALFA user.notice kernel: 0x000000040000-0x000000050000 : "u-boot-env"
Jan  1 12:00:00 ALFA user.notice kernel: 0x000000190000-0x000000fe0000 : "rootfs"
Jan  1 12:00:00 ALFA user.notice kernel: 0x000000050000-0x000000190000 : "uImage"
Jan  1 12:00:00 ALFA user.notice kernel: 0x000000fe0000-0x000000ff0000 : "NVRAM"
Jan  1 12:00:00 ALFA user.notice kernel: 0x000000ff0000-0x000001000000 : "ART"
Jan  1 12:00:00 ALFA user.notice kernel: 0x000000050000-0x000000ff0000 : "firmware"
Jan  1 12:00:00 ALFA user.info kernel: NET: Registered protocol family 26
Jan  1 12:00:00 ALFA user.warn kernel: GACT probability on
Jan  1 12:00:00 ALFA user.warn kernel: Mirror/redirect action on
Jan  1 12:00:00 ALFA user.info kernel: netem: version 1.2
Jan  1 12:00:00 ALFA user.warn kernel: u32 classifier
Jan  1 12:00:00 ALFA user.warn kernel:     Performance counters on
Jan  1 12:00:00 ALFA user.warn kernel:     input device check on 
Jan  1 12:00:00 ALFA user.warn kernel:     Actions configured 
Jan  1 12:00:00 ALFA user.warn kernel: Netfilter messages via NETLINK v0.30.
Jan  1 12:00:00 ALFA user.warn kernel: nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
Jan  1 12:00:00 ALFA user.warn kernel: CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
Jan  1 12:00:00 ALFA user.warn kernel: nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
Jan  1 12:00:00 ALFA user.warn kernel: sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
Jan  1 12:00:00 ALFA user.warn kernel: ctnetlink v0.93: registering with nfnetlink.
Jan  1 12:00:00 ALFA user.info kernel: xt_time: kernel timezone is -0000
Jan  1 12:00:00 ALFA user.info kernel: IPv4 over IPv4 tunneling driver
Jan  1 12:00:00 ALFA user.info kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan  1 12:00:00 ALFA user.info kernel: arp_tables: (C) 2002 David S. Miller
Jan  1 12:00:00 ALFA user.info kernel: TCP bic registered
Jan  1 12:00:00 ALFA user.info kernel: TCP cubic registered
Jan  1 12:00:00 ALFA user.info kernel: TCP westwood registered
Jan  1 12:00:00 ALFA user.info kernel: TCP htcp registered
Jan  1 12:00:00 ALFA user.info kernel: NET: Registered protocol family 10
Jan  1 12:00:00 ALFA user.info kernel: IPv6 over IPv4 tunneling driver
Jan  1 12:00:00 ALFA user.info kernel: NET: Registered protocol family 17
Jan  1 12:00:00 ALFA user.notice kernel: Bridge firewalling registered
Jan  1 12:00:00 ALFA user.info kernel: Ebtables v2.0 registered
Jan  1 12:00:00 ALFA user.info kernel: 802.1Q VLAN Support v1.8 Ben Greear 
Jan  1 12:00:00 ALFA user.info kernel: All bugs added by David S. Miller 
Jan  1 12:00:00 ALFA user.warn kernel: Register factory default success 0.
Jan  1 12:00:00 ALFA user.warn kernel: arch/mips/ar7240/gpio.c (ar7240_simple_config_init) AP_RESET_GPIO: 12
Jan  1 12:00:00 ALFA user.warn kernel: Init XLNA PIN Function.
Jan  1 12:00:00 ALFA user.warn kernel: Init Soft Reset Function.
Jan  1 12:00:00 ALFA user.warn kernel: ar7240wdt_init: Registering WDT success
Jan  1 12:00:00 ALFA user.warn kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Jan  1 12:00:00 ALFA user.info kernel: Freeing unused kernel memory: 152k freed
Jan  1 12:00:00 ALFA user.warn kernel: **** drop_caches_sysctl_handler: all done timer added ...**** 
Jan  1 12:00:00 ALFA user.warn kernel: ATHR_GMAC: Length per segment 1536
Jan  1 12:00:00 ALFA user.warn kernel: ATHR_GMAC: fifo cfg 3 01f00140
Jan  1 12:00:00 ALFA user.warn kernel: ATHR_GMAC: Mac address for unit 0
Jan  1 12:00:00 ALFA user.warn kernel: ATHR_GMAC: 00:c0:ca:96:54:49 
Jan  1 12:00:00 ALFA user.warn kernel: ATHR_GMAC: Max segments per packet :   1
Jan  1 12:00:00 ALFA user.warn kernel: ATHR_GMAC: Max tx descriptor count :   40
Jan  1 12:00:00 ALFA user.warn kernel: ATHR_GMAC: Max rx descriptor count :   252
Jan  1 12:00:00 ALFA user.warn kernel: ATHR_GMAC: Mac capability flags    :   4401
Jan  1 12:00:00 ALFA user.warn kernel: ATHR_GMAC: Mac address for unit 1
Jan  1 12:00:00 ALFA user.warn kernel: ATHR_GMAC: 00:c0:ca:96:54:48 
Jan  1 12:00:00 ALFA user.warn kernel: ATHR_GMAC: Max segments per packet :   1
Jan  1 12:00:00 ALFA user.warn kernel: ATHR_GMAC: Max tx descriptor count :   40
Jan  1 12:00:00 ALFA user.warn kernel: ATHR_GMAC: Max rx descriptor count :   252
Jan  1 12:00:00 ALFA user.warn kernel: ATHR_GMAC: Mac capability flags    :   4C81
Jan  1 12:00:00 ALFA user.info kernel: device eth0 entered promiscuous mode
Jan  1 12:00:00 ALFA user.info kernel: device eth1 entered promiscuous mode
Jan  1 12:00:03 ALFA user.warn kernel: athr_gmac_ring_alloc Allocated 640 at 0x83a49400
Jan  1 12:00:03 ALFA user.warn kernel: athr_gmac_ring_alloc Allocated 4032 at 0x83a5d000
Jan  1 12:00:03 ALFA user.warn kernel: Setting Drop CRC Errors, Pause Frames and Length Error frames 
Jan  1 12:00:03 ALFA user.warn kernel: Setting PHY...
Jan  1 12:00:03 ALFA user.warn kernel: ATHR_GMAC: Enet Unit:0 PHY:4 is UP Mii 100Mbps full duplex
Jan  1 12:00:03 ALFA user.warn kernel: ATHR_GMAC: done cfg2 0x7115 ifctl 0x10000 miictrl  
Jan  1 12:00:03 ALFA user.warn kernel: Setting Drop CRC Errors, Pause Frames and Length Error frames 
Jan  1 12:00:03 ALFA user.info kernel: br0: port 1(eth0) entering learning state
Jan  1 12:00:05 ALFA user.warn kernel: athr_gmac_ring_alloc Allocated 640 at 0x83a49000
Jan  1 12:00:05 ALFA user.warn kernel: athr_gmac_ring_alloc Allocated 4032 at 0x83a87000
Jan  1 12:00:05 ALFA user.warn kernel: Setting Drop CRC Errors, Pause Frames and Length Error frames 
Jan  1 12:00:05 ALFA user.warn kernel: ATHRS26: resetting s26
Jan  1 12:00:05 ALFA user.warn kernel: ATHRS26: s26 reset done
Jan  1 12:00:05 ALFA user.warn kernel: Setting PHY...
Jan  1 12:00:05 ALFA user.info kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jan  1 12:00:10 ALFA user.info kernel: br0: port 1(eth0) entering disabled state
Jan  1 12:00:10 ALFA user.info kernel: br0: port 1(eth0) entering forwarding state
Jan  1 12:00:11 ALFA user.warn kernel: Disable XLNA
Jan  1 12:00:11 ALFA user.warn kernel: asf: module license 'Proprietary' taints kernel.
Jan  1 12:00:11 ALFA user.warn kernel: Disabling lock debugging due to kernel taint
Jan  1 12:00:12 ALFA user.info kernel: ath_hal: 0.9.17.1 (AR9380, DEBUG, REGOPS_FUNC, WRITE_EEPROM, 11D)
Jan  1 12:00:12 ALFA user.info kernel: ath_rate_atheros: Copyright (c) 2001-2005 Atheros Communications, Inc, All Rights Reserved
Jan  1 12:00:12 ALFA user.info kernel: ath_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved
Jan  1 12:00:13 ALFA user.info kernel: ath_ahb: 9.2.0_U11.14 (Atheros/multi-bss)
Jan  1 12:00:13 ALFA user.warn kernel: __ath_attach: Set global_scn[0]
Jan  1 12:00:13 ALFA user.warn kernel: ACBKMinfree = 48
Jan  1 12:00:13 ALFA user.warn kernel: ACBEMinfree = 32
Jan  1 12:00:13 ALFA user.warn kernel: ACVIMinfree = 16
Jan  1 12:00:13 ALFA user.warn kernel: ACVOMinfree = 0
Jan  1 12:00:13 ALFA user.warn kernel: CABMinfree = 48
Jan  1 12:00:13 ALFA user.warn kernel: UAPSDMinfree = 0
Jan  1 12:00:13 ALFA user.info kernel: Bootstrap clock 25MHz
Jan  1 12:00:13 ALFA user.info kernel: ar9300RadioAttach: Need analog access recipe!!
Jan  1 12:00:13 ALFA user.info kernel: Restoring Cal data from Flash
Jan  1 12:00:13 ALFA user.warn kernel: SC Callback Registration for wifi0
Jan  1 12:00:13 ALFA user.info kernel: wifi0: Atheros 9380: mem=0xb8100000, irq=2
Jan  1 12:00:13 ALFA user.warn kernel: wlan_vap_create : enter. devhandle=0x830402c0, opmode=IEEE80211_M_HOSTAP, flags=0x1
Jan  1 12:00:13 ALFA user.warn kernel: wlan_vap_create : exit. devhandle=0x830402c0, opmode=IEEE80211_M_HOSTAP, flags=0x1.
Jan  1 12:00:13 ALFA user.warn kernel: Enter adf_net_vlan_attach()
Jan  1 12:00:13 ALFA user.warn kernel: Leave adf_net_vlan_attach()
Jan  1 12:00:13 ALFA user.warn kernel:  ieee80211_ioctl_siwmode: imr.ifm_active=131712, new mode=3, valid=1 
Jan  1 12:00:14 ALFA user.debug kernel: eth0: no IPv6 routers present
Jan  1 12:00:15 ALFA user.info kernel: device ath0 entered promiscuous mode
Jan  1 12:00:15 ALFA user.warn kernel: Setting Max Stations:127
Jan  1 12:00:16 ALFA user.info kernel: br0: port 3(ath0) entering forwarding state
Jan  1 12:00:16 ALFA daemon.info init: starting pid 465, tty '': '/sbin/getty -L ttyS0 115200'
Jan  1 12:00:16 ALFA daemon.info init: starting pid 466, tty '': '/usr/bin/webs'
Jan  1 12:00:21 ALFA user.debug kernel: br0: no IPv6 routers present
Jan  1 12:00:21 ALFA user.debug kernel: br0: no IPv6 routers present
Jan  1 12:00:26 ALFA user.debug kernel: ath0: no IPv6 routers present
Jan  1 12:00:56 ALFA user.warn kernel: ath_paprd_cal PAPRD excessive failure disabling PAPRD now

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1532


From lede-bugs at lists.infradead.org  Sun May  6 12:43:00 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 06 May 2018 19:43:00 +0000
Subject: [FS#1532] ar71xx - ath9k: probe of ar933x_wmac failed with error -5
In-Reply-To: <FS1532@bugs.openwrt.org>
References: <FS1532@bugs.openwrt.org>
Message-ID: <mailman.7436.1525635796.2282.lede-bugs@lists.infradead.org>

Piotr Dymacz has taken ownership of the following task:

FS#1532 - ar71xx - ath9k: probe of ar933x_wmac failed with error -5

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1532


From lede-bugs at lists.infradead.org  Sun May  6 12:44:40 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 06 May 2018 19:44:40 +0000
Subject: [FS#1532] ar71xx - ath9k: probe of ar933x_wmac failed with error -5
In-Reply-To: <FS1532@bugs.openwrt.org>
References: <FS1532@bugs.openwrt.org>
Message-ID: <mailman.7437.1525635895.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1532 - ar71xx - ath9k: probe of ar933x_wmac failed with error -5
User who did this - Piotr Dymacz (pepe2k)

----------
The problem is related to the wrong ART data offset caused by flash type change (8 -> 16 MB). I'm aware of this issue and will fix it.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1532#comment4702


From lede-bugs at lists.infradead.org  Sun May  6 14:36:53 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 06 May 2018 21:36:53 +0000
Subject: [FS#1533] Host configuration of phase2.builds.lede-project.org is
 broken via IPv6 HTTPS
In-Reply-To: <FS1533@bugs.openwrt.org>
References: <FS1533@bugs.openwrt.org>
Message-ID: <mailman.7443.1525642631.2282.lede-bugs@lists.infradead.org>

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

User who did this - Carl-Daniel Hailfinger (hailfinger) 

Attached to Project - OpenWrt/LEDE Project
Summary - Host configuration of phase2.builds.lede-project.org is broken via IPv6 HTTPS
Task Type - Bug Report
Category - Website
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - https://phase2.builds.lede-project.org/waterfall via IPv6 shows the phase1 builder.

Accessing phase2.builds.lede-project.org via HTTP works for IPv4 and IPv6.
Accessing phase2.builds.lede-project.org via HTTPS works only for IPv4.
Only the combination of IPv6 and HTTPS returns the wrong content.

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1533


From lede-bugs at lists.infradead.org  Sun May  6 22:38:42 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 07 May 2018 05:38:42 +0000
Subject: [FS#1498] Building gccgo failes
In-Reply-To: <FS1498@bugs.openwrt.org>
References: <FS1498@bugs.openwrt.org>
Message-ID: <mailman.7457.1525671670.2282.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#1498 - Building gccgo failes
User who did this - Yousong Zhou (yousong)

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


From lede-bugs at lists.infradead.org  Sun May  6 22:38:31 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 07 May 2018 05:38:31 +0000
Subject: [FS#1498] Building gccgo failes
In-Reply-To: <FS1498@bugs.openwrt.org>
References: <FS1498@bugs.openwrt.org>
Message-ID: <mailman.7458.1525671670.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1498 - Building gccgo failes
User who did this - Yousong Zhou (yousong)

----------
Fixed for 7.3.0 by https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=f172456edcee41d37d182bdb6423247c90a1333f

Thank you for the feedback.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1498#comment4703


From lede-bugs at lists.infradead.org  Mon May  7 22:08:27 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 08 May 2018 05:08:27 +0000
Subject: [FS#1510] busybox conflicts with flock
In-Reply-To: <FS1510@bugs.openwrt.org>
References: <FS1510@bugs.openwrt.org>
Message-ID: <mailman.7700.1525756257.2282.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#1510 - busybox conflicts with flock
User who did this - Yousong Zhou (yousong)

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


From lede-bugs at lists.infradead.org  Mon May  7 22:12:00 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 08 May 2018 05:12:00 +0000
Subject: [FS#1519] glibc source code download fails
In-Reply-To: <FS1519@bugs.openwrt.org>
References: <FS1519@bugs.openwrt.org>
Message-ID: <mailman.7703.1525756338.2282.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#1519 - glibc source code download fails
User who did this - Yousong Zhou (yousong)

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


From lede-bugs at lists.infradead.org  Mon May  7 22:12:14 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 08 May 2018 05:12:14 +0000
Subject: [FS#1529] Feature request: preserve official firmware in spare
 partition
In-Reply-To: <FS1529@bugs.openwrt.org>
References: <FS1529@bugs.openwrt.org>
Message-ID: <mailman.7704.1525756351.2282.lede-bugs@lists.infradead.org>

The following task has been changed.  The changes are listed below.  For full information about what has changed, visit the URL and click the History tab.

FS#1529 - Feature request: preserve official firmware in spare partition
User who did this: Yousong Zhou (yousong)
Task Type: Bug Report -> Feature Request

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1529


From lede-bugs at lists.infradead.org  Mon May  7 22:13:21 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 08 May 2018 05:13:21 +0000
Subject: [FS#1529] Preserve oem firmware in spare partition
In-Reply-To: <FS1529@bugs.openwrt.org>
References: <FS1529@bugs.openwrt.org>
Message-ID: <mailman.7705.1525756419.2282.lede-bugs@lists.infradead.org>

The following task has been changed.  The changes are listed below.  For full information about what has changed, visit the URL and click the History tab.

FS#1529 - Preserve oem firmware in spare partition
User who did this: Yousong Zhou (yousong)
Summary: Feature request: preserve official firmware in spare partition -> Preserve oem firmware in spare partition

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1529


From lede-bugs at lists.infradead.org  Mon May  7 22:15:36 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 08 May 2018 05:15:36 +0000
Subject: [FS#1242] SATA broken on kernel 4.9 on mt7621
In-Reply-To: <FS1242@bugs.openwrt.org>
References: <FS1242@bugs.openwrt.org>
Message-ID: <mailman.7706.1525756555.2282.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#1242 - SATA broken on kernel 4.9 on mt7621
User who did this - Yousong Zhou (yousong)

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


From lede-bugs at lists.infradead.org  Mon May  7 22:23:30 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 08 May 2018 05:23:30 +0000
Subject: [FS#1299] Build system can't build target-specific packages depending
 on generic packages
In-Reply-To: <FS1299@bugs.openwrt.org>
References: <FS1299@bugs.openwrt.org>
Message-ID: <mailman.7707.1525757030.2282.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#1299 - Build system can't build target-specific packages depending on generic packages
User who did this - Jo-Philipp Wich (jow-)

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


From lede-bugs at lists.infradead.org  Mon May  7 22:36:00 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 08 May 2018 05:36:00 +0000
Subject: [FS#1440] print_req_error: I/O error, dev mtdblock6, sector 198400  
 during boot up 
In-Reply-To: <FS1440@bugs.openwrt.org>
References: <FS1440@bugs.openwrt.org>
Message-ID: <mailman.7708.1525757779.2282.lede-bugs@lists.infradead.org>

The following task has been changed.  The changes are listed below.  For full information about what has changed, visit the URL and click the History tab.

FS#1440 - print_req_error: I/O error, dev mtdblock6, sector 198400   during boot up 
User who did this: Yousong Zhou (yousong)
Task details edited:
-------
This happens on EA9500
software version :trunk   --> kernel 4.14.23
Linux EA9500 4.14.23 #0 SMP Sat Mar 3 11:58:56 2018 armv7l GNU/Linux


I get the following messages with dmesg


42.447266] print_req_error: 30 callbacks suppressed
[ 42.447270] print_req_error: I/O error, dev mtdblock6, sector 198400
[ 42.459360] print_req_error: I/O error, dev mtdblock6, sector 198400
[ 42.465729] buffer_io_error: 10 callbacks suppressed
[ 42.465733] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[ 42.685316] print_req_error: I/O error, dev mtdblock6, sector 198400
[ 42.692500] print_req_error: I/O error, dev mtdblock6, sector 198400
[ 42.698876] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[ 42.908176] print_req_error: I/O error, dev mtdblock6, sector 198400
[ 42.915383] print_req_error: I/O error, dev mtdblock6, sector 198400
[ 42.921759] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[ 43.130302] print_req_error: I/O error, dev mtdblock6, sector 198400
[ 43.137507] print_req_error: I/O error, dev mtdblock6, sector 198400
[ 43.143877] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[ 43.252159] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[ 43.258771] br-lan: port 3(wlan1) entered blocking state
[ 43.264176] br-lan: port 3(wlan1) entered forwarding state
[ 43.393398] print_req_error: I/O error, dev mtdblock6, sector 198400
[ 43.400450] print_req_error: I/O error, dev mtdblock6, sector 198400
[ 43.406823] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[ 43.648404] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[ 43.858002] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[ 44.067634] Buffer I/O error on dev mtdblock6, logical block 24800, async page read
[ 44.281965] Buffer I/O error on dev mtdblock6, logical block 24800, async page read


here some info about the setup of mtd on my system


root at OpenWrt:/bin# cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00020000 "boot"
mtd1: 00100000 00020000 "nvram"
mtd2: 00080000 00020000 "nvram"
mtd3: 01d00000 00020000 "firmware"
mtd4: 003fffe4 00020000 "linux"
mtd5: 01900000 00020000 "ubi"
mtd6: 06100000 00020000 ?failsafe?


This different than you have it in your random noise blog:


[ 3.967344] Creating 7 MTD partitions on ?brcmnand.0?:
[ 3.972500] 0x000000000000-0x000000080000 : ?boot?
[ 3.977913] 0x000000080000-0x000000180000 : ?nvram?
[ 3.983348] 0x000000180000-0x000000200000 : ?nvram?
[ 3.988757] 0x000000200000-0x000001f00000 : ?firmware?
[ 3.994846] 0x000001f00000-0x000008000000 : ?failsafe?
[ 4.000664] 0x00000020001c-0x00000037c000 : ?linux?
[ 4.006107] 0x00000037c000-0x000001f00000 : ?rootfs?
[ 4.023962] 0x000000620000-0x000001f00000 : ?rootfs_data?
?
 
-------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1440


From lede-bugs at lists.infradead.org  Mon May  7 22:39:11 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 08 May 2018 05:39:11 +0000
Subject: [FS#1440] print_req_error: I/O error, dev mtdblock6, sector 198400  
 during boot up 
In-Reply-To: <FS1440@bugs.openwrt.org>
References: <FS1440@bugs.openwrt.org>
Message-ID: <mailman.7709.1525757969.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1440 - print_req_error: I/O error, dev mtdblock6, sector 198400   during boot up 
User who did this - Yousong Zhou (yousong)

----------
Hi, It seems that linksys-ea9500 is currently disabled in the image build code.  Could you please also post your fix to the mailing list?
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1440#comment4704


From lede-bugs at lists.infradead.org  Mon May  7 22:47:49 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 08 May 2018 05:47:49 +0000
Subject: [FS#1476] make toolchain breaks at binutils
In-Reply-To: <FS1476@bugs.openwrt.org>
References: <FS1476@bugs.openwrt.org>
Message-ID: <mailman.7710.1525758487.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1476 - make toolchain breaks at binutils
User who did this - Yousong Zhou (yousong)

----------
Please share steps of reproduce and output of "./script/diffconfig.sh"
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1476#comment4705


From lede-bugs at lists.infradead.org  Mon May  7 22:50:22 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 08 May 2018 05:50:22 +0000
Subject: [FS#1517] kernel error: CPU: 2 PID: 27318 at lib/iov_iter.c:695
 copy_page_to_iter+0xc4/0x508
In-Reply-To: <FS1517@bugs.openwrt.org>
References: <FS1517@bugs.openwrt.org>
Message-ID: <mailman.7711.1525758641.2282.lede-bugs@lists.infradead.org>

The following task has been changed.  The changes are listed below.  For full information about what has changed, visit the URL and click the History tab.

FS#1517 - kernel error: CPU: 2 PID: 27318 at lib/iov_iter.c:695 copy_page_to_iter+0xc4/0x508
User who did this: Yousong Zhou (yousong)
Task details edited:
-------
Supply the following if possible:
 - Device problem occurs on: MT 7621 - ZBT 3526)
 - Software versions: Model	ZBT-WG3526 (16M)
 - Firmware Version: TRUNK - OpenWrt SNAPSHOT r6755-d089a5d / LuCI Master (git-18.113.52925-0c30ee0)
 - Kernel Version	4.14.34

 - Steps to reproduce
after a while i get: kernel errors and affterwards reboot needed.


Thu Apr 26 12:59:00 2018 kern.warn kernel: [69277.917386] ------------[ cut here ]------------
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69277.922064] WARNING: CPU: 2 PID: 27318 at lib/iov_iter.c:695 copy_page_to_iter+0xc4/0x508
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69277.930339] Modules linked in: pppoe ppp_async option usb_wwan pptp pppox ppp_mppe ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 mt76x2e mt7603e mt76 mac80211 iptable_nat 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_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_FLOWOFFLOAD xt_DSCP xt_CT xt_CLASSIFY usbserial usb_storage ts_fsm ts_bm slhc nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.001388]  nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda macvlan iptable_mangle iptable_filter ipt_ECN ip_tables crc_ccitt compat br_netfilter fuse sch_cake nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_tbf sch_htb sch_hfsc sch_ingress ledtrig_usbport 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
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.072898]  ip6table_mangle ip6table_filter ip6_tables x_tables ip_gre gre ifb ip_tunnel tun vfat fat f2fs ext4 jbd2 mbcache nls_utf8 nls_iso8859_1 nls_cp437 sha1_generic ecb crc32c_generic crc32_generic mmc_block mtk_sd mmc_core leds_gpio xhci_mtk xhci_plat_hcd xhci_pci xhci_hcd ahci libahci libata sd_mod scsi_mod gpio_button_hotplug usbcore nls_base usb_common
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.105236] CPU: 2 PID: 27318 Comm: cat Not tainted 4.14.34 #0
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.111065] Stack : 00000000 00000000 00000000 00000000 805f7ada 00000032 00000000 00000000
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.119416]         8f0ac1f4 80590927 8051cabc 00000002 00006ab6 00000001 8dca3be8 b3f6da0b
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.127750]         00000000 00000000 805f0000 00008808 00000000 00000199 00000008 00000000
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.136087]         00000000 80590000 00019b14 00000000 80000000 00000000 805b0000 80229950
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.144432]         00000009 000002b7 00000000 8dca3db0 00000001 802911d0 00000008 805f0008
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.152779]         ...
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.155227] Call Trace:
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.157698] [] show_stack+0x58/0x100
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.162148] [] dump_stack+0x9c/0xe0
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.166501] [] __warn+0xe0/0x114
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.170581] [] warn_slowpath_null+0x1c/0x30
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.175621] [] copy_page_to_iter+0xc4/0x508
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.180656] [] shmem_file_read_iter+0x2c0/0x3c0
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.186080] [] generic_file_splice_read+0xec/0x170
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.191721] [] splice_direct_to_actor+0xc8/0x234
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.197187] [] do_splice_direct+0x98/0xd0
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.202061] [] do_sendfile+0x284/0x478
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.206683] [] SyS_sendfile64+0x84/0xd8
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.211399] [] syscall_common+0x34/0x58
Thu Apr 26 12:59:00 2018 kern.warn kernel: [69278.216566] ---[ end trace b0a90f34a85fa703 ]---

-------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1517


From lede-bugs at lists.infradead.org  Mon May  7 22:51:05 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 08 May 2018 05:51:05 +0000
Subject: [FS#1518] kernel error: CPU: 2 PID: 27318 Comm: cat Not tainted
 4.14.34
In-Reply-To: <FS1518@bugs.openwrt.org>
References: <FS1518@bugs.openwrt.org>
Message-ID: <mailman.7712.1525758685.2282.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#1518 - kernel error: CPU: 2 PID: 27318 Comm: cat Not tainted 4.14.34
User who did this - Yousong Zhou (yousong)

Reason for closing: Duplicate
Additional comments about closing: Duplicate of #1517

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1518


From lede-bugs at lists.infradead.org  Mon May  7 23:36:25 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 08 May 2018 06:36:25 +0000
Subject: [FS#1534] ramips: Can't mount flash on MZK-DP150N.
In-Reply-To: <FS1534@bugs.openwrt.org>
References: <FS1534@bugs.openwrt.org>
Message-ID: <mailman.7717.1525761407.2282.lede-bugs@lists.infradead.org>

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

User who did this - YuheiOKAWA (srchack) 

Attached to Project - OpenWrt/LEDE Project
Summary - ramips: Can't mount flash on MZK-DP150N.
Task Type - Bug Report
Category - Kernel
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - High
Priority - Very Low
Reported Version - All
Due in Version - Undecided
Due Date - Undecided
Details - Can not mount SPI Flash on MZK-DP150N.

[    4.435797] spi spi0.0: force spi mode3
[    4.444935] m25p80 spi0.0: unrecognized JEDEC id bytes: 1c, 70, 16
[    4.457452] m25p80: probe of spi0.0 failed with error -2

MZK-DP150N new revision hardware is SPI Flash change.
new revision is EN25QH32.

is not found linux driver for en25qh32.
I want the following patch.

--- a/drivers/mtd/spi-nor/spi-nor.c
+++ b/drivers/mtd/spi-nor/spi-nor.c
@@ -1007,6 +1007,7 @@
        { "en25p64",    INFO(0x1c2017, 0, 64 * 1024,  128, 0) },
        { "en25q64",    INFO(0x1c3017, 0, 64 * 1024,  128, SECT_4K) },
        { "en25q128",   INFO(0x1c3018, 0, 64 * 1024,  256, SECT_4K) },
+       { "en25qh32",   INFO(0x1c7016, 0, 64 * 1024,   64, 0) },
        { "en25qh128",  INFO(0x1c7018, 0, 64 * 1024,  256, 0) },
        { "en25qh256",  INFO(0x1c7019, 0, 64 * 1024,  512, 0) },
        { "en25s64",    INFO(0x1c3817, 0, 64 * 1024,  128, SECT_4K) },


This device can not access u-boot unless the case is destroyed.
I also want to correspond to LEDE 17.0x.


More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1534


From lede-bugs at lists.infradead.org  Tue May  8 10:35:59 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 08 May 2018 17:35:59 +0000
Subject: [FS#1535] NTP configuration is not fully exported/saved/preserved
In-Reply-To: <FS1535@bugs.openwrt.org>
References: <FS1535@bugs.openwrt.org>
Message-ID: <mailman.7902.1525801234.2282.lede-bugs@lists.infradead.org>

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

User who did this - George (George-TL) 

Attached to Project - OpenWrt/LEDE Project
Summary - NTP configuration is not fully exported/saved/preserved
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - lede-17.01
Due in Version - Undecided
Due Date - Undecided
Details - Hi,

In LuCI, on page "System / System", there is option called "Enable NTP client".
This setting is reset during sysupgrade.
Configuration file exported from web-ui does not contain above setting.

My guess is that startup list (enabled/disabled) is not saved in exported configuration.

I'm running lede-17.01 head, commit 81573ea259247f1c6c1a7a490de174d0a6c48a64.

Regards,
George

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1535


From lede-bugs at lists.infradead.org  Wed May  9 02:55:31 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 09 May 2018 09:55:31 +0000
Subject: [FS#1536] Ubus: not creating needed /var/run directory
In-Reply-To: <FS1536@bugs.openwrt.org>
References: <FS1536@bugs.openwrt.org>
Message-ID: <mailman.8035.1525859747.2282.lede-bugs@lists.infradead.org>

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

User who did this - Christian Schoenebeck (chris5560) 

Attached to Project - OpenWrt/LEDE Project
Summary - Ubus: not creating needed /var/run directory
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - All
Due in Version - Undecided
Due Date - Undecided
Details - /sbin/init create /tmp/run directory.
ubus uses /var/run directory that?s normally linked to /tmp aka /tmp/run and starts up.

If by accident /var is deleted and the router is rebooted the system hangs forever.
It does not help to create an empty /var directory /var/run is not created by ubus.

Console shows: ?procd - early -? and afterwards ?procd - ubus -?
The needed directories are created later inside ?/etc/rc.d/S10boot? aka ?/etc/init.d/boot?


More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1536


From lede-bugs at lists.infradead.org  Wed May  9 06:08:07 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 09 May 2018 13:08:07 +0000
Subject: [FS#1537] Problem with HDD connection
In-Reply-To: <FS1537@bugs.openwrt.org>
References: <FS1537@bugs.openwrt.org>
Message-ID: <mailman.8093.1525871603.2282.lede-bugs@lists.infradead.org>

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

User who did this - Super Robot (super_robot) 

Attached to Project - OpenWrt/LEDE Project
Summary - Problem with HDD connection
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 - OpenWrt SNAPSHOT r6808-3a45668 
Xiaomi mi router 3g
--------------------------------
Kernel log:

[  100.808464] usb 2-1: new SuperSpeed USB device number 3 using xhci-mtk
[  100.842477] scsi host0: uas
[  100.846266] xhci-mtk 1e1c0000.xhci: ERROR Transfer event for unknown stream ring slot 1 ep 4
[  100.854725] xhci-mtk 1e1c0000.xhci: @000000000f7c23c0 0e8c3200 00000000 05000000 01058001
[  100.862911] xhci-mtk 1e1c0000.xhci: ERROR Transfer event for unknown stream ring slot 1 ep 6
[  100.871325] xhci-mtk 1e1c0000.xhci: @000000000f7c23d0 0e8c3100 00000000 05000000 01078001
[  122.138530] scsi 0:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
[  122.146096] scsi 0:0:0:0: tag#0 CDB: opcode=0x12 12 00 00 00 24 00
[  122.152401] xhci-mtk 1e1c0000.xhci: Mismatch between completed Set TR Deq Ptr command & xHCI internal state.
[  122.162190] xhci-mtk 1e1c0000.xhci: ep deq seg = 8f068680, deq ptr = ae9c5010
[  123.248527] scsi host0: uas_eh_device_reset_handler FAILED to get lock err -16
[  123.255748] scsi 0:0:0:0: Device offlined - not ready after error recovery
[  144.048598] xhci-mtk 1e1c0000.xhci: Cannot set link state.
[  144.054111] usb usb2-port1: cannot disable (err = -32)
[  144.059381] usb 2-1: USB disconnect, device number 3
[  144.064694] xhci-mtk 1e1c0000.xhci: Mismatch between completed Set TR Deq Ptr command & xHCI internal state.
[  144.074484] xhci-mtk 1e1c0000.xhci: ep deq seg = 8e9dc200, deq ptr = aea78010
----------------------------------------------------------------------------------------
root at OpenWrt:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
--------------------------------------------------------------------------------------------
On stock firmware and PC connecting and working good.
 

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1537


From lede-bugs at lists.infradead.org  Wed May  9 06:28:14 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 09 May 2018 13:28:14 +0000
Subject: [FS#1538] <all-packages> lose in /snapshots/packages/mipsel_24kc
In-Reply-To: <FS1538@bugs.openwrt.org>
References: <FS1538@bugs.openwrt.org>
Message-ID: <mailman.8096.1525872508.2282.lede-bugs@lists.infradead.org>

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

User who did this - ??? (h2y) 

Attached to Project - OpenWrt/LEDE Project
Summary -  lose in /snapshots/packages/mipsel_24kc
Task Type - Bug Report
Category - Packages
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - High
Priority - Very Low
Reported Version - All
Due in Version - Undecided
Due Date - Undecided
Details - 

the opkg repo are empty.

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1538


From lede-bugs at lists.infradead.org  Wed May  9 10:06:05 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 09 May 2018 17:06:05 +0000
Subject: [FS#1527] AR8327 low throughput
In-Reply-To: <FS1527@bugs.openwrt.org>
References: <FS1527@bugs.openwrt.org>
Message-ID: <mailman.8157.1525885714.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1527 - AR8327 low throughput
User who did this - eripek (eripek)

----------
Probably a duplicate of #891
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1527#comment4706


From lede-bugs at lists.infradead.org  Wed May  9 13:04:39 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 09 May 2018 20:04:39 +0000
Subject: [FS#1532] ar71xx - ath9k: probe of ar933x_wmac failed with error -5
In-Reply-To: <FS1532@bugs.openwrt.org>
References: <FS1532@bugs.openwrt.org>
Message-ID: <mailman.8214.1525896294.2282.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#1532 - ar71xx - ath9k: probe of ar933x_wmac failed with error -5
User who did this - Piotr Dymacz (pepe2k)

Reason for closing: Fixed
Additional comments about closing: Fixed in master with: https://git.openwrt.org/ce4d2fb5cc
Fixed in lede-17.01 with: https://git.openwrt.org/b078753084

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1532


From lede-bugs at lists.infradead.org  Wed May  9 14:25:11 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 09 May 2018 21:25:11 +0000
Subject: [FS#1532] ar71xx - ath9k: probe of ar933x_wmac failed with error -5
In-Reply-To: <FS1532@bugs.openwrt.org>
References: <FS1532@bugs.openwrt.org>
Message-ID: <mailman.8215.1525901127.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1532 - ar71xx - ath9k: probe of ar933x_wmac failed with error -5
User who did this - rceccleston (rceccleston)

----------
Evening, thank you for your feedback, I really appreciate your time.

Please may I ask, is there a file I may edit or temporary solution? Thank you.

~ # cat /proc/mtd
dev:    size   erasesize  name

mtd0: 00040000 00010000 "u-boot"

mtd1: 00010000 00010000 "u-boot-env"

mtd2: 00e50000 00010000 "rootfs"

mtd3: 00140000 00010000 "uImage"

mtd4: 00010000 00010000 "NVRAM"

mtd5: 00010000 00010000 "ART"

mtd6: 00fa0000 00010000 "firmware"
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1532#comment4707


From lede-bugs at lists.infradead.org  Thu May 10 00:04:48 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 10 May 2018 07:04:48 +0000
Subject: [FS#1540] armvirt targets broken in phase1 buildbot:
 kmod-switch-rtl8366-smi dependency for of_mdio.ko
In-Reply-To: <FS1540@bugs.openwrt.org>
References: <FS1540@bugs.openwrt.org>
Message-ID: <mailman.8254.1525936031.2282.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 - OpenWrt/LEDE Project
Summary - armvirt targets broken in phase1 buildbot: kmod-switch-rtl8366-smi dependency for of_mdio.ko
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 - armvirt targets in phase1 buildbot are broken since a few days. That has been hard to notice among the DNS breakage, but this seems to be different.

http://phase1.builds.lede-project.org/builders/armvirt%2F32

(armvirt32 SDK is used in phase2 buildbot for some targets there, e.g. ipq806x = arm_cortex-a15_neon-vfpv4, so those packages are now compiled with old stale SDK in phase2.)

Based on failure logs, I think that that the failure is probably due to commit 3dc523f2 "kernel: add OF support to rtl8355 driver"

https://github.com/openwrt/openwrt/commit/3dc523f232ff01d31d59345f5fa6de508d5059ef

phase1 failure log:

http://phase1.builds.lede-project.org/builders/armvirt%2F32/builds/668/steps/pkgbuild/logs/stdio/text

Package kmod-switch-rtl8366-smi is missing dependencies for the following libraries:
of_mdio.ko
modules/netdevices.mk:222: recipe for target '/var/lib/buildbot/slaves/slashdirt-02/armvirt_32/build/bin/targets/armvirt/32/packages/kmod-switch-rtl8366-smi_4.14.37-1_arm_cortex-a15_neon-vfpv4.ipk' failed
make[2]: *** [/var/lib/buildbot/slaves/slashdirt-02/armvirt_32/build/bin/targets/armvirt/32/packages/kmod-switch-rtl8366-smi_4.14.37-1_arm_cortex-a15_neon-vfpv4.ipk] Error 1
make[2]: Leaving directory '/var/lib/buildbot/slaves/slashdirt-02/armvirt_32/build/package/kernel/linux'
Command exited with non-zero status 2
time: package/kernel/linux/compile#8.24#0.89#34.43
package/Makefile:107: recipe for target 'package/kernel/linux/compile' failed
make[1]: *** [package/kernel/linux/compile] Error 2


https://github.com/openwrt/openwrt/blob/master/package/kernel/linux/modules/netdevices.mk#L209


More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1540


From lede-bugs at lists.infradead.org  Thu May 10 01:23:50 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 10 May 2018 08:23:50 +0000
Subject: [FS#1540] armvirt targets broken in phase1 buildbot:
 kmod-switch-rtl8366-smi dependency for of_mdio.ko
In-Reply-To: <FS1540@bugs.openwrt.org>
References: <FS1540@bugs.openwrt.org>
Message-ID: <mailman.8265.1525940645.2282.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#1540 - armvirt targets broken in phase1 buildbot: kmod-switch-rtl8366-smi dependency for of_mdio.ko
User who did this - john (john)

Reason for closing: Fixed
Additional comments about closing: fixed with dc629d9cf5afc03f67a294078ca1001e831c66c9

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1540


From lede-bugs at lists.infradead.org  Thu May 10 01:49:52 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 10 May 2018 08:49:52 +0000
Subject: [FS#1541] Invalid Kernel logspam : sit: non-ECT from <various IPs,
 Invalid IPs>
In-Reply-To: <FS1541@bugs.openwrt.org>
References: <FS1541@bugs.openwrt.org>
Message-ID: <mailman.8268.1525942207.2282.lede-bugs@lists.infradead.org>

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

User who did this - plntyk (plntyk) 

Attached to Project - OpenWrt/LEDE Project
Summary - Invalid Kernel logspam : sit: non-ECT from 
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 - Invalid IP suggests sth. wrong ?

Logs:

 dmesg |grep sit | sed 's/\[\ *[0-9]*\.[0-9]*\]//g' |sort |uniq

 sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
 sit: non-ECT from 0.14.42.24 with TOS=0x2
 sit: non-ECT from 0.14.42.24 with TOS=0x6
 sit: non-ECT from 0.14.42.24 with TOS=0xb
 sit: non-ECT from 0.14.42.24 with TOS=0xe
 sit: non-ECT from 0.14.42.24 with TOS=0xf
 sit: non-ECT from 0.206.0.0 with TOS=0x1
 sit: non-ECT from 0.206.0.0 with TOS=0x9
 sit: non-ECT from 0.206.0.0 with TOS=0xa
 sit: non-ECT from 1.30.2.141 with TOS=0x5
 sit: non-ECT from 1.30.2.141 with TOS=0x9
 sit: non-ECT from 1.30.2.141 with TOS=0xb
 sit: non-ECT from 1.30.2.141 with TOS=0xf
 sit: non-ECT from 1.30.2.143 with TOS=0x3
 sit: non-ECT from 1.30.2.143 with TOS=0x5
 sit: non-ECT from 1.30.2.143 with TOS=0x9
 sit: non-ECT from 1.30.2.143 with TOS=0xe
 sit: non-ECT from 20.22.0.242 with TOS=0x5
 sit: non-ECT from 20.22.0.242 with TOS=0x9
 sit: non-ECT from 20.22.0.242 with TOS=0xb
 sit: non-ECT from 32.0.0.1 with TOS=0x6
 sit: non-ECT from 32.0.0.1 with TOS=0x9
 sit: non-ECT from 32.72.0.1 with TOS=0x6
 sit: non-ECT from 64.1.8.27 with TOS=0x2
 sit: non-ECT from 64.1.8.27 with TOS=0xb
 sit: non-ECT from 64.1.8.27 with TOS=0xd
 sit: non-ECT from 64.1.8.27 with TOS=0xf
 sit: non-ECT from 64.14.8.11 with TOS=0xe
 sit: non-ECT from 64.14.8.5 with TOS=0x5
 sit: non-ECT from 64.14.8.5 with TOS=0xd
 sit: non-ECT from 64.14.8.7 with TOS=0x1
 sit: non-ECT from 64.14.8.7 with TOS=0x2
 sit: non-ECT from 64.14.8.7 with TOS=0x3
 sit: non-ECT from 64.14.8.7 with TOS=0x6
 sit: non-ECT from 64.14.8.7 with TOS=0xa
 sit: non-ECT from 64.14.8.7 with TOS=0xd
 sit: non-ECT from 64.14.8.9 with TOS=0xd
 sit: non-ECT from 72.96.0.0 with TOS=0x1
 sit: non-ECT from 72.96.0.0 with TOS=0x2
 sit: non-ECT from 72.96.0.0 with TOS=0x3
 sit: non-ECT from 72.96.0.0 with TOS=0x5
 sit: non-ECT from 72.96.0.0 with TOS=0x6
 sit: non-ECT from 72.96.0.0 with TOS=0x7
 sit: non-ECT from 72.96.0.0 with TOS=0x9
 sit: non-ECT from 72.96.0.0 with TOS=0xa
 sit: non-ECT from 72.96.0.0 with TOS=0xb
 sit: non-ECT from 72.96.0.0 with TOS=0xe
 sit: non-ECT from 72.96.0.0 with TOS=0xf

Supply the following if possible:
 - Device problem occurs on

TP-Link WDR3600

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

root at OpenWrt:~# cat /etc/openwrt_version 
r6867-ce4d2fb5cc
root at OpenWrt:~# cat /etc/openwrt_release 
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='SNAPSHOT'
DISTRIB_REVISION='r6867-ce4d2fb5cc'
DISTRIB_TARGET='ar71xx/generic'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r6867-ce4d2fb5cc'
DISTRIB_TAINTS='no-all'

 - Steps to reproduce

Updated router to recent trunk (WDR3600)
kept config 


Guessing:
log spam might involve tunnelbroker tunnel or openvpn server


some issues with either comp_lzo or openvpn-mbedtls on updating 
were resolved with "compress lzo" and openvpn-openssl on server side

vpn client is LEDE r5099 (OpenVPN 2.4.4 mips-openwrt-linux-gnu [SSL (mbed TLS)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
library versions: mbed TLS 2.6.0, LZO 2.10)




More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1541


From lede-bugs at lists.infradead.org  Thu May 10 01:52:58 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 10 May 2018 08:52:58 +0000
Subject: [FS#1541] Invalid Kernel logspam : sit: non-ECT from <various IPs,
 Invalid IPs>
In-Reply-To: <FS1541@bugs.openwrt.org>
References: <FS1541@bugs.openwrt.org>
Message-ID: <mailman.8269.1525942398.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1541 - Invalid Kernel logspam : sit: non-ECT from 
User who did this - plntyk (plntyk)

----------
found https://forum.freifunk.net/t/kernel-ip-tunnel-non-ect-from-185-66-194-0-with-tos-0x/6149/5

But there the problem vanished after some random updates
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1541#comment4708


From lede-bugs at lists.infradead.org  Thu May 10 13:54:42 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 10 May 2018 20:54:42 +0000
Subject: [FS#1541] Invalid Kernel logspam : sit: non-ECT from <various IPs,
 Invalid IPs>
In-Reply-To: <FS1541@bugs.openwrt.org>
References: <FS1541@bugs.openwrt.org>
Message-ID: <mailman.8347.1525985825.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1541 - Invalid Kernel logspam : sit: non-ECT from 
User who did this - Arjen de Korte (arjendekorte)

----------
FWIW, I see this too. About two weeks ago this started. Fortunately, I still have a build available that is not affected, so I'll dig in next week to see what is the culprit. I guess it is something related to OpenVPN/routing, since I can no longer tunnel IPv6 over an IPv4 OpenVPN connection.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1541#comment4709


From lede-bugs at lists.infradead.org  Thu May 10 23:55:22 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 06:55:22 +0000
Subject: [FS#1542] DHCP (dnsmasq) server doesn't properly reply on requests on
 EdgeRouter Lite (LAN)
In-Reply-To: <FS1542@bugs.openwrt.org>
References: <FS1542@bugs.openwrt.org>
Message-ID: <mailman.8417.1526022129.2282.lede-bugs@lists.infradead.org>

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

User who did this - diizzyy (diizzyy) 

Attached to Project - OpenWrt/LEDE Project
Summary - DHCP (dnsmasq) server doesn't properly reply on requests on EdgeRouter Lite (LAN)
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 - There's some breakage on the EdgeRouter Lite regarding DHCP/dnsmasq on LAN.
Neither r6861 (local build) or r6868 (official snapshot) works.

Setting static ip on clients works so it's not a link issue.

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1542


From lede-bugs at lists.infradead.org  Fri May 11 06:00:07 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 13:00:07 +0000
Subject: [FS#1538] <all-packages> lose in /snapshots/packages/mipsel_24kc
In-Reply-To: <FS1538@bugs.openwrt.org>
References: <FS1538@bugs.openwrt.org>
Message-ID: <mailman.8489.1526043624.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1538 -  lose in /snapshots/packages/mipsel_24kc
User who did this - Rob White (bluewavenet)

----------
I thought it was fixed but it looks now like the build system is chasing its tail with packages coming and going with each build if the package depends on others.
Is is just a matter of waiting or is there something else wrong?
I am trying to submit a PR on https://github.com/openwrt/packages and Travis is failing on dependencies. The failures change from one run to another without any changes in the PR.....
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1538#comment4710


From lede-bugs at lists.infradead.org  Fri May 11 06:37:38 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 13:37:38 +0000
Subject: [FS#1543] Many packages in snapshot failing on one build, ok on next
 but no code changes.
In-Reply-To: <FS1543@bugs.openwrt.org>
References: <FS1543@bugs.openwrt.org>
Message-ID: <mailman.8492.1526046008.2282.lede-bugs@lists.infradead.org>

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

User who did this - Rob White (bluewavenet) 

Attached to Project - OpenWrt/LEDE Project
Summary - Many packages in snapshot failing on one build, ok on next but no code changes.
Task Type - Build Failure
Category - Packages
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Critical
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Snapshot/Packages
Occurs on all architectures apparently at random with faillogs.
After next build some that failed will be ok and some that previously built will fail.
eg submit a PR on https://github.com/openwrt/packages
Travis shows fail on dependencies. After next automated build, Travis errors will be different, or if lucky will pass, only to fail again after the next build.
It seems the build system is chasing its tail somehow.

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1543


From lede-bugs at lists.infradead.org  Fri May 11 06:49:11 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 13:49:11 +0000
Subject: [FS#1543] Many packages in snapshot failing on one build, ok on next
 but no code changes.
In-Reply-To: <FS1543@bugs.openwrt.org>
References: <FS1543@bugs.openwrt.org>
Message-ID: <mailman.8494.1526046565.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1543 - Many packages in snapshot failing on one build, ok on next but no code changes.
User who did this - Jo-Philipp Wich (jow-)

----------
Not sure what to make out of this ticket. Do you have any *specific* examples I can investigate? I need at least *some* pointers to correlate things...
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1543#comment4711


From lede-bugs at lists.infradead.org  Fri May 11 08:10:28 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 15:10:28 +0000
Subject: [FS#1543] Many packages in snapshot failing on one build, ok on next
 but no code changes.
In-Reply-To: <FS1543@bugs.openwrt.org>
References: <FS1543@bugs.openwrt.org>
Message-ID: <mailman.8515.1526051443.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1543 - Many packages in snapshot failing on one build, ok on next but no code changes.
User who did this - Rob White (bluewavenet)

----------
A long story, so I will try to keep it short.
I noticed this after one of my custom image builds began having a problem with lighttpd after 25th April (LEDE 17.01.4)
The version in snapshot should have the fix but a line in Makefile was missed out. 
I noticed lighttpd was missing in snapshot/packages so looked at faillogs and found many errors.
However later the faillog was different and in fact seemed to change every time the build system re-ran.
I looked at other packages and found the same pattern of apparently random things happening.
The other day lighttpd re-appeared in snapshots, but later failed again (but no changes in the code).
This morning it was back again.
I tried resubmitting my previous PR and Travis failed again (with different errors yet again).
Looking at faillogs for many other packages I can see similar things going on.

I might be misunderstanding how this all works, but it seems to me to be a package will fail to build if a dependency has also failed, which seems reasonable, but this seems to be leading to the build system chasing its tail, or somehow there was a "storm of errors". 
Here is my last Travis log:
https://travis-ci.org/openwrt/packages/builds/377700000

My past experience in IT support made me imagine maintainers tearing their hair out trying to fix something causing this, hence my initial sketchy ticket details. If I am doing something wrong, or there is something wrong with the package, then I can look in depth there, but the same pattern seems to appear in the faillogs for other packages...

----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1543#comment4712


From lede-bugs at lists.infradead.org  Fri May 11 08:13:22 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 15:13:22 +0000
Subject: [FS#1543] Many packages in snapshot failing on one build, ok on next
 but no code changes.
In-Reply-To: <FS1543@bugs.openwrt.org>
References: <FS1543@bugs.openwrt.org>
Message-ID: <mailman.8516.1526051617.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1543 - Many packages in snapshot failing on one build, ok on next but no code changes.
User who did this - Rob White (bluewavenet)

----------
See also:
https://github.com/openwrt/packages/issues/6012
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1543#comment4713


From lede-bugs at lists.infradead.org  Fri May 11 08:13:36 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 15:13:36 +0000
Subject: [FS#1543] Many packages in snapshot failing on one build, ok on next
 but no code changes.
In-Reply-To: <FS1543@bugs.openwrt.org>
References: <FS1543@bugs.openwrt.org>
Message-ID: <mailman.8517.1526051630.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1543 - Many packages in snapshot failing on one build, ok on next but no code changes.
User who did this - Jo-Philipp Wich (jow-)

----------
The travis build job is totally unrelated to the snapshot mirrors though, it uses the SDK to build the package and all its dependencies locally. It does not utilize the opkg repositories at all.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1543#comment4714


From lede-bugs at lists.infradead.org  Fri May 11 08:42:04 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 15:42:04 +0000
Subject: [FS#1543] Many packages in snapshot failing on one build, ok on next
 but no code changes.
In-Reply-To: <FS1543@bugs.openwrt.org>
References: <FS1543@bugs.openwrt.org>
Message-ID: <mailman.8520.1526053338.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1543 - Many packages in snapshot failing on one build, ok on next but no code changes.
User who did this - Rob White (bluewavenet)

----------
I guessed that, but the errors seemed to be the same or similar, although both change without the code changing.
Looking at it at this moment, it does seem to have stabilised, whereas couple of days ago, some architectures had no packages at all. 
I still can't get Travis to pass my PR though. Feeling very frustrated by it all!

----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1543#comment4715


From lede-bugs at lists.infradead.org  Fri May 11 08:46:07 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 15:46:07 +0000
Subject: [FS#1543] Many packages in snapshot failing on one build, ok on next
 but no code changes.
In-Reply-To: <FS1543@bugs.openwrt.org>
References: <FS1543@bugs.openwrt.org>
Message-ID: <mailman.8521.1526053582.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1543 - Many packages in snapshot failing on one build, ok on next but no code changes.
User who did this - Jo-Philipp Wich (jow-)

----------
I can understand that... will see if I can take a deeper look at it later. Note that the travis integration is not directly administered by OpenWrt/LEDE, it is local to the Github package repository. The toplevel travis scripts in the repo should probably get adjusted to actually show the compile logs (or to build the package with V=s in the first place).
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1543#comment4716


From lede-bugs at lists.infradead.org  Fri May 11 08:59:30 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 15:59:30 +0000
Subject: [FS#1533] Host configuration of phase2.builds.lede-project.org is
 broken via IPv6 HTTPS
In-Reply-To: <FS1533@bugs.openwrt.org>
References: <FS1533@bugs.openwrt.org>
Message-ID: <mailman.8524.1526054378.2282.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#1533 - Host configuration of phase2.builds.lede-project.org is broken via IPv6 HTTPS
User who did this - Jo-Philipp Wich (jow-)

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


From lede-bugs at lists.infradead.org  Fri May 11 08:59:24 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 15:59:24 +0000
Subject: [FS#1533] Host configuration of phase2.builds.lede-project.org is
 broken via IPv6 HTTPS
In-Reply-To: <FS1533@bugs.openwrt.org>
References: <FS1533@bugs.openwrt.org>
Message-ID: <mailman.8525.1526054378.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1533 - Host configuration of phase2.builds.lede-project.org is broken via IPv6 HTTPS
User who did this - Jo-Philipp Wich (jow-)

----------
Fixed, the issue was caused by a missing listen [::]:443 ssl; directive for the phase2 vhost caused this.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1533#comment4717


From lede-bugs at lists.infradead.org  Fri May 11 09:40:56 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 16:40:56 +0000
Subject: [FS#1543] Many packages in snapshot failing on one build, ok on next
 but no code changes.
In-Reply-To: <FS1543@bugs.openwrt.org>
References: <FS1543@bugs.openwrt.org>
Message-ID: <mailman.8550.1526056882.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1543 - Many packages in snapshot failing on one build, ok on next but no code changes.
User who did this - Rob White (bluewavenet)

----------
Much appreciated, along with all your other efforts!
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1543#comment4718


From lede-bugs at lists.infradead.org  Fri May 11 09:51:21 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 16:51:21 +0000
Subject: [FS#1543] Many packages in snapshot failing on one build, ok on next
 but no code changes.
In-Reply-To: <FS1543@bugs.openwrt.org>
References: <FS1543@bugs.openwrt.org>
Message-ID: <mailman.8551.1526057495.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1543 - Many packages in snapshot failing on one build, ok on next but no code changes.
User who did this - Rob White (bluewavenet)

----------
The 25th of April seems to be a common date.
The version of lighttpd in lede 17.01.4 jumped from 1.4.45-3 (working with SSL) to 1.4.28-1 (broken for SSL) on that date.

I thought package version jumps did not push into the stable release but stayed only available in snapshots, or have I got that wrong?
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1543#comment4719


From lede-bugs at lists.infradead.org  Fri May 11 10:02:32 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 17:02:32 +0000
Subject: [FS#1533] Host configuration of phase2.builds.lede-project.org is
 broken via IPv6 HTTPS
In-Reply-To: <FS1533@bugs.openwrt.org>
References: <FS1533@bugs.openwrt.org>
Message-ID: <mailman.8554.1526058166.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1533 - Host configuration of phase2.builds.lede-project.org is broken via IPv6 HTTPS
User who did this - Carl-Daniel Hailfinger (hailfinger)

----------
Thank you!
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1533#comment4720


From lede-bugs at lists.infradead.org  Fri May 11 12:26:26 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 11 May 2018 19:26:26 +0000
Subject: [FS#1544] High load on Ubiquiti Nanostation XM - maybe related to
 "workingset_refault" (vmstat)
In-Reply-To: <FS1544@bugs.openwrt.org>
References: <FS1544@bugs.openwrt.org>
Message-ID: <mailman.8595.1526066814.2282.lede-bugs@lists.infradead.org>

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

User who did this - Lars (sumpfralle) 

Attached to Project - OpenWrt/LEDE Project
Summary - High load on Ubiquiti Nanostation XM - maybe related to "workingset_refault" (vmstat)
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 - Our local wireless community uses a lot of Ubiquiti devices.

They all worked well with Chaos Calmer.

With LEDE 17.01 we started to see load issues with Nanostation M5 XM devices (the older Nanostation model, only 32 MB). We did not notice the issue with any other device up to now.

After a few hours of uptime the routers will start to develop persistent high load (>8) and usually "recover" only after a reboot. "wifi up/down" do not seem to affect the issue.

The problem is almost non-existing for devices using only a single ethernet port. Devices using both ethernet ports suffer greatly (problems starting usually within 24 hours). Thus I could imagine, that [[https://bugs.openwrt.org/index.php?do=details&task_id=296|issue #296]] is related (just wild guessing).

Traffic on the wireless interface seems to increase the likelyhood of the problem (maybe CPU utilization in general).

"top" and other tools do not show processes, that could cause the high load.

The only unusual metric that seems to be connected to the high-load situation seems to be "workingset_refault" (see /proc/vmstat).
See the following output:

root at AP-1-96:~# while sleep 10; do grep workingset_ /proc/vmstat; done
workingset_refault 1304983
workingset_activate 392198
workingset_nodereclaim 10330
workingset_refault 1308585
workingset_activate 393391
workingset_nodereclaim 10352
workingset_refault 1308671
workingset_activate 393412
workingset_nodereclaim 10352
workingset_refault 1310284
workingset_activate 393940
workingset_nodereclaim 10374
workingset_refault 1317360
workingset_activate 396226
workingset_nodereclaim 10454
workingset_refault 1317465
workingset_activate 396251
workingset_nodereclaim 10454
workingset_refault 1317540
workingset_activate 396292
workingset_nodereclaim 10454
workingset_refault 1324449
workingset_activate 398402
workingset_nodereclaim 10508
workingset_refault 1328418
workingset_activate 399908
workingset_nodereclaim 10536
workingset_refault 1328796
workingset_activate 400114
workingset_nodereclaim 10536
workingset_refault 1329186
workingset_activate 400213
workingset_nodereclaim 10546
workingset_refault 1333889
workingset_activate 401528
workingset_nodereclaim 10594


Above you see 13k "workingset_refault" events within 60 seconds. The "workingset_refault" value stays at zero for routers with the same kernel, that do now show this problem. Thus I could imagine, that this is related to the high load.

Now I am running out of ideas, how to research the issue. Maybe someone can give me a hint, what I could try?

Just for reference: we are also discussing this issue in the bug tracker of our local wireless community (https://dev.opennet-initiative.de/ticket/187 - only in German). But this discussion may be a bit hard to read, as we were hunting down different potential causes of the problem. But sadly each of our theories dissolved without giving a hint for the root cause.

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1544


From lede-bugs at lists.infradead.org  Sat May 12 08:08:05 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 12 May 2018 15:08:05 +0000
Subject: [FS#1542] DHCP (dnsmasq) server doesn't properly reply on requests on
 EdgeRouter Lite (LAN)
In-Reply-To: <FS1542@bugs.openwrt.org>
References: <FS1542@bugs.openwrt.org>
Message-ID: <mailman.8661.1526137702.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1542 - DHCP (dnsmasq) server doesn't properly reply on requests on EdgeRouter Lite (LAN)
User who did this - diizzyy (diizzyy)

----------
r6745 (local build), broken
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1542#comment4721


From lede-bugs at lists.infradead.org  Sat May 12 10:25:32 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 12 May 2018 17:25:32 +0000
Subject: [FS#1545] Firewall unnecessarily logging connection closes
In-Reply-To: <FS1545@bugs.openwrt.org>
References: <FS1545@bugs.openwrt.org>
Message-ID: <mailman.8662.1526145948.2282.lede-bugs@lists.infradead.org>

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

User who did this - Philip Prindeville (pprindeville) 

Attached to Project - OpenWrt/LEDE Project
Summary - Firewall unnecessarily logging connection closes
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

x86_64, generic (in this case, Supermicro SYS-5018D-FN8T)

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

OpenWrt master

 - Steps to reproduce
   
This is fairly easy.  A while back (around 1997) Sun (which then was the go-to manufacturer for Web servers) decided that a clean 2-way close of a socket (including quiet-time) was too time consuming and that in an effort to be able to cycle through the 5-tuple space more quickly (i.e. in under 250 seconds... keep in mind we were still using HTTP 1.0 back then which didn't allow connection reuse) they'd do a RESET on the connection to circumvent the clean shutdown and quiet-time.

Well, it worked, and now lots of servers tend to do a RESET on the connection.  Some still do a 2-way close...

The problem is that this confuses NAT state on firewalls, which drop the connection information as soon as they see the outbound (since it's closer it's usually seen first) RESET packet, but then they see the inbound reset and they're confused because they've already dropped the state associated with the connection.  Or else the firewall sees the outbound FIN, ACK but doesn't bother to wait for the FIN at this point before deleting NAT state, since it's the server's problem if he doesn't get it...

If they held onto it (connection state) for a couple of seconds, then it would make more sense... but it would also interfere with cycling through the 5-tuple space quickly.  So they can't.

As a result (you were wondering when I was going to get to the point, right?  I know I was...), you end up seeing a lot of these harmless but annoying messages in your logs:

May 12 10:54:09 OpenWrt3 kernel: [481026.650247] DROP(src wan): IN=eth5 OUT= SRC=17.249.44.10 DST=66.232.81.197 LEN=117 TOS=0x00 PREC=0x00 TTL=54 ID=30282 DF PROTO=TCP SPT=443 DPT=49664 WINDOW=235 RES=0x00 ACK PSH URGP=0 
May 12 10:54:09 OpenWrt3 kernel: [481026.700207] DROP(src wan): IN=eth5 OUT= SRC=17.249.44.10 DST=66.232.81.197 LEN=64 TOS=0x00 PREC=0x00 TTL=54 ID=30283 DF PROTO=TCP SPT=443 DPT=49664 WINDOW=235 RES=0x00 ACK FIN URGP=0 
May 12 10:54:09 OpenWrt3 kernel: [481026.984519] DROP(src wan): IN=eth5 OUT= SRC=17.249.44.10 DST=66.232.81.197 LEN=64 TOS=0x00 PREC=0x00 TTL=54 ID=30284 DF PROTO=TCP SPT=443 DPT=49664 WINDOW=235 RES=0x00 ACK FIN URGP=0 
May 12 10:54:10 OpenWrt3 kernel: [481027.855512] DROP(src wan): IN=eth5 OUT= SRC=17.249.44.10 DST=66.232.81.197 LEN=117 TOS=0x00 PREC=0x00 TTL=54 ID=30285 DF PROTO=TCP SPT=443 DPT=49664 WINDOW=235 RES=0x00 ACK PSH FIN URGP=0 


For UDP, there's so connection state so messages related to packets which can't get admitted will always be logged.  That's fine, and most traffic isn't UDP anyway, so that's not a problem.

But for TCP, logging incoming connection attempts or obviously wrong connection state makes sense... but do we need to log sloppy connection closes?

Can we filter out FIN packets?  I guess that would leave us unaware of stealth scans, but I can't think of a better solution... especially on boxes with limited persistent logging resources.


More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1545


From lede-bugs at lists.infradead.org  Sat May 12 12:18:31 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 12 May 2018 19:18:31 +0000
Subject: [FS#1546] Make firewall logging prefixes more consistent
In-Reply-To: <FS1546@bugs.openwrt.org>
References: <FS1546@bugs.openwrt.org>
Message-ID: <mailman.8665.1526152726.2282.lede-bugs@lists.infradead.org>

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

User who did this - Philip Prindeville (pprindeville) 

Attached to Project - OpenWrt/LEDE Project
Summary - Make firewall logging prefixes more consistent
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 - Supply the following if possible:
 - Device problem occurs on

x86_64, generic

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

OpenWrt HEAD

 - Steps to reproduce
   
When MSS fix-up is enabled, such changes are logged with the following --log-prefix:

    snprintf(buf, sizeof(buf) - 1, "MSSFIX(%s): ", zone->name);

However, the zone prefixes don't include the colon/space at the end.

Attaching a patch to make this more consistent.

 

One or more files have been attached.

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1546


From lede-bugs at lists.infradead.org  Sat May 12 16:49:57 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sat, 12 May 2018 23:49:57 +0000
Subject: [FS#1542] DHCP (dnsmasq) server doesn't properly reply on requests on
 EdgeRouter Lite (LAN)
In-Reply-To: <FS1542@bugs.openwrt.org>
References: <FS1542@bugs.openwrt.org>
Message-ID: <mailman.8676.1526169014.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1542 - DHCP (dnsmasq) server doesn't properly reply on requests on EdgeRouter Lite (LAN)
User who did this - diizzyy (diizzyy)

----------
r6443 (local build), broken
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1542#comment4722


From lede-bugs at lists.infradead.org  Sun May 13 00:26:00 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 07:26:00 +0000
Subject: [FS#1542] DHCP (dnsmasq) server doesn't properly reply on requests on
 EdgeRouter Lite (LAN)
In-Reply-To: <FS1542@bugs.openwrt.org>
References: <FS1542@bugs.openwrt.org>
Message-ID: <mailman.8687.1526196505.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1542 - DHCP (dnsmasq) server doesn't properly reply on requests on EdgeRouter Lite (LAN)
User who did this - diizzyy (diizzyy)

----------
r6018 (local build), broken
r6017 (local build), broken
LEDE 17.01.1 (release build), works
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1542#comment4723


From lede-bugs at lists.infradead.org  Sun May 13 01:05:07 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 08:05:07 +0000
Subject: [FS#1476] make toolchain breaks at binutils
In-Reply-To: <FS1476@bugs.openwrt.org>
References: <FS1476@bugs.openwrt.org>
Message-ID: <mailman.8688.1526198723.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1476 - make toolchain breaks at binutils
User who did this - diizzyy (diizzyy)

----------
Looks like a broken git clone and/or very old trunk seeing as it uses GCC 5.5.0
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1476#comment4724


From lede-bugs at lists.infradead.org  Sun May 13 01:06:37 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 08:06:37 +0000
Subject: [FS#1464] Perl built with gcc > v5 segfaults on apm821xx
In-Reply-To: <FS1464@bugs.openwrt.org>
References: <FS1464@bugs.openwrt.org>
Message-ID: <mailman.8689.1526198813.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1464 - Perl built with gcc > v5 segfaults on apm821xx
User who did this - diizzyy (diizzyy)

----------
Still an issue, perhaps ping Philip on Github (where this should have been reported on in the first place as it's in the package repo)?
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1464#comment4725


From lede-bugs at lists.infradead.org  Sun May 13 01:07:23 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 08:07:23 +0000
Subject: [FS#1362] kernel hangs unexpectedly on mt7621
In-Reply-To: <FS1362@bugs.openwrt.org>
References: <FS1362@bugs.openwrt.org>
Message-ID: <mailman.8690.1526198858.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1362 - kernel hangs unexpectedly on mt7621
User who did this - diizzyy (diizzyy)

----------
Still an issue on master/trunk?
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1362#comment4726


From lede-bugs at lists.infradead.org  Sun May 13 01:10:56 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 08:10:56 +0000
Subject: [FS#1347] Asus WL500GP V2 reboots when you`re trying to send file
In-Reply-To: <FS1347@bugs.openwrt.org>
References: <FS1347@bugs.openwrt.org>
Message-ID: <mailman.8691.1526199070.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1347 - Asus WL500GP V2 reboots when you`re trying to send file
User who did this - diizzyy (diizzyy)

----------
I honestly think it's the router showing its age, I used to have quite a few of these and they would easily reboot due to overload (too slow SoC) and/or OOM however that was years back and software today is even less "optimized" for this kind of platform(s).
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1347#comment4727


From lede-bugs at lists.infradead.org  Sun May 13 01:12:46 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 08:12:46 +0000
Subject: [FS#1305] Not working UAS driver for usb hdd case ORICO 2599US3-V1
In-Reply-To: <FS1305@bugs.openwrt.org>
References: <FS1305@bugs.openwrt.org>
Message-ID: <mailman.8692.1526199179.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1305 - Not working UAS driver for usb hdd case ORICO 2599US3-V1
User who did this - diizzyy (diizzyy)

----------
This should be fixed in trunk/master, still an issue?
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1305#comment4728


From lede-bugs at lists.infradead.org  Sun May 13 01:13:14 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 08:13:14 +0000
Subject: [FS#1362] kernel hangs unexpectedly on mt7621
In-Reply-To: <FS1362@bugs.openwrt.org>
References: <FS1362@bugs.openwrt.org>
Message-ID: <mailman.8693.1526199208.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1362 - kernel hangs unexpectedly on mt7621
User who did this - easyteacher (easyteacher)

----------
I guess it should be fixed. The problem was likely to be related to the old mt76 driver.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1362#comment4729


From lede-bugs at lists.infradead.org  Sun May 13 01:30:04 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 08:30:04 +0000
Subject: [FS#1476] make toolchain breaks at binutils
In-Reply-To: <FS1476@bugs.openwrt.org>
References: <FS1476@bugs.openwrt.org>
Message-ID: <mailman.8696.1526200220.2282.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#1476 - make toolchain breaks at binutils
User who did this - Yousong Zhou (yousong)

Reason for closing: Invalid report
Additional comments about closing: Insufficient info.

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1476


From lede-bugs at lists.infradead.org  Sun May 13 01:31:58 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 08:31:58 +0000
Subject: [FS#1538] <all-packages> lose in /snapshots/packages/mipsel_24kc
In-Reply-To: <FS1538@bugs.openwrt.org>
References: <FS1538@bugs.openwrt.org>
Message-ID: <mailman.8697.1526200332.2282.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#1538 -  lose in /snapshots/packages/mipsel_24kc
User who did this - Yousong Zhou (yousong)

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


From lede-bugs at lists.infradead.org  Sun May 13 03:05:44 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 10:05:44 +0000
Subject: [FS#1539] kernel crash on wireguard with flow offload
In-Reply-To: <FS1539@bugs.openwrt.org>
References: <FS1539@bugs.openwrt.org>
Message-ID: <mailman.8700.1526205959.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1539 - kernel crash on wireguard with flow offload
User who did this - Aleksei Nosachev (nos1609)

----------
Same thing on Keenetic Omni MT7620
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1539#comment4730


From lede-bugs at lists.infradead.org  Sun May 13 06:03:27 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 13:03:27 +0000
Subject: [FS#1547] ath79/wndr3800: jffs2 errors booting image
In-Reply-To: <FS1547@bugs.openwrt.org>
References: <FS1547@bugs.openwrt.org>
Message-ID: <mailman.8706.1526216626.2282.lede-bugs@lists.infradead.org>

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

User who did this - Jo?o Chainho (joaochainho) 

Attached to Project - OpenWrt/LEDE Project
Summary - ath79/wndr3800: jffs2 errors booting image
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 - 


### SQUASHFS loading 'image/uImage' to 0x80800000
### SQUASHFS load complete: 1638400 bytes loaded to 0x80800000
## Booting image at 80800000 ...
   Image Name:   MIPS OpenWrt Linux-4.14.37
   Created:      2018-05-12  21:53:44 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1583450 Bytes =  1.5 MB
   Load Address: 80060000
   Entry Point:  80060000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
No initrd
## Transferring control to Linux (at address 80060000) ...
## Giving linux memsize in bytes, 134217728

Starting kernel ...

[    0.000000] Linux version 4.14.37 (openwrt at lab) (gcc version 7.3.0 (OpenWrt GCC 7.3.0 r6427-ed3860c)) #0 Sat May 12 21:53:44 2018
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019374 (MIPS 24Kc)
[    0.000000] MIPS: machine is Netgear WNDR3800
[    0.000000] SoC: Atheros AR7161 rev 2
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 08000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
[    0.000000] random: get_random_bytes called from start_kernel+0x8c/0x474 with crng_init=0
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=31:02 rootfstype=jffs2 init=/sbin/init mtdparts=ar7100-nor0:256k(uboot),128k(env),6144k(rootfs),64k(caldata),1024k(uImage) rootfstype=squashfs,jffs2
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 123372K/131072K available (3651K kernel code, 141K rwdata, 868K rodata, 1220K init, 212K bss, 7700K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 51
[    0.000000] CPU clock: 680.000 MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 5621354254 ns
[    0.000008] sched_clock: 32 bits at 340MHz, resolution 2ns, wraps every 6316128254ns
[    0.007798] Calibrating delay loop... 452.19 BogoMIPS (lpj=2260992)
[    0.074072] pid_max: default: 32768 minimum: 301
[    0.078876] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.085484] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.095783] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.105642] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.111794] pinctrl core: initialized pinctrl subsystem
[    0.117422] NET: Registered protocol family 16
[    0.426377] PCI host bridge /ahb/apb/pcie-controller at 180c0000 ranges:
[    0.432830]  MEM 0x0000000010000000..0x0000000016ffffff
[    0.438041]   IO 0x0000000000000000..0x0000000000000000
[    0.454372] PCI host bridge to bus 0000:00
[    0.458475] pci_bus 0000:00: root bus resource [mem 0x10000000-0x16ffffff]
[    0.465382] pci_bus 0000:00: root bus resource [io  0x0000]
[    0.470945] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
[    0.477723] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.486161] pci 0000:00:11.0: BAR 0: assigned [mem 0x10000000-0x1000ffff]
[    0.492976] pci 0000:00:12.0: BAR 0: assigned [mem 0x10010000-0x1001ffff]
[    0.500295] clocksource: Switched to clocksource MIPS
[    0.506186] NET: Registered protocol family 2
[    0.511221] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.518185] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.524585] TCP: Hash tables configured (established 1024 bind 1024)
[    0.531070] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.536901] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.543413] NET: Registered protocol family 1
[    0.550850] Crashlog allocated RAM at address 0x3f00000
[    0.556915] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[    0.567315] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.573175] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.588710] io scheduler noop registered
[    0.592681] io scheduler deadline registered (default)
[    0.598014] ar7100-usb-phy 18030000.usb-phy: phy reset is missing
[    0.604954] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[    0.611925] console [ttyS0] disabled
[    0.615537] 18020000.uart: ttyS0 at MMIO 0x18020000 (irq = 8, base_baud = 10625000) is a 16550A
[    0.624277] console [ttyS0] enabled
[    0.624277] console [ttyS0] enabled
[    0.631242] bootconsole [early0] disabled
[    0.631242] bootconsole [early0] disabled
[    0.643469] m25p80 spi0.0: mx25l12805d (16384 Kbytes)
[    0.648564] 4 fixed-partitions partitions found on MTD device spi0.0
[    0.654952] Creating 4 MTD partitions on "spi0.0":
[    0.659738] 0x000000000000-0x000000050000 : "u-boot"
[    0.665419] 0x000000050000-0x000000070000 : "u-boot-env"
[    0.671394] 0x000000070000-0x000000ff0000 : "firmware"
[    0.690082] 2 netgear-fw partitions found on MTD device firmware
[    0.696117] 0x000000070000-0x0000001f3440 : "kernel"
[    0.701721] 0x0000001f3440-0x000000ff0000 : "rootfs"
[    0.707254] mtd: device 4 (rootfs) set to be root filesystem
[    0.712984] 1 squashfs-split partitions found on MTD device rootfs
[    0.719154] 0x000000bb0000-0x000000ff0000 : "rootfs_data"
[    0.725149] 0x000000ff0000-0x000001000000 : "art"
[    0.730808] Realtek RTL8366S ethernet switch driver version 0.2.2
[    0.736945] rtl8366s rtl8366s: using GPIO pins 5 (SDA) and 7 (SCK)
[    0.743256] rtl8366s rtl8366s: RTL8366 ver. 1 chip found
[    0.796096] libphy: rtl8366s: probed
[    0.800948] libphy: Fixed MDIO Bus: probed
[    0.806470] ag71xx 19000000.eth: invalid MAC address, using random address
[    1.441879] ag71xx 19000000.eth: connected to PHY at fixed-0:00 [uid=00000000, driver=Generic PHY]
[    1.451417] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII
[    1.457726] ag71xx 1a000000.eth: invalid MAC address, using random address
[    1.802150] ag71xx 1a000000.eth: connected to PHY at rtl8366s:04 [uid=001cc960, driver=Generic PHY]
[    1.811750] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:RGMII
[    1.819791] NET: Registered protocol family 10
[    1.827830] Segment Routing with IPv6
[    1.831634] NET: Registered protocol family 17
[    1.836110] 8021q: 802.1Q VLAN Support v1.8
[    1.843723] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000: 0x3337 instead
[    1.853247] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004: 0x436a instead
[    1.862712] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008: 0x5af7 instead
[    1.872175] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c: 0x0018 instead
[    1.881639] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010: 0xbf07 instead
[    1.891104] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014: 0xbf07 instead
[    1.900568] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000018: 0x84fe instead
[    1.910023] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000001c: 0x0505 instead
[    1.919487] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000020: 0x4d49 instead
[    1.928951] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024: 0x204f instead
[    1.938411] jffs2: Further such events for this erase block will not be printed
[    1.947603] jffs2: Empty flash at 0x000000b0 ends at 0x000000b4
...
[    2.394143] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040000: 0x75f3 instead
[    2.403612] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040004: 0xc6b3 instead
[    2.413075] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040008: 0xc9a5 instead
[    2.422539] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0004000c: 0x7f22 instead
[    2.432002] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040010: 0x3134 instead
[    2.441466] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040014: 0xdee2 instead
[    2.450931] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040018: 0x5048 instead
[    2.460394] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0004001c: 0x88ff instead
[    2.469851] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040020: 0x5b05 instead
[    2.479314] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040024: 0xdd61 instead
[    2.488774] jffs2: Further such events for this erase block will not be printed
[    2.529956] jffs2: Old JFFS2 bitmask found at 0x0004f538
[    2.535265] jffs2: You cannot use older JFFS2 filesystems with newer kernels
[    2.542628] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00050000: 0x5031 instead
[    2.552094] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00050004: 0x82da instead
[    2.561556] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00050008: 0x1d48 instead
[    2.571020] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0005000c: 0x2145 instead
[    2.580480] random: fast init done
...
[   26.743675] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00b30018: 0xc4f0 instead
[   26.753154] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00b3001c: 0x214f instead
[   26.762624] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00b30020: 0xf01e instead
[   26.772085] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00b30024: 0x3f7e instead
[   26.781545] jffs2: Further such events for this erase block will not be printed
[   26.823317] jffs2_scan_eraseblock(): End of filesystem marker found at 0xb40000
[   26.830632] jffs2: Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
[   26.839051] jffs2: empty_blocks 68, bad_blocks 0, c->nr_blocks 248
[   26.845353] VFS: Cannot open root device "31:02" or unknown-block(31,2): error -5
[   26.852832] Please append a correct "root=" boot option; here are the available partitions:
[   26.861173] 1f00             320 mtdblock0 
[   26.861177]  (driver?)
[   26.867698] 1f01             128 mtdblock1 
[   26.867701]  (driver?)
[   26.874226] 1f02           15872 mtdblock2 
[   26.874229]  (driver?)
[   26.880755] 1f03            1549 mtdblock3 
[   26.880758]  (driver?)
[   26.887275] 1f04           14322 mtdblock4 
[   26.887278]  (driver?)
[   26.893804] 1f05            4352 mtdblock5 
[   26.893806]  (driver?)
[   26.900336] 1f06              64 mtdblock6 
[   26.900339]  (driver?)
[   26.906860] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
[   26.922099] Rebooting in 1 seconds..


More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1547


From lede-bugs at lists.infradead.org  Sun May 13 07:13:16 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 14:13:16 +0000
Subject: [FS#1547] ath79/wndr3800: jffs2 errors booting image
In-Reply-To: <FS1547@bugs.openwrt.org>
References: <FS1547@bugs.openwrt.org>
Message-ID: <mailman.8713.1526220938.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1547 - ath79/wndr3800: jffs2 errors booting image
User who did this - Jo?o Chainho (joaochainho)

----------
Found differences in the command line args:

**ar71xx target**

[    0.000000] Kernel command line:  board=WNDR3700 mtdparts=spi0.0:320k(u-boot)ro,128k(u-boot-env)ro,15872k(firmware),64k(art)ro console=ttyS0,115200 rootfstype=squashfs noinitrd


** ath79 target**

[    0.000000] Kernel command line: console=ttyS0,115200 root=31:02 rootfstype=jffs2 init=/sbin/init mtdparts=ar7100-nor0:256k(uboot),128k(env),6144k(rootfs),64k(caldata),1024k(uImage) rootfstype=squashfs,jffs2

----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1547#comment4731


From lede-bugs at lists.infradead.org  Sun May 13 07:55:03 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 14:55:03 +0000
Subject: [FS#1541] Invalid Kernel logspam : sit: non-ECT from <various IPs,
 Invalid IPs>
In-Reply-To: <FS1541@bugs.openwrt.org>
References: <FS1541@bugs.openwrt.org>
Message-ID: <mailman.8714.1526223319.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1541 - Invalid Kernel logspam : sit: non-ECT from 
User who did this - menno (mennozon)

----------
I ran into this as well, the workaround for me is to do 'echo N > /sys/module/sit/parameters/log_ecn_error'

My guess is that the default changed at some point but I have not yet looked further into this.

----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1541#comment4732


From lede-bugs at lists.infradead.org  Sun May 13 13:13:55 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 20:13:55 +0000
Subject: [FS#1501] DS-Lite is broken on snapshot with some models
In-Reply-To: <FS1501@bugs.openwrt.org>
References: <FS1501@bugs.openwrt.org>
Message-ID: <mailman.8737.1526242452.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1501 - DS-Lite is broken on snapshot with some models
User who did this - Hans Dedecker (dedeckeh)

----------
Thanks for providing the requested traces; unfortunately I can't find any indication to the observed problem as the iptables packet counters show the expected values while the interface status is as expected.
Would you be able to run tcpdump on eth1.2 (tcpdump -i eth1.2 -vvv)? I would like to check if we see IPv6 packets containing the ping request on the wan device.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1501#comment4733


From lede-bugs at lists.infradead.org  Sun May 13 14:13:21 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Sun, 13 May 2018 21:13:21 +0000
Subject: [FS#1501] DS-Lite is broken on snapshot with some models
In-Reply-To: <FS1501@bugs.openwrt.org>
References: <FS1501@bugs.openwrt.org>
Message-ID: <mailman.8740.1526246146.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1501 - DS-Lite is broken on snapshot with some models
User who did this - Tim Biermann (TimB87)

----------
Sure, this is again with the most current snapshot, WAN unmanaged and dslite configured.
On one my clients I ran ping on 8.8.8.8.

root at OpenWrt:~# ifconfig ds-wan6_4
ds-wan6_4 Link encap:UNSPEC  HWaddr 2A-02-09-08-13-00-00-0C-00-00-00-00-00-00-00-00
          inet addr:192.0.0.2  P-t-P:192.0.0.1  Mask:255.255.255.255
          inet6 addr: fe80::943a:ecff:fe51:15b2/64 Scope:Link
          UP POINTOPOINT RUNNING NOARP  MTU:1280  Metric:1
          RX packets:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:183 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:200 (200.0 B)  TX bytes:10912 (10.6 KiB)
root at OpenWrt:~# tcpdump -i eth1.2 -vvv -w ping-t8.8.8.8.output
tcpdump: listening on eth1.2, link-type EN10MB (Ethernet), capture size 262144 bytes
^C1393 packets captured
1470 packets received by filter
0 packets dropped by kernel
root at OpenWrt:~# 

Please see the attached capture. Thanks :)
----------

One or more files have been attached.

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1501#comment4734


From lede-bugs at lists.infradead.org  Sun May 13 18:50:14 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 14 May 2018 01:50:14 +0000
Subject: [FS#1204] zedboard kernel not boot
In-Reply-To: <FS1204@bugs.openwrt.org>
References: <FS1204@bugs.openwrt.org>
Message-ID: <mailman.8749.1526262635.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1204 - zedboard kernel not boot
User who did this - Luis Araneda Mendez (luaraneda)

----------
I had the same problem and I did some modifications to fix it.

You can find my changes on the pull request [[https://github.com/openwrt/openwrt/pull/942|#942]]

Can you please test my changes on your board to validate my results?

Cheers,

Luis Araneda.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1204#comment4735


From lede-bugs at lists.infradead.org  Mon May 14 00:17:56 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 14 May 2018 07:17:56 +0000
Subject: [FS#1526] rpcd: memory leak in the current package version
In-Reply-To: <FS1526@bugs.openwrt.org>
References: <FS1526@bugs.openwrt.org>
Message-ID: <mailman.8780.1526282297.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1526 - rpcd: memory leak in the current package version
User who did this - Jo-Philipp Wich (jow-)

----------
Fixed in rpcd.git with https://git.openwrt.org/?p=project/rpcd.git;a=commitdiff;h=820621952d537c49deba470c6f61c40df93f4ba8 and the package update in https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=6aaeec666d0af4240b1d61f5654d91a53cf35a82
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1526#comment4736


From lede-bugs at lists.infradead.org  Mon May 14 00:18:01 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 14 May 2018 07:18:01 +0000
Subject: [FS#1526] rpcd: memory leak in the current package version
In-Reply-To: <FS1526@bugs.openwrt.org>
References: <FS1526@bugs.openwrt.org>
Message-ID: <mailman.8781.1526282301.2282.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#1526 - rpcd: memory leak in the current package version
User who did this - Jo-Philipp Wich (jow-)

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


From lede-bugs at lists.infradead.org  Mon May 14 07:00:18 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 14 May 2018 14:00:18 +0000
Subject: [FS#1362] kernel hangs unexpectedly on mt7621
In-Reply-To: <FS1362@bugs.openwrt.org>
References: <FS1362@bugs.openwrt.org>
Message-ID: <mailman.8940.1526306568.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1362 - kernel hangs unexpectedly on mt7621
User who did this - Victor Zhestkov (vzhestkov)

----------
The router running r6807-58f7b5b build with 8 days uptime, but the issue was not permanent and sometimes there were no hangs for at least 2 weeks and then 3-5 hangs in a day. That's why I can't really say if the issue gone. When was the new driver version implemented?
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1362#comment4737


From lede-bugs at lists.infradead.org  Mon May 14 12:23:19 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Mon, 14 May 2018 19:23:19 +0000
Subject: [FS#1541] Invalid Kernel logspam : sit: non-ECT from <various IPs,
 Invalid IPs>
In-Reply-To: <FS1541@bugs.openwrt.org>
References: <FS1541@bugs.openwrt.org>
Message-ID: <mailman.9021.1526325814.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1541 - Invalid Kernel logspam : sit: non-ECT from 
User who did this - Arjen de Korte (arjendekorte)

----------
I changed the contents '/etc/modules.d/32-sit' of from

    sit
to
    sit log_ecn_error=0

This will suppress the errors too after rebooting. It doesn't fix the underlying problem though.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1541#comment4738


From lede-bugs at lists.infradead.org  Tue May 15 06:12:54 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 15 May 2018 13:12:54 +0000
Subject: [FS#1241] firewall: Enabling logging for the WAN zone causes
 excessive "MSSFIX" log spam
In-Reply-To: <FS1241@bugs.openwrt.org>
References: <FS1241@bugs.openwrt.org>
Message-ID: <mailman.9239.1526389992.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1241 - firewall: Enabling logging for the WAN zone causes excessive "MSSFIX" log spam
User who did this - linuxonlinehelp (linuxonlinehelp)

----------
I agree, my Routers logs mssfix too.


----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1241#comment4739


From lede-bugs at lists.infradead.org  Tue May 15 11:47:19 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 15 May 2018 18:47:19 +0000
Subject: [FS#1464] Perl built with gcc > v5 segfaults on apm821xx
In-Reply-To: <FS1464@bugs.openwrt.org>
References: <FS1464@bugs.openwrt.org>
Message-ID: <mailman.9322.1526410182.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1464 - Perl built with gcc > v5 segfaults on apm821xx
User who did this - Russell Senior (russell)

----------
diizzyy, it was reported here intetionally, because it was/is not clear if this is a general build system problem for apm821xx, or a problem that is specific to the perl package.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1464#comment4740


From lede-bugs at lists.infradead.org  Tue May 15 19:44:15 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 16 May 2018 02:44:15 +0000
Subject: [FS#1541] Invalid Kernel logspam : sit: non-ECT from <various IPs,
 Invalid IPs>
In-Reply-To: <FS1541@bugs.openwrt.org>
References: <FS1541@bugs.openwrt.org>
Message-ID: <mailman.9365.1526438797.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1541 - Invalid Kernel logspam : sit: non-ECT from 
User who did this - Kufat (Kufat)

----------
I also have this issue on a recent custom build of the 17.01 branch. I have a tunnelbroker IPv6 tunnel but don't use a VPN, if that helps narrow things down.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1541#comment4741


From lede-bugs at lists.infradead.org  Wed May 16 00:08:53 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 16 May 2018 07:08:53 +0000
Subject: [FS#1483] Firewall - firewall rules with time+date don't seem to work
In-Reply-To: <FS1483@bugs.openwrt.org>
References: <FS1483@bugs.openwrt.org>
Message-ID: <mailman.9408.1526454548.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1483 - Firewall - firewall rules with time+date don't seem to work
User who did this - Jo-Philipp Wich (jow-)

----------
https://git.openwrt.org/?p=project/firewall3.git;a=commitdiff;h=0e77bf296648c5db92c269c678d27f6846de4e9f
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1483#comment4742


From lede-bugs at lists.infradead.org  Wed May 16 00:17:14 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 16 May 2018 07:17:14 +0000
Subject: [FS#1501] DS-Lite is broken on snapshot with some models
In-Reply-To: <FS1501@bugs.openwrt.org>
References: <FS1501@bugs.openwrt.org>
Message-ID: <mailman.9409.1526455048.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1501 - DS-Lite is broken on snapshot with some models
User who did this - Hans Dedecker (dedeckeh)

----------
The pcap capture shows the IPv4 ping is encapsulated as an IPv6 packet and sent on the wire.
However the remote end returns an ICMPv6 indicating an unrecognized next header type; I suspect the IPv6 destination option could be the problem.
Are you able to run the same test on a lede-17.01.4 build ? It would be interesting to see if the IPv6 destination option is included as well in the IPv6 packet containing the IPv4 ping

----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1501#comment4743


From lede-bugs at lists.infradead.org  Wed May 16 01:18:37 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 16 May 2018 08:18:37 +0000
Subject: [FS#1548] ZBT-WE1326: Wireless access points stopped working
In-Reply-To: <FS1548@bugs.openwrt.org>
References: <FS1548@bugs.openwrt.org>
Message-ID: <mailman.9420.1526458735.2282.lede-bugs@lists.infradead.org>

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

User who did this - Timur Elzhov (indexless) 

Attached to Project - OpenWrt/LEDE Project
Summary - ZBT-WE1326: Wireless access points stopped working
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: ZBT-WE1326

Software: OpenWrt SNAPSHOT r6909-ac70ac3 / LuCI Master (git-18.135.54932-47971d2)

Steps to reproduce: In LuCI navigate to Network -> Wireless and find 'Wireless is disabled or not associated' against each access point. Rolling back to the snapshot from May 14 fixes the issue.

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1548


From lede-bugs at lists.infradead.org  Wed May 16 01:43:09 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 16 May 2018 08:43:09 +0000
Subject: [FS#1549] kmod-crypto-xts is loaded but not usable
In-Reply-To: <FS1549@bugs.openwrt.org>
References: <FS1549@bugs.openwrt.org>
Message-ID: <mailman.9450.1526460229.2282.lede-bugs@lists.infradead.org>

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

User who did this - Matthias (g5577) 

Attached to Project - OpenWrt/LEDE Project
Summary - kmod-crypto-xts is loaded but not usable
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 - kmod-crypto-xts:
   xts module is loaded (appears in lsmod) but is not usable (does not appear in /proc/crypto)

device: 
  openwrt-ramips-mt7621-device-gb-pc1

versions:
   OpenWrt 18.06-SNAPSHOT r6909-dc7487885e
 
----

lsmod:

ahci                   14208  0 
authenc                 3643  0 
btrfs                1007310  0 
crc_ccitt               1067  1 ppp_async
crc32c_generic          1456  2 
cryptodev              32034  0 
ctr                     3280  0 
dax                     9026  1 dm_mod
dm_crypt               24608  0 
dm_log                  7905  2 dm_mirror,dm_region_hash
dm_mirror              12464  0 
dm_mod                 88120  3 dm_crypt,dm_mirror,dm_log
dm_region_hash          7508  1 dm_mirror
drbg                   17456  0 
gf128mul                6782  0 
gpio_button_hotplug     6512  0 
hmac                    2576  0 
ip_tables              10509  3 iptable_nat,iptable_mangle,iptable_filter
ip6_tables             10241  2 ip6table_mangle,ip6table_filter
ip6t_REJECT             1104  2 
ip6table_filter          720  1 
ip6table_mangle         1232  0 
ipt_MASQUERADE           752  1 
ipt_REJECT              1040  2 
iptable_filter           720  1 
iptable_mangle           976  0 
iptable_nat              784  1 
jitterentropy_rng       7448  0 
leds_gpio               2992  0 
libahci                18515  1 ahci
libata                147133  2 ahci,libahci
libcrc32c                695  0 
mmc_block              22374  0 
mmc_core               85661  2 mmc_block,mtk_sd
mtk_sd                 20320  0 
nf_conntrack           62792 12 nf_conntrack_ipv6,ipt_MASQUERADE,xt_state,xt_nat,xt_conntrack,xt_REDIRECT,nf_nat_masquerade_ipv4,nf_conntrack_ipv4,nf_nat_ipv4,nf_nat,nf_flow_table,nf_conntrack_rtcache
nf_conntrack_ipv4       4464 11 
nf_conntrack_ipv6       4672  5 
nf_conntrack_rtcache    2800  0 
nf_defrag_ipv4          1078  1 nf_conntrack_ipv4
nf_defrag_ipv6         13358  1 nf_conntrack_ipv6
nf_flow_table          13500  2 xt_FLOWOFFLOAD,nf_flow_table_hw
nf_flow_table_hw        2336  1 
nf_log_common           2767  2 nf_log_ipv4,nf_log_ipv6
nf_log_ipv4             3536  0 
nf_log_ipv6             4208  0 
nf_nat                 13611  4 xt_nat,nf_nat_redirect,nf_nat_masquerade_ipv4,nf_nat_ipv4
nf_nat_ipv4             3473  1 iptable_nat
nf_nat_masquerade_ipv4    1660  1 ipt_MASQUERADE
nf_nat_redirect         1531  1 xt_REDIRECT
nf_reject_ipv4          2179  1 ipt_REJECT
nf_reject_ipv6          2568  1 ip6t_REJECT
nls_base                5456  2 nls_utf8,usbcore
nls_utf8                 912  0 
ppp_async               7136  0 
ppp_generic            23138  3 pppoe,ppp_async,pppox
pppoe                   8656  0 
pppox                   1418  1 pppoe
raid6_pq               86832  1 btrfs
scsi_mod               93234  3 usb_storage,libata,sd_mod
sd_mod                 29600  0 
seqiv                   1872  0 
sha256_generic         10489  0 
slhc                    5275  1 ppp_generic
usb_common              2583  1 usbcore
usb_storage            39579  0 
usbcore               134429  5 usb_storage,xhci_mtk,xhci_plat_hcd,xhci_pci,xhci_hcd
x_tables               14159 23 ipt_REJECT,ipt_MASQUERADE,xt_time,xt_tcpudp,xt_state,xt_nat,xt_multiport,xt_mark,xt_mac,xt_limit,xt_conntrack,xt_comment,xt_TCPMSS,xt_REDIRECT,xt_LOG,xt_FLOWOFFLOAD,iptable_mangle,iptable_filter,ip_tables,ip6t_REJECT,ip6table_mangle,ip6table_filter,ip6_tables
xhci_hcd               92041  3 xhci_mtk,xhci_plat_hcd,xhci_pci
xhci_mtk                4432  0 
xhci_pci                2832  0 
xhci_plat_hcd           5584  0 
xor                     6331  1 btrfs
xt_FLOWOFFLOAD          2592  0 
xt_LOG                   848  0 
xt_REDIRECT              784  0 
xt_TCPMSS               2864  0 
xt_comment               560119 
xt_conntrack            2384 14 
xt_limit                1264 20 
xt_mac                   688  0 
xt_mark                  752  0 
xt_multiport            1360  0 
xt_nat                  1616  0 
xt_state                 784  0 
xt_tcpudp               1872  8 
xt_time                 1840  0 
xts                     5066  0 
xxhash                  8139  2 zstd_decompress,zstd_compress
zstd_compress         156106  1 btrfs
zstd_decompress        58732  1 btrfs

/proc/crypto:

  name         : sha224
driver       : sha224-generic
module       : sha256_generic
priority     : 0
refcnt       : 1
selftest     : passed
internal     : no
type         : shash
blocksize    : 64
digestsize   : 28

name         : sha256
driver       : sha256-generic
module       : sha256_generic
priority     : 0
refcnt       : 1
selftest     : passed
internal     : no
type         : shash
blocksize    : 64
digestsize   : 32

name         : jitterentropy_rng
driver       : jitterentropy_rng
module       : jitterentropy_rng
priority     : 100
refcnt       : 1
selftest     : passed
internal     : no
type         : rng
seedsize     : 0

name         : stdrng
driver       : drbg_nopr_hmac_sha256
module       : drbg
priority     : 207
refcnt       : 1
selftest     : passed
internal     : no
type         : rng
seedsize     : 0

name         : stdrng
driver       : drbg_nopr_hmac_sha512
module       : drbg
priority     : 206
refcnt       : 1
selftest     : passed
internal     : no
type         : rng
seedsize     : 0

name         : stdrng
driver       : drbg_nopr_hmac_sha384
module       : drbg
priority     : 205
refcnt       : 1
selftest     : passed
internal     : no
type         : rng
seedsize     : 0

name         : stdrng
driver       : drbg_nopr_hmac_sha1
module       : drbg
priority     : 204
refcnt       : 1
selftest     : passed
internal     : no
type         : rng
seedsize     : 0

name         : stdrng
driver       : drbg_pr_hmac_sha256
module       : drbg
priority     : 203
refcnt       : 1
selftest     : passed
internal     : no
type         : rng
seedsize     : 0

name         : stdrng
driver       : drbg_pr_hmac_sha512
module       : drbg
priority     : 202
refcnt       : 1
selftest     : passed
internal     : no
type         : rng
seedsize     : 0

name         : stdrng
driver       : drbg_pr_hmac_sha384
module       : drbg
priority     : 201
refcnt       : 1
selftest     : passed
internal     : no
type         : rng
seedsize     : 0

name         : stdrng
driver       : drbg_pr_hmac_sha1
module       : drbg
priority     : 200
refcnt       : 1
selftest     : passed
internal     : no
type         : rng
seedsize     : 0

name         : crc32c
driver       : crc32c-generic
module       : crc32c_generic
priority     : 100
refcnt       : 3
selftest     : passed
internal     : no
type         : shash
blocksize    : 1
digestsize   : 4

name         : lzo
driver       : lzo-scomp
module       : kernel
priority     : 0
refcnt       : 1
selftest     : passed
internal     : no
type         : scomp

name         : lzo
driver       : lzo-generic
module       : kernel
priority     : 0
refcnt       : 2
selftest     : passed
internal     : no
type         : compression

name         : zlib-deflate
driver       : zlib-deflate-scomp
module       : kernel
priority     : 0
refcnt       : 1
selftest     : passed
internal     : no
type         : scomp

name         : deflate
driver       : deflate-scomp
module       : kernel
priority     : 0
refcnt       : 1
selftest     : passed
internal     : no
type         : scomp

name         : deflate
driver       : deflate-generic
module       : kernel
priority     : 0
refcnt       : 2
selftest     : passed
internal     : no
type         : compression

name         : ecb(arc4)
driver       : ecb(arc4)-generic
module       : kernel
priority     : 100
refcnt       : 1
selftest     : passed
internal     : no
type         : blkcipher
blocksize    : 1
min keysize  : 1
max keysize  : 256
ivsize       : 0
geniv        : 

name         : arc4
driver       : arc4-generic
module       : kernel
priority     : 0
refcnt       : 1
selftest     : passed
internal     : no
type         : cipher
blocksize    : 1
min keysize  : 1
max keysize  : 256

name         : aes
driver       : aes-generic
module       : kernel
priority     : 100
refcnt       : 2
selftest     : passed
internal     : no
type         : cipher
blocksize    : 16
min keysize  : 16
max keysize  : 32

name         : digest_null
driver       : digest_null-generic
module       : kernel
priority     : 0
refcnt       : 1
selftest     : passed
internal     : no
type         : shash
blocksize    : 1
digestsize   : 0

name         : compress_null
driver       : compress_null-generic
module       : kernel
priority     : 0
refcnt       : 1
selftest     : passed
internal     : no
type         : compression

name         : ecb(cipher_null)
driver       : ecb-cipher_null
module       : kernel
priority     : 100
refcnt       : 1
selftest     : passed
internal     : no
type         : blkcipher
blocksize    : 1
min keysize  : 0
max keysize  : 0
ivsize       : 0
geniv        : 

name         : cipher_null
driver       : cipher_null-generic
module       : kernel
priority     : 0
refcnt       : 1
selftest     : passed
internal     : no
type         : cipher
blocksize    : 1
min keysize  : 0
max keysize  : 0
 

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1549


From lede-bugs at lists.infradead.org  Wed May 16 02:07:36 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 16 May 2018 09:07:36 +0000
Subject: [FS#1550] Unable to handle kernel paging request causes router to
 reboot
In-Reply-To: <FS1550@bugs.openwrt.org>
References: <FS1550@bugs.openwrt.org>
Message-ID: <mailman.9459.1526461804.2282.lede-bugs@lists.infradead.org>

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

User who did this - Bartosz Markocki (bartekm) 

Attached to Project - OpenWrt/LEDE Project
Summary - Unable to handle kernel paging request causes router to reboot
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 -  - Device problem occurs on
Xiaomi mi router 3G (R3G)

 - Software versions of OpenWrt/LEDE release, packages, etc.
Latest trunk (r6893-bfbdeeb) custom build

 - Steps to reproduce
Did not notice there is a pattern here.   

 - The issue
The kernel crash causes the router to reboot. Here are two traces I was able to catch

May 13 07:24:52 router kernel: [82948.434471] CPU 1 Unable to handle kernel paging request at virtual address 07407800, epc == 80136a70, ra == 8013694c
May 13 07:24:52 router kernel: [82948.445103] Oops[#1]:
May 13 07:24:52 router kernel: [82948.447387] CPU: 1 PID: 1977 Comm: kworker/u8:1 Not tainted 4.14.37 #0
May 13 07:24:52 router kernel: [82948.453909] Workqueue: writeback wb_workfn (flush-8:0)
May 13 07:24:52 router kernel: [82948.459046] task: 8ff3ddc0 task.stack: 8dd62000
May 13 07:24:52 router kernel: [82948.463565] $ 0   : 00000000 00000001 00000000 812286b0
May 13 07:24:52 router kernel: [82948.468800] $ 4   : 805aa44c 00000001 00000001 07407800
May 13 07:24:52 router kernel: [82948.474019] $ 8   : 000facb3 000facb2 00000002 00064000
May 13 07:24:52 router kernel: [82948.479248] $12   : 00000009 0004001a fffeffff 00001000
May 13 07:24:52 router kernel: [82948.484473] $16   : 8fc02c00 000001b8 01011200 8022b6f0
May 13 07:24:52 router kernel: [82948.489695] $20   : 8ebb0000 8006a664 8e56d81c 01400000
May 13 07:24:52 router kernel: [82948.494913] $24   : 81196320 00000000
May 13 07:24:52 router kernel: [82948.500133] $28   : 8dd62000 8dd63950 8fd77d40 8013694c
May 13 07:24:52 router kernel: [82948.505351] Hi    : 00000000
May 13 07:24:52 router kernel: [82948.508214] Lo    : 00840480
May 13 07:24:52 router kernel: [82948.511113] epc   : 80136a70 __kmalloc+0x1f8/0x2ec
May 13 07:24:52 router kernel: [82948.515887] ra    : 8013694c __kmalloc+0xd4/0x2ec
May 13 07:24:52 router kernel: [82948.520568] Status: 11007c03#011KERNEL EXL IE
May 13 07:24:52 router kernel: [82948.524750] Cause : 40800008 (ExcCode 02)
May 13 07:24:52 router kernel: [82948.528740] BadVA : 07407800
May 13 07:24:52 router kernel: [82948.531605] PrId  : 0001992f (MIPS 1004Kc)
May 13 07:24:52 router kernel: [82948.535679] Modules linked in: pppoe ppp_async pppox ppp_generic nf_conntrack_ipv6 mt76x2e mt7603e mt76 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 cdc_ether xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_FLOWOFFLOAD xt_DSCP xt_CLASSIFY usbnet slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack libcrc32c iptable_mangle iptable_filter ipt_ECN ip_tables crc_ccitt compat ledtrig_usbport xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport
May 13 07:24:52 router kernel: [82948.606444]  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 vfat fat nls_utf8 nls_iso8859_1 nls_cp437 usb_storage leds_gpio xhci_mtk xhci_plat_hcd xhci_pci xhci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache usbcore nls_base usb_common mii crc32c_generic
May 13 07:24:52 router kernel: [82948.655996] Process kworker/u8:1 (pid: 1977, threadinfo=8dd62000, task=8ff3ddc0, tls=00000000)
May 13 07:24:52 router kernel: [82948.664578] Stack : 01011200 00400000 8006a664 8f0c719c 00000001 00000000 8fd33300 01011200
May 13 07:24:52 router kernel: [82948.672925]         8fe74850 01011200 00000001 00400000 8006a664 8022b6f0 8fe74850 01011200
May 13 07:24:52 router kernel: [82948.681267]         01411200 8fdf9e00 01011200 01411200 8e56d800 800ecd30 8fe74850 01011200
May 13 07:24:52 router kernel: [82948.689609]         01411200 8fdf9d00 01400000 00400000 8006a664 800ecd30 00060000 00000001
May 13 07:24:52 router kernel: [82948.697952]         8dd63a48 8fe74850 00000000 8fe74850 00000001 8fe74850 00000000 8fe74878
May 13 07:24:52 router kernel: [82948.706292]         ...
May 13 07:24:52 router kernel: [82948.708733] Call Trace:
May 13 07:24:52 router kernel: [82948.711201] [] __kmalloc+0x1f8/0x2ec
May 13 07:24:52 router kernel: [82948.715643] [] alloc_request_size+0x2c/0x7c
May 13 07:24:52 router kernel: [82948.720708] [] mempool_alloc+0x6c/0x178
May 13 07:24:52 router kernel: [82948.725402] [] get_request+0x360/0x76c
May 13 07:24:52 router kernel: [82948.730005] [] blk_queue_bio+0x1cc/0x430
May 13 07:24:52 router kernel: [82948.734781] [] generic_make_request+0xd8/0x288
May 13 07:24:52 router kernel: [82948.740078] [] submit_bio+0x124/0x164
May 13 07:24:52 router kernel: [82948.744663] [] ext4_io_submit+0x50/0x64 [ext4]
May 13 07:24:52 router kernel: [82948.749989] [] ext4_mark_inode_dirty+0xeac/0x1368 [ext4]
May 13 07:24:52 router kernel: [82948.756166] Code: 32428000  8e020014  00e23821  1000002c  cc400000  1280ffbc  00000000  8e060010
May 13 07:24:52 router kernel: [82948.765910]
May 13 07:24:52 router kernel: [82948.767638] ---[ end trace e8f9893fb33e6a26 ]---

and the second case

May 15 15:52:16 router kernel: [67618.480256] CPU 0 Unable to handle kernel paging request at virtual address 07402800, epc == 80136784, ra == 800ecd30
May 15 15:52:16 router kernel: [67618.490997] Oops[#1]:
May 15 15:52:16 router kernel: [67618.493275] CPU: 0 PID: 14159 Comm: kworker/u8:1 Not tainted 4.14.37 #0
May 15 15:52:16 router kernel: [67618.499875] Workqueue: writeback wb_workfn (flush-8:0)
May 15 15:52:16 router kernel: [67618.504997] task: 8c3276c0 task.stack: 8b656000
May 15 15:52:16 router kernel: [67618.509500] $ 0   : 00000000 00000001 00000000 8121a6c0
May 15 15:52:16 router kernel: [67618.514709] $ 4   : 805aa44c 00000001 00000001 07402800
May 15 15:52:16 router kernel: [67618.519918] $ 8   : 00005ddf 00005dde 8fb9b6a0 00000120
May 15 15:52:16 router kernel: [67618.525127] $12   : 8000001f 00000010 00000124 00000001
May 15 15:52:16 router kernel: [67618.530336] $16   : 8fd4a200 01011200 800ecd30 8b0e0000
May 15 15:52:16 router kernel: [67618.535545] $20   : 00400000 8006a664 8fd4981c 80660000
May 15 15:52:16 router kernel: [67618.540754] $24   : ffffffe0 ffff0000
May 15 15:52:16 router kernel: [67618.545963] $28   : 8b656000 8b657970 8f1c2c24 800ecd30
May 15 15:52:16 router kernel: [67618.551174] Hi    : 00000000
May 15 15:52:16 router kernel: [67618.554035] Lo    : 008402f0
May 15 15:52:16 router kernel: [67618.556924] epc   : 80136784 kmem_cache_alloc+0x13c/0x230
May 15 15:52:16 router kernel: [67618.562323] ra    : 800ecd30 mempool_alloc+0x6c/0x178
May 15 15:52:16 router kernel: [67618.567345] Status: 11008403#011KERNEL EXL IE
May 15 15:52:16 router kernel: [67618.571515] Cause : 40800008 (ExcCode 02)
May 15 15:52:16 router kernel: [67618.575499] BadVA : 07402800
May 15 15:52:16 router kernel: [67618.578361] PrId  : 0001992f (MIPS 1004Kc)
May 15 15:52:16 router kernel: [67618.582431] Modules linked in: pppoe ppp_async pppox ppp_generic nf_conntrack_ipv6 mt76x2e mt7603e mt76 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 cdc_ether xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_FLOWOFFLOAD xt_DSCP xt_CLASSIFY usbnet slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack libcrc32c iptable_mangle iptable_filter ipt_ECN ip_tables crc_ccitt compat ledtrig_usbport xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport
May 15 15:52:16 router kernel: [67618.653177]  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 vfat fat nls_utf8 nls_iso8859_1 nls_cp437 usb_storage leds_gpio xhci_mtk xhci_plat_hcd xhci_pci xhci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache usbcore nls_base usb_common mii crc32c_generic
May 15 15:52:16 router kernel: [67618.702675] Process kworker/u8:1 (pid: 14159, threadinfo=8b656000, task=8c3276c0, tls=00000000)
May 15 15:52:16 router kernel: [67618.711326] Stack : 8e648b20 8f147e00 8e648b20 01011200 00000001 8022b710 00000002 01011200
May 15 15:52:16 router kernel: [67618.719658]         01411200 8fd49800 01400000 00400000 8006a664 800ecd30 00000001 01011200
May 15 15:52:16 router kernel: [67618.727990]         01411200 8fd49700 01400000 00400000 8006a664 800ecd30 8e330030 8c499000
May 15 15:52:16 router kernel: [67618.736322]         8fd9f000 8b657a2c 01400000 8fd49800 01400000 01400000 8e47fa00 8d44d8f8
May 15 15:52:16 router kernel: [67618.744655]         80660000 80225974 8fd49600 00000100 01400000 8d48d7c0 8e47fa00 8fd49600
May 15 15:52:16 router kernel: [67618.752989]         ...
May 15 15:52:16 router kernel: [67618.755425] Call Trace:
May 15 15:52:16 router kernel: [67618.757859] [] kmem_cache_alloc+0x13c/0x230
May 15 15:52:16 router kernel: [67618.762897] [] mempool_alloc+0x6c/0x178
May 15 15:52:16 router kernel: [67618.767596] [] bvec_alloc+0xdc/0x154
May 15 15:52:16 router kernel: [67618.772020] [] bio_alloc_bioset+0x158/0x250
May 15 15:52:16 router kernel: [67618.777111] [] ext4_bio_write_page+0x320/0x5c4 [ext4]
May 15 15:52:16 router kernel: [67618.783028] [] ext4_convert_inline_data+0x874/0x21a8 [ext4]
May 15 15:52:16 router kernel: [67618.789461] [] ext4_convert_inline_data+0xce0/0x21a8 [ext4]
May 15 15:52:16 router kernel: [67618.795881] Code: 32228000  8e020014  00e23821  1000002d  cc400000  1260ffbc  00000000  8e060010
May 15 15:52:16 router kernel: [67618.805607]
May 15 15:52:16 router kernel: [67618.807332] ---[ end trace 3b32ff5399a1bc64 ]---

 

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1550


From lede-bugs at lists.infradead.org  Wed May 16 10:41:40 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 16 May 2018 17:41:40 +0000
Subject: [FS#714] ARP/Broadcast does not reach other clients in the same WLAN
In-Reply-To: <FS714@bugs.openwrt.org>
References: <FS714@bugs.openwrt.org>
Message-ID: <mailman.9744.1526492646.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#714 - ARP/Broadcast does not reach other clients in the same WLAN
User who did this - wutr (wutr)

----------

Same for me on LEDE Reboot 17.01.4 on TP-Link Archer C5 v1.20

I have a 2.4GHz, 5GHz and Ethernet network and devices connected to each. When running "wifi" everything works, but after a yet-to-be-determined time the following is the case:

pinging that works:

2.4wlan -> lan
5.0wlan -> lan
5.0wlan -> 5.0wlan
2.4wlan -> 5.0wlan
lan > wlan

pinging that doesn't work:

2.4wlan > 2.4wlan
5.0wlan > 2.4wlan
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=714#comment4744


From lede-bugs at lists.infradead.org  Wed May 16 11:44:33 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 16 May 2018 18:44:33 +0000
Subject: [FS#1501] DS-Lite is broken on snapshot with some models
In-Reply-To: <FS1501@bugs.openwrt.org>
References: <FS1501@bugs.openwrt.org>
Message-ID: <mailman.9790.1526496290.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1501 - DS-Lite is broken on snapshot with some models
User who did this - Tim Biermann (TimB87)

----------
Hey Hans,

please see the attached pcap capture, as well as some commands on console & Process/Kernel logs.
I was using your modified dslite.sh version on 17.01.4 for this. Hope this helps!

Best regards,
Tim 
----------

One or more files have been attached.

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1501#comment4745


From lede-bugs at lists.infradead.org  Wed May 16 19:41:34 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 17 May 2018 02:41:34 +0000
Subject: [FS#1551] HW flow offload on MT7621 stop functioning with Commit
 a3096b4b33dcc5fcc07b229346ef337aa5962019
In-Reply-To: <FS1551@bugs.openwrt.org>
References: <FS1551@bugs.openwrt.org>
Message-ID: <mailman.9842.1526525039.2282.lede-bugs@lists.infradead.org>

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

User who did this - mcaptur (mcaptur) 

Attached to Project - OpenWrt/LEDE Project
Summary - HW flow offload on MT7621 stop functioning with Commit a3096b4b33dcc5fcc07b229346ef337aa5962019
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 -    
Tested this on xiaomi router 3g HW flow offload does not function with trunk build. As soon as i revert https://github.com/openwrt/openwrt/commit/a3096b4b33dcc5fcc07b229346ef337aa5962019.patch hw offload works fine..

see https://forum.lede-project.org/t/flow-offloading-hw-1-not-working-on-latest-trunk/14481 for more details
 

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1551


From lede-bugs at lists.infradead.org  Wed May 16 23:22:54 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 17 May 2018 06:22:54 +0000
Subject: [FS#1551] HW flow offload on MT7621 stop functioning with Commit
 a3096b4b33dcc5fcc07b229346ef337aa5962019
In-Reply-To: <FS1551@bugs.openwrt.org>
References: <FS1551@bugs.openwrt.org>
Message-ID: <mailman.9887.1526538197.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1551 - HW flow offload on MT7621 stop functioning with Commit a3096b4b33dcc5fcc07b229346ef337aa5962019
User who did this - Felix Fietkau (nbd)

----------
Fixed in r6930-e9cb1b720d
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1551#comment4746


From lede-bugs at lists.infradead.org  Wed May 16 23:22:59 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 17 May 2018 06:22:59 +0000
Subject: [FS#1551] HW flow offload on MT7621 stop functioning with Commit
 a3096b4b33dcc5fcc07b229346ef337aa5962019
In-Reply-To: <FS1551@bugs.openwrt.org>
References: <FS1551@bugs.openwrt.org>
Message-ID: <mailman.9888.1526538198.2282.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#1551 - HW flow offload on MT7621 stop functioning with Commit a3096b4b33dcc5fcc07b229346ef337aa5962019
User who did this - Felix Fietkau (nbd)

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


From lede-bugs at lists.infradead.org  Thu May 17 04:35:08 2018
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 17 May 2018 11:35:08 +0000
Subject: [FS#1363] QMI does not use correct APN
In-Reply-To: <FS1363@bugs.openwrt.org>
References: <FS1363@bugs.openwrt.org>
Message-ID: <mailman.9969.1526557055.2282.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#1363 - QMI does not use correct APN
User who did this - dchard (dchard)

----------
Ok, I tested this patch in an outage situation, and I can confirm the modem is not connecting back to the network when this patch is apllied, so this is not a solution.

The trick is that the modem attaches, so if you ping the modem IP from external sources, you will get a reply, but on the router there is no internet and UQMI also repsonds with "Out of call". The annoying part is in this case the wwan interface is still up.

It fixes the APN issue (partially), but creates another (bigger) issue.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1363#comment4747


