[LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure

[Dheeran Senthilvel]

> On 22-May-2016, at 3:25 PM, Dheeran Senthilvel <dheeranmech at gmail.com> wrote:
> 
> 
>> On 22-May-2016, at 3:22 PM, Dheeran Senthilvel <dheeranmech at gmail.com> wrote:
>> 
>> 
>>> On 22-May-2016, at 3:21 PM, Dheeran Senthilvel <dheeranmech at gmail.com> wrote:
>>> 
>>> 
>>>> On 22-May-2016, at 3:02 PM, Dheeran Senthilvel <dheeranmech at gmail.com> wrote:
>>>> 
>>>> 
>>>>> On 21-May-2016, at 7:55 PM, Dheeran Senthilvel <dheeranmech at gmail.com> wrote:
>>>>> 
>>>>> 
>>>>>> On 21-May-2016, at 6:48 PM, Felix Fietkau <nbd at nbd.name> wrote:
>>>>>> 
>>>>>> On 2016-05-21 14:05, Dheeran Senthilvel wrote:
>>>>>>> Hi Guys,
>>>>>>> 	
>>>>>>> Nice work there getting everything to Linux 4.4.11. Tested the new
>>>>>>> build (r321 dated 20/05/2016) Everything is seems to work pretty
>>>>>>> decently, except that upon reboot (both manually or through command
>>>>>>> line) the device is struck. When serially accessed an error is seen
>>>>>> Please make a clean build from the latest version and reflash the image
>>>>>> from the boot loader. I just pushed some flash driver fixes...
>>>>>> 
>>>>>> - Felix
>>>>> 
>>>>> Thanks will try and will reply.
>>>>> 
>>>> 
>>>> Hi, 
>>>> 
>>>> 	Pretty quick work there, having merged the new mwlwifi driver. The driver does improve performance - 374MBytes/s at 2.4g and 1645MBytes/s at 5g using iperf for 30sec flooding. Also the long pings reported previously on OEM and lede/openwrt seems to have been rectified on this new driver.
>>>> 
>>>> 	Also the LEDs now work by default. Thanks again for that quick fix.
>>>> 
>>>> 	But the NAND fix did not fix my problem of reboot/boot crashing. Same error
>>>> 
>>>> Regards
>>>> Dheeran
>>> 
>>> Running r339
>>> 
>>> root at lede:/# uname -a 
>>> 
>>> Linux lede 4.4.11 #1 SMP Sat May 21 22:47:44 UTC 2016 armv7l GNU/Linux
>>> 
>>> This is serial output after reboot command 
>>> 
>>> [ 1237.769778] br-lan: port 3(wlan0) entered disabled state
>>> [ 1237.775198] br-lan: port 2(wlan1) entered disabled state
>>> [ 1237.780566] br-lan: port 1(eth1) entered disabled state
>>> [ 1237.788228] device eth1 left promiscuous mode
>>> [ 1237.792676] br-lan: port 1(eth1) entered disabled state
>>> [ 1237.803425] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
>>> [ 1237.810859] device wlan0 left promiscuous mode
>>> [ 1237.815361] br-lan: port 3(wlan0) entered disabled state
>>> [ 1237.820853] device wlan1 left promiscuous mode
>>> [ 1237.825347] br-lan: port 2(wlan1) entered disabled state
>>> [ 1239.000372] UBIFS (ubi1:0): un-mount UBI device 1
>>> [ 1239.005105] UBIFS (ubi1:0): background thread "ubifs_bgt1_0" stops
>>> crond[985]: USER root pid 2226 cmd /sbin/fan_ctrl.sh
>>> [ 1242.121994] reboot: Restarting system
>>> S-ENV offset == 0x240000
>>> 
>>> If you need anything else please mail me i will definitely try to my best to help to diagnose the problem.
>>> 
>>> Regards
>>> Dheeran
>> 
>> Haven’t setup a build system on my PC. Currently testing from the snapshot from the repos
>> 
> 
> root at lede:/# env
> SHLVL=3
> HOME=/root
> mtdparts=armada-nand:2048K(uboot)ro,256K(u_env),256K(s_env),1m at 9m(devinfo),40m at 10m(kernel),34m at 16m(rootfs),40m at 50m(alt_kernel),34m at 56m(alt_rootfs),80m at 10m(ubifs
> ),- at 90m(syscfg)
> PS1=\u@\h:\w\$
> mangled_fs=jffs2
> TERM=linux
> PATH=/usr/sbin:/usr/bin:/sbin:/bin
> PWD=/
> 
> 
> 

Hi,
	Successfully compiled a new build from the repo, but yet the boot failure hasn’t been solved. Same error. Is there a way to verify if the before said "nand patch”
 is used during compilation.

Regards 
Dheeran