From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@sirena.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Long stalls during boot with -next
Date: Thu, 29 Sep 2011 15:02:20 +0200 [thread overview]
Message-ID: <s5hfwjfa4df.wl%tiwai@suse.de> (raw)
In-Reply-To: <20110929125035.GA2085@sirena.org.uk>
At Thu, 29 Sep 2011 13:50:36 +0100,
Mark Brown wrote:
>
> Since Tuesday I've been experiencing stalls on boot with -next kernels.
> The boot appears to proceed normally but there appears to be a good ten
> second delay somewhere around the late_initcall() stage with no
> indication in the logs:
>
> [ 3.110000] regulator_init_complete: PVDD_1V2: disabling
> [ 3.120000] input: gpio-keys as /devices/platform/gpio-keys.0/input/input5
> [ 3.120000] wm831x-rtc wm831x-rtc.10: hctosys: unable to read the hardware clock
> [ 13.690000] kjournald starting. Commit interval 5 seconds
> [ 13.690000] EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
>
> (which happens before or at about the time console output starts
> appearing, I'd expect it to appear much earlier). I've had a poke
> around and I didn't spot anything yet, none of the development I've
> noticed going on recently looks suspicious.
Did you check with initcall_debug boot option?
Takashi
next prev parent reply other threads:[~2011-09-29 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 12:50 Long stalls during boot with -next Mark Brown
2011-09-29 13:02 ` Takashi Iwai [this message]
2011-09-29 13:44 ` Mark Brown
2011-10-07 11:50 ` Mark Brown
2011-10-07 13:27 ` Thomas Abraham
2011-10-07 14:23 ` Mark Brown
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=s5hfwjfa4df.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=broonie@sirena.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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