Re: [LEDE-DEV] WRT1900ACS - Kernel 4.4.12 boot failure
00 altKernAddr=0x320 altKernSize=0x060 altnandboot=setenv bootargs console=ttyS0,115200 root=/dev/mtdblock7 ro rootdelay=1 rootfstype=jffs2 earlyprintk $mtdparts;nand read $defaultLoadAddr $altKernAd dr $altKernSize; bootm $defaultLoadAddr auto_recovery=yes autoload=no baudrate=115200 boot_order=hd_scr usb_scr mmc_scr hd_img usb_img mmc_img pxe net_img net_scr boot_part=1 boot_part_ready=3 bootargs_dflt=$console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_para ms clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel bootargs_end=:10.4.50.254:255.255.255.0:Armada38x:eth0:none bootargs_root=root=/dev/nfs rw bootcmd=run nandboot bootcmd_auto=stage_boot $boot_order bootcmd_fdt=tftpboot 0x200 $image_name;tftpboot $fdtaddr $fdtfile;setenv bootargs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip= $ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x200 - $fdtaddr; bootcmd_fdt_boot=tftpboot 0x200 $image_name; setenv bootargs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$boo targs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x200 - $fdtaddr; bootcmd_fdt_edit=tftpboot $fdtaddr $fdtfile; fdt addr $fdtaddr; setenv bootcmd $bootcmd_fdt_boot bootcmd_lgcy=tftpboot 0x200 $image_name; setenv bootargs $bootargs_dflt; bootm 0x200; bootdelay=3 cacheShare=no console=console=ttyS0,115200 defaultLoadAddr=0x200 device_partition=0:1 disaMvPnp=no eeeEnable=no enaClockGating=no enaCpuStream=no enaFPU=yes enaMonExt=no enaWrAllo=no eth1addr=00:50:43:7a:d1:e5 eth1mtu=1500 eth2addr=00:50:43:7a:45:d5 eth2mtu=1500 eth3addr=00:50:43:e1:45:8a eth3mtu=1500 ethact=egiga0 ethaddr=00:50:43:45:e1:f5 ethmtu=1500 ethprime=egiga0 fdt_addr=204 fdt_skip_update=no fdtaddr=0x100 fdtfile=armada-38x-modular.dtb firmwareName=cobra.img flash_alt_image=tftpboot $defaultLoadAddr $firmwareName && nand erase $altKernAddr $altFwSize && nand write $defaultLoadAddr $altKernAddr $filesize flash_pri_image=tftpboot $defaultLoadAddr $firmwareName && nand erase $priKernAddr $priFwSize && nand write $defaultLoadAddr $priKernAddr $filesize ide_path=/ image_name=uImage initrd_name=uInitrd ipaddr=192.168.1.1 kernel_addr_r=208 lcd0_enable=0 lcd0_params=640x480-16@60 lcd_panel=0 loadaddr=0x0200 loads_echo=0 mtdids=nand0=armada-nand mtdparts=mtdparts=armada-nand:2048K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),34m@16m(rootfs),40m@50m(alt_kernel),34m@56m(alt_rootfs),80m@ 10m(ubifs),-@90m(syscfg) mvNetConfig=mv_net_config=4,(00:50:43:11:11:11,0:1:2:3),mtu=1500 mv_pon_addr=00:50:43:e5:45:7a nandEcc=nfcConfig=4bitecc nandboot=setenv bootargs console=ttyS0,115200 root=/dev/mtdblock5 ro rootdelay=1 rootfstype=jffs2 earlyprintk $mtdparts;nand read $defaultLoadAddr $priKernAddr $priKernSize; bootm $defaultLoadAddr netbsd_en=no netmask=255.255.255.0 netretry=no pcieTune=no pexMode=RC priFwSize=0x280 priKernAddr=0x0a0 priKernSize=0x060 pxe_files_load=:default.arm-armadaxp-db:default.arm-armadaxp:default.arm pxefile_addr_r=310 ramdisk_addr_r=288 rootpath=/srv/nfs/ sata_delay_reset=0 sata_dma_mode=yes script_addr_r=300 script_name=boot.scr serverip=192.168.1.254 standalone=fsload 0x200 $image_name;setenv bootargs $console $nandEcc $mtdparts root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm 0x200; stderr=serial stdin=serial stdout=serial update_both_images=tftpboot $defaultLoadAddr $firmwareName && nand erase $priKernAddr $priFwSize && nand erase $altKernAddr $altFwSize && nand write $defaultLoa dAddr $priKernAddr $filesize && nand write $defaultLoadAddr $altKernAddr $filesize usb0Mode=host usbActive=0 usbType=2 vxworks_en=no yuk_ethaddr=00:00:00:EE:41:71 ===> Step 3: Reboot <== After the above procedures, I don’t have the error anymore. Wonder what really caused the problem in first place. Also when we reboot from Failsafe the recovery is automatically triggered - is this normal. One more doubt would be, should 'env reset' be in this order. resetenv ——> reset ——> printing ——> saveenv ——> reset I am building from the current git, will flash that and see if after the flash - the error occurs or not. Thank you, very much… I have been trying to solve this for about 3 weeks. Now I can keep lede and won’t have to flash stock when I leave for work. Regards Dheeran senthilvel > On 07-Jun-2016, at 7:40 PM, Claudio Leite <lei...@gmail.com> wrote: > > Thanks for the clear output. > > * Dheeran Senthilvel (dheeranm...@gmail.com) wrote: > [snip] >> ===> Step 3: Intrupt boot into failsafe <
Re: [LEDE-DEV] WRT1900ACS - Kernel 4.4.12 boot failure
-
root@WRT1900ACS:/# fw_printenv
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath}
ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200
auto_recovery=yes
root@WRT1900ACS:/# strings /dev/mtd1
Z'ybootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath}
ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200
auto_recovery=yes
I think this will help. Let me know if you need to do any other test.
> On 07-Jun-2016, at 7:03 PM, Claudio Leite <lei...@gmail.com> wrote:
>
> 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 <lei...@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> * Dheeran Senthilvel (dheeranm...@gmail.com) wrote:
>>>> Hi,
>>>> Thanks for the reply. But I already documented it in my previous
>>>> mails in May 2016.
>>>> This is temporary, once again when reboot is done the same error occurs.
>>>
>>> I see, sorry for the noise.
>>>
>>>>
>>>> I haven't been able to solve this issue. Also if altnandboot is
>>>> performed and used having lede in nandboot there seems to be no problem.
>>>> But once lede boots the error is imminent upon reboot.
>>>
>>> I'm not sure I understand this part. Is the same image, with no custom
>>> settings, stored in both partitions?
>> Sorry for that! What I mean to say is if I boot ‘altnandboot’ (recovery
>> official firmware) having lede in the primary_image partition, the problem
>> doesn’t occur. Once I invoke nandboot and allow lede to boot and issue a
>> reboot command, the error occurs. I gave this statement to clarify that the
>> problem lede and not the 'hardware' or 'u-boot’.
>
> OK, I understand now-you have the factory firmware on the secondary
> partition.
>
>>>
>>> What does fw_printenv look like after a "resetenv; reset" and boot into
>>> a recent LEDE? At that point, the linksys-recovery stuff will already
>>> have run.
>> But I really don’t understand the problem. This OpenWrt WiKi page -
>> https://wiki.openwrt.org/doc/techref/bootloader/uboot.config , shows that
>> this kind of error show only when the partition map is incorrect (That is
>> what i understood) and as the following command shows that flash mapping
>> recognised by lede is incorrect
>
> It's not incorrect; it's just how LEDE/OpenWrt defines it. The partition
> map is baked into the kernel image via the dtb. The relevant partition
> is mtd1, u_env (and s_env, for the 'resetbc' stuff) which is correctly
> defined and matches up with the bootloader's (and factory firmware's)
> expectations.
>
> From your own output:
>
> lede:
>
> [0.973995] 0x-0x0020 : "u-boot"
> [0.979273] 0x0020-0x0024 : "u_env"
> [0.984435] 0x0024-0x0028 : "s_env"
>
> factory:
>
> 0x-0x0020 : "uboot"
> 0x0020-0x0024 : "u_env"
> 0x0024-0x0028 : "s_env"
>
> Given the output you posted from fw_printenv earlier,
>
> root at WRT1900ACS:/# fw_printenv
> bootcmd=bootp; setenv bootargs root=/dev/nfs
> nfsroot=${serverip}:${rootpath}
> ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
> bootdelay=5
> baudrate=115200
> auto_recovery=yes
>
> there's some very strange corruption going on. It would probably help to
> determine if this is happening during the auto_recovery/resetbc stuff
> during boot, when it writes to u-env. If there's something off still
> with the NAND driver this could cause the corruption you see.
>
> Could you try this:
>
> 1. reboot and run "resetenv; reset"
> 2. boot into LEDE, but drop into failsafe mode (when prompted, type
> f)
>
> 3. from failsafe mode, run
> strings /dev/mtd1
>
> this should be the complete and long set of default variables.
>
> 4. still from failsafe, run 'reboot'
>
> During this time nothing new is written to u-env, so upon a reboot it
> should still be functional. The 'printenv' command from u-boot should
> list the variables intact, and it should boot normally.
>
> Once booted into LEDE normally, if the fw_setenv command during the boot
> sequence is causing the corruption, fw_printenv or "strings /dev/mtd1"
> will now show some sort of corrupted output.
>
> -Claudio
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] WRT1900ACS - Kernel 4.4.12 boot failure
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 <lei...@gmail.com> wrote: > > Hi, > > * Dheeran Senthilvel (dheeranm...@gmail.com) wrote: >> Hi, >> Thanks for the reply. But I already documented it in my previous >> mails in May 2016. >> This is temporary, once again when reboot is done the same error occurs. > > I see, sorry for the noise. > >> >> I haven't been able to solve this issue. Also if altnandboot is >> performed and used having lede in nandboot there seems to be no problem. >> But once lede boots the error is imminent upon reboot. > > I'm not sure I understand this part. Is the same image, with no custom > settings, stored in both partitions? Sorry for that! What I mean to say is if I boot ‘altnandboot’ (recovery official firmware) having lede in the primary_image partition, the problem doesn’t occur. Once I invoke nandboot and allow lede to boot and issue a reboot command, the error occurs. I gave this statement to clarify that the problem lede and not the 'hardware' or 'u-boot’. > > What does fw_printenv look like after a "resetenv; reset" and boot into > a recent LEDE? At that point, the linksys-recovery stuff will already > have run. But I really don’t understand the problem. This OpenWrt WiKi page - https://wiki.openwrt.org/doc/techref/bootloader/uboot.config , shows that this kind of error show only when the partition map is incorrect (That is what i understood) and as the following command shows that flash mapping recognised by lede is incorrect root@WRT1900ACS:/# cat /proc/mtd dev:size erasesize name mtd0: 0020 0002 "u-boot" mtd1: 0004 0002 "u_env" mtd2: 0004 0002 "s_env" mtd3: 0010 0002 "devinfo" mtd4: 0280 0002 "kernel1" mtd5: 0220 0002 "ubi" mtd6: 0280 0002 "kernel2" mtd7: 0220 0002 "rootfs2" mtd8: 0260 0002 "syscfg" mtd9: 0068 0002 “unused_area" whereas boot to altnandboot gives something like this armada-nand f10d.nand: Initialize HAL based NFC in 8bit mode with DMA Disabled using BCH 4bit ECC NAND device: Manufacturer ID: 0x01, Chip ID: 0xf1 (AMD/Spansion NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64 Bad block table found at page 65472, version 0x01 Bad block table found at page 65408, version 0x01 10 cmdlinepart partitions found on MTD device armada-nand Creating 10 MTD partitions on "armada-nand": 0x-0x0020 : "uboot" 0x0020-0x0024 : "u_env" 0x0024-0x0028 : "s_env" 0x0090-0x00a0 : "devinfo" 0x00a0-0x0320 : "kernel" 0x0100-0x0320 : "rootfs" 0x0320-0x05a0 : "alt_kernel" 0x0380-0x05a0 : "alt_rootfs" 0x00a0-0x05a0 : "ubifs" 0x05a0-0x0800 : "syscfg" > > -Claudio > >> On 07-Jun-2016 3:27 pm, "Claudio Leite" <lei...@gmail.com> wrote: >> >>> * Dheeran Senthilvel (dheeranm...@gmail.com) wrote: >>>> Hi, >>>> Compiled build r504 followed by clean build. Still not clear what >>> is causing the boot error mentioned previously in mailing list - May 2016. >>> [snip] >>>> >>>> auto_recovery_check changes bootcmd: run nandboot >>>> Hit any key to stop autoboot: 0 >>>> ## Error: "nandboot" not defined >>> >>> Have you tried the 'resetenv' command from u-boot? >>> >>> resetenv- resetenv - earse environment sector to reset all >>> variables to default. >>> >>> I haven't tried this on a WRT1900AC, but on the EA4500 (which has a >>> somewhat similar u-boot) it correctly resets everything to default >>> values. Given that your u-boot settings are gone one way or another (as >>> your fw_printenv later shows) this might be worth a try. >>> >>> -Claudio >>> ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] WRT1900ACS - Kernel 4.4.12 boot failure
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 failure Syrone Wong • [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure Felix Fietkau • [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure Dheeran Senthilvel • [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure Dheeran Senthilvel • [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure Felix Fietkau • [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure Dheeran Senthilvel • [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure Dheeran Senthilvel • [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure Dheeran Senthilvel • [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure Dheeran Senthilvel Found some info that might help diagnose the problem. === Initial Boot_Official Firm == __ __ _ _ | \/ | __ _ _ _| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_|\_/ \___|_|_| _ _ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/|/ \___/ \___/ \__| ** LOADER ** U-Boot 2013.01 (Mar 27 2015 - 16:50:46) Marvell version: 2014_T3.0p6 Boot version : v1.0.13 Board: RD-NAS-88F6820-DDR3 SoC: MV88F6820 Rev A0 running 2 CPUs CPU: ARM Cortex A9 MPCore (Rev 1) LE CPU 0 CPU@ 1600 [MHz] L2 @ 800 [MHz] TClock @ 200 [MHz] DDR@ 800 [MHz] DDR 32 Bit Width, FastPath Memory Access, DLB Enabled, ECC Disabled DRAM: 512 MiB Map: Code:0x1fea9000:0x1ff7632c BSS: 0x1ffef6b4 Stack: 0x1f9a8f20 Heap:0x1f9a9000:0x1fea9000 raise: Signal # 8 caught U-ENV offset == 0x20 raise: Signal # 8 caught U-ENV offset == 0x20 U-Boot Environment: 0x0020:0x0022 (NAND) NAND: 128 MiB MMC: mv_sdh: 0 DEVINFO offset == 0x90 U-ENV offset == 0x20 U-ENV offset == 0x20 *** Warning - bad CRC, using default environment S-ENV offset == 0x24 auto_recovery [u_env] get auto_recovery == yes [u_env] get auto_recovery == yes [u_env] get boot_part == 1 [u_env] get boot_part_ready == 3 auto_recovery enabled:1, boot_part:1, boot_part_ready:3 S-ENV offset == 0x24 [boot_count_read] block:0x24, size:128KB, records:64 [boot_count_read_record] boot_count:0, next_record:47 [boot_count_write] erase:0, auto_recovery->block_offset:0x24 offset=0x257800 Updating boot_count ... [boot_count_write] offset:0x257800 , length:2048 done PCI-e 0 (IF 0 - bus 0) Root Complex Interface, Detected Link X1, GEN 2.0 PCI-e 1 (IF 1 - bus 1) Root Complex Interface, Detected Link X1, GEN 1.1 USB2.0 0: Host Mode USB3.0 1: Host Mode USB3.0 0: Host Mode Board configuration detected: mvEthE6171SwitchBasicInit init Net: | port | Interface | PHY address | ||---|--| | egiga0 | RGMII | 0x01 | | egiga1 | SGMII | 0x00 | egiga0 [PRIME], egiga1 auto_recovery_check changes bootcmd: run nandboot Hit any key to stop autoboot: 0 NAND read: device 0 offset 0xa0, size 0x60 6291456 bytes read: OK ## Booting kernel from Legacy Image at 0200 ... Image Name: Linksys WRT1900ACS Router Created: 2015-10 ———x———x———x———x——— === Initial Boot_LEDE(r504) == __ __ _ _ | \/ | __ _ _ _| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_|\_/ \___|_|_| _ _ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/|/ \___/ \___/ \__| ** LOADER ** U-Boot 2013.01 (Mar 27 2015 - 16:50:46) Marvell version: 2014_T3.0p6 Boot version : v1.0.13 Board: RD-NAS-88F6820-DDR3 SoC: MV88F6820 Rev A0 running 2 CPUs CPU: ARM Cortex A9 MPCore (Rev 1) LE CPU 0 CPU@ 1600 [MHz] L2 @ 800 [MHz] TClock @ 200 [MHz] DDR@ 800 [MHz] DDR 32 Bit Width, FastPath Memory Access, DLB Enabled, ECC Disabled DRAM: 512 MiB Map: Code:0x1fea9000:0x1ff7632c BSS: 0x1ffef6b4 Stack: 0x1f9a8f20 Heap:0x1f9a9000:0x1fea9000 raise: Signal # 8 caught U-ENV offset == 0x20 ra
Re: [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure
> On 22-May-2016, at 3:25 PM, Dheeran Senthilvel <dheeranm...@gmail.com> wrote: > > >> On 22-May-2016, at 3:22 PM, Dheeran Senthilvel <dheeranm...@gmail.com> wrote: >> >> >>> On 22-May-2016, at 3:21 PM, Dheeran Senthilvel <dheeranm...@gmail.com> >>> wrote: >>> >>> >>>> On 22-May-2016, at 3:02 PM, Dheeran Senthilvel <dheeranm...@gmail.com> >>>> wrote: >>>> >>>> >>>>> On 21-May-2016, at 7:55 PM, Dheeran Senthilvel <dheeranm...@gmail.com> >>>>> wrote: >>>>> >>>>> >>>>>> On 21-May-2016, at 6:48 PM, Felix Fietkau <n...@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@2.4g and 1645MBytes/s@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@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 == 0x24 >>> >>> 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@lede:/# env > SHLVL=3 > HOME=/root > mtdparts=armada-nand:2048K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),34m@16m(rootfs),40m@50m(alt_kernel),34m@56m(alt_rootfs),80m@10m(ubifs > ),-@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 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure
> On 22-May-2016, at 3:22 PM, Dheeran Senthilvel <dheeranm...@gmail.com> wrote: > > >> On 22-May-2016, at 3:21 PM, Dheeran Senthilvel <dheeranm...@gmail.com> wrote: >> >> >>> On 22-May-2016, at 3:02 PM, Dheeran Senthilvel <dheeranm...@gmail.com> >>> wrote: >>> >>> >>>> On 21-May-2016, at 7:55 PM, Dheeran Senthilvel <dheeranm...@gmail.com> >>>> wrote: >>>> >>>> >>>>> On 21-May-2016, at 6:48 PM, Felix Fietkau <n...@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@2.4g and 1645MBytes/s@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@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 == 0x24 >> >> 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@lede:/# env SHLVL=3 HOME=/root mtdparts=armada-nand:2048K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),34m@16m(rootfs),40m@50m(alt_kernel),34m@56m(alt_rootfs),80m@10m(ubifs ),-@90m(syscfg) PS1=\u@\h:\w\$ mangled_fs=jffs2 TERM=linux PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/ ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure
> On 22-May-2016, at 3:21 PM, Dheeran Senthilvel <dheeranm...@gmail.com> wrote: > > >> On 22-May-2016, at 3:02 PM, Dheeran Senthilvel <dheeranm...@gmail.com> wrote: >> >> >>> On 21-May-2016, at 7:55 PM, Dheeran Senthilvel <dheeranm...@gmail.com> >>> wrote: >>> >>> >>>> On 21-May-2016, at 6:48 PM, Felix Fietkau <n...@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@2.4g and 1645MBytes/s@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@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 == 0x24 > > 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 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure
> On 21-May-2016, at 7:55 PM, Dheeran Senthilvel <dheeranm...@gmail.com> wrote: > > >> On 21-May-2016, at 6:48 PM, Felix Fietkau <n...@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@2.4g and 1645MBytes/s@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 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure
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
__ __ _ _
| \/ | __ _ _ _| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_|\_/ \___|_|_|
_ _ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/|/ \___/ \___/ \__|
** LOADER **
U-Boot 2013.01 (Mar 27 2015 - 16:50:46) Marvell version: 2014_T3.0p6
Boot version : v1.0.13
Board: RD-NAS-88F6820-DDR3
SoC: MV88F6820 Rev A0
running 2 CPUs
CPU: ARM Cortex A9 MPCore (Rev 1) LE
CPU 0
CPU@ 1600 [MHz]
L2 @ 800 [MHz]
TClock @ 200 [MHz]
DDR@ 800 [MHz]
DDR 32 Bit Width, FastPath Memory Access, DLB Enabled, ECC Disabled
DRAM: 512 MiB
Map: Code:0x1fea9000:0x1ff7632c
BSS: 0x1ffef6b4
Stack: 0x1f9a8f20
Heap:0x1f9a9000:0x1fea9000
raise: Signal # 8 caught
U-ENV offset == 0x20
raise: Signal # 8 caught
U-ENV offset == 0x20
U-Boot Environment: 0x0020:0x0022 (NAND)
NAND: 128 MiB
MMC: mv_sdh: 0
DEVINFO offset == 0x90
U-ENV offset == 0x20
U-ENV offset == 0x20
S-ENV offset == 0x24
auto_recovery
[u_env] get auto_recovery == yes
[u_env] get auto_recovery == yes
[u_env] get boot_part ==
set boot_part=1 as default value at u_env
[u_env] get boot_part_ready ==
set boot_part_ready=3 as default value at u_env
auto_recovery enabled:1, boot_part:1, boot_part_ready:3
S-ENV offset == 0x24
[boot_count_read] block:0x24, size:128KB, records:64
[boot_count_read_record] boot_count:0, next_record:51
[boot_count_write] erase:0, auto_recovery->block_offset:0x24 offset=0x259800
Updating boot_count ...
[boot_count_write] offset:0x259800 , length:2048
done
PCI-e 0 (IF 0 - bus 0) Root Complex Interface, Detected Link X1, GEN 2.0
PCI-e 1 (IF 1 - bus 1) Root Complex Interface, Detected Link X1, GEN 1.1
USB2.0 0: Host Mode
USB3.0 1: Host Mode
USB3.0 0: Host Mode
Board configuration detected:
mvEthE6171SwitchBasicInit init
Net:
| port | Interface | PHY address |
||---|--|
| egiga0 | RGMII | 0x01 |
| egiga1 | SGMII | 0x00 |
egiga0 [PRIME], egiga1
auto_recovery_check changes bootcmd: run nandboot
Hit any key to stop autoboot: 0
## Error: "nandboot" not defined
Marvell>>
## The env variables during error boot is as follows
##
Marvell>> printenv
CASset=max
MALLOC_len=5
MPmode=SMP
auto_recovery=yes
autoload=no
baudrate=115200
boot_order=hd_scr usb_scr mmc_scr hd_img usb_img mmc_img pxe net_img net_scr
boot_part=1
boot_part_ready=3
bootargs_dflt=$console $nandEcc $mtdparts $bootargs_root
nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig
video=dovefb:lcd0:$lcd0_para
ms clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel
bootargs_end=:10.4.50.254:255.255.255.0:Armada38x:eth0:none
bootargs_root=root=/dev/nfs rw
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath}
ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootcmd_auto=stage_boot $boot_order
bootcmd_fdt=tftpboot 0x200 $image_name;tftpboot $fdtaddr $fdtfile;setenv
bootargs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath
ip=
$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params
clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x200 -
$fdtaddr;
bootcmd_fdt_boot=tftpboot 0x200 $image_name; setenv bootargs $console
$nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath
ip=$ipaddr:$serverip$boo
targs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params
clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x200 -
$fdtaddr;
bootcmd_fdt_edit=tftpboot $fdtaddr $fdtfile; fdt addr $fdtaddr; setenv bootcmd
$bootcmd_fdt_boot
bootcmd_lgcy=tftpboot 0x200 $image_name; setenv bootargs $bootargs_dflt;
bootm 0x200;
bootdelay=5
cacheShare=no
console=console=ttyS0,115200
device_partition=0:1
disaMvPnp=no
eeeEnable=no
enaClockGating=no
enaCpuStream=no
enaFPU=yes
enaMonExt=no
enaWrAllo=no
eth1addr=00:50:43:87:dd:02
eth1mtu=1500
eth2addr=00:50:43:87:9c:02
eth2mtu=1500
eth3addr=00:50:43:dd:9c:87
eth3mtu=1500
ethact=egiga0
ethaddr=00:50:43:9c:dd:02
ethmtu=1500
ethprime=egiga0
fdt_addr=204
fdt_skip_update=no
fdtaddr=0x100
fdtfile=armada-38x-modular.dtb
ide_path=/
image_name=uImage
initrd_name=uInitrd
kernel_addr_r=208
lcd0_enable=0
lcd0_params=640x480-16@60
lcd_panel=0
loadaddr=0x0200
mtdids=nand0=armada-nand
Re: [LEDE-DEV] WRT1900ACS Testing
> On 19-May-2016, at 4:07 PM, Dheeran Senthilvel <dheeranm...@gmail.com> wrote: > > Hi, > I am currently running LEDE r274 build dated 18-May-2015. The build seems to > be stable as of now, have been flashing the images ever since the snapshot > was made available in the repository. Current Status of the device is as > follows, > > # Wireless - both 2.4Ghz (@297MB/s) and 5Ghz(@1079MB/s) are working > fine.(Speed tested using iperf). > > # USB - Not Tested > > # LEDs - Only Power, WiFi & LAN leds are functioning. WAN & USB are not > working (Similar OpenWrt Ticket - https://dev.openwrt.org/ticket/21825) > > #Terminal Output > > >> root@Shelby:~# lsmod > > ahci_mvebu 1653 0 > ahci_platform 2367 0 > armada_thermal 3284 0 > cfg80211 220675 2 mwlwifi > compat 13025 2 mac80211 > crc_ccitt979 1 ppp_async > ehci_hcd 34246 2 ehci_orion > ehci_orion 2563 0 > ehci_platform 4368 0 > gpio_button_hotplug 5988 0 > hwmon 2026 3 tmp421 > i2c_core 18339 3 tmp421 > i2c_dev 4551 0 > i2c_mv64xxx 7033 0 > ip6_tables 9625 3 ip6table_raw > ip6t_REJECT 1056 2 > ip6table_filter 682 1 > ip6table_mangle 1042 1 > ip6table_raw 648 0 > ip_tables 9775 4 iptable_nat > ipt_MASQUERADE 698 1 > ipt_REJECT 914 2 > iptable_filter 736 1 > iptable_mangle 868 1 > iptable_nat 1029 1 > iptable_raw 702 0 > ledtrig_usbdev 2307 0 > libahci19501 3 ahci_mvebu > libahci_platform4501 2 ahci_mvebu > libata127382 5 ahci_mvebu > mac80211 401118 1 mwlwifi > mmc_block 21754 0 > mmc_core 77838 2 mvsdio > mvsdio 7362 0 > mwlwifi69628 0 > nf_conntrack 60523 9 nf_nat_ipv4 > nf_conntrack_ipv4 6125 11 > nf_conntrack_ipv6 6564 6 > nf_conntrack_rtcache2461 0 > nf_defrag_ipv4 884 1 nf_conntrack_ipv4 > nf_defrag_ipv6 13185 1 nf_conntrack_ipv6 > nf_log_common 2407 2 nf_log_ipv4 > nf_log_ipv4 3218 0 > nf_log_ipv6 3663 0 > nf_nat 10036 4 nf_nat_ipv4 > nf_nat_ipv4 4054 1 iptable_nat > nf_nat_masquerade_ipv41509 1 ipt_MASQUERADE > nf_nat_redirect 919 1 xt_REDIRECT > nf_reject_ipv4 1911 1 ipt_REJECT > nf_reject_ipv6 2236 1 ip6t_REJECT > nls_base5190 1 usbcore > ppp_async 6521 0 > ppp_generic19930 3 pppoe > pppoe 8047 0 > pppox 1239 1 pppoe > pwm_fan 2840 0 > sata_mv26825 0 > scsi_mod 88117 3 usb_storage > sd_mod 23412 0 > slhc4543 1 ppp_generic > thermal_sys20307 2 armada_thermal > tmp421 2500 0 > usb_common 1676 1 usbcore > usb_storage37368 0 > usbcore 120847 8 ledtrig_usbdev > x_tables 10689 26 ipt_REJECT > xhci_hcd 81489 2 xhci_plat_hcd > xhci_pci2324 0 > xhci_plat_hcd 3897 0 > xt_CT 2797 0 > xt_LOG 851 0 > xt_REDIRECT 825 0 > xt_TCPMSS 2660 2 > xt_comment 511 62 > xt_conntrack2516 16 > xt_id506129 > xt_limit1241 20 > xt_mac 631 0 > xt_mark 704 0 > xt_multiport1308 0 > xt_nat 1329 0 > xt_state 801 0 > xt_tcpudp 1800 10 > xt_time 1670 0 > >> root@Shelby:~# cat /etc/config/system > > config system > option hostname 'Shelby' > option timezone 'IST-5:30' > option ttylogin '0' > > config timeserver 'ntp' > list server '0.openwrt.pool.ntp.org' > list server '1.openwrt.pool.ntp.org' > list server '2.openwrt.pool.ntp.org' > list server '3.openwrt.pool.ntp.org' > option enabled '1' > option enable_server '0' > > config led 'led_wan' > option name 'WAN' > option sysfs 'pca963x:shelby:white:wan' > option trigger 'netdev' > option mode 'link tx rx' >
