linux-kernel - Re: Long stalls during boot with -next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 29 Sep 2011 15:02:20 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Mark Brown <broonie@...ena.org.uk>
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: Long stalls during boot with -next

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/