On Thu, Oct 22, 2020 at 02:36:51PM +0600, Roman Kuzmitskii wrote:
> yeah, i found that it is broken too.
> i tested on few octeon boards and all of them fall in ‘high memory device’ 
> category.
> 
> reverting commit brings back the working tree back.
> 
> i would suggest to revert for now and do better testing next time.

I don't really understand which commit broke your build:
commit 2812ea3acb88c7e3649c912d6ad761bf8818fc51 (origin/master, origin/HEAD)
Author: Petr Štetiar <yn...@true.cz>
Date:   Thu Oct 22 11:49:07 2020 +0200

Revert "target: select procd-{ujail,seccomp} if !SMALL_FLASH"

This reverts commit 6a56a6eb30799fcec9eecc3ee860dc4d8a5d952a as several
users have reported unbootable systems.

Ref: https://lists.openwrt.org/pipermail/openwrt-devel/2020-October/031838.html
Suggested-by: Roman Kuzmitskii <damex...@icloud.com>
Signed-off-by: Petr Štetiar <yn...@true.cz>

and did this fix it then?

> 
> related log after flashing image with that commit:
> 
> [   18.661817] procd: Create service ubus
> [   18.665645] procd: Start instance ubus::instance1
> [   18.670675] procd: Started instance ubus::instance1[614]
> [   18.676106] procd: running /etc/init.d/ubus running
> [   18.681303] procd: glob failed on /etc/init.d/ubus
> [   18.686204] procd: Instance ubus::instance1 exit with error code 65280 
> after 0 seconds
> [   18.711471] procd: Connection to ubus failed
> [   18.815073] procd: Connection to ubus failed
> [   19.018736] procd: Connection to ubus failed
> [   19.422610] procd: Connection to ubus failed
> [   19.695516] procd: Started instance ubus::instance1[615]
> [   19.703165] procd: Instance ubus::instance1 exit with error code 65280 
> after 0 seconds
> [   20.226890] procd: Connection to ubus failed
> [   20.711994] procd: Started instance ubus::instance1[616]
> [   20.719593] procd: Instance ubus::instance1 exit with error code 65280 
> after 0 seconds
> [   21.231312] procd: Connection to ubus failed
> [   21.728430] procd: Started instance ubus::instance1[617]
> [   21.736023] procd: Instance ubus::instance1 exit with error code 65280 
> after 0 seconds
> [   22.235724] procd: Connection to ubus failed
> [   22.744871] procd: Started instance ubus::instance1[618]
> [   22.752489] procd: Instance ubus::instance1 exit with error code 65280 
> after 0 seconds
> [   23.240180] procd: Connection to ubus failed
> [   23.654955] procd: Ping
> [   23.760869] procd: Started instance ubus::instance1[619]
> [   23.768453] procd: Instance ubus::instance1 exit with error code 65280 
> after 0 seconds
> [   24.245134] procd: Connection to ubus failed
> [   24.777303] procd: Started instance ubus::instance1[620]
> [   24.784902] procd: Instance ubus::instance1 exit with error code 65280 
> after 0 seconds
> [   25.249421] procd: Connection to ubus failed
> [   25.794608] procd: Started instance ubus::instance1[621]
> [   25.802266] procd: Instance ubus::instance1 exit with error code 65280 
> after 0 seconds
> [   26.253912] procd: Connection to ubus failed
> [   26.811123] procd: Started instance ubus::instance1[622]
> [   26.818762] procd: Instance ubus::instance1 exit with error code 65280 
> after 0 seconds
> [   27.258402] procd: Connection to ubus failed
> [   27.828596] procd: Started instance ubus::instance1[623]
> [   27.836209] procd: Instance ubus::instance1 exit with error code 65280 
> after 0 seconds
> [   28.262838] procd: Connection to ubus failed
> [   28.658590] procd: Ping
> [   28.844571] procd: Started instance ubus::instance1[624]
> [   28.852204] procd: Instance ubus::instance1 exit with error code 65280 
> after 0 seconds
> 
> also when you start a fresh built from initramfs - it boots bot gives lots of 
> segfaults:
> 
> [   37.210492] do_page_fault(): sending SIGSEGV to ujail for invalid read 
> access from 00000100f380dc81
> [   37.219578] epc = 000000aaaaea42dc in ujail[aaaae9e000+11000]
> [   37.225349] ra  = 000000aaaaea4840 in ujail[aaaae9e000+11000]
> [   42.235990] do_page_fault(): sending SIGSEGV to ujail for invalid read 
> access from 00000100f38a1c81
> [   42.245090] epc = 000000aaaafd02dc in ujail[aaaafca000+11000]
> [   42.250865] ra  = 000000aaaafd0840 in ujail[aaaafca000+11000]
> [   47.263899] do_page_fault(): sending SIGSEGV to ujail for invalid read 
> access from 00000100f3736c81
> [   47.272998] epc = 000000aaaad5c2dc in ujail[aaaad56000+11000]
> [   47.278774] ra  = 000000aaaad5c840 in ujail[aaaad56000+11000]
> [   52.291922] do_page_fault(): sending SIGSEGV to ujail for invalid read 
> access from 00000100f2f77c81
> [   52.301033] epc = 000000aaab0682dc in ujail[aaab062000+11000]
> [   52.306805] ra  = 000000aaab068840 in ujail[aaab062000+11000]
> [   54.313652] br-lan: port 1(eth0) entered blocking state
> [   54.318946] br-lan: port 1(eth0) entered disabled state
> [   54.324469] device eth0 entered promiscuous mode
> [   55.346609] eth0: 1000 Mbps Full duplex, port 0, queue 0
> [   56.360423] br-lan: port 1(eth0) entered blocking state
> [   56.365667] br-lan: port 1(eth0) entered forwarding state
> [   56.371366] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
> [   57.318164] do_page_fault(): sending SIGSEGV to ujail for invalid read 
> access from 00000100f3708c81
> [   57.327255] epc = 000000aaaae922dc in ujail[aaaae8c000+11000]
> [   57.333021] ra  = 000000aaaae92840 in ujail[aaaae8c000+11000]
> [   58.865884] do_page_fault(): sending SIGSEGV to ujail for invalid read 
> access from 00000100f3d9bc81
> [   58.874966] epc = 000000aaab8432dc in ujail[aaab83d000+11000]
> [   58.880736] ra  = 000000aaab843840 in ujail[aaab83d000+11000]
> [   59.365354] do_page_fault(): sending SIGSEGV to ujail for invalid read 
> access from 00000100f3797c81
> [   59.374432] epc = 000000aaab6d82dc in ujail[aaab6d2000+11000]
> [   59.380222] ra  = 000000aaab6d8840 in ujail[aaab6d2000+11000]
> 
> 
> 
> > On Oct 22, 2020, at 2:15 PM, e9hack <e9h...@gmail.com> wrote:
> > 
> > Hi,
> > 
> > after commit 
> > 
> > a2def3663a0feff12550906c33f9ecc3e5fb2a5d
> > procd: jail: clean up capability handling and non-root ubusd
> > 
> > system doesn't work properly. After sysupgrade, system does not restart 
> > completely and hangs somewhere in the boot process. I've to do a hard 
> > reset. After this, system does boot, but password is reset to no password. 
> > I don't know if other settings are reset too. ubusd is not started. uhttpd 
> > fails to start, because ubus socket isn't available. If I apply a 
> > previously saved backup with 'sysupgrade -r ...' and force a reboot, system 
> > starts, but tries to initialize a ext rootfs, which doesn't exist, and 
> > hangs in the boot process. At this point, I've to do a recovery via uboot. 
> > My router is a tp-link Archer C7.
> > 
> > Regards,
> > Hartmut
> > 
> > _______________________________________________
> > openwrt-devel mailing list
> > openwrt-devel@lists.openwrt.org
> > https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> 

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to