Re: [LEDE-DEV] WRT1900ACS - Kernel 4.4.12 boot failure

2016-06-07 Thread Claudio Leite
On 06/07/2016 11:00 AM, Claudio Leite wrote: On 06/07/2016 10:48 AM, Dheeran Senthilvel wrote: [snip] ===> Step 3: Reboot <== After the above procedures, I don’t have the error anymore. Great -- so you're all set, as far as you can tell? Wonder what really caused the problem in

Re: [LEDE-DEV] WRT1900ACS - Kernel 4.4.12 boot failure

2016-06-07 Thread Dheeran Senthilvel
===> Step 1 : resetenv & reset <=== __ __ _ _ | \/ | __ _ _ _| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_|\_/ \___|_|_| _ _ _ | | | | | __ ) ___ ___ | |_

Re: [LEDE-DEV] WRT1900ACS - Kernel 4.4.12 boot failure

2016-06-07 Thread Claudio Leite
Thanks for the clear output. * Dheeran Senthilvel (dheeranm...@gmail.com) wrote: [snip] > ===> Step 3: Intrupt boot into failsafe <=== > > 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 > f > -

Re: [LEDE-DEV] WRT1900ACS - Kernel 4.4.12 boot failure

2016-06-07 Thread Dheeran Senthilvel
===> Step 1: Reboot <=== BusyBox v1.24.2 () built-in shell (ash) _ //\ ____ ___ ___ / LE/ \| | | __| \| __| /DE /\ | |__| _|| |) | _| // LE \ ||___|___/|___| lede-project.org \\

Re: [LEDE-DEV] WRT1900ACS - Kernel 4.4.12 boot failure

2016-06-07 Thread Claudio Leite
Hello Dheeran, * Dheeran Senthilvel (dheeranm...@gmail.com) wrote: > Hi, > Yes even after I run resetenv followed by a reset command, the > fw_printenv produces the same output every time. > > > On 07-Jun-2016, at 3:54 PM, Claudio Leite wrote: > > > > Hi, > > > > *

Re: [LEDE-DEV] libubox, procd: init process hangs

2016-06-07 Thread Yousong Zhou
On 7 June 2016 at 06:11, Xinxing Hu wrote: > Hi Guys, > > I have another idea about this issue. Maybe it is not kernel, but uloop > related. I read procd and libubox code a little bit, and it seems there is a > potential issue existing in uloop_run(). > > In general,

Re: [LEDE-DEV] WRT1900ACS - Kernel 4.4.12 boot failure

2016-06-07 Thread Dheeran Senthilvel
Hi, Yes even after I run resetenv followed by a reset command, the fw_printenv produces the same output every time. > On 07-Jun-2016, at 3:54 PM, Claudio Leite wrote: > > Hi, > > * Dheeran Senthilvel (dheeranm...@gmail.com) wrote: >> Hi, >> Thanks for the

[LEDE-DEV] ACL kernel config options and 3.18

2016-06-07 Thread Daniel Curran-Dickinson
iVBORw0KGgoNSUhEUgAAADAwAQMAAABtzGvEBlBMVEX///8AAABVwtN+eklEQVQY04XQzQ2EIBAF4IdMDIc5UAIlUIKlWMr0ZiMm28jOj+6iMXEOfBBmXgJAVLGlBkU3wcZ9I3Q7EdrAveowx6hZ0q6QJDsRnHlJwr+W4CHF7vLqTEenXABeUnSssbP8SdwdjTHEwcFDtQGKFuWjH8Lna8vAmfEF3NMPdAOsBscASUVORK5CYII= Content-Type: text/plain;

[LEDE-DEV] WRT1900ACS - Kernel 4.4.12 boot failure

2016-06-07 Thread Dheeran Senthilvel
Hi, Compiled build r504 followed by clean build. Still not clear what is causing the boot error mentioned previously in mailing list - May 2016. • [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure Dheeran Senthilvel • [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot