Boot loop with latest git master

Linksys WRT1900AC v1 (mamba)
r19294 works, r19320 doesn't. Did anything significant change between these two? Is this a bug?

I get this error with sysupgrade image:

And uploading factory image leads to this boot loop that doesn't print any error. It just continuously restarts itself:

[    2.905853] UBI: auto-attach mtd5
[    2.909187] ubi0: attaching mtd5
[    2.915021] mv88e6085 f1072004.mdio-mii:00: Link is Up - 1Gbps/Full - flow control off
[    3.108396] ubi0: scanning is finished
[    3.120556] ubi0: attached mtd5 (name "ubi", size 36 MiB)
[    3.126005] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    3.132922] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    3.139731] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[    3.146725] ubi0: good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[    3.152760] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[    3.160004] ubi0: max/mean erase counter: 2/1, WL threshold: 256, image sequence number: 1648663444
[    3.169085] ubi0: available PEBs: 0, total reserved PEBs: 288, PEBs reserved for bad PEB handling: 20
[    3.178817] ubi0: background thread "ubi_bgt0d" started, PID 793
[    3.179174] block ubiblock0_0: created from ubi0:0(rootfs)
[    3.190377] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem
[    3.206336] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    3.216902] devtmpfs: mounted
[    3.221112] Freeing unused kernel memory: 1024K
[    3.263123] Run /sbin/init as init process
[    3.538744] init: Console is alive
[    3.542342] init: - watchdog -
[    3.885302] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    3.917117] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    3.928652] init: - preinit -
[    4.424661] random: jshn: uninitialized urandom read (4 bytes read)
[    4.461277] random: jshn: uninitialized urandom read (4 bytes read)
[    4.752358] random: jshn: uninitialized urandom read (4 bytes read)
[    4.975262] mvneta f1070000.ethernet eth0: configuring for fixed/rgmii-id link mode
[    4.983550] mvneta f1070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[    4.991161] mv88e6085 f1072004.mdio-mii:00 lan1: configuring for phy/gmii link mode
[    4.999509] 8021q: adding VLAN 0 to HW filter on device lan1
[    5.005251] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
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
[   12.121510] reboot: Restarting system

BootROM 1.20
Booting from NAND flash

If you sysupgraded using the factory file instead of the sysupgrade file - then that's the problem. The warning stated not to use sysupgrade. It said to perform a "new installation".

You will have to follow the instructions properly to restore the device now. Try loading the factory image properly (i.e. when you first installed OpenWrt) and let us know your results.

There was a kernel reservation space change some time back, but if you were already running that first version you should already have made the change by way of a factory flash; both partitions?

1 Like

Might be the busybox bug that was introduced yesterday (r19319), and fixed an hour ago (as r19332)

With the Linksys mvebu routers, there is no OEM header at the image start, so forcing a factory image in sysupgrade should actually work.


Second partition is r19294, working, and I'm writing r19320 to the first partition.

OK, that might explain the boot loop. I'll make a new image today.
But why the sysupgrade error?

No good answer for you, but the warning surfaces if your /etc/config/system does not contain a compat_version option set by once upgrading to the new firmware.

If you have e.g. restored an old backup, it is well possible that your settings do not contain the indicator that your current settings are compatible with the new firmware.

Boot loop solved in r19337, but sysupgrade warning is still there. I wrote the factory image, not sysupgrade.

There is no compat_version in /etc/config/system, but there is compat_version 1.1 in /etc/board.json
After deleting both, the system recreates them as they are. Not 2.0.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.