From lede-bugs at lists.infradead.org  Tue Jun 21 06:16:15 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Tue, 21 Jun 2016 13:16:15 +0000
Subject: [#20] Testing lede-bugs@lists.infradead.org - Task opened
In-Reply-To: <FS20@bugs.lede-project.org>
References: <FS20@bugs.lede-project.org>
Message-ID: <mailman.41972.1466515243.1639.lede-bugs@lists.infradead.org>

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

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

User who did this - Jo-Philipp Wich (jow-) 

Attached to Project - LEDE Project
Summary - Testing lede-bugs at lists.infradead.org
Task Type - Bug Report
Category - Base system
Status - New
Assigned To - 
Operating System - All
Severity - Low
Priority - Medium
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Test, please ignore.

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

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.


From lede-bugs at lists.infradead.org  Tue Jun 21 06:16:27 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Tue, 21 Jun 2016 13:16:27 +0000
Subject: [#20] Testing lede-bugs@lists.infradead.org - Comment added
In-Reply-To: <FS20@bugs.lede-project.org>
References: <FS20@bugs.lede-project.org>
Message-ID: <mailman.41973.1466515247.1639.lede-bugs@lists.infradead.org>

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#20 - Testing lede-bugs at lists.infradead.org
User who did this - Jo-Philipp Wich (jow-)

----------
Comment #1
----------

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

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.


From lede-bugs at lists.infradead.org  Tue Jun 21 06:21:16 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Tue, 21 Jun 2016 13:21:16 +0000
Subject: [#20] Testing lede-bugs@lists.infradead.org - Comment added
In-Reply-To: <FS20@bugs.lede-project.org>
References: <FS20@bugs.lede-project.org>
Message-ID: <mailman.41974.1466515301.1639.lede-bugs@lists.infradead.org>

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#20 - Testing lede-bugs at lists.infradead.org
User who did this - Jo-Philipp Wich (jow-)

----------
Closing.
----------

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

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.


From lede-bugs at lists.infradead.org  Tue Jun 21 06:21:35 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Tue, 21 Jun 2016 13:21:35 +0000
Subject: [#20] Testing lede-bugs@lists.infradead.org - Task closed
In-Reply-To: <FS20@bugs.lede-project.org>
References: <FS20@bugs.lede-project.org>
Message-ID: <mailman.41975.1466515320.1639.lede-bugs@lists.infradead.org>

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task is now closed:

FS#20 - Testing lede-bugs at lists.infradead.org
User who did this - Jo-Philipp Wich (jow-)

Reason for closing: Works for me
Additional comments about closing: Messages seem to arrive now.

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

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.


From lede-bugs at lists.infradead.org  Tue Jun 21 06:48:19 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Tue, 21 Jun 2016 13:48:19 +0000
Subject: [#21] Save log to file option - Task opened
In-Reply-To: <FS21@bugs.lede-project.org>
References: <FS21@bugs.lede-project.org>
Message-ID: <mailman.41980.1466516925.1639.lede-bugs@lists.infradead.org>

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

User who did this - Ansuel (Ansuel) 

Attached to Project - LEDE Project
Summary - Save log to file option
Task Type - Feature Request
Category - Luci
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Is it possible to add an option in the luci system to save the log to a file in a specific location 

I think it's not that hard to create a script that kill the log daemon and renable it to save the log in a specific position and it would be usefull if the router reboot randomly so you can underestand what happen when it shout down for no reason

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


From lede-bugs at lists.infradead.org  Tue Jun 21 07:09:50 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Tue, 21 Jun 2016 14:09:50 +0000
Subject: [#14] MQMaker WiTi's Tx Power cannot be increased. - Comment added
In-Reply-To: <FS14@bugs.lede-project.org>
References: <FS14@bugs.lede-project.org>
Message-ID: <mailman.41981.1466518218.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#14 - MQMaker WiTi's Tx Power cannot be increased.
User who did this - Jo-Philipp Wich (jow-)

----------
Noise floor reporting is not supported by the driver and the 14dBm limit are enforced by the drivers EEPROM, please raise an issue at https://github.com/openwrt/mt76/issues if you think you should be able to achieve higher values.

The reported default of 30dBm in no way relates to the hardware capability, its is just the displayed theoretical limit.
----------

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


From lede-bugs at lists.infradead.org  Tue Jun 21 07:13:19 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Tue, 21 Jun 2016 14:13:19 +0000
Subject: [#14] MQMaker WiTi's Tx Power cannot be increased. - Task closed
In-Reply-To: <FS14@bugs.lede-project.org>
References: <FS14@bugs.lede-project.org>
Message-ID: <mailman.41982.1466518423.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#14 - MQMaker WiTi's Tx Power cannot be increased.
User who did this - Jo-Philipp Wich (jow-)

Reason for closing: Different project
Additional comments about closing: Closing this as the problem is not LEDE specific, if at all it is a problem with the mt76 driver but I highly doubt that there is any problem at all. 14dBm sounds reasonable for 11AC / 5GHz

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


From lede-bugs at lists.infradead.org  Tue Jun 21 12:08:05 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Tue, 21 Jun 2016 19:08:05 +0000
Subject: [#17] DNS Issues - Task closed
In-Reply-To: <FS17@bugs.lede-project.org>
References: <FS17@bugs.lede-project.org>
Message-ID: <mailman.42046.1466536110.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#17 - DNS Issues
User who did this - Ted Hess (thess)

Reason for closing: Not a bug
Additional comments about closing: [Solved] Manual config not complete

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


From lede-bugs at lists.infradead.org  Tue Jun 21 17:30:25 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Wed, 22 Jun 2016 00:30:25 +0000
Subject: [#9] Kernel panic with SQM scripts - Comment added
In-Reply-To: <FS9@bugs.lede-project.org>
References: <FS9@bugs.lede-project.org>
Message-ID: <mailman.42071.1466555450.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#9 - Kernel panic with SQM scripts
User who did this - neheb (neheb)

----------
cake is still out of tree and you need to install it separately from sqm. won't be default soon.

the difference between cake and the default SQM setup is that cake has lower CPU usage.
----------

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


From lede-bugs at lists.infradead.org  Wed Jun 22 00:22:35 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Wed, 22 Jun 2016 07:22:35 +0000
Subject: [#22] [regression] STP does not flow over WDS links - Task opened
In-Reply-To: <FS22@bugs.lede-project.org>
References: <FS22@bugs.lede-project.org>
Message-ID: <mailman.42125.1466580181.1639.lede-bugs@lists.infradead.org>

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

User who did this - plntyk (plntyk) 

Attached to Project - LEDE Project
Summary - [regression] STP does not flow over WDS links
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 - reported by a user on IRC:
3.18 is working - 4.1/4.4 is not working


 trying to upgrade a few things here, and I've discovered STP doesn't flow over my atheros wds links with the latest builds on stuff
 is this a known issue of some sort ?
 using 4addr type wds links
 i've got a few gadgets, and have been doing various tests to try understand where it is and is not flowing
 after many combinations and permutations, the conclusion is
 anything running the older 3.18 kernel based builds all seem to work fine
 but anything setting up 4addr wds link using a 4.1 or 4.4 based setup, stp doesn't flow over the 4addr client connection
 but, it does flow from a 4.x system runnign the ap side of the link, to a 3.x running the client side of the link

 ive tested this with nanostation, picostation, and unifiac units
 the unifiac is the reason I'm trying to update things, to a kernel rev that has unifiac support
 groz: you probably should file a bug at http://bugs.lede-project.org/ - since the behaviour changed between kernel versions there must be some bug .
 Title: Flyspray::LEDE Project: Tasklist (at bugs.lede-project.org)
 i've been reading up a bit, and it seems upstream broke 4addr mode at 3.9

 what ath, ath9k, 10k?

 both
 happens on my 10K units with 4.1 or 4.4
 and on my 9k units with 4.1 of 4.4
 but with 3.18 the 9k stuff works fine
 I just cant get the new 10K unit to bridge properly
 Ive built a considerable number of different configurations to try isolate and identify
 I haven't tried that config, but someone else was complaining about WDS with ath10k, seems it mostly worked for them though.
 what happens is, with the wds link in place
 each unit becomes its own root bridge
 because stp isn't flowing over the link
 so they dont honor the overall network root bridge
 you wont notice this if you aren't using stp
 my environment depeds on it, because I have a high capacity main link, and a lower capacity backup link
 between the two networks

 my environment depeds on it, because I have a high capacity main link, and a lower capacity backup link
 between the two networks
 my test case is using a pair of unifi ath10K units, which were not backported to the 3.18 revs, hence i build something newer
 my current live links are using ubiquity loco for the backup link, and fiber optic for the primary
 but if my power goes out at the midpoint (happens once in a while), then I need the network between the observatory and the house to fail onto the wifi links transparently
 dunno...I have to run, see you all laters.
 that wont work correctly without stp working correctly



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


From lede-bugs at lists.infradead.org  Wed Jun 22 01:02:24 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Wed, 22 Jun 2016 08:02:24 +0000
Subject: [#22] [regression] STP does not flow over WDS links - Task closed
In-Reply-To: <FS22@bugs.lede-project.org>
References: <FS22@bugs.lede-project.org>
Message-ID: <mailman.42144.1466582571.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#22 - [regression] STP does not flow over WDS links
User who did this - john (john)

Reason for closing: Won't fix
Additional comments about closing: please make a sane report with a summary of the conversation

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


From lede-bugs at lists.infradead.org  Wed Jun 22 01:16:10 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Wed, 22 Jun 2016 08:16:10 +0000
Subject: [#24] [regression] STP does not flow over WDS links  - Task opened
In-Reply-To: <FS24@bugs.lede-project.org>
References: <FS24@bugs.lede-project.org>
Message-ID: <mailman.42147.1466583395.1639.lede-bugs@lists.infradead.org>

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

User who did this - plntyk (plntyk) 

Attached to Project - LEDE Project
Summary - [regression] STP does not flow over WDS links 
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 - 
ath10k,ath9k with Kernel 4.1, Kernel 4.4: No STP flow over the 4addr client connection

Hardware: nanostation, picostation, unifiac
Setup: main link (network), backup link (wifi), midpoint

expected behaviour: fallback to backup link works

current behaviour: 
- fallback is not working w. 4.1 , 4.4
- fallback is working w. ath9k and 3.18
- stp flow is working w. 4.x system runnign the ap side of the link  to a 3.x running the client side of the link

reported by groz on IRC

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


From lede-bugs at lists.infradead.org  Wed Jun 22 01:30:57 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Wed, 22 Jun 2016 08:30:57 +0000
Subject: [#7] hostapd fails to start if automatic channel selection is set -
 Comment added
In-Reply-To: <FS7@bugs.lede-project.org>
References: <FS7@bugs.lede-project.org>
Message-ID: <mailman.42152.1466584282.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#7 - hostapd fails to start if automatic channel selection is set
User who did this - Kevin Darbyshire-Bryant (kdarbyshirebryant)

----------
This needs more info, like the particular radio type in use.  However I have 2 wireless interfaces (ath9k & ath10k) set to use 'auto'/acs_survey and hostapd works fine:

channel=acs_survey
ieee80211n=1
ht_coex=0
ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40]
vht_oper_chwidth=1
vht_oper_centr_freq_seg0_idx=-6
ieee80211ac=1
vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7

----------

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


From lede-bugs at lists.infradead.org  Wed Jun 22 02:10:35 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Wed, 22 Jun 2016 09:10:35 +0000
Subject: [#9] Kernel panic with SQM scripts - Comment added
In-Reply-To: <FS9@bugs.lede-project.org>
References: <FS9@bugs.lede-project.org>
Message-ID: <mailman.42163.1466586660.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#9 - Kernel panic with SQM scripts
User who did this - Ansuel (Ansuel)

----------
if it better than the default one why it's not included? 
----------

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


From lede-bugs at lists.infradead.org  Wed Jun 22 04:59:15 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Wed, 22 Jun 2016 11:59:15 +0000
Subject: [#25] Bug change emails should be less verbose - Task opened
In-Reply-To: <FS25@bugs.lede-project.org>
References: <FS25@bugs.lede-project.org>
Message-ID: <mailman.42208.1466596780.1639.lede-bugs@lists.infradead.org>

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

User who did this - Jonas Gorski (jogo) 

Attached to Project - LEDE Project
Summary - Bug change emails should be less verbose
Task Type - Feature Request
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 - Currently the subjects and contents of bug change emails are overly verbose.

The subjects always contain the type of change, which prevents e.g. Gmail from grouping them as "discussions". So I propose to shorten the subject to just "[#] ".

Likewise the contents have redundant information in them. E.g. the comment emails say:
"The following task has a new comment added:

FS#20 - Testing lede-bugs at lists.infradead.org
User who did this - Jo-Philipp Wich (jow-)"

The Task description is already in the subject, so doesn't need to be repeated, and it would be more readable if this was reduced to e.g.

"Jo-Philipp Wich (jow-) added a new comment:"

Same for the Task Opened/Closed emails.


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


From lede-bugs at lists.infradead.org  Wed Jun 22 05:01:46 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Wed, 22 Jun 2016 12:01:46 +0000
Subject: [#26] Comment formatting syntax should be documented - Task opened
In-Reply-To: <FS26@bugs.lede-project.org>
References: <FS26@bugs.lede-project.org>
Message-ID: <mailman.42209.1466596934.1639.lede-bugs@lists.infradead.org>

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

User who did this - Jonas Gorski (jogo) 

Attached to Project - LEDE Project
Summary - Comment formatting syntax should be documented
Task Type - Feature Request
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 - Currently the formatting options are not documented anywhere, and I failed to find any documentation with google. There are a few buttons to use, but they seem to be rather limited (e.g. nothing for quotations).

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


From lede-bugs at lists.infradead.org  Wed Jun 22 06:42:45 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Wed, 22 Jun 2016 13:42:45 +0000
Subject: [#24] [regression] STP does not flow over WDS links  - Comment added
In-Reply-To: <FS24@bugs.lede-project.org>
References: <FS24@bugs.lede-project.org>
Message-ID: <mailman.42242.1466602994.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#24 - [regression] STP does not flow over WDS links 
User who did this - Gerry Rozema (grozzie2)

----------
I see this got here before I got here to write it up.

The easiest way to reproduce / confirm this issue, set up a wds link using 4addr style connection with bridging on both ends, stp enabled on the bridge.  brctl showstp will show that both ends of the link are operating as independant root bridges (assuming no other bridges providing stp over a wired link).  This used to work correctly with openwrt.cc level code where stp flowed over the link and the system had a single root bridge.
----------

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


From lede-bugs at lists.infradead.org  Wed Jun 22 09:49:35 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Wed, 22 Jun 2016 18:49:35 +0200
Subject: e2fsprogs does not compile after version bump to 1.43.1
Message-ID: <mailman.42296.1466614201.1639.lede-bugs@lists.infradead.org>

Hi all,

Since commit e2d2b136b34e907e9258911537ce002b70e49133 (e2fsprogs: Bump to v1.43.1), 
e2fsprogs compilation brakes.

erros message:

make[3]: Entering directory '/Users/bluse/Desktop/Coding-Area/LEDE/package/utils/e2fsprogs'
make   -C /Users/bluse/Desktop/Coding-Area/LEDE/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util BUILDCC="gcc" CFLAGS="" CPPFLAGS="" LDFLAGS="" subst
make[4]: Entering directory '/Users/bluse/Desktop/Coding-Area/LEDE/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util'
        CC subst.c
subst.c:332:14: error: variable has incomplete type 'struct stat'
        struct stat stbuf;
                    ^
subst.c:332:9: note: forward declaration of 'struct stat'
        struct stat stbuf;
               ^
subst.c:391:8: warning: implicit declaration of function 'fstat' is invalid in C99 [-Wimplicit-function-declaration]
                        if (fstat(fd, &stbuf) == 0) {
                            ^
subst.c:437:12: warning: implicit declaration of function 'fchmod' is invalid in C99 [-Wimplicit-function-declaration]
                                (void) fchmod(ofd, 0444);
                                       ^
2 warnings and 1 error generated.
make[4]: *** [Makefile:329: subst.o] Error 1


first troubleshooting attempts:

-funcktion fstst() is defined in sys/stat.h
-if sys/stat.h is not included that means  HAVE_SYS_STAT_H is not defined
-checking the configure logfile shows this problem


relevant lines from build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1//config.log

  809 | #include <argz.h>
  810 configure:9551: result: no
  811 configure:9551: checking argz.h presence
  812 configure:9551: x86_64-openwrt-linux-musl-gcc -E -I/Users/bluse/Desktop/Coding-Area/LEDE/staging_dir/target-x86_64_musl-1.1.14/usr/include/Users/bluse/Desktop/Coding-Area/LEDE/staging_dir/target-x86_64_musl-1.1.14/include -I/Users/bluse/Desktop/Coding-Area/LEDE/staging_dir/toolchain-x86_64_gcc-5.3.0_musl-1.1.14/usr/include -I/Users/bluse/Desktop/Coding-Area/LEDE/staging_dir/toolchain-x86_64_gcc-5.3.0_musl-1.1.14/include/fortify -I/Users/bluse/Desktop/Coding-Area/LEDE/staging_dir/toolchain-x86_64_gcc-5.3.0_musl-1.1.14/include  conftest.c
  813 conftest.c:50:18: fatal error: argz.h: No such file or directory
  814 compilation terminated.
  815 configure:9551: $? = 1
  816 configure: failed program was:
  817 | /* confdefs.h */
  818 | #define PACKAGE_NAME ""
  819 | #define PACKAGE_TARNAME ""
  820 | #define PACKAGE_VERSION ""
  821 | #define PACKAGE_STRING ""
  822 | #define PACKAGE_BUGREPORT ""
  823 | #define PACKAGE_URL ""
  824 | #define STDC_HEADERS 1
  825 | #define HAVE_SYS_TYPES_H 1
  826 | #define HAVE_SYS_STAT_H 1


As I am not confident with automake, I would need some help what to do next.

Greetings from Berlin
Bluse

From lede-bugs at lists.infradead.org  Wed Jun 22 10:34:32 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Wed, 22 Jun 2016 19:34:32 +0200
Subject: e2fsprogs does not compile after version bump to 1.43.1
In-Reply-To: <mailman.42296.1466614201.1639.lede-bugs@lists.infradead.org>
References: <mailman.42296.1466614201.1639.lede-bugs@lists.infradead.org>
Message-ID: <mailman.42301.1466616904.1639.lede-bugs@lists.infradead.org>



On 22/06/2016 18:49, lede-bugs at lists.infradead.org wrote:
> Hi all,
> 
> Since commit e2d2b136b34e907e9258911537ce002b70e49133 (e2fsprogs: Bump to v1.43.1), 
> e2fsprogs compilation brakes.
> 
> erros message:
> 
> make[3]: Entering directory '/Users/bluse/Desktop/Coding-Area/LEDE/package/utils/e2fsprogs'
> make   -C /Users/bluse/Desktop/Coding-Area/LEDE/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util BUILDCC="gcc" CFLAGS="" CPPFLAGS="" LDFLAGS="" subst
> make[4]: Entering directory '/Users/bluse/Desktop/Coding-Area/LEDE/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util'
>         CC subst.c
> subst.c:332:14: error: variable has incomplete type 'struct stat'
>         struct stat stbuf;
>                     ^
> subst.c:332:9: note: forward declaration of 'struct stat'
>         struct stat stbuf;
>                ^
> subst.c:391:8: warning: implicit declaration of function 'fstat' is invalid in C99 [-Wimplicit-function-declaration]
>                         if (fstat(fd, &stbuf) == 0) {
>                             ^
> subst.c:437:12: warning: implicit declaration of function 'fchmod' is invalid in C99 [-Wimplicit-function-declaration]
>                                 (void) fchmod(ofd, 0444);
>                                        ^
> 2 warnings and 1 error generated.
> make[4]: *** [Makefile:329: subst.o] Error 1
> 
> 
> first troubleshooting attempts:
> 
> -funcktion fstst() is defined in sys/stat.h
> -if sys/stat.h is not included that means  HAVE_SYS_STAT_H is not defined
> -checking the configure logfile shows this problem
> 
> 
> relevant lines from build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1//config.log
> 
>   809 | #include <argz.h>
>   810 configure:9551: result: no
>   811 configure:9551: checking argz.h presence
>   812 configure:9551: x86_64-openwrt-linux-musl-gcc -E -I/Users/bluse/Desktop/Coding-Area/LEDE/staging_dir/target-x86_64_musl-1.1.14/usr/include/Users/bluse/Desktop/Coding-Area/LEDE/staging_dir/target-x86_64_musl-1.1.14/include -I/Users/bluse/Desktop/Coding-Area/LEDE/staging_dir/toolchain-x86_64_gcc-5.3.0_musl-1.1.14/usr/include -I/Users/bluse/Desktop/Coding-Area/LEDE/staging_dir/toolchain-x86_64_gcc-5.3.0_musl-1.1.14/include/fortify -I/Users/bluse/Desktop/Coding-Area/LEDE/staging_dir/toolchain-x86_64_gcc-5.3.0_musl-1.1.14/include  conftest.c
>   813 conftest.c:50:18: fatal error: argz.h: No such file or directory
>   814 compilation terminated.
>   815 configure:9551: $? = 1
>   816 configure: failed program was:
>   817 | /* confdefs.h */
>   818 | #define PACKAGE_NAME ""
>   819 | #define PACKAGE_TARNAME ""
>   820 | #define PACKAGE_VERSION ""
>   821 | #define PACKAGE_STRING ""
>   822 | #define PACKAGE_BUGREPORT ""
>   823 | #define PACKAGE_URL ""
>   824 | #define STDC_HEADERS 1
>   825 | #define HAVE_SYS_TYPES_H 1
>   826 | #define HAVE_SYS_STAT_H 1
> 
> 
> As I am not confident with automake, I would need some help what to do next.
> 
> Greetings from Berlin
> Bluse

maybe your tree is in some inconsistent state ? the builders managed to
build that package for all targets successfully last night.

	John



From lede-bugs at lists.infradead.org  Wed Jun 22 14:03:50 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Wed, 22 Jun 2016 21:03:50 +0000
Subject: [#24] [regression] STP does not flow over WDS links  - Comment added
In-Reply-To: <FS24@bugs.lede-project.org>
References: <FS24@bugs.lede-project.org>
Message-ID: <mailman.42328.1466629457.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#24 - [regression] STP does not flow over WDS links 
User who did this - Gerry Rozema (grozzie2)

----------
Update, I started trying to track down specifically which rev broke things for STP, and have discovered my original working build was prior to the CC release of openwrt, had kernel rev 3.18.19.  I just finished  scratch build of openwrt CC which has kernel 3.18.29, and it's broken there too.

Going to continue working backwards to find where this breakage started.


----------

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


From lede-bugs at lists.infradead.org  Thu Jun 23 02:04:50 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Thu, 23 Jun 2016 11:04:50 +0200
Subject: e2fsprogs does not compile after version bump to 1.43.1
References: <07818329-DF80-4D70-94D8-AEDEBF1AAAD2@inet.tu-berlin.de>
Message-ID: <mailman.42380.1466672718.1639.lede-bugs@lists.infradead.org>

Hi John,

I just cloned out a fresh LEDE into /tmp, selected the x86_64 target & e2fsprogs, everything else default.
The compile process brakes as well with:

make[3]: Entering directory '/private/tmp/lede-test-e2fsprogs/package/utils/e2fsprogs'
make   -C /private/tmp/lede-test-e2fsprogs/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util BUILDCC="gcc" CFLAGS="" CPPFLAGS="" LDFLAGS="" subst
make[4]: Entering directory '/private/tmp/lede-test-e2fsprogs/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util'
       CC subst.c
subst.c:332:14: error: variable has incomplete type 'struct stat'
       struct stat stbuf;
                   ^
subst.c:332:9: note: forward declaration of 'struct stat'
       struct stat stbuf;
              ^
subst.c:391:8: warning: implicit declaration of function 'fstat' is invalid in C99 [-Wimplicit-function-declaration]
                       if (fstat(fd, &stbuf) == 0) {
                           ^
subst.c:437:12: warning: implicit declaration of function 'fchmod' is invalid in C99 [-Wimplicit-function-declaration]
                               (void) fchmod(ofd, 0444);
                                      ^
2 warnings and 1 error generated.
make[4]: *** [Makefile:329: subst.o] Error 1


So if the builders were able to compile e2fsprogs without probs, maybe it is target specific ? or as I am building on my macbook with OS X, I will try today a vanilla linux machine to check that direction as well.


Greetings Thomas


> On 22 Jun 2016, at 19:34, lede-bugs at lists.infradead.org wrote:
> 
> maybe your tree is in some inconsistent state ? the builders managed to
> build that package for all targets successfully last night.
> 
> 	John
> 
> 
> _______________________________________________
> lede-bugs mailing list
> lede-bugs at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-bugs




From lede-bugs at lists.infradead.org  Thu Jun 23 02:22:45 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Thu, 23 Jun 2016 11:22:45 +0200
Subject: e2fsprogs does not compile after version bump to 1.43.1
In-Reply-To: <mailman.42380.1466672718.1639.lede-bugs@lists.infradead.org>
References: <07818329-DF80-4D70-94D8-AEDEBF1AAAD2@inet.tu-berlin.de>
 <mailman.42380.1466672718.1639.lede-bugs@lists.infradead.org>
Message-ID: <mailman.42381.1466673790.1639.lede-bugs@lists.infradead.org>



On 23/06/2016 11:04, lede-bugs at lists.infradead.org wrote:
> Hi John,
> 
> I just cloned out a fresh LEDE into /tmp, selected the x86_64 target & e2fsprogs, everything else default.
> The compile process brakes as well with:
> 
> make[3]: Entering directory '/private/tmp/lede-test-e2fsprogs/package/utils/e2fsprogs'
> make   -C /private/tmp/lede-test-e2fsprogs/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util BUILDCC="gcc" CFLAGS="" CPPFLAGS="" LDFLAGS="" subst
> make[4]: Entering directory '/private/tmp/lede-test-e2fsprogs/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util'
>        CC subst.c
> subst.c:332:14: error: variable has incomplete type 'struct stat'
>        struct stat stbuf;
>                    ^
> subst.c:332:9: note: forward declaration of 'struct stat'
>        struct stat stbuf;
>               ^
> subst.c:391:8: warning: implicit declaration of function 'fstat' is invalid in C99 [-Wimplicit-function-declaration]
>                        if (fstat(fd, &stbuf) == 0) {
>                            ^
> subst.c:437:12: warning: implicit declaration of function 'fchmod' is invalid in C99 [-Wimplicit-function-declaration]
>                                (void) fchmod(ofd, 0444);
>                                       ^
> 2 warnings and 1 error generated.
> make[4]: *** [Makefile:329: subst.o] Error 1
> 
> 
> So if the builders were able to compile e2fsprogs without probs, maybe it is target specific ? or as I am building on my macbook with OS X, I will try today a vanilla linux machine to check that direction as well.
> 
> 
> Greetings Thomas
> 
> 
>> On 22 Jun 2016, at 19:34, lede-bugs at lists.infradead.org wrote:
>>
>> maybe your tree is in some inconsistent state ? the builders managed to
>> build that package for all targets successfully last night.
>>
>> 	John

i would guess it i OSX related. felix will fix it when he returns, he
uses OSX aswell

	John


From lede-bugs at lists.infradead.org  Thu Jun 23 03:27:26 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Thu, 23 Jun 2016 10:27:26 +0000
Subject: [#9] Kernel panic with SQM scripts - Comment added
In-Reply-To: <FS9@bugs.lede-project.org>
References: <FS9@bugs.lede-project.org>
Message-ID: <mailman.42386.1466677672.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#9 - Kernel panic with SQM scripts
User who did this - moeller0 (moeller0)

----------
Dear All,

Please let me try to answer a few of the questions above:

Why is cake not the default?
Cake is not per-se "better" than htb+fq_codel and cake is still under (more or less) active development so it certainly is not yet ready for becoming the default. Simple.qos with its combination of HTB and fq_codel still is the recommended default, so unless you want to participate in active debugging and development please stick to simple.qos or simplest.qos.

Why cake is not included?
Cake just became available as an easy to install kernel module in LEDE to allow wider testing. But since it is not (yet) recommended as default it also is not installed by default (people might be unhappy if sqm-scripts would install unnecessary modules wasting their space).

Does cake use less CPU than HTB+fq_codel?
Some time last year tests with an earlier version of cake indicated that in a CPU limited situation cake might allow a higher overall shaper bandwidth than the default HTB+fq_codel combination. More recent tests are not that conclusive. Especially it was shown that HTB behaves differently from HFSC and cake in CPU limited mode: HTB will keep the added latency low, sacrificing more bandwidth (sometimes considerably more bandwidth) while the other two shaper sacrifice less bandwidth but will also increase the latency under load (or show more bufferbloat).

What about sqm-scripts-extra scripts?
The sqm-scripts extra scripts are really just for wider testing, please do not relay on them being available for longer times/.

[OT] SQM-scripts-exts: What is the difference between the _LAN_ and _WAN_ variants?
Cake promises much better isolation of internal host IPs versus each other than the other qdiscs. But to be able to implement per-internal-host-IP fairness cake needs to see the internal IPs, in the typical home situation sqm gets instantiated on the WAN interface that typically also performs NAT for IPv4. Cake will only be able to see one internal address if instantiated there, making per-internal-IP isolation degrade into the default per-flw isolation. To allow to test whether cake's two relevant isolation options (triple and dual) actually work in the real world the _LAN_ scripts are prepared to be instantiated on internal LAN interfaces of a home router, since on the LAN ports the internal IPs are still visible. Please note that typically the bridged WLAN interfaces will not be covered by the shaping, making the LAN variant scripts not generally recommended solutions, but pure testing devices. The ideal test would be to hook upp another switch/dumbAP behind the shaped LAN port and try to mix traffic from different host and see if for example heavy bit-torrenting still badly affects the connections of other internal hosts. If anybody actually tests this, please report any results as issues under https://github.com/tohojo/sqm-scripts thanks in advance
[/OT]
Best Regards
        M.

----------

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


From lede-bugs at lists.infradead.org  Thu Jun 23 05:58:59 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Thu, 23 Jun 2016 12:58:59 +0000
Subject: [#9] Kernel panic with SQM scripts - Comment added
In-Reply-To: <FS9@bugs.lede-project.org>
References: <FS9@bugs.lede-project.org>
Message-ID: <mailman.42416.1466686764.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#9 - Kernel panic with SQM scripts
User who did this - Ansuel (Ansuel)

----------
thx for the explanation. Currently i'm using the triple wan script with cake 
My connetion is a pppoe with atm overhead so is it wrong how i set the sqm settings? 

And you did'nt explain the wan variants. It's the same?
----------

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


From lede-bugs at lists.infradead.org  Thu Jun 23 06:24:21 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Thu, 23 Jun 2016 15:24:21 +0200
Subject: [#9] Kernel panic with SQM scripts - Comment added
In-Reply-To: <mailman.42416.1466686764.1639.lede-bugs@lists.infradead.org>
References: <FS9@bugs.lede-project.org>
 <mailman.42416.1466686764.1639.lede-bugs@lists.infradead.org>
Message-ID: <mailman.42417.1466688288.1639.lede-bugs@lists.infradead.org>

Hi Ansuel,

> On Jun 23, 2016, at 14:58 , lede-bugs at lists.infradead.org wrote:
> 
> The following task has a new comment added:
> 
> FS#9 - Kernel panic with SQM scripts
> User who did this - Ansuel (Ansuel)
> 
> ----------
> thx for the explanation. Currently i?m using the triple wan script with cake 

	Unless you have no NAT or are using mostly IPv6, I predict that this does not work any different from piece_of_cake.qos from the standard sqm-scripts (it might actually consume more CPU while doing the same flow isolation)

> My connetion is a pppoe with atm overhead so is it wrong how i set the sqm settings?

	Hard to say, if you would like to share your /etc/config/sqm I might be able to tell you more, but I am unsure whether this here is the right venue?

> 
> And you did'nt explain the wan variants. It?s the same?

	Okay, I guess I need to go into the details here. The main difference between sqm on WAN and sqm on LAN is related to the fact that the bandwidth directions in the GUI are always from the view of the device sqm is running on (your router). 
	So for the typical WAN situation the download direction for SQM and for internal hosts are aligned, and so are the upload directions. But if you instantiate sqm on a LAN interface the upload from the LAN interface or its egress direction now points into your LAN, so the GUI?s upload field now actually controls the download direction as seen from your hosts. The same apparent directionality flip also holds true for the other direction. 
	The _LAN_ scripts handle that for you by flipping the bandwidth internally so the GUI keeps reflecting the view from end-hosts to the internet. That in itself is not too complicated and could easily be explained to advanced users as yourself (I believe the help texts of the extra scripts should mention something to that regard). But for the dual isolation modes in cake we have a similar flip in the directions, and that gets quite tedious to explain. Triple-isolate is un-directional in that it attempts to do the right thing independent of direction. But triple-isolate is also not fully tested so we need the dual isolation options to sanity check triple-isolate mode
	The dual-dsthost and dual-srchost options however are directional and need to be set correctly, otherwise you might end up with per-external-host-IP fairness instead of the typically expected/requested per-internal-host-IP fairness. For sqm on WAN you want dual-dsthost on ingress and dual-srchost on egress, but for sqm on LAN you want dual-srchost for ingress (since that corresponds to the internal address) and dual-dsthost on egress. 
	And as I did not aim to troubleshoot each and every tester ?by hand? (as that has a scalability issue) I opted for creating separate LAN and WAN variants? But please note for most users the LAN versions will not be good solutions since they most likely will either not shape WLAN at all, or worse will apply the shaper to both traffic from LAN to WAN and LAN to WLAN, so talking to a WLAN host will eat upo your internet speed. Have I mentioned that the sqm-scripts-extra package is only for wider testing purposes yet? If not let me repeat they are not for production, but rather to help experimenting to find the best settings to inplement in the sqm-scripts bread-and-butter scripts?
	
Best Regards
        M.

> ----------
> 
> More information can be found at the following URL:
> https://bugs.lede-project.org/index.php?do=details&task_id=9#comment54
> 
> _______________________________________________
> lede-bugs mailing list
> lede-bugs at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-bugs



From lede-bugs at lists.infradead.org  Thu Jun 23 07:45:30 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Thu, 23 Jun 2016 14:45:30 +0000
Subject: [#26] Comment formatting syntax should be documented - Comment added
In-Reply-To: <FS26@bugs.lede-project.org>
References: <FS26@bugs.lede-project.org>
Message-ID: <mailman.42430.1466693156.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#26 - Comment formatting syntax should be documented
User who did this - Ted Hess (thess)

----------
FS currently supports DokuWiki markup
https://www.dokuwiki.org/wiki:syntax#formatting_syntax

Quoting (for example) is done with %%> or >>, etc.%% prefixes\\
> Currently the formatting options are not documented anywhere, and I failed to find any documentation with google. There are a few buttons to use, but they seem to be rather limited (e.g. nothing for quotations).


----------

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


From lede-bugs at lists.infradead.org  Thu Jun 23 07:50:06 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Thu, 23 Jun 2016 14:50:06 +0000
Subject: [#26] Comment formatting syntax should be documented - Task changed
In-Reply-To: <FS26@bugs.lede-project.org>
References: <FS26@bugs.lede-project.org>
Message-ID: <mailman.42431.1466693432.1639.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#26 - Comment formatting syntax should be documented
User who did this: Ted Hess (thess)
Category: Website -> Other
Status: Unconfirmed -> Researching

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


From lede-bugs at lists.infradead.org  Thu Jun 23 08:23:10 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Thu, 23 Jun 2016 15:23:10 +0000
Subject: [FS#25] Bug change emails should be less verbose - Task changed
In-Reply-To: <FS25@bugs.lede-project.org>
References: <FS25@bugs.lede-project.org>
Message-ID: <mailman.42436.1466695416.1639.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#25 - Bug change emails should be less verbose
User who did this: Ted Hess (thess)
Category: Website -> Other
Status: Unconfirmed -> Researching

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


From lede-bugs at lists.infradead.org  Thu Jun 23 08:24:20 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Thu, 23 Jun 2016 15:24:20 +0000
Subject: [FS#25] Bug change emails should be less verbose - User took ownership
In-Reply-To: <FS25@bugs.lede-project.org>
References: <FS25@bugs.lede-project.org>
Message-ID: <mailman.42437.1466695484.1639.lede-bugs@lists.infradead.org>

Ted Hess has taken ownership of the following task:

FS#25 - Bug change emails should be less verbose

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


From lede-bugs at lists.infradead.org  Thu Jun 23 10:39:52 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Thu, 23 Jun 2016 19:39:52 +0200
Subject: e2fsprogs does not compile after version bump to 1.43.1
References: <0B7C0A15-DAF9-4201-90A5-46B168E8C4FA@gmx.net>
Message-ID: <mailman.42469.1466703629.1639.lede-bugs@lists.infradead.org>

Hi all,

e2fsprogs does built when using a vanilla Linux machine? so it seems to be an OS X issue.

The compile log under Linux shows in the comparable section (where the build under OS X fails) the following warning:

config.status: creating po/Makefile
rm -f /home/leecher/Desktop/lede-test-e2fsprogs/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/.configured_*
touch /home/leecher/Desktop/lede-test-e2fsprogs/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/.configured_yyy
make   -C /home/leecher/Desktop/lede-test-e2fsprogs/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util BUILDCC="gcc" CFLAGS="" CPPFLAGS="" LDFLAGS="" subst
make[3]: Entering directory '/home/leecher/Desktop/lede-test-e2fsprogs/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util'
        CREATE dirpaths.h
        CC subst.c
subst.c: In function 'main':
subst.c:391:8: warning: implicit declaration of function 'fstat' [-Wimplicit-function-declaration]
    if (fstat(fd, &stbuf) == 0) {
        ^~~~~
subst.c:437:12: warning: implicit declaration of function 'fchmod' [-Wimplicit-function-declaration]
     (void) fchmod(ofd, 0444);
            ^~~~~~
        LD subst
make[3]: Leaving directory ?/home/leecher/Desktop/lede-test-e2fsprogs/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util'


The compile log in OS X shows while braking:

config.status: creating po/Makefile
rm -f /Users/bluse/Desktop/Coding-Area/LEDE/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/.configured_*
touch /Users/bluse/Desktop/Coding-Area/LEDE/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/.configured_yyynynynynyyn
make   -C /Users/bluse/Desktop/Coding-Area/LEDE/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util BUILDCC="gcc" CFLAGS="" CPPFLAGS="" LDFLAGS="" subst
make[3]: Entering directory '/Users/bluse/Desktop/Coding-Area/LEDE/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util'
        CREATE dirpaths.h
        CC subst.c
subst.c:332:14: error: variable has incomplete type 'struct stat'
        struct stat stbuf;
                    ^
subst.c:332:9: note: forward declaration of 'struct stat'
        struct stat stbuf;
               ^
subst.c:391:8: warning: implicit declaration of function 'fstat' is invalid in C99 [-Wimplicit-function-declaration]
                        if (fstat(fd, &stbuf) == 0) {
                            ^
subst.c:437:12: warning: implicit declaration of function 'fchmod' is invalid in C99 [-Wimplicit-function-declaration]
                                (void) fchmod(ofd, 0444);
                                       ^
2 warnings and 1 error generated.
make[3]: *** [Makefile:329: subst.o] Error 1


current workaround:

manually edit subst.c in the build dir to enforce the include of header file ?sys/stats.h"

vim build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util/subst.c

	// #ifdef HAVE_SYS_STAT_H 26 
	#include <sys/stat.h> 27 
	// #endif

Greetings from Berlin
Bluse

> 
> i would guess it i OSX related. felix will fix it when he returns, he
> uses OSX aswell
> 
> 	John
> 
> _______________________________________________
> lede-bugs mailing list
> lede-bugs at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-bugs




From lede-bugs at lists.infradead.org  Thu Jun 23 11:59:40 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Thu, 23 Jun 2016 18:59:40 +0000
Subject: [FS#2] Enable email and jabber notifications - Comment added
In-Reply-To: <FS2@bugs.lede-project.org>
References: <FS2@bugs.lede-project.org>
Message-ID: <mailman.42495.1466708407.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#2 - Enable email and jabber notifications
User who did this - Bluse-Blue (Bluse)

----------
Hi all,

I can confirm the symptoms of the disapearing AP functionality after a couple of hours as you've discribed on my router as well.

Hardware: TP-Link TL-WR1043N/ND v3
Lede version: r580
wireless config: ap mode (details given under [1])

Symptoms: after a couple of hours proper AP functionality, the ssid of the same router disapears, new clients are not able to connect to this AP

Troubleshooting:

  * issuing the command wifi does not bring back the AP

  * creating am monitor device with iw phy phy0 add interface mon0 type monitor leads to the error output: command failed: Too many open files in system (-23), after increasing the max_files by issuing echo 32768 > /proc/sys/fs/file-max the monitor device creation with iw works, but after bringing up mon0 by ifconfig mon0 up the mon0 inferface does not show any increase in packet count (it stays at 0) nor any output via tcpdump -nei mon0

  * output of dmesg shows some potential problem user.notice : Command failed: Not found, but I have not yet investigated if a wifi config is triggering this, maybe someone sees an issue under [1]


  * a second wifi router on the same channel with an monitor interface does not receive any beacons from the TPLink 1043

educated guess:

  * beacons seem to get stuck after some hours in AP mode and are not been sent out anymore

workaround:

  * hard reboot

[1] cat /etc/config/wireless


config wifi-device 'radio0'
        option type 'mac80211'
        option channel '6'
        option hwmode '11g'
        option path 'platform/qca955x_wmac'
        option htmode 'HT20'
        option txpower '18'
        option distance '1500'
        option country 'HT'
        option frag '2346'
        option rts '2346'
        option basic_rate '6000 12000 24000'
        option disabled '0'

config wifi-iface
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'test_lede'
        option encryption 'psk2'
        option key 'test123456789'
        option mcast_rate '6000'
        option disassoc_low_ack '1'
        option skip_inactivity_poll '0'



Greetings from Berlin
Bluse
----------

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


From lede-bugs at lists.infradead.org  Thu Jun 23 12:00:38 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Thu, 23 Jun 2016 19:00:38 +0000
Subject: [FS#13] Ath9k AP stays up for connected clients but doesn't show in
 scan on new ones - Comment added
In-Reply-To: <FS13@bugs.lede-project.org>
References: <FS13@bugs.lede-project.org>
Message-ID: <mailman.42496.1466708463.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#13 - Ath9k AP stays up for connected clients but doesn't show in scan on new ones
User who did this - Bluse-Blue (Bluse)

----------
Hi all,

I can confirm the symptoms of the disapearing AP functionality after a couple of hours as you've discribed on my router as well.

Hardware: TP-Link TL-WR1043N/ND v3
Lede version: r580
wireless config: ap mode (details given under [1])

Symptoms: after a couple of hours proper AP functionality, the ssid of the same router disapears, new clients are not able to connect to this AP

Troubleshooting:

  * issuing the command wifi does not bring back the AP

  * creating am monitor device with iw phy phy0 add interface mon0 type monitor leads to the error output: command failed: Too many open files in system (-23), after increasing the max_files by issuing echo 32768 > /proc/sys/fs/file-max the monitor device creation with iw works, but after bringing up mon0 by ifconfig mon0 up the mon0 inferface does not show any increase in packet count (it stays at 0) nor any output via tcpdump -nei mon0

  * output of dmesg shows some potential problem user.notice : Command failed: Not found, but I have not yet investigated if a wifi config is triggering this, maybe someone sees an issue under [1]


  * a second wifi router on the same channel with an monitor interface does not receive any beacons from the TPLink 1043

educated guess:

  * beacons seem to get stuck after some hours in AP mode and are not been sent out anymore

workaround:

  * hard reboot

[1] cat /etc/config/wireless


config wifi-device 'radio0'
        option type 'mac80211'
        option channel '6'
        option hwmode '11g'
        option path 'platform/qca955x_wmac'
        option htmode 'HT20'
        option txpower '18'
        option distance '1500'
        option country 'HT'
        option frag '2346'
        option rts '2346'
        option basic_rate '6000 12000 24000'
        option disabled '0'

config wifi-iface
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'test_lede'
        option encryption 'psk2'
        option key 'test123456789'
        option mcast_rate '6000'
        option disassoc_low_ack '1'
        option skip_inactivity_poll '0'



Greetings from Berlin
Bluse
----------

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


From lede-bugs at lists.infradead.org  Fri Jun 24 04:34:23 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Fri, 24 Jun 2016 11:34:23 +0000
Subject: [FS#27] BT Home Hub 5 Type A - Switch problem when enabling WAN port
 - Comment added
In-Reply-To: <FS27@bugs.lede-project.org>
References: <FS27@bugs.lede-project.org>
Message-ID: <mailman.42598.1466768087.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#27 - BT Home Hub 5 Type A - Switch problem when enabling WAN port
User who did this - Jo-Philipp Wich (jow-)

----------
Please try to re-acquire DHCP on your client after the device fully booted and see if it works then.
----------

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


From lede-bugs at lists.infradead.org  Fri Jun 24 04:43:17 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Fri, 24 Jun 2016 11:43:17 +0000
Subject: [FS#28] Upnp lot's of 404 error - Task opened
In-Reply-To: <FS28@bugs.lede-project.org>
References: <FS28@bugs.lede-project.org>
Message-ID: <mailman.42601.1466768623.1639.lede-bugs@lists.infradead.org>

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

User who did this - Ansuel (Ansuel) 

Attached to Project - LEDE Project
Summary - Upnp lot's of 404 error
Task Type - Bug Report
Category - Packages
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Fri Jun 24 13:21:23 2016 daemon.notice miniupnpd[26156]: / not found, responding ERROR 404
Fri Jun 24 13:21:23 2016 daemon.notice miniupnpd[26156]: /HNAP1/ not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/a2/out.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/ajaxmail not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/arr/index.shtml not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/at3/out.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/atc/out.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/atx/out.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/auth not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/bbs/postlist.pl not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/bbs/postshow.pl not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/bp_revision.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/br5.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/click.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/clicks.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/crtr/out.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/fg.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/findweather/getForecast not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/findweather/hdfForecast not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/frame_html not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/getattach not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/hotspotlogin.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/hslogin.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/ib/301_start.pl not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/index.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/index not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/krcgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/krcgistart not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/link not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/login.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/login not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/logout not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/logout not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/mainmenu.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/mainsrch not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/msglist not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/navega not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/openwebmail/openwebmail-main.pl not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/out.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/passremind not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/rbaccess/rbcgi3m01 not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/rbaccess/rbunxcgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/readmsg not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/rshop.pl not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/search.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/spcnweb not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/sse.dll not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/start not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/te/o.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/tjcgi1 not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/top/out not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/traffic/process.fcgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/verify.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/webproc not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/webscr not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/wingame.pl not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /das/cgi-bin/session.cgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /fcgi-bin/dispatch.fcgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /fcgi-bin/performance.fcgi not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /redir/cgi-bin/ajaxmail not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: / not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /cgi-bin/webproc?getpage=/../../etc/passwd&var:language=en_us&var:page=* not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /etc/passwd not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /etc/passwd not found, responding ERROR 404
Fri Jun 24 13:21:38 2016 daemon.notice miniupnpd[26156]: /rom-0 not found, responding ERROR 404



what could cause this problem? 

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


From lede-bugs at lists.infradead.org  Fri Jun 24 04:50:39 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Fri, 24 Jun 2016 11:50:39 +0000
Subject: [FS#28] Upnp lot's of 404 error - Comment added
In-Reply-To: <FS28@bugs.lede-project.org>
References: <FS28@bugs.lede-project.org>
Message-ID: <mailman.42602.1466769063.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#28 - Upnp lot's of 404 error
User who did this - Jo-Philipp Wich (jow-)

----------
This is most likely caused by https://blog.avast.com/2014/11/04/avast-2015-new-feature-home-network-security-scanning/ - see also https://forum.pfsense.org/index.php?action=profile;area=showposts;sa=messages;u=285861 http://nazarenolatella.myblog.it/tag/malware/ and https://forum.pfsense.org/index.php?topic=111140.0

A machine in your lan runs Avast with the "Home security" feature enabled which is executing exploit tests against your internal network.
----------

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


From lede-bugs at lists.infradead.org  Fri Jun 24 04:50:50 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Fri, 24 Jun 2016 11:50:50 +0000
Subject: [FS#28] Upnp lot's of 404 error - Task closed
In-Reply-To: <FS28@bugs.lede-project.org>
References: <FS28@bugs.lede-project.org>
Message-ID: <mailman.42603.1466769073.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#28 - Upnp lot's of 404 error
User who did this - Jo-Philipp Wich (jow-)

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


From lede-bugs at lists.infradead.org  Fri Jun 24 05:02:43 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Fri, 24 Jun 2016 12:02:43 +0000
Subject: [FS#27] BT Home Hub 5 Type A - Switch problem when enabling WAN port
 - Comment added
In-Reply-To: <FS27@bugs.lede-project.org>
References: <FS27@bugs.lede-project.org>
Message-ID: <mailman.42606.1466769787.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#27 - BT Home Hub 5 Type A - Switch problem when enabling WAN port
User who did this - Bill L. (bill888)

----------
I'm afraid forcing PC to release and re-acquire DHCP IP address does not resolve issue.

I have also configured a static IP address and DNS setting on client PC.  Here are ping results shortly after the Hub has been switched on:


C:\Users\admin>ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=8ms TTL=53
Reply from 8.8.8.8: bytes=32 time=9ms TTL=53
Reply from 8.8.8.8: bytes=32 time=8ms TTL=53
Reply from 8.8.8.8: bytes=32 time=8ms TTL=53
Reply from 8.8.8.8: bytes=32 time=8ms TTL=53
Reply from 8.8.8.8: bytes=32 time=8ms TTL=53
Reply from 8.8.8.8: bytes=32 time=8ms TTL=53
Reply from 8.8.8.8: bytes=32 time=8ms TTL=53
Reply from 8.8.8.8: bytes=32 time=8ms TTL=53
Reply from 8.8.8.8: bytes=32 time=3616ms TTL=53
Reply from 8.8.8.8: bytes=32 time=1517ms TTL=53
Reply from 8.8.8.8: bytes=32 time=641ms TTL=53
Request timed out.
Reply from 8.8.8.8: bytes=32 time=1114ms TTL=53

Ping statistics for 8.8.8.8:
    Packets: Sent = 14, Received = 13, Lost = 1 (7% loss),
Approximate round trip times in milli-seconds:
    Minimum = 8ms, Maximum = 3616ms, Average = 535ms
Control-C
^C
C:\Users\admin>ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.


When the above pings fail from client PC connected to LAN port of Hub, I am still seeing these 'eth0: tx ring full' messages on serial console:

[   95.372341] eth1: transmit timed out, disable the dma channel irq
[   95.381099] eth1: tx ring full
[   95.381134] eth0: tx ring full
[  105.953032] eth1: transmit timed out, disable the dma channel irq
[  105.957949] eth1: tx ring full
[  124.961063] eth0: transmit timed out, disable the dma channel irq
[  124.965868] eth0: tx ring full
[  162.758301] eth0: tx ring full
[  162.823880] eth1: tx ring full
[  164.023015] eth1: tx ring full
[  166.845388] eth0: port 4 lost link
[  166.849247] br-lan: port 1(eth0.1) entered disabled state
[  169.845683] eth1: port 5 lost link


As another test, I have just installed r48886 image from OpenWRT BT Home Hub 5 Type A wiki to a second Hub.  Using the same  network configuration file changes, internet through WAN port (DHCP client mode) works perfectly.







----------

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


From lede-bugs at lists.infradead.org  Fri Jun 24 07:35:09 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Fri, 24 Jun 2016 14:35:09 +0000
Subject: [FS#27] BT Home Hub 5 Type A - Switch problem when enabling WAN port
 - Comment added
In-Reply-To: <FS27@bugs.lede-project.org>
References: <FS27@bugs.lede-project.org>
Message-ID: <mailman.42625.1466778934.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#27 - BT Home Hub 5 Type A - Switch problem when enabling WAN port
User who did this - Bill L. (bill888)

----------
Further to my earlier posts, I have gone back and tried some other sysupgrade tar files.

openwrt r49377 is OK.
LEDE r508 is OK.
LEDE r619 has same issue as witnessed with R742.

I can only conclude something is 'broken' after r508 and before r619.
----------

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


From lede-bugs at lists.infradead.org  Fri Jun 24 15:39:14 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Fri, 24 Jun 2016 22:39:14 +0000
Subject: [FS#29] WiTi - laptop cannot connect when configured to use 80MHz -
 Task opened
In-Reply-To: <FS29@bugs.lede-project.org>
References: <FS29@bugs.lede-project.org>
Message-ID: <mailman.42686.1466807979.1639.lede-bugs@lists.infradead.org>

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

User who did this - neheb (neheb) 

Attached to Project - LEDE Project
Summary - WiTi - laptop cannot connect when configured to use 80MHz
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 have a laptop with an atheros card(ath9k, 802.11n). If I leave the WiTi to its defaults of 80MHz - channel 36, I become unable to connect. Changing the channel width to 40MHz fixes the issue. The ac setting does not matter. I think another person mentioned VHT being broken?

Interestingly enough, my phone(Nexus 5X) has no problem with it. Probably because it's an ac device.

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


From lede-bugs at lists.infradead.org  Fri Jun 24 15:41:49 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Fri, 24 Jun 2016 22:41:49 +0000
Subject: [FS#29] WiTi - laptop cannot connect when configured to use 80MHz -
 Comment added
In-Reply-To: <FS29@bugs.lede-project.org>
References: <FS29@bugs.lede-project.org>
Message-ID: <mailman.42687.1466808133.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#29 - WiTi - laptop cannot connect when configured to use 80MHz
User who did this - neheb (neheb)

----------
I forgot to mention, this is on kernel 4.4 on the laptop(Ubuntu 16.04). No idea if a newer kernel fixes some issue on my laptop's side.

Oh another thing. I read journalctl and apparently, it succeeds in connecting to the AP(4 way handshake i guess?) but it fails upon trying to get a DHCP address. No idea if that helps.
----------

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


From lede-bugs at lists.infradead.org  Fri Jun 24 21:58:45 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Sat, 25 Jun 2016 04:58:45 +0000
Subject: [FS#30] x86: SDK: host-compile of grub2 build error - Task opened
In-Reply-To: <FS30@bugs.lede-project.org>
References: <FS30@bugs.lede-project.org>
Message-ID: <mailman.42701.1466830750.1639.lede-bugs@lists.infradead.org>

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

User who did this - Daniel Dickinson (dfc-d) 

Attached to Project - LEDE Project
Summary - x86: SDK: host-compile of grub2 build error
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 - When using the SDK on x86_64 and building grub (e.g. for squashfs images), the host-compile phase ends with the following error:

/home/user/Build/openwrt/sdk/lede-sdk--x86-64_gcc-5.3.0_glibc-2.22.Linux-x86_64/staging_dir/host/lib/liblzma.a: error adding symbols: Archive has no index; run ranlib to add one

manually running ranlib from host on liblzma allows the build to succeed.

>From the logs it appears ranlib is never run on liblzma by the grub2 build process.

ranlib is run by tools/xz compile but this doesn't seem to carry over to the SDK staging dir.

Perhaps this is a relocation issue? i.e. does ranlib need to be re-run in the SDK because the path has changed?

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


From lede-bugs at lists.infradead.org  Sat Jun 25 02:49:22 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Sat, 25 Jun 2016 09:49:22 +0000
Subject: [FS#27] BT Home Hub 5 Type A - Switch problem when enabling WAN port
 - Comment added
In-Reply-To: <FS27@bugs.lede-project.org>
References: <FS27@bugs.lede-project.org>
Message-ID: <mailman.42708.1466848188.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#27 - BT Home Hub 5 Type A - Switch problem when enabling WAN port
User who did this - Bill L. (bill888)

----------

Commit cc3bfdb "lantiq: enable SMP for XRX200" 

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

is responsible for the TX ring full WAN port issue.  I am advised the ticket needs to be assigned to 'nbd' for attention.


Tnx to mkrenis for providing test images, to help narrow down and identify the problematic commit.


----------

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


From lede-bugs at lists.infradead.org  Sat Jun 25 07:11:01 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Sat, 25 Jun 2016 14:11:01 +0000
Subject: [FS#31] firewall3 fails to reload iptables policy extension - Task
 opened
In-Reply-To: <FS31@bugs.lede-project.org>
References: <FS31@bugs.lede-project.org>
Message-ID: <mailman.42719.1466863886.1639.lede-bugs@lists.infradead.org>

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

User who did this - Mirko Parthey (mpa) 

Attached to Project - LEDE Project
Summary - firewall3 fails to reload iptables policy extension
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 - * Source revision:
LEDE Reboot (HEAD, r607)

* Affected device:
Tested on TP-LINK TD-W8980 and on a x86 VM. This issue is likely device-independent.

* Issue description:
In firewall3, the iptables extension libxt_policy.so only works for the first (address family; table) combination and fails for all subsequent ones.  Where it fails, the firewall rules containing the policy match are missing, and a warning is printed instead.  
This is a regression from OpenWrt CHAOS CALMER (15.05.1).

* Steps to reproduce:

###download and install firmware image lede-lantiq-xrx200-TDW8980-squashfs-sysupgrade.bin
# fw3 -d restart
Result: firewall rules as expected

# opkg install iptables-mod-ipsec
# uci set "firewall. at zone[0].extra_src=-m policy --dir in --pol none"
# uci set "firewall. at zone[0].extra_dest=-m policy --dir out --pol none"
# fw3 -d restart
Results:
- firewall rules with "-m policy" are missing in all tables except IPv4 filter.
- repeated output: Warning: fw3_ipt_rule_append(): Can't find match 'policy'

* What you have already done to fix the problem / Any additional info you think is important

My experiments seem to confirm that this is caused by missing dlclose support in musl libc.
firewall3 uses dlclose/dlopen to reload iptables extensions for each address family and table,
and it expects the extensions' constructor functions to be called each time.
In musl, dlclose does nothing, and unloading/reloading of a shared library does not call its constructor function again.
To check my theory, I added explicit calls to the extensions' _init() functions via dlsym.
This made the policy match work again in all tables, but then firewall3 hangs on exit (tested with LEDE r289).
I don't now if it is actually allowed to call dynamic library constructor functions explicitly.

Then I considered a more complex solution, but have no code for it yet.
In short:
- split off xtables/iptc-related functions from iptables.c to run in a child process
- an RPC-like mechanism based on pipes, to call these functions
- terminate and recreate the child process at each fw3_ipt_close/fw3_ipt_open

However, I would like to hear your opinion first how this bug should best be solved.
If you want to work on this yourself, I'll step back and watch.

Regards
Mirko


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


From lede-bugs at lists.infradead.org  Sat Jun 25 09:25:33 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Sat, 25 Jun 2016 16:25:33 +0000
Subject: [FS#32] WNDR4300 - image (firmware) not build (r792) - Task opened
 (Attachment added)
In-Reply-To: <FS32@bugs.lede-project.org>
References: <FS32@bugs.lede-project.org>
Message-ID: <mailman.42722.1466871959.1639.lede-bugs@lists.infradead.org>

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

User who did this - build000 (build000) 

Attached to Project - LEDE Project
Summary - WNDR4300 - image (firmware) not build (r792)
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 - 
# make -j8
(...)
make[2] package/install
 make[3] -C package/system/opkg host-install
 make[3] package/preconfig
 make[2] target/install
 make[3] -C target/linux install
 make[6] -C target/linux/ar71xx/image legacy-images-prepare
 make[6] -C target/linux/ar71xx/image legacy-images
make -r world: build failed. Please re-run make with -j1 V=s to see what's going on
/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/include/toplevel.mk:193: polecenia dla obiektu 'world' nie powiod?y si?
make: *** [world] B??d 1

# make -j1 V=s
(...)
Makefile:102: recipe for target 'image_prepare' failed
make[5]: [image_prepare] Error 1 (ignored)
export MAKEFLAGS= ;make -w legacy-images-prepare
make[6]: Entering directory '/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/target/linux/ar71xx/image'
make[6]: Nothing to be done for 'legacy-images-prepare'.
make[6]: Leaving directory '/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/target/linux/ar71xx/image'
# Use symbolic permissions to avoid clobbering SUID/SGID/sticky bits
find /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/root-ar71xx -type f -not -perm /0100 -not -name 'ssh_host*' -not -name 'shadow' -print0 | xargs -r -0 chmod u+rw,g+r,o+r
find /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/root-ar71xx -type f -perm /0100 -print0 | xargs -r -0 chmod u+rwx,g+rx,o+rx
find /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/root-ar71xx -type d -print0 | xargs -r -0 chmod u+rwx,g+rx,o+rx
install -d -m0755 /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/root-ar71xx/tmp /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/root-ar71xx/overlay
chmod 1777 /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/root-ar71xx/tmp
cp /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/vmlinux.elf /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/bin/targets/ar71xx/nand/lede-ar71xx-nand-vmlinux.elf
cp /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/vmlinux /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/bin/targets/ar71xx/nand/lede-ar71xx-nand-vmlinux.bin
dd if=/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/vmlinux.bin.lzma of=/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/bin/targets/ar71xx/nand/lede-ar71xx-nand-vmlinux.lzma bs=65536 conv=sync
21+1 records in
22+0 records out
1441792 bytes (1.4 MB, 1.4 MiB) copied, 0.00384363 s, 375 MB/s
dd if=/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/vmlinux.bin.gz of=/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/bin/targets/ar71xx/nand/lede-ar71xx-nand-vmlinux.gz bs=65536 conv=sync
30+1 records in
31+0 records out
2031616 bytes (2.0 MB, 1.9 MiB) copied, 0.00490435 s, 414 MB/s
mkimage -A mips -O linux -T kernel -a 0x80060000 -C gzip  -e 0x80060000 -n 'MIPS OpenWrt Linux-4.4.13' -d /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/vmlinux.bin.gz /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/bin/targets/ar71xx/nand/lede-ar71xx-nand-uImage-gzip.bin
Image Name:   MIPS OpenWrt Linux-4.4.13
Created:      Fri Jun 24 13:59:36 2016
Image Type:   MIPS Linux Kernel Image (gzip compressed)
Data Size:    2027658 Bytes = 1980.13 kB = 1.93 MB
Load Address: 80060000
Entry Point:  80060000
mkimage -A mips -O linux -T kernel -a 0x80060000 -C lzma  -e 0x80060000 -n 'MIPS OpenWrt Linux-4.4.13' -d /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/vmlinux.bin.lzma /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/bin/targets/ar71xx/nand/lede-ar71xx-nand-uImage-lzma.bin
Image Name:   MIPS OpenWrt Linux-4.4.13
Created:      Fri Jun 24 13:59:36 2016
Image Type:   MIPS Linux Kernel Image (lzma compressed)
Data Size:    1431437 Bytes = 1397.89 kB = 1.37 MB
Load Address: 80060000
Entry Point:  80060000
cp /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/loader-generic.elf /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/bin/targets/ar71xx/nand/lede-ar71xx-nand-vmlinux-lzma.elf
mkdir -p /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/tmp
/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/staging_dir/host/bin/mksquashfs4 /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/root-ar71xx /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/root.squashfs -nopad -noappend -root-owned -comp xz -Xpreset 9 -Xe -Xlc 0 -Xlp 2 -Xpb 2  -b 256k -p '/dev d 755 0 0' -p '/dev/console c 600 0 0 5 1' -processors 1 -fixed-time 1466776776
Parallel mksquashfs: Using 1 processor
Creating 4.0 filesystem on /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/root.squashfs, block size 262144.
Pseudo file "/dev" exists in source filesystem "/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/root-ar71xx/dev".
Ignoring, exclude it (-e/-ef) to override.
[=========================================================================================================================\] 2201/2201 100%
Exportable Squashfs 4.0 filesystem, xz compressed, data block size 262144
	compressed data, compressed metadata, compressed fragments, no xattrs
	duplicates are removed
Filesystem size 10172.50 Kbytes (9.93 Mbytes)
	33.21% of uncompressed filesystem size (30633.02 Kbytes)
Inode table size 21596 bytes (21.09 Kbytes)
	22.61% of uncompressed inode table size (95502 bytes)
Directory table size 27596 bytes (26.95 Kbytes)
	45.46% of uncompressed directory table size (60698 bytes)
Number of duplicate files found 90
Number of inodes 2772
Number of files 2160
Number of fragments 64
Number of symbolic links  460
Number of device nodes 1
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 151
Number of ids (unique uids + gids) 1
Number of uids 1
	root (0)
Number of gids 1
	root (0)
tar -cp --numeric-owner --owner=0 --group=0 --sort=name --mtime="@1466776776" -C /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/root-ar71xx/ . | gzip -9n > /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/bin/targets/ar71xx/nand/lede-ar71xx-nand-device-wndr4300-rootfs.tar.gz
export MAKEFLAGS= ;make -w legacy-images
make[6]: Entering directory '/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/target/linux/ar71xx/image'
cp /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/vmlinux /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/tmp/vmlinux-wndr3700v4
/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/staging_dir/host/bin/patch-cmdline /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/tmp/vmlinux-wndr3700v4 "board=WNDR3700_V4 console=ttyS0,115200 mtdparts=ar934x-nfc:256k(u-boot)ro,256k(u-boot-env)ro,256k(caldata),512k(pot),2048k(language),512k(config),3072k(traffic_meter),2048k(kernel),23552k(ubi),25600k at 0x6c0000(firmware),256k(caldata_backup),-(reserved)"
search space used is default of 16KB
/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/staging_dir/host/bin/lzma e /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/tmp/vmlinux-wndr3700v4 -lc1 -lp2 -pb2 -d20 /home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/tmp/vmlinux-wndr3700v4.bin.lzma

LZMA 4.65 : Igor Pavlov : Public domain : 2009-02-03
dd if=/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/tmp/vmlinux-wndr3700v4.bin.lzma of=/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/tmp/vmlinux-wndr3700v4.bin.tmp bs=$$((2097152-131072-2*64-1)) count=1 conv=sync
bash: -c: line 0: syntax error near unexpected token `('
bash: -c: line 0: `dd if=/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/tmp/vmlinux-wndr3700v4.bin.lzma of=/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/build_dir/target-mips_34kc_musl-1.1.14/linux-ar71xx_nand/tmp/vmlinux-wndr3700v4.bin.tmp bs=$$((2097152-131072-2*64-1)) count=1 conv=sync'
Makefile:102: recipe for target 'legacy-image-WNDR4300' failed
make[6]: *** [legacy-image-WNDR4300] Error 1
make[6]: Leaving directory '/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/target/linux/ar71xx/image'
Makefile:102: recipe for target 'legacy-images-make' failed
make[5]: *** [legacy-images-make] Error 2
make[5]: Leaving directory '/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/target/linux/ar71xx/image'
Makefile:24: recipe for target 'install' failed
make[4]: *** [install] Error 2
make[4]: Leaving directory '/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/target/linux/ar71xx'
Makefile:13: recipe for target 'install' failed
make[3]: *** [install] Error 2
make[3]: Leaving directory '/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/target/linux'
target/Makefile:21: recipe for target 'target/linux/install' failed
make[2]: *** [target/linux/install] Error 2
make[2]: Leaving directory '/home/slawekj/Pulpit/Projects/LEDE-WNDR4300'
target/Makefile:17: recipe for target '/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/staging_dir/target-mips_34kc_musl-1.1.14/stamp/.target_install' failed
make[1]: *** [/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/staging_dir/target-mips_34kc_musl-1.1.14/stamp/.target_install] Error 2
make[1]: Leaving directory '/home/slawekj/Pulpit/Projects/LEDE-WNDR4300'
/home/slawekj/Pulpit/Projects/LEDE-WNDR4300/include/toplevel.mk:193: polecenia dla obiektu 'world' nie powiod?y si?
make: *** [world] B??d 2


One or more files have been attached.

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


From lede-bugs at lists.infradead.org  Sat Jun 25 09:36:29 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Sat, 25 Jun 2016 16:36:29 +0000
Subject: [FS#32] WNDR4300 - image (firmware) not build (r792) - Task closed
In-Reply-To: <FS32@bugs.lede-project.org>
References: <FS32@bugs.lede-project.org>
Message-ID: <mailman.42725.1466872614.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#32 - WNDR4300 - image (firmware) not build (r792)
User who did this - john (john)

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


From lede-bugs at lists.infradead.org  Sun Jun 26 10:52:10 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Sun, 26 Jun 2016 17:52:10 +0000
Subject: [FS#33] openvpn-polarssl crashes - Task opened
In-Reply-To: <FS33@bugs.lede-project.org>
References: <FS33@bugs.lede-project.org>
Message-ID: <mailman.42781.1466963556.1639.lede-bugs@lists.infradead.org>

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

User who did this - Daniel Golle (dangowrt) 

Attached to Project - LEDE Project
Summary - openvpn-polarssl crashes
Task Type - Bug Report
Category - Base system
Status - New
Assigned To - 
Operating System - All
Severity - Low
Priority - Medium
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - 
[  902.550000] do_page_fault(): sending SIGSEGV to openvpn for invalid read access from 00000000
[  902.560000] epc = 778f2410 in libc.so[77880000+91000]
[  902.570000] ra  = 004299e9 in openvpn[400000+3e000]


OpenVPN config:

client
persist-key
ca /etc/luci-uploads/cbid.openvpn.xxx.ca
cert /etc/luci-uploads/cbid.openvpn.xxx.cert
comp-lzo yes
dev tap
dh dh1024.pem
key /etc/luci-uploads/cbid.openvpn.xxx.key
port 3022
remote xxx.yy
remote-cert-tls server
reneg-sec 0


The same configuration works well with openvpn-openssl

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


From lede-bugs at lists.infradead.org  Sun Jun 26 23:05:37 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Mon, 27 Jun 2016 06:05:37 +0000
Subject: [FS#8] ARV7518PW kernel panic after any network activity - Comment
 added
In-Reply-To: <FS8@bugs.lede-project.org>
References: <FS8@bugs.lede-project.org>
Message-ID: <mailman.42816.1467007561.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#8 - ARV7518PW kernel panic after any network activity
User who did this - john (john)

----------
i have managed to reproduce this and my assumption is that the bootloader is not correctly setting up the memory causing this problem. i dont think i will be able to fix this issue in a timely manner. the bootloader situation on this device is just too bad to be able to test stuff. i will keep the ticket open for a few more weeks to see if anyone else tries to fix it.
----------

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


From lede-bugs at lists.infradead.org  Sun Jun 26 23:06:08 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Mon, 27 Jun 2016 06:06:08 +0000
Subject: [FS#29] WiTi - laptop cannot connect when configured to use 80MHz -
 Task changed
In-Reply-To: <FS29@bugs.lede-project.org>
References: <FS29@bugs.lede-project.org>
Message-ID: <mailman.42817.1467007596.1639.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#29 - WiTi - laptop cannot connect when configured to use 80MHz
User who did this: john (john)
Assigned To: [-] -> Felix Fietkau

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


From lede-bugs at lists.infradead.org  Sun Jun 26 23:06:37 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Mon, 27 Jun 2016 06:06:37 +0000
Subject: [FS#23] Sitecom WL-351 Switch driver problem - No network
 connectivity to router - User took ownership
In-Reply-To: <FS23@bugs.lede-project.org>
References: <FS23@bugs.lede-project.org>
Message-ID: <mailman.42818.1467007622.1639.lede-bugs@lists.infradead.org>

john has taken ownership of the following task:

FS#23 - Sitecom WL-351 Switch driver problem - No network connectivity to router

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


From lede-bugs at lists.infradead.org  Sun Jun 26 23:46:07 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Mon, 27 Jun 2016 06:46:07 +0000
Subject: [FS#21] Save log to file option - User took ownership
In-Reply-To: <FS21@bugs.lede-project.org>
References: <FS21@bugs.lede-project.org>
Message-ID: <mailman.42823.1467009989.1639.lede-bugs@lists.infradead.org>

john has taken ownership of the following task:

FS#21 - Save log to file option

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


From lede-bugs at lists.infradead.org  Sun Jun 26 23:46:03 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Mon, 27 Jun 2016 06:46:03 +0000
Subject: [FS#7] hostapd fails to start if automatic channel selection is set -
 Task changed
In-Reply-To: <FS7@bugs.lede-project.org>
References: <FS7@bugs.lede-project.org>
Message-ID: <mailman.42824.1467009989.1639.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#7 - hostapd fails to start if automatic channel selection is set
User who did this: john (john)
Assigned To: [-] -> Felix Fietkau

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


From lede-bugs at lists.infradead.org  Mon Jun 27 02:40:01 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Mon, 27 Jun 2016 09:40:01 +0000
Subject: [FS#8] ARV7518PW kernel panic after any network activity - Comment
 added (Attachment added)
In-Reply-To: <FS8@bugs.lede-project.org>
References: <FS8@bugs.lede-project.org>
Message-ID: <mailman.42854.1467020426.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#8 - ARV7518PW kernel panic after any network activity
User who did this - Mohammed Berdai (medber)

----------
Hi John, First of all thanks. Yesterday I was testing the latest LEDE git revisions. I managed to buy another arv7518pw. This time I flashed this u-boot (built for arv7518pw not like the other built for arv4518pw) http://www.mediafire.com/download/4mvdn90l302nssn/U-boot.zip

Then I proceeded to flash OpenWrt 15.05.1 (latest git revisions) and LEDE and recorded both bootlogs then made a diff between the two. I attached the diff file below. Maybe it will give you a hint.


just a quick note: the old u-boot never had issues with OpenWrt CC nor BB.
----------

One or more files have been attached.

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


From lede-bugs at lists.infradead.org  Mon Jun 27 02:59:32 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Mon, 27 Jun 2016 09:59:32 +0000
Subject: [FS#8] ARV7518PW kernel panic after any network activity - Comment
 added
In-Reply-To: <FS8@bugs.lede-project.org>
References: <FS8@bugs.lede-project.org>
Message-ID: <mailman.42859.1467021596.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#8 - ARV7518PW kernel panic after any network activity
User who did this - john (john)

----------
hi, does that uboot that you linked provide functional ethernet ?
----------

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


From lede-bugs at lists.infradead.org  Mon Jun 27 04:46:32 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Mon, 27 Jun 2016 11:46:32 +0000
Subject: [FS#27] BT Home Hub 5 Type A - Switch problem when enabling WAN port
 - Comment added
In-Reply-To: <FS27@bugs.lede-project.org>
References: <FS27@bugs.lede-project.org>
Message-ID: <mailman.42886.1467028016.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#27 - BT Home Hub 5 Type A - Switch problem when enabling WAN port
User who did this - Felix Fietkau (nbd)

----------
Commit reverted in 2270fc59
----------

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


From lede-bugs at lists.infradead.org  Mon Jun 27 04:47:20 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Mon, 27 Jun 2016 11:47:20 +0000
Subject: [FS#27] BT Home Hub 5 Type A - Switch problem when enabling WAN port
 - Comment added
In-Reply-To: <FS27@bugs.lede-project.org>
References: <FS27@bugs.lede-project.org>
Message-ID: <mailman.42889.1467028067.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#27 - BT Home Hub 5 Type A - Switch problem when enabling WAN port
User who did this - Felix Fietkau (nbd)

----------
I will try to find the time to rework the ethernet driver soon and will write a comment in this ticket when I have something to test
----------

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


From lede-bugs at lists.infradead.org  Mon Jun 27 04:47:37 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Mon, 27 Jun 2016 11:47:37 +0000
Subject: [FS#27] BT Home Hub 5 Type A - Switch problem when enabling WAN port
 - User took ownership
In-Reply-To: <FS27@bugs.lede-project.org>
References: <FS27@bugs.lede-project.org>
Message-ID: <mailman.42890.1467028080.1639.lede-bugs@lists.infradead.org>

Felix Fietkau has taken ownership of the following task:

FS#27 - BT Home Hub 5 Type A - Switch problem when enabling WAN port

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


From lede-bugs at lists.infradead.org  Mon Jun 27 04:47:45 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Mon, 27 Jun 2016 11:47:45 +0000
Subject: [FS#27] BT Home Hub 5 Type A - Switch problem when enabling WAN port
 - Task changed
In-Reply-To: <FS27@bugs.lede-project.org>
References: <FS27@bugs.lede-project.org>
Message-ID: <mailman.42893.1467028090.1639.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#27 - BT Home Hub 5 Type A - Switch problem when enabling WAN port
User who did this: Felix Fietkau (nbd)
Percent Complete: 0% -> 50%

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


From lede-bugs at lists.infradead.org  Mon Jun 27 08:25:06 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Mon, 27 Jun 2016 15:25:06 +0000
Subject: [FS#8] ARV7518PW kernel panic after any network activity - Comment
 added
In-Reply-To: <FS8@bugs.lede-project.org>
References: <FS8@bugs.lede-project.org>
Message-ID: <mailman.42927.1467041134.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#8 - ARV7518PW kernel panic after any network activity
User who did this - Mohammed Berdai (medber)

----------
Hi John, Yes it does. I flashed LEDE image using ethernet instead of YModem like the old one. Better use Firefox/IceCat/Iceweasl/Seamonkey to send it than Chrome.

As stated by Pteridium here http://foro.seguridadwireless.net/openwrt/openwrt-para-roters-astoria-de-ya-com/msg256236/#msg256236  sometime you need to start http server manually like :

ARV7518PW => http
starting httpd server from server 192.168.1.1
http start

----------

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


From lede-bugs at lists.infradead.org  Mon Jun 27 14:38:56 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Mon, 27 Jun 2016 21:38:56 +0000
Subject: [FS#27] BT Home Hub 5 Type A - Switch problem when enabling WAN port
 - Comment added
In-Reply-To: <FS27@bugs.lede-project.org>
References: <FS27@bugs.lede-project.org>
Message-ID: <mailman.42954.1467063562.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#27 - BT Home Hub 5 Type A - Switch problem when enabling WAN port
User who did this - Mohammed Berdai (medber)

----------
By the way, enabling SMP doesn't seem to cause any issues for ARV7519RW22 which is a XRX200 too. I've tested it extensively for days under tens of gigabytes of wan traffic daily.

----------

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


From lede-bugs at lists.infradead.org  Mon Jun 27 14:44:29 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Mon, 27 Jun 2016 21:44:29 +0000
Subject: [FS#27] BT Home Hub 5 Type A - Switch problem when enabling WAN port
 - Comment added
In-Reply-To: <FS27@bugs.lede-project.org>
References: <FS27@bugs.lede-project.org>
Message-ID: <mailman.42955.1467063895.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#27 - BT Home Hub 5 Type A - Switch problem when enabling WAN port
User who did this - Felix Fietkau (nbd)

----------
I think the issue is probably specific to devices that use both eth0 and eth1
----------

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


From lede-bugs at lists.infradead.org  Mon Jun 27 23:35:12 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Tue, 28 Jun 2016 06:35:12 +0000
Subject: [FS#24] [regression] STP does not flow over WDS links  - Comment added
In-Reply-To: <FS24@bugs.lede-project.org>
References: <FS24@bugs.lede-project.org>
Message-ID: <mailman.43012.1467095736.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#24 - [regression] STP does not flow over WDS links 
User who did this - Gerry Rozema (grozzie2)

----------
Further on this, I have isolated the root cause, it's in most recent versions of compat-wireless.

net/wireless/util.c

line 512 is
		tmp.h_proto = htons(skb->len);

should read

		tmp.h_proto = htons(skb->len-hdrlen);

The next line, pulls hdrlen off the skb, then the skb is copied, net result is, h_proto is the wrong size, ie, to large.  Later in llc_input.c the validation checks on size for the skb fail, so it's not passed on to the stp processor.

Fixing the size in h_proto allows the frames to pass consistency checks in llc processing, and they are passed on to the stp processor in bridge code, and now bridging starts to work correctly over the wds link.





----------

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


From lede-bugs at lists.infradead.org  Tue Jun 28 07:37:46 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Tue, 28 Jun 2016 14:37:46 +0000
Subject: [FS#33] openvpn-polarssl crashes - Comment added
In-Reply-To: <FS33@bugs.lede-project.org>
References: <FS33@bugs.lede-project.org>
Message-ID: <mailman.43153.1467124692.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#33 - openvpn-polarssl crashes
User who did this - Daniel Golle (dangowrt)

----------
Supposedly fixed by commit f98f4601de762251c4644047786affd34d5fb10c
----------

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


From lede-bugs at lists.infradead.org  Tue Jun 28 07:41:00 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Tue, 28 Jun 2016 14:41:00 +0000
Subject: [FS#33] openvpn-polarssl crashes - Task changed
In-Reply-To: <FS33@bugs.lede-project.org>
References: <FS33@bugs.lede-project.org>
Message-ID: <mailman.43154.1467124884.1639.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#33 - openvpn-polarssl crashes
User who did this: Daniel Golle (dangowrt)
Percent Complete: 0% -> 90%
Status: New -> Requires testing

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


From lede-bugs at lists.infradead.org  Tue Jun 28 08:15:55 2016
From: lede-bugs at lists.infradead.org (lede-bugs at lists.infradead.org)
Date: Tue, 28 Jun 2016 15:15:55 +0000
Subject: [FS#34] WRT160NL wireless issues - Task opened
In-Reply-To: <FS34@bugs.lede-project.org>
References: <FS34@bugs.lede-project.org>
Message-ID: <mailman.43163.1467126983.1639.lede-bugs@lists.infradead.org>

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

User who did this - grega (gregecslo) 

Attached to Project - LEDE Project
Summary - WRT160NL wireless issues
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 - Hi!

When using latest LEDE r813 wireless is unstable on this router.
When I do a speedtest or 2 wifi disconnects and this is what is in syslog:

Tue Jun 28 17:01:49 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:01:49 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:01:50 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:01:51 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:01:52 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:01:54 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:02:00 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:02:01 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:02:05 2016 daemon.info hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: disassociated
Tue Jun 28 17:02:05 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:02:06 2016 daemon.info hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Tue Jun 28 17:02:10 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:02:15 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:02:20 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:02:25 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:02:30 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:02:35 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:02:40 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:02:45 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:02:50 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:02:55 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:00 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:04 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:05 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:10 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:14 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:15 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:20 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:25 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:29 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:29 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:29 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:30 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: Could not set STA to kernel driver
Tue Jun 28 17:03:30 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:30 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:30 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:31 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:31 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:31 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:31 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:32 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:36 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:41 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:46 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:51 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:03:56 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:04:01 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:04:06 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:04:11 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:04:16 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:04:21 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:04:26 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:04:31 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:04:36 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:04:41 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:04:44 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:04:46 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:04:51 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:04:53 2016 daemon.info hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: disconnected due to excessive missing ACKs
Tue Jun 28 17:04:56 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:05:02 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:05:07 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:05:12 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:05:17 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:05:22 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:05:23 2016 daemon.info hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Tue Jun 28 17:05:27 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:05:32 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:05:37 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:05:42 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:05:47 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:05:52 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:05:57 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:06:02 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:06:07 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:06:12 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:06:17 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:06:34 2016 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: did not acknowledge authentication response
Tue Jun 28 17:07:05 2016 daemon.info hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: disassociated due to inactivity
Tue Jun 28 17:07:06 2016 daemon.info hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Tue Jun 28 17:07:13 2016 daemon.info hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: disassociated due to inactivity
Tue Jun 28 17:07:14 2016 daemon.info hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Tue Jun 28 17:08:31 2016 daemon.info hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: disassociated due to inactivity
Tue Jun 28 17:08:32 2016 daemon.info hostapd: wlan0: STA 00:00:00:00:00:00 (masked) IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
All clients disconnect.

If I do "wifi" in console or reboot it it works until next speedtest...

This doesn`t happen with any Openwrt build...

Some info from kernel log if it helps:


[    0.000000] Linux version 4.4.14 (buildbot at builds) (gcc version 5.3.0 (LEDE GCC 5.3.0 r810) ) #2 Tue Jun 28 13:00:49 UTC 2016
[    0.000000] MyLoader: sysp=aaaa5554, boardp=aaaa5554, parts=aaaa5554
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019374 (MIPS 24Kc)
[    0.000000] SoC: Atheros AR9130 rev 2
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 02000000 @ 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-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 804265d0, node_mem_map 81000000
[    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] 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: 8128
[    0.000000] Kernel command line: board=WRT160NL console=ttyS0,115200 rootfstype=squashfs,jffs2 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: 27544K/32768K available (3058K kernel code, 162K rwdata, 768K rodata, 292K init, 205K bss, 5224K 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:5.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.007882] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
[    0.090589] pid_max: default: 32768 minimum: 301
[    0.095363] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.101977] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.112343] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.123796] NET: Registered protocol family 16
[    0.129984] MIPS: machine is Linksys WRT160NL
[    0.686373] clocksource: Switched to clocksource MIPS
[    0.693134] NET: Registered protocol family 2
[    0.698783] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.705759] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.712176] TCP: Hash tables configured (established 1024 bind 1024)
[    0.718665] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.724510] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.731141] NET: Registered protocol family 1
[    0.735545] PCI: CLS 0 bytes, default 32
[    0.736855] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.764319] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.770219] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.783048] io scheduler noop registered
[    0.787050] io scheduler deadline registered (default)
[    0.792495] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.802782] console [ttyS0] disabled
[    0.826402] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 12500000) is a 16550A
[    0.835089] console [ttyS0] enabled
[    0.842115] bootconsole [early0] disabled
[    0.856198] m25p80 spi0.0: found en25p64, expected m25p80
[    0.861728] m25p80 spi0.0: en25p64 (8192 Kbytes)
[    0.867480] 6 cybertan partitions found on MTD device spi0.0
[    0.873180] Creating 6 MTD partitions on "spi0.0":
[    0.878062] 0x000000000000-0x000000040000 : "u-boot"
[    0.884841] 0x000000040000-0x000000190000 : "kernel"
[    0.891886] 0x000000190000-0x0000007e0000 : "rootfs"
[    0.898910] mtd: device 2 (rootfs) set to be root filesystem
[    0.904691] 1 squashfs-split partitions found on MTD device rootfs
[    0.910975] 0x000000370000-0x0000007e0000 : "rootfs_data"
[    0.918445] 0x0000007e0000-0x0000007f0000 : "nvram"
[    0.925349] 0x0000007f0000-0x000000800000 : "art"
[    0.932205] 0x000000040000-0x0000007e0000 : "firmware"
[    0.954132] libphy: ag71xx_mdio: probed
[    1.366882] Registering RTL8306SD switch with Chip ID: 0x5988, version: 0x0000
[    1.374193] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=00008306, driver=Realtek RTL8306S]
[    1.384783] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RMII
[    1.786426] ag71xx ag71xx.1: connected to PHY at ag71xx-mdio.0:04 [uid=00008306, driver=Realtek RTL8306S]
[    1.797030] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:RMII
[    1.805987] NET: Registered protocol family 10
[    1.815472] NET: Registered protocol family 17
[    1.820116] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    1.832889] Bridge firewalling registered
[    1.837098] 8021q: 802.1Q VLAN Support v1.8
[    1.850259] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
[    1.859212] Freeing unused kernel memory: 292K (80447000 - 80490000)
[    3.088898] init: Console is alive
[    3.092569] init: - watchdog -
[    4.377018] usbcore: registered new interface driver usbfs
[    4.382660] usbcore: registered new interface driver hub
[    4.388176] usbcore: registered new device driver usb
[    4.399626] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    4.408128] ehci-platform: EHCI generic platform driver
[    4.413493] ehci-platform ehci-platform: EHCI Host Controller
[    4.419380] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
[    4.427497] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
[    4.446423] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
[    4.453883] hub 1-0:1.0: USB hub found
[    4.458141] hub 1-0:1.0: 1 port detected
[    4.465516] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    4.473527] ohci-platform: OHCI generic platform driver
[    4.482422] init: - preinit -
[    5.461968] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    5.492204] random: procd urandom read with 8 bits of entropy available
[    7.406704] ar71xx: pll_reg 0xb8050014: 0x13000a44
[    7.406738] eth0: link up (100Mbps/Full duplex)
[    7.411441] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    8.718282] jffs2: notice: (388) 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.738103] mount_root: switching to jffs2 overlay
[    8.790454] eth0: link down
[    8.811810] procd: - early -
[    8.814838] procd: - watchdog -
[    9.524322] procd: - ubus -
[    9.581693] procd: - init -
[   10.150172] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   10.174032] Loading modules backported from Linux version wt-2016-05-12-0-g7a54796
[   10.181730] Backport generated by backports.git backports-20160216-0-ge3c56e4
[   10.192938] ip_tables: (C) 2000-2006 Netfilter Core Team
[   10.211306] nf_conntrack version 0.5.0 (434 buckets, 1736 max)
[   10.260994] xt_time: kernel timezone is -0000
[   10.335052] PPP generic driver version 2.4.2
[   10.342996] NET: Registered protocol family 24
[   10.417090] ath: EEPROM regdomain: 0x0
[   10.417117] ath: EEPROM indicates default country code should be used
[   10.417130] ath: doing EEPROM country->regdmn map search
[   10.417155] ath: country maps to regdmn code: 0x3a
[   10.417171] ath: Country alpha2 being used: US
[   10.417184] ath: Regpair used: 0x3a
[   10.437431] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   10.441324] ieee80211 phy0: Atheros AR9100 MAC/BB Rev:7 AR2122 RF Rev:a2 mem=0xb80c0000, irq=2


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


From lede-bugs at lists.infradead.org  Tue Jun 28 14:54:03 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 28 Jun 2016 21:54:03 +0000
Subject: [FS#24] [regression] STP does not flow over WDS links  - Comment added
In-Reply-To: <FS24@bugs.lede-project.org>
References: <FS24@bugs.lede-project.org>
Message-ID: <mailman.43232.1467150867.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#24 - [regression] STP does not flow over WDS links 
User who did this - Jo-Philipp Wich (jow-)

----------
I committed your proposed change with https://git.lede-project.org/?p=source.git;a=commitdiff;h=1e03998e2b85e0250dd55da5146199a720e214af .
----------

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


From lede-bugs at lists.infradead.org  Tue Jun 28 14:54:34 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 28 Jun 2016 21:54:34 +0000
Subject: [FS#24] [regression] STP does not flow over WDS links  - Task closed
In-Reply-To: <FS24@bugs.lede-project.org>
References: <FS24@bugs.lede-project.org>
Message-ID: <mailman.43233.1467150898.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#24 - [regression] STP does not flow over WDS links 
User who did this - Jo-Philipp Wich (jow-)

Reason for closing: Fixed
Additional comments about closing: Proposed patch has been pushed.

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


From lede-bugs at lists.infradead.org  Tue Jun 28 16:43:03 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 28 Jun 2016 23:43:03 +0000
Subject: [FS#35] mynet-n750 factory images don't find root partition - Task
 opened
In-Reply-To: <FS35@bugs.lede-project.org>
References: <FS35@bugs.lede-project.org>
Message-ID: <mailman.43243.1467157409.1639.lede-bugs@lists.infradead.org>

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

User who did this - Steven Haigh (CRCinAU) 

Attached to Project - LEDE Project
Summary - mynet-n750 factory images don't find root partition
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 - The LEDE Project factory images do not boot when flashed from either the web interface or the emergency recovery web site.

Boot logs as of r813:
verify_seama: data=0x81000000, size=3406568
SEAMA ==========================================
  magic      : 5ea3a417
  meta size  : 24 bytes
  meta data  : signature=wrgnd13_wd_av
  image size : 0 bytes
================================================
SEAMA ==========================================
  magic      : 5ea3a417
  meta size  : 36 bytes
  meta data  : dev=/dev/mtdblock/1
  meta data  : type=firmware
  meta data  :
  meta data  :
  image size : 3406464 bytes
  checksum   : 8969D9077B2CAAF8CE87548FC252A30A
  digest     : 8969D9077B2CAAF8CE87548FC252A30A
  Selected !!!
================================================
(ENV) begin addr=0x9f070000,end=0x9ffeffff
Erase Flash from 0x9f070000 to 0x9ffeffff in Bank # 1
First 0x7 last 0xfe sector size 0x10000                                                                                                                                                                                                   254
Erased 248 sectors
write addr: 9f070000

Write runtime image into flash...OK,dest addr=0x9f070000
Upload file OK!

U-Boot 1.1.4 (Mar 26 2012 - 21:53:42)

SVN revision: 51
Target board: WRG-ND13

DRAM:
sri
Wasp 1.2
wasp_ddr_initial_config(255): (32bit) ddr2 init
128 MB
Top of RAM usable for U-Boot at: 88000000
Reserving 242k for U-Boot at: 87fc0000
Reserving 192k for malloc() at: 87f90000
Reserving 44 Bytes for Board Info at: 87f8ffd4
Reserving 36 Bytes for Global Data at: 87f8ffb0
Reserving 128k for boot params() at: 87f6ffb0
Stack Pointer at: 87f6ff98
Now running in RAM - U-Boot at: 87fc0000
id read 0x100000ff
flash size 16 MB, sector count = 256
Flash: 16 MB
pci_init_board: PCIe PLL not set for 40MHz refclk
In:    serial
Out:   serial
Err:   serial
Net:   ag934x_enet_initialize...
 wasp  reset mask:c03300
WASP  ----> S17 PHY *
: cfg1 0x7 cfg2 0x7114
eth0: 00:90:a9:ad:67:21
athrs17_reg_init: complete
eth0 up
GIGA: athrs17_link_down all port...
eth0
Hit any key to stop autoboot:  0
## Booting image at 9f070000 ...
Verifying Checksum ...
Uncompressing SEAMA linux.lzma ... OK
do_boot_linux entry = 80002000
## Transferring control to Linux (at address 00000000) ...
## Giving linux memsize in bytes, 134217728

Starting kernel ...



OpenWrt kernel loader for AR7XXX/AR9XXX
Copyright (C) 2011 Gabor Juhos 
Decompressing kernel... done!
Starting kernel at 80060000...

[    0.000000] Linux version 4.4.14 (openwrt at openwrt.crc.id.au) (gcc version 5.3.0 (LEDE GCC 5.3.0 r418) ) #2 Tue Jun 28 14:07:32 UTC 2016
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0001974c (MIPS 74Kc)
[    0.000000] SoC: Atheros AR9344 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] No valid device tree found, continuing without
[    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] 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] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: board=MYNET-N750 console=ttyS0,115200 mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,64k(devdata)ro,64k(devconf)ro,15872k(firmware),64k(radiocfg)ro rootfstype=squashfs,jffs2 noinitrd
[    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: 125008K/131072K available (3058K kernel code, 162K rwdata, 768K rodata, 292K init, 205K bss, 6064K 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:560.000MHz, DDR:480.000MHz, AHB:240.000MHz, Ref:40.000MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6825930166 ns
[    0.000010] sched_clock: 32 bits at 280MHz, resolution 3ns, wraps every 7669584382ns
[    0.008295] Calibrating delay loop... 278.93 BogoMIPS (lpj=1394688)
[    0.081138] pid_max: default: 32768 minimum: 301
[    0.086170] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.093222] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.103130] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.114813] NET: Registered protocol family 16
[    0.120895] MIPS: machine is WD My Net N750
[    0.152462] registering PCI controller with io_map_base unset
[    0.401712] PCI host bridge to bus 0000:00
[    0.406082] pci_bus 0000:00: root bus resource [mem 0x10000000-0x13ffffff]
[    0.413443] pci_bus 0000:00: root bus resource [io  0x0000]
[    0.419372] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
[    0.426607] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.435105] pci 0000:00:00.0: invalid calibration data
[    0.441018] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x1001ffff 64bit]
[    0.448817] pci 0000:00:00.0: BAR 6: assigned [mem 0x10020000-0x1002ffff pref]
[    0.456533] pci 0000:00:00.0: using irq 40 for pin 1
[    0.462678] clocksource: Switched to clocksource MIPS
[    0.469411] NET: Registered protocol family 2
[    0.474938] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.482368] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.489178] TCP: Hash tables configured (established 1024 bind 1024)
[    0.496027] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.502253] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.509216] NET: Registered protocol family 1
[    0.514876] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.538034] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.544301] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.557084] io scheduler noop registered
[    0.561270] io scheduler deadline registered (default)
[    0.567034] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.576566] console [ttyS0] disabled
[    0.600439] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 2500000) is a 16550A
[    0.609633] console [ttyS0] enabled
[    0.609633] console [ttyS0] enabled
[    0.617055] bootconsole [early0] disabled
[    0.617055] bootconsole [early0] disabled
[    0.630332] m25p80 spi0.0: found mx25l12805d, expected m25p80
[    0.636239] m25p80 spi0.0: mx25l12805d (16384 Kbytes)
[    0.641394] 6 cmdlinepart partitions found on MTD device spi0.0
[    0.647415] Creating 6 MTD partitions on "spi0.0":
[    0.652285] 0x000000000000-0x000000040000 : "u-boot"
[    0.659357] 0x000000040000-0x000000050000 : "u-boot-env"
[    0.666314] 0x000000050000-0x000000060000 : "devdata"
[    0.673008] 0x000000060000-0x000000070000 : "devconf"
[    0.679646] 0x000000070000-0x000000ff0000 : "firmware"
[    0.719345] 0x000000ff0000-0x000001000000 : "radiocfg"
[    1.732792] switch0: Atheros AR8327 rev. 2 switch registered on ag71xx-mdio.0
[    1.799647] libphy: ag71xx_mdio: probed
[    3.391236] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd033, driver=Atheros AR8216/AR8236/AR8316]
[    3.402671] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII
[    3.411028] NET: Registered protocol family 10
[    3.419183] NET: Registered protocol family 17
[    3.423820] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    3.436672] Bridge firewalling registered
[    3.440862] 8021q: 802.1Q VLAN Support v1.8
[    3.447760] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[    3.455394] Please append a correct "root=" boot option; here are the available partitions:
[    3.463882] 1f00             256 mtdblock0  (driver?)
[    3.469016] 1f01              64 mtdblock1  (driver?)
[    3.474154] 1f02              64 mtdblock2  (driver?)
[    3.479284] 1f03              64 mtdblock3  (driver?)
[    3.484424] 1f04           15872 mtdblock4  (driver?)
[    3.489554] 1f05              64 mtdblock5  (driver?)
[    3.494692] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    3.503948] Rebooting in 1 seconds..

The missing magic line seems to be:
[    0.715565] 2 seama-fw partitions found on MTD device firmware

I *CAN* install openwrt-15.05.1-ar71xx-generic-mynet-n750-squashfs-factory.bin, then sysupgrade to r813 sysupgrade image without a problem.

I built r813 with a test patch from jow: http://openwrt.crc.id.au/r813/EXTRA_PATCHES/00-try-to-fix-factory-images.patch

This did not fix the factory images. I tested as far back as r555 - which also did not boot correctly when flashed via the emergency httpsvr in uboot.

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


From lede-bugs at lists.infradead.org  Tue Jun 28 16:44:49 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Tue, 28 Jun 2016 23:44:49 +0000
Subject: [FS#35] mynet-n750 factory images don't find root partition - Comment
 added
In-Reply-To: <FS35@bugs.lede-project.org>
References: <FS35@bugs.lede-project.org>
Message-ID: <mailman.43244.1467157513.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#35 - mynet-n750 factory images don't find root partition
User who did this - Steven Haigh (CRCinAU)

----------
As a comparison, this is the mtd layout for a working r813 installed via sysupgrade:

[    0.641377] 6 cmdlinepart partitions found on MTD device spi0.0
[    0.647398] Creating 6 MTD partitions on "spi0.0":
[    0.652268] 0x000000000000-0x000000040000 : "u-boot"
[    0.659339] 0x000000040000-0x000000050000 : "u-boot-env"
[    0.666300] 0x000000050000-0x000000060000 : "devdata"
[    0.672994] 0x000000060000-0x000000070000 : "devconf"
[    0.679627] 0x000000070000-0x000000ff0000 : "firmware"
[    0.715565] 2 seama-fw partitions found on MTD device firmware
[    0.721501] 0x000000070040-0x0000001d0000 : "kernel"
[    0.727929] 0x0000001d0000-0x000000ff0000 : "rootfs"
[    0.734550] mtd: device 6 (rootfs) set to be root filesystem
[    0.740345] 1 squashfs-split partitions found on MTD device rootfs
[    0.746668] 0x0000003b0000-0x000000ff0000 : "rootfs_data"
[    0.753793] 0x000000ff0000-0x000001000000 : "radiocfg"
----------

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


From lede-bugs at lists.infradead.org  Tue Jun 28 19:08:19 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 02:08:19 +0000
Subject: [FS#35] mynet-n750 factory images don't find root partition - Comment
 added
In-Reply-To: <FS35@bugs.lede-project.org>
References: <FS35@bugs.lede-project.org>
Message-ID: <mailman.43256.1467166125.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#35 - mynet-n750 factory images don't find root partition
User who did this - Steven Haigh (CRCinAU)

----------
Just to update the record, I pinged yousong regarding this as suggested by jow - got the following reply:

Probably because recently I submitted a patch to use mtdsplit to
auto-split rootfs from firmware partition for HiWiFi HC6361.  I will
see if I can find the cause of issue in the case of mynet-n750 ;)
----------

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


From lede-bugs at lists.infradead.org  Tue Jun 28 23:38:48 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 06:38:48 +0000
Subject: [FS#27] BT Home Hub 5 Type A - Switch problem when enabling WAN port
 - Task closed
In-Reply-To: <FS27@bugs.lede-project.org>
References: <FS27@bugs.lede-project.org>
Message-ID: <mailman.43277.1467182352.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#27 - BT Home Hub 5 Type A - Switch problem when enabling WAN port
User who did this - john (john)

Reason for closing: Fixed
Additional comments about closing: issue was related to SMP being enabled. the driver obviously has a race condition.

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


From lede-bugs at lists.infradead.org  Wed Jun 29 00:24:32 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 07:24:32 +0000
Subject: [FS#13] Ath9k AP stays up for connected clients but doesn't show in
 scan on new ones - Comment added
In-Reply-To: <FS13@bugs.lede-project.org>
References: <FS13@bugs.lede-project.org>
Message-ID: <mailman.43298.1467185098.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#13 - Ath9k AP stays up for connected clients but doesn't show in scan on new ones
User who did this - Bluse-Blue (Bluse)

----------
Hi all,

A additional observation I made is:
If the ap in question is in such a mode where no beacons are send and WiFi is not working anymore, the OS does not show any increase in interrupt counts for the ath9k card. You can check this by triggering cat /proc/interrupts and watch the line with ath9k, e.g.:
           CPU0
  4:      10907      MIPS   4  eth0
  5:     524477      MIPS   5  eth1
  7:    5958616      MIPS   7  timer
 11:         26      MISC  serial
 47:     121776     dummy  ath9k
 48:          0     dummy  ehci_hcd:usb1
 49:          0     dummy  ehci_hcd:usb2
ERR:        738

Can anyone confirm this "stop if interrupts" on his/her side as well ?

Bye Bluse
----------

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


From lede-bugs at lists.infradead.org  Wed Jun 29 03:25:33 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 10:25:33 +0000
Subject: [FS#13] Ath9k AP stays up for connected clients but doesn't show in
 scan on new ones - Comment added
In-Reply-To: <FS13@bugs.lede-project.org>
References: <FS13@bugs.lede-project.org>
Message-ID: <mailman.43337.1467195958.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#13 - Ath9k AP stays up for connected clients but doesn't show in scan on new ones
User who did this - Bluse-Blue (Bluse)

----------
Hi all,

Just tested another mips router TPLink CPE210 (ath9k based) and I do see the same not-working AP functionality sometimes. At the moment I can not reproduce the stuck-AP in dedicated way, so the "sometimes" means after some hours or right after reboot.
The interrupt counter does not increase and stucks at count 27, which is quite low and could indicate that right after initialising the device by the OS, it got stuck.

LEDE version 811

Greetings Bluse
----------

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


From lede-bugs at lists.infradead.org  Wed Jun 29 04:26:34 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 11:26:34 +0000
Subject: [FS#13] Ath9k AP stays up for connected clients but doesn't show in
 scan on new ones - Comment added
In-Reply-To: <FS13@bugs.lede-project.org>
References: <FS13@bugs.lede-project.org>
Message-ID: <mailman.43346.1467199619.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#13 - Ath9k AP stays up for connected clients but doesn't show in scan on new ones
User who did this - Bluse-Blue (Bluse)

----------
Hi all,

I was able to find a way to reproduce the issue with "not interrupt increase" for ath9k and hence AP stops from operation.

steps to reproduce:

  * for better observability just establish two ssh session to your router, side-by-side 

  * in window A watch the interrupt counter for ath9k by while true; do cat /proc/interrupts ; sleep 1; done


  * in window B issue wifi severale times. After 2-4 "wifi" triggers, I am able to stop the interrupt counter and the overall wifi and after another 2-4 "wifi" triggers the interrupt counter increases its count again and wifi is back.

dmesg output:
to get some debug output from ath9k, I used echo "0x00000793" > /sys/kernel/debug/ieee80211/phy0/ath9k/debug, which shows:
[[http://pastebin.com/38EMU31e|dmesg output with ath9k debug]]

Can someone test this steps and report if the same is observeable ?

Bye Bluse

----------

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


From lede-bugs at lists.infradead.org  Wed Jun 29 04:56:16 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 11:56:16 +0000
Subject: [FS#31] firewall3 fails to reload iptables policy extension - Comment
 added
In-Reply-To: <FS31@bugs.lede-project.org>
References: <FS31@bugs.lede-project.org>
Message-ID: <mailman.43351.1467201401.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#31 - firewall3 fails to reload iptables policy extension
User who did this - Jo-Philipp Wich (jow-)

----------
Phew, thanks for the report. I'll investigate.
----------

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


From lede-bugs at lists.infradead.org  Wed Jun 29 04:56:25 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 11:56:25 +0000
Subject: [FS#31] firewall3 fails to reload iptables policy extension - User
 took ownership
In-Reply-To: <FS31@bugs.lede-project.org>
References: <FS31@bugs.lede-project.org>
Message-ID: <mailman.43352.1467201411.1639.lede-bugs@lists.infradead.org>

Jo-Philipp Wich has taken ownership of the following task:

FS#31 - firewall3 fails to reload iptables policy extension

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


From lede-bugs at lists.infradead.org  Wed Jun 29 06:15:16 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 13:15:16 +0000
Subject: [FS#23] Sitecom WL-351 Switch driver problem - No network
 connectivity to router - Comment added
In-Reply-To: <FS23@bugs.lede-project.org>
References: <FS23@bugs.lede-project.org>
Message-ID: <mailman.43363.1467206140.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#23 - Sitecom WL-351 Switch driver problem - No network connectivity to router
User who did this - john (john)

----------
pushed a patch to my staging tree, please see if that works for you.
----------

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


From lede-bugs at lists.infradead.org  Wed Jun 29 06:18:52 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 13:18:52 +0000
Subject: [FS#23] Sitecom WL-351 Switch driver problem - No network
 connectivity to router - Comment added
In-Reply-To: <FS23@bugs.lede-project.org>
References: <FS23@bugs.lede-project.org>
Message-ID: <mailman.43364.1467206356.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#23 - Sitecom WL-351 Switch driver problem - No network connectivity to router
User who did this - Timeless (Timeless)

----------
Ok great, does that include the reworked patch I linked in my bugreport?
----------

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


From lede-bugs at lists.infradead.org  Wed Jun 29 06:19:08 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 13:19:08 +0000
Subject: [FS#23] Sitecom WL-351 Switch driver problem - No network
 connectivity to router - Task changed
In-Reply-To: <FS23@bugs.lede-project.org>
References: <FS23@bugs.lede-project.org>
Message-ID: <mailman.43365.1467206372.1639.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#23 - Sitecom WL-351 Switch driver problem - No network connectivity to router
User who did this: john (john)
Percent Complete: 0% -> 50%

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


From lede-bugs at lists.infradead.org  Wed Jun 29 06:19:14 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 13:19:14 +0000
Subject: [FS#23] Sitecom WL-351 Switch driver problem - No network
 connectivity to router - Task changed
In-Reply-To: <FS23@bugs.lede-project.org>
References: <FS23@bugs.lede-project.org>
Message-ID: <mailman.43366.1467206379.1639.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#23 - Sitecom WL-351 Switch driver problem - No network connectivity to router
User who did this: john (john)
Status: Assigned -> Waiting on reporter

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


From lede-bugs at lists.infradead.org  Wed Jun 29 06:27:25 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 13:27:25 +0000
Subject: [FS#23] Sitecom WL-351 Switch driver problem - No network
 connectivity to router - Comment added
In-Reply-To: <FS23@bugs.lede-project.org>
References: <FS23@bugs.lede-project.org>
Message-ID: <mailman.43369.1467206869.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#23 - Sitecom WL-351 Switch driver problem - No network connectivity to router
User who did this - john (john)

----------
yep, all inclusive, in theory it should work but lets see what your testing yields
----------

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


From lede-bugs at lists.infradead.org  Wed Jun 29 06:31:17 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 13:31:17 +0000
Subject: [FS#23] Sitecom WL-351 Switch driver problem - No network
 connectivity to router - Comment added
In-Reply-To: <FS23@bugs.lede-project.org>
References: <FS23@bugs.lede-project.org>
Message-ID: <mailman.43370.1467207101.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#23 - Sitecom WL-351 Switch driver problem - No network connectivity to router
User who did this - Timeless (Timeless)

----------
Ah nvm I can find all the changes in your staging tree. Thanks, will try it asap
----------

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


From lede-bugs at lists.infradead.org  Wed Jun 29 07:31:16 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 14:31:16 +0000
Subject: [FS#37] 192.168.1.1 connection refused - Task opened
In-Reply-To: <FS37@bugs.lede-project.org>
References: <FS37@bugs.lede-project.org>
Message-ID: <mailman.43395.1467210701.1639.lede-bugs@lists.infradead.org>

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

User who did this - Julian (El3c7r1x) 

Attached to Project - LEDE Project
Summary - 192.168.1.1 connection refused
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 - hi i do have to apologize if something is wrong with my post
i am not on forums that often, plus my english aint the best

so recently i **flashed lede onto** my existing **openwrt** system

[from Index of /lede/**snapshots**/targets/ar71xx/generic on 28th this month]
[**tplink wr841n v10**]

after rebooting i tried **accessing 192.168.1.1** as in openwrt
but it **failed**

i get errors like "page unavailable" or "connection refused"

did i do something wrong or perhaps there aint no gui for lede yet?

i can still access the failsafe mode via ssh
i am somewhat unfamiliar when it comes to programming but i will do my best to provide more information

regards, Julian

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


From lede-bugs at lists.infradead.org  Wed Jun 29 07:37:11 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 14:37:11 +0000
Subject: [FS#37] 192.168.1.1 connection refused - Comment added
In-Reply-To: <FS37@bugs.lede-project.org>
References: <FS37@bugs.lede-project.org>
Message-ID: <mailman.43396.1467211056.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#37 - 192.168.1.1 connection refused
User who did this - Julian (El3c7r1x)

----------
ok thanks for the reply
so it was my fault after all
simply did not knew that
----------

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


From lede-bugs at lists.infradead.org  Wed Jun 29 07:32:41 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 14:32:41 +0000
Subject: [FS#37] 192.168.1.1 connection refused - Comment added
In-Reply-To: <FS37@bugs.lede-project.org>
References: <FS37@bugs.lede-project.org>
Message-ID: <mailman.43397.1467211210.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#37 - 192.168.1.1 connection refused
User who did this - Jo-Philipp Wich (jow-)

----------
LEDE builds do not contain any gui yet, they're like OpenWrt snapshot builds.
----------

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


From lede-bugs at lists.infradead.org  Wed Jun 29 07:47:39 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 14:47:39 +0000
Subject: [FS#37] 192.168.1.1 connection refused - Task closed
In-Reply-To: <FS37@bugs.lede-project.org>
References: <FS37@bugs.lede-project.org>
Message-ID: <mailman.43404.1467211683.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#37 - 192.168.1.1 connection refused
User who did this - john (john)

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


From lede-bugs at lists.infradead.org  Wed Jun 29 07:53:32 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 14:53:32 +0000
Subject: [FS#36] 192.168.1.1 Interface is unavailable - Task closed
In-Reply-To: <FS36@bugs.lede-project.org>
References: <FS36@bugs.lede-project.org>
Message-ID: <mailman.43413.1467212038.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#36 - 192.168.1.1 Interface is unavailable
User who did this - john (john)

Reason for closing: Duplicate
Additional comments about closing: duplicate of #37

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


From lede-bugs at lists.infradead.org  Wed Jun 29 08:54:12 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Wed, 29 Jun 2016 15:54:12 +0000
Subject: [FS#38] Problem with Tor - Task opened
In-Reply-To: <FS38@bugs.lede-project.org>
References: <FS38@bugs.lede-project.org>
Message-ID: <mailman.43430.1467215677.1639.lede-bugs@lists.infradead.org>

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

User who did this - Ansuel (Ansuel) 

Attached to Project - LEDE Project
Summary - Problem with Tor
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 have some problem with the tor package... 

one is about pid, currently i run tor with a separate user and not as root and it can't create a pid file Unable to open "/var/run/tor.pid" for writing: Permission denied

and i have other problem with signature but i think is something related with my configuration Error reading router descriptor: invalid signature.

Has anyone an idea about this?

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


From lede-bugs at lists.infradead.org  Thu Jun 30 00:39:48 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 30 Jun 2016 07:39:48 +0000
Subject: [FS#35] mynet-n750 factory images don't find root partition - User
 took ownership
In-Reply-To: <FS35@bugs.lede-project.org>
References: <FS35@bugs.lede-project.org>
Message-ID: <mailman.43566.1467272413.1639.lede-bugs@lists.infradead.org>

john has taken ownership of the following task:

FS#35 - mynet-n750 factory images don't find root partition

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


From lede-bugs at lists.infradead.org  Thu Jun 30 00:39:57 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 30 Jun 2016 07:39:57 +0000
Subject: [FS#35] mynet-n750 factory images don't find root partition - Task
 changed
In-Reply-To: <FS35@bugs.lede-project.org>
References: <FS35@bugs.lede-project.org>
Message-ID: <mailman.43567.1467272422.1639.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#35 - mynet-n750 factory images don't find root partition
User who did this: john (john)
Status: Assigned -> Waiting on reporter

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


From lede-bugs at lists.infradead.org  Thu Jun 30 00:40:28 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 30 Jun 2016 07:40:28 +0000
Subject: [FS#35] mynet-n750 factory images don't find root partition - Comment
 added
In-Reply-To: <FS35@bugs.lede-project.org>
References: <FS35@bugs.lede-project.org>
Message-ID: <mailman.43568.1467272453.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#35 - mynet-n750 factory images don't find root partition
User who did this - john (john)

----------
can you please test if this still happens with yousongs patch which i applied to my staging tree ?
----------

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


From lede-bugs at lists.infradead.org  Thu Jun 30 00:49:38 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 30 Jun 2016 07:49:38 +0000
Subject: [FS#34] WRT160NL wireless issues - Task changed
In-Reply-To: <FS34@bugs.lede-project.org>
References: <FS34@bugs.lede-project.org>
Message-ID: <mailman.43574.1467273002.1639.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#34 - WRT160NL wireless issues
User who did this: john (john)
Status: Unconfirmed -> Assigned
Assigned To: [-] -> Felix Fietkau

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


From lede-bugs at lists.infradead.org  Thu Jun 30 01:34:00 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 30 Jun 2016 08:34:00 +0000
Subject: [FS#8] ARV7518PW kernel panic after any network activity - Comment
 added
In-Reply-To: <FS8@bugs.lede-project.org>
References: <FS8@bugs.lede-project.org>
Message-ID: <mailman.43591.1467275665.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#8 - ARV7518PW kernel panic after any network activity
User who did this - john (john)

----------
does this bootloader have the problem where it takes several hours to upload the file ?
----------

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


From lede-bugs at lists.infradead.org  Thu Jun 30 02:20:17 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 30 Jun 2016 09:20:17 +0000
Subject: [FS#21] Save log to file option - Task closed
In-Reply-To: <FS21@bugs.lede-project.org>
References: <FS21@bugs.lede-project.org>
Message-ID: <mailman.43598.1467278442.1639.lede-bugs@lists.infradead.org>

The following task is now closed:

FS#21 - Save log to file option
User who did this - john (john)

Reason for closing: Fixed
Additional comments about closing: i have created a patch and sent a PR for this. it will take a few days until it treacled down to you tree

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


From lede-bugs at lists.infradead.org  Thu Jun 30 05:26:19 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 30 Jun 2016 12:26:19 +0000
Subject: [FS#30] x86: SDK: host-compile of grub2 build error - User took
 ownership
In-Reply-To: <FS30@bugs.lede-project.org>
References: <FS30@bugs.lede-project.org>
Message-ID: <mailman.43656.1467289604.1639.lede-bugs@lists.infradead.org>

john has taken ownership of the following task:

FS#30 - x86: SDK: host-compile of grub2 build error

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


From lede-bugs at lists.infradead.org  Thu Jun 30 05:33:12 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 30 Jun 2016 12:33:12 +0000
Subject: [FS#30] x86: SDK: host-compile of grub2 build error - Comment added
In-Reply-To: <FS30@bugs.lede-project.org>
References: <FS30@bugs.lede-project.org>
Message-ID: <mailman.43659.1467290016.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#30 - x86: SDK: host-compile of grub2 build error
User who did this - john (john)

----------
i cannot reproduce this on 3 different machines. a few questions
1) did you build the SDK yourself or download it
2) what distro are you building on
3) if it is a self built SDK can you retry with a fresh tree, lzma got updated recently maybe this is a spurious build error due to that update
----------

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


From lede-bugs at lists.infradead.org  Thu Jun 30 05:33:19 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 30 Jun 2016 12:33:19 +0000
Subject: [FS#30] x86: SDK: host-compile of grub2 build error - Task changed
In-Reply-To: <FS30@bugs.lede-project.org>
References: <FS30@bugs.lede-project.org>
Message-ID: <mailman.43660.1467290024.1639.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#30 - x86: SDK: host-compile of grub2 build error
User who did this: john (john)
Status: Assigned -> Waiting on reporter

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


From lede-bugs at lists.infradead.org  Thu Jun 30 14:53:58 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 30 Jun 2016 21:53:58 +0000
Subject: [FS#29] WiTi - laptop cannot connect when configured to use 80MHz -
 Comment added
In-Reply-To: <FS29@bugs.lede-project.org>
References: <FS29@bugs.lede-project.org>
Message-ID: <mailman.43781.1467323662.1639.lede-bugs@lists.infradead.org>

The following task has a new comment added:

FS#29 - WiTi - laptop cannot connect when configured to use 80MHz
User who did this - neheb (neheb)

----------
the issue is with the 80 MHz setting. selecting 40 fixes everything.
----------

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


From lede-bugs at lists.infradead.org  Thu Jun 30 21:52:46 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 01 Jul 2016 04:52:46 +0000
Subject: [FS#33] openvpn-polarssl crashes - Task changed
In-Reply-To: <FS33@bugs.lede-project.org>
References: <FS33@bugs.lede-project.org>
Message-ID: <mailman.43832.1467348790.1639.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#33 - openvpn-polarssl crashes
User who did this: john (john)
Assigned To: [-] -> Daniel Golle

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


From lede-bugs at lists.infradead.org  Thu Jun 23 01:41:58 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Thu, 23 Jun 2016 08:41:58 -0000
Subject: e2fsprogs does not compile after version bump to 1.43.1
In-Reply-To: <mailman.42301.1466616904.1639.lede-bugs@lists.infradead.org>
References: <mailman.42296.1466614201.1639.lede-bugs@lists.infradead.org>
 <mailman.42301.1466616904.1639.lede-bugs@lists.infradead.org>
Message-ID: <mailman.46547.1468830540.1639.lede-bugs@lists.infradead.org>

Hi John,

I just cloned out a fresh LEDE into /tmp, selected the x86_64 target & e2fsprogs, everything else default.
The compile process brakes as well with:

make[3]: Entering directory '/private/tmp/lede-test-e2fsprogs/package/utils/e2fsprogs'
make   -C /private/tmp/lede-test-e2fsprogs/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util BUILDCC="gcc" CFLAGS="" CPPFLAGS="" LDFLAGS="" subst
make[4]: Entering directory '/private/tmp/lede-test-e2fsprogs/build_dir/target-x86_64_musl-1.1.14/e2fsprogs-1.43.1/util'
        CC subst.c
subst.c:332:14: error: variable has incomplete type 'struct stat'
        struct stat stbuf;
                    ^
subst.c:332:9: note: forward declaration of 'struct stat'
        struct stat stbuf;
               ^
subst.c:391:8: warning: implicit declaration of function 'fstat' is invalid in C99 [-Wimplicit-function-declaration]
                        if (fstat(fd, &stbuf) == 0) {
                            ^
subst.c:437:12: warning: implicit declaration of function 'fchmod' is invalid in C99 [-Wimplicit-function-declaration]
                                (void) fchmod(ofd, 0444);
                                       ^
2 warnings and 1 error generated.
make[4]: *** [Makefile:329: subst.o] Error 1


So if the builders were able to compile e2fsprogs without probs, maybe it is target specific ? or as I am building on my macbook with OS X, I will try today a vanilla linux machine to check that direction as well.


Greetings Thomas


> On 22 Jun 2016, at 19:34, lede-bugs at lists.infradead.org wrote:
> 
> maybe your tree is in some inconsistent state ? the builders managed to
> build that package for all targets successfully last night.
> 
> 	John
> 
> 
> _______________________________________________
> lede-bugs mailing list
> lede-bugs at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-bugs



From lede-bugs at lists.infradead.org  Fri Jun 24 03:42:31 2016
From: lede-bugs at lists.infradead.org (LEDE Bugs)
Date: Fri, 24 Jun 2016 10:42:31 -0000
Subject: [FS#27] BT Home Hub 5 Type A - Switch problem when enabling WAN port
 - Task opened
In-Reply-To: <FS27@bugs.lede-project.org>
References: <FS27@bugs.lede-project.org>
Message-ID: <mailman.46548.1468830540.1639.lede-bugs@lists.infradead.org>

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

User who did this - Bill L. (bill888) 

Attached to Project - LEDE Project
Summary - BT Home Hub 5 Type A - Switch problem when enabling WAN port
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 - 
LEDE Project r742
BT Home Hub 5 Type A with WAN port (port 5) enabled as a DHCP client, connected to existing LAN (subnet 192.168.1.x)

Client wired to Home Hub LAN port can initially ping and connect to external websites for first few seconds after Home Hub is powered up, but it stops working seconds later.

/etc/config/network:

config interface 'loopback'
	option ifname 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fdcc:19d3:6f89::/48'

config atm-bridge 'atm'
	option vpi '1'
	option vci '32'
	option encaps 'llc'
	option payload 'bridged'

config interface 'lan'
	option type 'bridge'
	option ifname 'eth0.1'
	option proto 'static'
	option netmask '255.255.255.0'
	option ip6assign '60'
	option ipaddr '192.168.0.1'

config device 'lan_dev'
	option name 'eth0.1'
	option macaddr '40:f2:01:18:0f:ec'

config interface 'wan'
	option ifname 'eth1.2'
	option _orig_ifname 'eth1.2'
	option _orig_bridge 'false'
	option proto 'dhcp'
        # broadcast setting makes NO difference to reported bug.
	option broadcast '1'

config device 'wan_dev'
	option name 'eth1.2'
	option macaddr '40:f2:01:18:0f:ed'

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

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

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

LUCI reports WAN port of BT Home Hub 5 successfully acquires local LAN IP address 192.168.1.74 and DNS server settings.
---------

Capture of serial console.  Attempt to ping external IP address such as google DNS server from console.  Eventually fails.


ROM VER: 1.1.4
CFG 06
NAND
NAND Read OK

DDR autotuning Rev 0.3d
DDR size from 0xa0000000 - 0xa7ffffff
DDR check ok... start booting...



U-Boot 2010.06-LANTIQ-v-2.2.46 (Sep 07 2013 - 02:57:04 on tester at clean-machine)

CLOCK CPU 500M RAM 250M
secure boot
DRAM:  125 MiB
NAND:  ONFI flash detected
ONFI param page 0 valid
NAND device: Manufacturer ID: 0x01, Chip ID: 0xf1 (AMD S34ML01G1)
128 MiB
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: Bad block at 0x0000023c0000
nand_read_bbt: Bad block at 0x000004bc0000
nand_read_bbt: Bad block at 0x000005500000
In:    serial
Out:   serial
Err:   serial
Net:   Internal phy(GE) firmware version: 0x841b
vr9 Switch

Type "run flash_nfs" to mount root filesystem over NFS

Hit any key to stop autoboot:  0
Creating 1 MTD partitions on "nand0":
0x000000100000-0x000007f80000 : "mtd=0"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=0"
UBI: MTD device size:            126 MiB
UBI: number of good PEBs:        1009
UBI: number of bad PEBs:         3
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     4
UBI: available PEBs:             7
UBI: total number of reserved PEBs: 1002
UBI: number of PEBs reserved for bad PEB handling: 10
UBI: max/mean erase counter: 118/18
Volume kernel found at volume id 0
read 0 bytes from volume 0 to 80800000(buf address)
Read [1806336] bytes
## Booting kernel from Legacy Image at 80800000 ...
   Image Name:   MIPS OpenWrt Linux-4.4.13
   Created:      2016-06-19  18:16:23 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1799932 Bytes = 1.7 MiB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

[    0.000000] Linux version 4.4.13 (mkresin at desktop) (gcc version 5.3.0 (LEDE GCC 5.3.0 r608) ) #1 SMP Sun Jun 19 18:30:14 UTC 2016
[    0.000000] SoC: xRX200 rev 1.2
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019556 (MIPS 34Kc)
[    0.000000] MIPS: machine is BTHOMEHUBV5A - BT Home Hub 5A
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 08000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    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] Detected 1 available secondary CPU(s)
[    0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] PERCPU: Embedded 9 pages/cpu @8110c000 s8128 r8192 d20544 u36864
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyLTQ0,115200 init=/etc/preinit
[    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=00041ca3
[    0.000000] Readback ErrCtl register=00041ca3
[    0.000000] Memory: 122908K/131072K available (4029K kernel code, 175K rwdata, 1172K rodata, 1264K init, 222K bss, 8164K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:256
[    0.000000] Setting up vectored interrupts
[    0.000000] Setting up IPI vectored interrupts
[    0.000000] CPU Clock: 500MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041786 ns
[    0.000011] sched_clock: 32 bits at 250MHz, resolution 4ns, wraps every 8589934590ns
[    0.007877] Calibrating delay loop... 332.54 BogoMIPS (lpj=665088)
[    0.042371] pid_max: default: 32768 minimum: 301
[    0.047243] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.053788] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.064870] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    0.064885] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.065117] CPU1 revision is: 00019556 (MIPS 34Kc)
[    0.124589] Synchronize counters for CPU 1: done.
[    0.129514] Brought up 2 CPUs
[    0.137057] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.146877] pinctrl core: initialized pinctrl subsystem
[    0.152802] NET: Registered protocol family 16
[    0.163415] pinctrl-xway 1e100b10.pinmux: Init done
[    0.169457] dma-xway 1e104100.dma: Init done - hw rev: 7, ports: 7, channels: 28
[    0.282556] dcdc-xrx200 1f106a00.dcdc: Core Voltage : 1016 mV
[    0.301654] PCI host bridge /fpi at 10000000/pci at E105400 ranges:
[    0.307329]  MEM 0x0000000018000000..0x0000000019ffffff
[    0.312601]   IO 0x000000001ae00000..0x000000001affffff
[    0.437395] ath9k,eeprom ath9k_eep: failed to load eeprom address
[    0.468347] usbcore: registered new interface driver usbfs
[    0.473947] usbcore: registered new interface driver hub
[    0.479326] usbcore: registered new device driver usb
[    0.485081] PCI host bridge to bus 0000:00
[    0.489107] pci_bus 0000:00: root bus resource [mem 0x18000000-0x19ffffff]
[    0.496022] pci_bus 0000:00: root bus resource [io  0x1ae00000-0x1affffff]
[    0.502984] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
[    0.509810] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.518513] pci 0000:00:0e.0: BAR 0: assigned [mem 0x18000000-0x1800ffff]
[    0.525427] PCI host bridge to bus 0000:01
[    0.529448] pci_bus 0000:01: root bus resource [mem 0x1c000000-0x1cffffff]
[    0.536359] pci_bus 0000:01: root bus resource [io  0x1d800000-0x1d8fffff]
[    0.543320] pci_bus 0000:01: root bus resource [??? 0x00000000 flags 0x0]
[    0.550182] pci_bus 0000:01: No busn resource found for root bus, will use [bus 01-ff]
[    0.558258] ifx_pcie_rc_class_early_fixup: fixed pcie host bridge to pci-pci bridge
[    0.576485] pci 0000:01:00.0: bridge configuration invalid ([bus 02-00]), reconfiguring
[    0.585662] pci 0000:01:00.0: BAR 8: assigned [mem 0x1c000000-0x1c1fffff]
[    0.592376] pci 0000:01:00.0: BAR 9: assigned [mem 0x1c200000-0x1c2fffff pref]
[    0.599667] pci 0000:02:00.0: BAR 0: assigned [mem 0x1c000000-0x1c1fffff 64bit]
[    0.607063] pci 0000:02:00.0: BAR 6: assigned [mem 0x1c200000-0x1c20ffff pref]
[    0.614318] pci 0000:01:00.0: PCI bridge to [bus 02]
[    0.619360] pci 0000:01:00.0:   bridge window [mem 0x1c000000-0x1c1fffff]
[    0.626188] pci 0000:01:00.0:   bridge window [mem 0x1c200000-0x1c2fffff pref]
[    0.633570] ifx_pcie_bios_map_irq port 0 dev 0000:01:00.0 slot 0 pin 1
[    0.640171] ifx_pcie_bios_map_irq dev 0000:01:00.0 irq 144 assigned
[    0.646540] ifx_pcie_bios_map_irq port 0 dev 0000:02:00.0 slot 0 pin 1
[    0.653172] ifx_pcie_bios_map_irq dev 0000:02:00.0 irq 144 assigned
[    0.661291] clocksource: Switched to clocksource MIPS
[    0.669062] NET: Registered protocol family 2
[    0.674304] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.681248] TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
[    0.687599] TCP: Hash tables configured (established 1024 bind 1024)
[    0.694119] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.699971] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.706603] NET: Registered protocol family 1
[    0.711499] gptu: totally 6 16-bit timers/counters
[    0.716372] gptu: misc_register on minor 63
[    0.720558] gptu: succeeded to request irq 126
[    0.725038] gptu: succeeded to request irq 127
[    0.729534] gptu: succeeded to request irq 128
[    0.734077] gptu: succeeded to request irq 129
[    0.738596] gptu: succeeded to request irq 130
[    0.743095] gptu: succeeded to request irq 131
[    0.749305] phy-xrx200 gphy-xrx200: requesting lantiq/vr9_phy11g_a2x.bin
[    0.756753] phy-xrx200 gphy-xrx200: booting GPHY0 firmware at 7A00000
[    0.763117] phy-xrx200 gphy-xrx200: booting GPHY1 firmware at 7A00000
[    0.872765] futex hash table entries: 512 (order: 2, 16384 bytes)
[    0.897786] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.903542] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.916336] io scheduler noop registered
[    0.920205] io scheduler deadline registered (default)
[    0.926543] 1e100c00.serial: ttyLTQ0 at MMIO 0x1e100c00 (irq = 112, base_baud = 0) is a lantiq,asc
[    0.935456] console [ttyLTQ0] enabled
[    0.935456] console [ttyLTQ0] enabled
[    0.942792] bootconsole [early0] disabled
[    0.942792] bootconsole [early0] disabled
[    0.953845] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xf1
[    0.958912] nand: AMD/Spansion S34ML01G1
[    0.962724] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    0.971993] Bad block table found at page 65472, version 0x01
[    0.979570] Bad block table found at page 65408, version 0x01
[    0.984186] nand_read_bbt: bad block at 0x0000023c0000
[    0.989068] nand_read_bbt: bad block at 0x000004bc0000
[    0.994175] nand_read_bbt: bad block at 0x000005500000
[    0.999447] 4 ofpart partitions found on MTD device 14000000.nand-parts
[    1.005931] Creating 4 MTD partitions on "14000000.nand-parts":
[    1.011869] 0x000000000000-0x0000000a0000 : "u-boot"
[    1.018983] 0x0000000a0000-0x0000000c0000 : "uboot-env"
[    1.025054] 0x0000000c0000-0x000000100000 : "caldata_backup"
[    1.031504] 0x000000100000-0x000007f80000 : "ubi"
[    1.144846] libphy: lantiq,xrx200-mdio: probed
[    1.217981] eth0: attached PHY [Lantiq XWAY PEF7071] (phy_addr=0:00, irq=-1)
[    1.285959] eth0: attached PHY [Lantiq XWAY PEF7071] (phy_addr=0:01, irq=-1)
[    1.353946] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.4] (phy_addr=0:11, irq=-1)
[    1.421943] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.4] (phy_addr=0:13, irq=-1)
[    1.493964] eth1: attached PHY [Lantiq XWAY PEF7071] (phy_addr=0:05, irq=-1)
[    1.501846] wdt 1f8803f0.watchdog: Init done
[    1.511509] NET: Registered protocol family 10
[    1.516525] NET: Registered protocol family 17
[    1.519756] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    1.532214] 8021q: 802.1Q VLAN Support v1.8
[    1.540299] ath9k,eeprom ath9k_eep: pci slot: 14
[    1.543525] pci 0000:00:0e.0: fixup device configuration
[    1.550481] pci 0000:00:0e.0: fixup info: [168c:002d] revision 01 class 0x028000
[    1.556502] ath9k,eeprom ath9k_eep: loaded ath9k eeprom
[    1.565852] UBI: auto-attach mtd3
[    1.567553] ubi0: attaching mtd3
[    2.219236] ubi0: scanning is finished
[    2.262267] ubi0: attached mtd3 (name "ubi", size 126 MiB)
[    2.266362] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[    2.273252] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[    2.279916] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[    2.286731] ubi0: good PEBs: 1009, bad PEBs: 3, corrupted PEBs: 0
[    2.292827] ubi0: user volume: 4, internal volumes: 1, max. volumes count: 128
[    2.300036] ubi0: max/mean erase counter: 118/18, WL threshold: 4096, image sequence number: 255302225
[    2.309347] ubi0: available PEBs: 0, total reserved PEBs: 1009, PEBs reserved for bad PEB handling: 17
[    2.318797] ubi0: background thread "ubi_bgt0d" started, PID 342
[    2.320924] block ubiblock0_1: created from ubi0:1(rootfs)
[    2.320936] ubiblock: device ubiblock0_1 (rootfs) set to be root[    2.348929] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    2.358771] Freeing unused kernel memory: 1264K (80544000 - 80680000)
[    3.955688] init: Console is alive
[    3.958085] init: - watchdog -
[    4.568660] eth0: port 4 got link
[    6.566306] SCSI subsystem initialized
[    6.576996] dwc2 1e101000.ifxhcd: requested GPIO 495
[    6.580616] dwc2 1e101000.ifxhcd: Configuration mismatch. Forcing host mode
[    7.445552] dwc2 1e101000.ifxhcd: DWC OTG Controller
[    7.449124] dwc2 1e101000.ifxhcd: new USB bus registered, assigned bus number 1
[    7.456498] dwc2 1e101000.ifxhcd: irq 62, io mem 0x00000000
[    7.461988] dwc2 1e101000.ifxhcd: Hardware does not support descriptor DMA mode -
[    7.469442] dwc2 1e101000.ifxhcd: falling back to buffer DMA mode.
[    7.477111] hub 1-0:1.0: USB hub found
[    7.479601] hub 1-0:1.0: 1 port detected
[    7.488402] usbcore: registered new interface driver usb-storage
[    7.503767] init: - preinit -
[    7.950686] random: procd urandom read with 69 bits of entropy available
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[   11.265997] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 437
[   11.459683] UBIFS (ubi0:2): recovery needed
[   11.822800] UBIFS (ubi0:2): recovery completed
[   11.825989] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs_data"
[   11.833681] UBIFS (ubi0:2): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[   11.843600] UBIFS (ubi0:2): FS size: 118573056 bytes (113 MiB, 919 LEBs), journal size 5935104 bytes (5 MiB, 46 LEBs)
[   11.854213] UBIFS (ubi0:2): reserved for root: 4952683 bytes (4836 KiB)
[   11.860839] UBIFS (ubi0:2): media format: w4/r0 (latest is w4/r0), UUID 3076099A-3245-4285-A490-0B4743539E0B, small LPT model
[   11.876455] mount_root: switching to jffs2 overlay
[   11.917636] procd: - early -
[   11.919238] procd: - watchdog -
[   12.633276] eth0: port 4 lost link
[   12.681475] procd: - ubus -
[   12.847597] procd: - init -
Please press Enter to activate this console.
[   13.305331] IFXOS, Version 1.5.19 (c) Copyright 2009, Lantiq Deutschland GmbH
[   13.315603] NET: Registered protocol family 8
[   13.318579] NET: Registered protocol family 20
[   13.329376] PPP generic driver version 2.4.2
[   13.339328] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   13.364973] Lantiq (VRX) DSL CPE MEI driver, version 1.4.8.5, (c) 2013 Lantiq Deutschland GmbH

Lantiq CPE API Driver version: DSL CPE API V4.16.6.3
[   13.385860]
[   13.385860] Predefined debug level: 3
[   13.394393] Loading modules backported from Linux version wt-2016-05-12-0-g7a54796
[   13.400590] Backport generated by backports.git backports-20160216-0-ge3c56e4
[   13.472028] PCI: Enabling device 0000:01:00.0 (0000 -> 0002)
[   13.476430] PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
[   13.482223] ath10k_pci 0000:02:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[   13.675575] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
[   13.684907] ath10k_pci 0000:02:00.0: Falling back to user helper
[   13.745179] firmware ath10k!pre-cal-pci-0000:02:00.0.bin: firmware_loading_store: map pages failed
[   14.108536] ath10k_pci 0000:02:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[   14.116464] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[   14.132378] ath10k_pci 0000:02:00.0: firmware ver 10.2.4.97 api 5 features no-p2p crc32 f91e34f2
[   14.139982] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[   14.150219] ath10k_pci 0000:02:00.0: Falling back to user helper
[   14.207676] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
[   14.215862] ath10k_pci 0000:02:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[   14.937331] random: nonblocking pool is initialized
[   15.271030] ath10k_pci 0000:02:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal file max-sta 128 raw 0 hwcrypto 1
[   15.402899] ip_tables: (C) 2000-2006 Netfilter Core Team
[   15.415842] Infineon Technologies DEU driver version 2.0.0
[   15.422888] IFX DEU DES initialized (multiblock).
[   15.428212] IFX DEU AES initialized (multiblock).
[   15.432183] IFX DEU ARC4 initialized (multiblock).
[   15.436810] IFX DEU SHA1 initialized.
[   15.440490] IFX DEU MD5 initialized.
[   15.447146] IFX DEU SHA1_HMAC initialized.
[   15.452050] IFX DEU MD5_HMAC initialized.
[   15.467271] nf_conntrack version 0.5.0 (1940 buckets, 7760 max)
[   15.536445] NET: Registered protocol family 24
[   15.558670] xt_time: kernel timezone is -0000
[   15.589059] PCI: Enabling device 0000:00:0e.0 (0000 -> 0002)
[   15.599259] ath: phy1: Ignoring endianness difference in EEPROM magic bytes.
[   15.628151] ieee80211 phy1: Atheros AR9287 Rev:2 mem=0xb8000000, irq=30
[   24.901931] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   24.920700] device eth0.1 entered promiscuous mode
[   24.924174] device eth0 entered promiscuous mode
[   24.937884] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[   25.007210] device eth1 entered promiscuous mode
[   25.797674] eth0: port 4 got link
[   25.800413] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   25.813698] br-lan: port 1(eth0.1) entered forwarding state
[   25.818033] br-lan: port 1(eth0.1) entered forwarding state
[   25.832222] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[   27.821224] br-lan: port 1(eth0.1) entered forwarding state



BusyBox v1.24.2 () built-in shell (ash)

     _________
    /        /\      _    ___ ___  ___
   /  LE    /  \    | |  | __|   \| __|
  /    DE  /    \   | |__| _|| |) | _|
 /________/  LE  \  |____|___|___/|___|                      lede-project.org
 \        \   DE /
  \    LE  \    /  -----------------------------------------------------------
   \  DE    \  /    Reboot (HEAD, r742)
    \________\/    -----------------------------------------------------------

root at lede:/#
root at lede:/#
root at lede:/# [   33.797392] eth1: port 5 got link

root at lede:/# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=54 time=9.422 ms
64 bytes from 8.8.8.8: seq=1 ttl=54 time=8.321 ms
64 bytes from 8.8.8.8: seq=2 ttl=54 time=8.277 ms
64 bytes from 8.8.8.8: seq=3 ttl=54 time=8.139 ms
64 bytes from 8.8.8.8: seq=4 ttl=54 time=9.094 ms
64 bytes from 8.8.8.8: seq=5 ttl=54 time=8.285 ms
64 bytes from 8.8.8.8: seq=6 ttl=54 time=8.171 ms
64 bytes from 8.8.8.8: seq=7 ttl=54 time=8.605 ms
64 bytes from 8.8.8.8: seq=8 ttl=54 time=8.323 ms
^C
--- 8.8.8.8 ping statistics ---
9 packets transmitted, 9 packets received, 0% packet loss
round-trip min/avg/max = 8.139/8.515/9.422 ms
root at lede:/# ping 8.8.4.4
PING 8.8.4.4 (8.8.4.4): 56 data bytes
64 bytes from 8.8.4.4: seq=0 ttl=57 time=13.242 ms
64 bytes from 8.8.4.4: seq=0 ttl=57 time=14.290 ms (DUP!)
^C
--- 8.8.4.4 ping statistics ---
5 packets transmitted, 1 packets received, 1 duplicates, 80% packet loss
round-trip min/avg/max = 13.242/13.766/14.290 ms
root at lede:/#
root at lede:/# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C
--- 8.8.8.8 ping statistics ---
10 packets transmitted, 0 packets received, 100% packet loss
root at lede:/#
root at lede:/#





-----------------
Another capture of serial console.

PC wired to LAN port of BT Home Hub 5 and attempting to ping external IP address, and try to access external website.  Works Very briefly, but then eventually fails.


U-Boot 2010.06-LANTIQ-v-2.2.46 (Sep 07 2013 - 02:57:04 on tester at clean-machine)

CLOCK CPU 500M RAM 250M
secure boot
DRAM:  125 MiB
NAND:  ONFI flash detected
ONFI param page 0 valid
NAND device: Manufacturer ID: 0x01, Chip ID: 0xf1 (AMD S34ML01G1)
128 MiB
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: Bad block at 0x0000023c0000
nand_read_bbt: Bad block at 0x000004bc0000
nand_read_bbt: Bad block at 0x000005500000
In:    serial
Out:   serial
Err:   serial
Net:   Internal phy(GE) firmware version: 0x841b
vr9 Switch

Type "run flash_nfs" to mount root filesystem over NFS

Hit any key to stop autoboot:  0
Creating 1 MTD partitions on "nand0":
0x000000100000-0x000007f80000 : "mtd=0"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=0"
UBI: MTD device size:            126 MiB
UBI: number of good PEBs:        1009
UBI: number of bad PEBs:         3
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     4
UBI: available PEBs:             7
UBI: total number of reserved PEBs: 1002
UBI: number of PEBs reserved for bad PEB handling: 10
UBI: max/mean erase counter: 118/18
Volume kernel found at volume id 0
read 0 bytes from volume 0 to 80800000(buf address)
Read [1806336] bytes
## Booting kernel from Legacy Image at 80800000 ...
   Image Name:   MIPS OpenWrt Linux-4.4.13
   Created:      2016-06-19  18:16:23 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1799932 Bytes = 1.7 MiB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

[    0.000000] Linux version 4.4.13 (mkresin at desktop) (gcc version 5.3.0 (LEDE GCC 5.3.0 r608) ) #1 SMP Sun Jun 19 18:30:14 UTC 2016
[    0.000000] SoC: xRX200 rev 1.2
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019556 (MIPS 34Kc)
[    0.000000] MIPS: machine is BTHOMEHUBV5A - BT Home Hub 5A
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 08000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    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] Detected 1 available secondary CPU(s)
[    0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] PERCPU: Embedded 9 pages/cpu @8110c000 s8128 r8192 d20544 u36864
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyLTQ0,115200 init=/etc/preinit
[    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=00051da1
[    0.000000] Readback ErrCtl register=00051da1
[    0.000000] Memory: 122908K/131072K available (4029K kernel code, 175K rwdata, 1172K rodata, 1264K init, 222K bss, 8164K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:256
[    0.000000] Setting up vectored interrupts
[    0.000000] Setting up IPI vectored interrupts
[    0.000000] CPU Clock: 500MHz
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041786 ns
[    0.000011] sched_clock: 32 bits at 250MHz, resolution 4ns, wraps every 8589934590ns
[    0.007877] Calibrating delay loop... 332.54 BogoMIPS (lpj=665088)
[    0.042371] pid_max: default: 32768 minimum: 301
[    0.047243] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.053787] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.064868] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[    0.064883] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.065116] CPU1 revision is: 00019556 (MIPS 34Kc)
[    0.124580] Synchronize counters for CPU 1: done.
[    0.129502] Brought up 2 CPUs
[    0.137050] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.146868] pinctrl core: initialized pinctrl subsystem
[    0.152793] NET: Registered protocol family 16
[    0.163402] pinctrl-xway 1e100b10.pinmux: Init done
[    0.169453] dma-xway 1e104100.dma: Init done - hw rev: 7, ports: 7, channels: 28
[    0.282529] dcdc-xrx200 1f106a00.dcdc: Core Voltage : 1016 mV
[    0.301629] PCI host bridge /fpi at 10000000/pci at E105400 ranges:
[    0.307303]  MEM 0x0000000018000000..0x0000000019ffffff
[    0.312575]   IO 0x000000001ae00000..0x000000001affffff
[    0.437371] ath9k,eeprom ath9k_eep: failed to load eeprom address
[    0.468118] usbcore: registered new interface driver usbfs
[    0.473732] usbcore: registered new interface driver hub
[    0.479151] usbcore: registered new device driver usb
[    0.484924] PCI host bridge to bus 0000:00
[    0.488985] pci_bus 0000:00: root bus resource [mem 0x18000000-0x19ffffff]
[    0.495904] pci_bus 0000:00: root bus resource [io  0x1ae00000-0x1affffff]
[    0.502865] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
[    0.509685] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.518358] pci 0000:00:0e.0: BAR 0: assigned [mem 0x18000000-0x1800ffff]
[    0.525281] PCI host bridge to bus 0000:01
[    0.529310] pci_bus 0000:01: root bus resource [mem 0x1c000000-0x1cffffff]
[    0.536220] pci_bus 0000:01: root bus resource [io  0x1d800000-0x1d8fffff]
[    0.543181] pci_bus 0000:01: root bus resource [??? 0x00000000 flags 0x0]
[    0.550015] pci_bus 0000:01: No busn resource found for root bus, will use [bus 01-ff]
[    0.558099] ifx_pcie_rc_class_early_fixup: fixed pcie host bridge to pci-pci bridge
[    0.576316] pci 0000:01:00.0: bridge configuration invalid ([bus 02-00]), reconfiguring
[    0.585481] pci 0000:01:00.0: BAR 8: assigned [mem 0x1c000000-0x1c1fffff]
[    0.592203] pci 0000:01:00.0: BAR 9: assigned [mem 0x1c200000-0x1c2fffff pref]
[    0.599493] pci 0000:02:00.0: BAR 0: assigned [mem 0x1c000000-0x1c1fffff 64bit]
[    0.606889] pci 0000:02:00.0: BAR 6: assigned [mem 0x1c200000-0x1c20ffff pref]
[    0.614145] pci 0000:01:00.0: PCI bridge to [bus 02]
[    0.619187] pci 0000:01:00.0:   bridge window [mem 0x1c000000-0x1c1fffff]
[    0.626014] pci 0000:01:00.0:   bridge window [mem 0x1c200000-0x1c2fffff pref]
[    0.633396] ifx_pcie_bios_map_irq port 0 dev 0000:01:00.0 slot 0 pin 1
[    0.639997] ifx_pcie_bios_map_irq dev 0000:01:00.0 irq 144 assigned
[    0.646366] ifx_pcie_bios_map_irq port 0 dev 0000:02:00.0 slot 0 pin 1
[    0.653013] ifx_pcie_bios_map_irq dev 0000:02:00.0 irq 144 assigned
[    0.661135] clocksource: Switched to clocksource MIPS
[    0.669163] NET: Registered protocol family 2
[    0.674390] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.681285] TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
[    0.687709] TCP: Hash tables configured (established 1024 bind 1024)
[    0.694206] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.700059] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.706693] NET: Registered protocol family 1
[    0.711597] gptu: totally 6 16-bit timers/counters
[    0.716467] gptu: misc_register on minor 63
[    0.720653] gptu: succeeded to request irq 126
[    0.725170] gptu: succeeded to request irq 127
[    0.729621] gptu: succeeded to request irq 128
[    0.734171] gptu: succeeded to request irq 129
[    0.738691] gptu: succeeded to request irq 130
[    0.743190] gptu: succeeded to request irq 131
[    0.749391] phy-xrx200 gphy-xrx200: requesting lantiq/vr9_phy11g_a2x.bin
[    0.756839] phy-xrx200 gphy-xrx200: booting GPHY0 firmware at 7A00000
[    0.763195] phy-xrx200 gphy-xrx200: booting GPHY1 firmware at 7A00000
[    0.872824] futex hash table entries: 512 (order: 2, 16384 bytes)
[    0.896720] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.902510] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.915385] io scheduler noop registered
[    0.919273] io scheduler deadline registered (default)
[    0.925663] 1e100c00.serial: ttyLTQ0 at MMIO 0x1e100c00 (irq = 112, base_baud = 0) is a lantiq,asc
[    0.934570] console [ttyLTQ0] enabled
[    0.934570] console [ttyLTQ0] enabled
[    0.941906] bootconsole [early0] disabled
[    0.941906] bootconsole [early0] disabled
[    0.952847] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xf1
[    0.957819] nand: AMD/Spansion S34ML01G1
[    0.961734] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    0.971008] Bad block table found at page 65472, version 0x01
[    0.978575] Bad block table found at page 65408, version 0x01
[    0.983175] nand_read_bbt: bad block at 0x0000023c0000
[    0.988091] nand_read_bbt: bad block at 0x000004bc0000
[    0.993249] nand_read_bbt: bad block at 0x000005500000
[    0.998457] 4 ofpart partitions found on MTD device 14000000.nand-parts
[    1.004948] Creating 4 MTD partitions on "14000000.nand-parts":
[    1.010855] 0x000000000000-0x0000000a0000 : "u-boot"
[    1.017999] 0x0000000a0000-0x0000000c0000 : "uboot-env"
[    1.024065] 0x0000000c0000-0x000000100000 : "caldata_backup"
[    1.030658] 0x000000100000-0x000007f80000 : "ubi"
[    1.143965] libphy: lantiq,xrx200-mdio: probed
[    1.213807] eth0: attached PHY [Lantiq XWAY PEF7071] (phy_addr=0:00, irq=-1)
[    1.281783] eth0: attached PHY [Lantiq XWAY PEF7071] (phy_addr=0:01, irq=-1)
[    1.349767] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.4] (phy_addr=0:11, irq=-1)
[    1.417766] eth0: attached PHY [Lantiq XWAY VR9 GPHY 11G v1.4] (phy_addr=0:13, irq=-1)
[    1.489788] eth1: attached PHY [Lantiq XWAY PEF7071] (phy_addr=0:05, irq=-1)
[    1.497665] wdt 1f8803f0.watchdog: Init done
[    1.507223] NET: Registered protocol family 10
[    1.512237] NET: Registered protocol family 17
[    1.515466] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    1.527925] 8021q: 802.1Q VLAN Support v1.8
[    1.536012] ath9k,eeprom ath9k_eep: pci slot: 14
[    1.539236] pci 0000:00:0e.0: fixup device configuration
[    1.546193] pci 0000:00:0e.0: fixup info: [168c:002d] revision 01 class 0x028000
[    1.552212] ath9k,eeprom ath9k_eep: loaded ath9k eeprom
[    1.561539] UBI: auto-attach mtd3
[    1.563237] ubi0: attaching mtd3
[    2.214377] ubi0: scanning is finished
[    2.257326] ubi0: attached mtd3 (name "ubi", size 126 MiB)
[    2.261427] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[    2.268319] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[    2.274988] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[    2.281797] ubi0: good PEBs: 1009, bad PEBs: 3, corrupted PEBs: 0
[    2.287893] ubi0: user volume: 4, internal volumes: 1, max. volumes count: 128
[    2.295104] ubi0: max/mean erase counter: 118/18, WL threshold: 4096, image sequence number: 255302225
[    2.304414] ubi0: available PEBs: 0, total reserved PEBs: 1009, PEBs reserved for bad PEB handling: 17
[    2.313862] ubi0: background thread "ubi_bgt0d" started, PID 342
[    2.315975] block ubiblock0_1: created from ubi0:1(rootfs)
[    2.315987] ubiblock: device ubiblock0_1 (rootfs) set to be roo[    2.344044] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    2.353939] Freeing unused kernel memory: 1264K (80544000 - 80680000)
[    3.951100] init: Console is alive
[    3.953522] init: - watchdog -
[    4.472070] eth0: port 4 got link
[    6.561779] SCSI subsystem initialized
[    6.572193] dwc2 1e101000.ifxhcd: requested GPIO 495
[    6.575816] dwc2 1e101000.ifxhcd: Configuration mismatch. Forcing host mode
[    7.437391] dwc2 1e101000.ifxhcd: DWC OTG Controller
[    7.440959] dwc2 1e101000.ifxhcd: new USB bus registered, assigned bus number 1
[    7.448336] dwc2 1e101000.ifxhcd: irq 62, io mem 0x00000000
[    7.453855] dwc2 1e101000.ifxhcd: Hardware does not support descriptor DMA mode -
[    7.461288] dwc2 1e101000.ifxhcd: falling back to buffer DMA mode.
[    7.468959] hub 1-0:1.0: USB hub found
[    7.471467] hub 1-0:1.0: 1 port detected
[    7.480232] usbcore: registered new interface driver usb-storage
[    7.486314] init: - preinit -
[    7.932358] random: procd urandom read with 68 bits of entropy available
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[   11.243719] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 437
[   11.443232] UBIFS (ubi0:2): recovery needed
[   11.801003] UBIFS (ubi0:2): recovery completed
[   11.804204] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs_data"
[   11.811942] UBIFS (ubi0:2): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[   11.821858] UBIFS (ubi0:2): FS size: 118573056 bytes (113 MiB, 919 LEBs), journal size 5935104 bytes (5 MiB, 46 LEBs)
[   11.832470] UBIFS (ubi0:2): reserved for root: 4952683 bytes (4836 KiB)
[   11.839095] UBIFS (ubi0:2): media format: w4/r0 (latest is w4/r0), UUID 3076099A-3245-4285-A490-0B4743539E0B, small LPT model
[   11.856027] mount_root: switching to jffs2 overlay
[   11.897871] procd: - early -
[   11.899464] procd: - watchdog -
[   12.653219] eth0: port 4 lost link
[   12.660881] procd: - ubus -
[   12.826965] procd: - init -
Please press Enter to activate this console.
[   13.282524] IFXOS, Version 1.5.19 (c) Copyright 2009, Lantiq Deutschland GmbH
[   13.292864] NET: Registered protocol family 8
[   13.295874] NET: Registered protocol family 20
[   13.306755] PPP generic driver version 2.4.2
[   13.316709] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   13.340859] Lantiq (VRX) DSL CPE MEI driver, version 1.4.8.5, (c) 2013 Lantiq Deutschland GmbH

Lantiq CPE API Driver version: DSL CPE API V4.16.6.3
[   13.361683]
[   13.361683] Predefined debug level: 3
[   13.370218] Loading modules backported from Linux version wt-2016-05-12-0-g7a54796
[   13.376412] Backport generated by backports.git backports-20160216-0-ge3c56e4
[   13.447764] PCI: Enabling device 0000:01:00.0 (0000 -> 0002)
[   13.452164] PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
[   13.457970] ath10k_pci 0000:02:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[   13.651198] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
[   13.660558] ath10k_pci 0000:02:00.0: Falling back to user helper
[   13.720746] firmware ath10k!pre-cal-pci-0000:02:00.0.bin: firmware_loading_store: map pages failed
[   14.083004] ath10k_pci 0000:02:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[   14.090946] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[   14.106801] ath10k_pci 0000:02:00.0: firmware ver 10.2.4.97 api 5 features no-p2p crc32 f91e34f2
[   14.114422] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[   14.124647] ath10k_pci 0000:02:00.0: Falling back to user helper
[   14.181926] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
[   14.190088] ath10k_pci 0000:02:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[   15.005152] random: nonblocking pool is initialized
[   15.245489] ath10k_pci 0000:02:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal file max-sta 128 raw 0 hwcrypto 1
[   15.376526] ip_tables: (C) 2000-2006 Netfilter Core Team
[   15.389626] Infineon Technologies DEU driver version 2.0.0
[   15.396609] IFX DEU DES initialized (multiblock).
[   15.402099] IFX DEU AES initialized (multiblock).
[   15.406267] IFX DEU ARC4 initialized (multiblock).
[   15.410634] IFX DEU SHA1 initialized.
[   15.414273] IFX DEU MD5 initialized.
[   15.417979] IFX DEU SHA1_HMAC initialized.
[   15.422756] IFX DEU MD5_HMAC initialized.
[   15.438283] nf_conntrack version 0.5.0 (1940 buckets, 7760 max)
[   15.504248] NET: Registered protocol family 24
[   15.526208] xt_time: kernel timezone is -0000
[   15.556060] PCI: Enabling device 0000:00:0e.0 (0000 -> 0002)
[   15.566252] ath: phy1: Ignoring endianness difference in EEPROM magic bytes.
[   15.597126] ieee80211 phy1: Atheros AR9287 Rev:2 mem=0xb8000000, irq=30
[   24.895725] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   24.914918] device eth0.1 entered promiscuous mode
[   24.918374] device eth0 entered promiscuous mode
[   24.932462] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[   25.018428] device eth1 entered promiscuous mode
[   25.041497] eth0: port 4 got link
[   25.049843] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   25.065324] br-lan: port 1(eth0.1) entered forwarding state
[   25.069675] br-lan: port 1(eth0.1) entered forwarding state
[   25.094805] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[   27.073051] br-lan: port 1(eth0.1) entered forwarding state

[   55.041221] eth1: port 5 got link
[   58.214821] eth0: tx ring full
[   58.257474] eth0: tx ring full
[   69.694267] eth0: tx ring full
[   72.660442] eth0: tx ring full
[   93.041206] eth1: port 5 lost link


BusyBox v1.24.2 () built-in shell (ash)

     _________
    /        /\      _    ___ ___  ___
   /  LE    /  \    | |  | __|   \| __|
  /    DE  /    \   | |__| _|| |) | _|
 /________/  LE  \  |____|___|___/|___|                      lede-project.org
 \        \   DE /
  \    LE  \    /  -----------------------------------------------------------
   \  DE    \  /    Reboot (HEAD, r742)
    \________\/    -----------------------------------------------------------



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


