Long stalls during boot with -next

[Mark Brown]

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