I'm also having these problems. The bug is very easy to reproduce. Just using the jffs2 image instead of squashfs, the problems are shown with the first boot, and you can see lot of funny names just listing /etc/init.d
root@(none):/# ls -l /etc/init.d/ -rwxr-xr-x 1 root root 1993 Jan 2 2014 boot -rwxr-xr-x 1 root root 368 Dec 20 2013 ciciixixmeme -rwxr-xr-x 1 root root 729 Dec 20 2013 cron -rwxr-xr-x 1 root root 3920 Jan 2 2014 dropbear -rwxr-xr-x 1 root root 4173 Jan 2 2014 eleld?d -rwxr-xr-x 1 root root 262 Jan 2 2014 firellll -rwxr-xr-x 1 root root 2015 Dec 20 2013 led -rwxr-xr-x 1 root root 926 Dec 20 2013 lnlnet -rwxr-xr-x 1 root root 1694 Jan 2 2014 log -rwxr-xr-x 1 root root 835 Dec 20 2013 lucihchcmimigrate -rwxr-xr-x 1 root root 308 Dec 20 2013 nene -rwxr-xr-x 1 root root 125 Dec 20 2013 scsctl -rwxr-xr-x 1 root root 13640 Jan 2 2014 smsmq?q -rwxr-xr-x 1 root root 718 Dec 20 2013 snsnd?d -rwxr-xr-x 1 root root 945 Jan 2 2014 twtwk?k -rwxr-xr-x 1 root root 3324 Jan 2 2014 uhttpd -rwxr-xr-x 1 root root 106 Jan 2 2014 umount -rwxr-xr-x 1 root root 522 Dec 20 2013 ununndnd It's like a baby learning to talk. Since this is happening when using a jffs2 image, overlayfs isn't used, isn't it?, then the problem shouldn't be related to the overlayfs driver. I noticed another thing, probably not related to this, when I configure the main thread to be the second core In CFE, openwrt gets stalled booting the second core, I suppose the code lacks mechanisms to detect which core is up and boot the other. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
