Hi Tony, On Thu, Oct 01, 2020 at 11:17:48AM +0300, Tony Lindgren wrote: > * Tony Lindgren <tony@xxxxxxxxxxx> [201001 07:53]: > > * Peter Ujfalusi <peter.ujfalusi@xxxxxx> [200930 12:41]: > > > Fwiw on my beagle x15 > > > > > > v5.8 > > > [ 9.908787] Run /sbin/init as init process > > > > > > v5.9-rc7 > > > [ 15.085373] Run /sbin/init as init process > > > > > > > > > It appears to be 'fixed' in next-20200928: the board does not even boot. > > > > Yeah so it seems :( > > > > > next-20200928 on omap5 > > > [ 9.936806] Run /sbin/init as init process > > > > > > > > > -rc7 spends most of it's time: > > > [ 7.635530] Micrel KSZ9031 Gigabit PHY 48485000.mdio:01: attached PHY driver [Micrel KSZ9031 Gigabit PHY] (mii_bus:phy_addr=48485000.mdio:01, irq=POLL) > > > [ 14.956671] cpsw 48484000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off > > > [ 15.005211] IP-Config: Complete: > > > > Booting with initcall_debug I see this with current Linux next: > > > > ... > > [ 1.697313] cpuidle: using governor menu > > [ 1.701353] initcall init_menu+0x0/0xc returned 0 after 0 usecs > > [ 1.707458] calling gpmc_init+0x0/0x10 @ 1 > > [ 1.711784] initcall gpmc_init+0x0/0x10 returned 0 after 0 usecs > > [ 1.717974] calling omap3_l3_init+0x0/0x10 @ 1 > > [ 1.722653] initcall omap3_l3_init+0x0/0x10 returned 0 after 0 usecs > > [ 1.729201] calling omap_l3_init+0x0/0x10 @ 1 > > [ 1.733791] initcall omap_l3_init+0x0/0x10 returned 0 after 0 usecs > > [ 1.740314] calling gate_vma_init+0x0/0x70 @ 1 > > [ 1.744976] initcall gate_vma_init+0x0/0x70 returned 0 after 0 usecs > > [ 1.751522] calling customize_machine+0x0/0x30 @ 1 > > [ 3.823114] initcall customize_machine+0x0/0x30 returned 0 after 2011718 usecs > > [ 3.830566] calling init_atags_procfs+0x0/0xec @ 1 > > [ 3.835583] No ATAGs? > > And the long time above with customize_machine() ends up being > pdata_quirks_init() calling of_platform_populate(). That's what the delay is for me (I think I've reported that initially). > > Laurent & Tomi, care to check what you guys see in the slow booting case > > after booting with initcall_debug? > > But maybe the long delay is something else for you guys so please check. -- Regards, Laurent Pinchart
