From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: Slow booting on x15
Date: Thu, 1 Oct 2020 10:53:44 +0300 [thread overview]
Message-ID: <20201001075344.GU9471@atomide.com> (raw)
In-Reply-To: <d8d81891-7e22-81a2-19df-6e9a5f8679c4@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [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?
Laurent & Tomi, care to check what you guys see in the slow booting case
after booting with initcall_debug?
Regards,
Tony
next prev parent reply other threads:[~2020-10-01 7:53 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 15:25 Slow booting on x15 Tomi Valkeinen
2020-09-18 15:58 ` Laurent Pinchart
2020-09-23 7:07 ` Tony Lindgren
2020-09-23 11:13 ` Laurent Pinchart
2020-09-24 5:42 ` Tony Lindgren
2020-09-24 5:53 ` Tony Lindgren
2020-09-24 6:04 ` Tomi Valkeinen
2020-09-24 6:08 ` Tony Lindgren
2020-09-24 13:30 ` Laurent Pinchart
2020-09-25 11:51 ` Tony Lindgren
2020-09-25 11:58 ` Laurent Pinchart
2020-09-30 5:20 ` Tony Lindgren
2020-09-30 12:41 ` Peter Ujfalusi
2020-10-01 7:53 ` Tony Lindgren [this message]
2020-10-01 8:17 ` Tony Lindgren
2020-10-01 8:22 ` Laurent Pinchart
2020-10-01 12:56 ` Grygorii Strashko
2020-10-01 13:11 ` Geert Uytterhoeven
2020-10-01 13:49 ` Grygorii Strashko
2020-10-01 18:24 ` Saravana Kannan
2020-10-01 19:43 ` Grygorii Strashko
2020-10-01 22:22 ` Saravana Kannan
2020-10-01 22:30 ` Saravana Kannan
2020-10-01 22:38 ` Laurent Pinchart
2020-10-01 22:44 ` Saravana Kannan
2020-10-01 22:59 ` [PATCH v1] of: platform: Batch fwnode parsing in the init_machine() path Saravana Kannan
2020-10-01 23:19 ` Laurent Pinchart
2020-10-02 11:40 ` Grygorii Strashko
2020-10-02 15:03 ` Grygorii Strashko
2020-10-02 17:48 ` Saravana Kannan
2020-10-02 18:11 ` Grygorii Strashko
2020-10-02 14:07 ` Rob Herring
2020-10-02 17:51 ` Saravana Kannan
2020-10-02 17:54 ` Laurent Pinchart
2020-10-02 17:58 ` Saravana Kannan
2020-10-02 18:27 ` Laurent Pinchart
2020-10-02 18:35 ` Grygorii Strashko
2020-10-02 19:56 ` Saravana Kannan
2020-10-03 0:13 ` Laurent Pinchart
2020-10-27 3:29 ` Saravana Kannan
2020-10-28 7:34 ` Tomi Valkeinen
2020-10-02 20:29 ` Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201001075344.GU9471@atomide.com \
--to=tony@atomide.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=tomi.valkeinen@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox