From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756428Ab1I2NCY (ORCPT ); Thu, 29 Sep 2011 09:02:24 -0400 Received: from cantor2.suse.de ([195.135.220.15]:37290 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756395Ab1I2NCV (ORCPT ); Thu, 29 Sep 2011 09:02:21 -0400 Date: Thu, 29 Sep 2011 15:02:20 +0200 Message-ID: From: Takashi Iwai To: Mark Brown Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: Long stalls during boot with -next In-Reply-To: <20110929125035.GA2085@sirena.org.uk> References: <20110929125035.GA2085@sirena.org.uk> User-Agent: Wanderlust/2.15.6 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.7 Emacs/23.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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