merged. We should also either have a plan to figure out the root cause of this, or we should patch the Kconfig to be broken if enabled .. that way we'll prevent others from turning it on by mistake.
Bruce In message: [linux-yocto] [kernel-cache yocto-5.2/master] [PATCH] ti-am335x: enable GCC -O2 optimization on 29/10/2019 Jun Miao wrote: > Ti-am335x bsp includes the standard.scc file, which will set > CONFIG_CC_OPTIMIZE_FOR_SIZE=y. > As a result, the system boot hangs like below in v5.4.0-rc4 kernel version: > When we enable CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE for -O2 Optimization level, > the boot succeeds. > > boot log: > systemd[1]: Set hostname to <ti-am335x>. > systemd[1]: Failed to open netlink: Operation not permitted > systemd-fstab-generator[120]: Failed to write unit file -.mount: Bad address > systemd-fstab-generator[120]: Failed to write unit file var-volatile.mount: > Bad address > ... ... > systemd[1]: Failed to start device monitor: Bad address > systemd[1]: SO_PASSCRED failed: Bad address > [!!!!!!] Failed to start up manager. > systemd[1]: Freezing execution. > > Signed-off-by: Jun Miao <[email protected]> > --- > bsp/ti-am335x/ti-am335x.cfg | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/bsp/ti-am335x/ti-am335x.cfg b/bsp/ti-am335x/ti-am335x.cfg > index 71884fd7..190cb876 100644 > --- a/bsp/ti-am335x/ti-am335x.cfg > +++ b/bsp/ti-am335x/ti-am335x.cfg > @@ -258,3 +258,5 @@ CONFIG_OMAP_CONTROL_PHY=y > > CONFIG_TI_PIPE3=y > CONFIG_ARM_PMU=y > + > +CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y > -- > 2.17.1 > -- _______________________________________________ linux-yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/linux-yocto
