Long stalls during boot with -next
Thomas Abraham
thomas.abraham at linaro.org
Fri Oct 7 09:27:19 EDT 2011
Hi Mark,
On 7 October 2011 17:20, Mark Brown <broonie at opensource.wolfsonmicro.com> wrote:
> On Thu, Sep 29, 2011 at 01:50:36PM +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:
>
> I identified the problem here, the behaviour of LL_DEBUG was changed to
> make it select DEBUG_ICEDCC by default which is unfortunate if one
> doesn't have an EmbeddedICE connected.
Thanks for your suggestion. The long stall during boot problem occurs
on Samsung boards as well with linux-next. As per your suggestion, the
following diff fixes this issue.
diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
index 65cf8c6..035f5cd 100644
--- a/arch/arm/Kconfig.debug
+++ b/arch/arm/Kconfig.debug
@@ -120,6 +120,15 @@ choice
Say Y here if you want the debug print routines to direct
their output to the second serial port on these devices.
+ config DEBUG_SAMSUNG_UART
+ bool "Kernel low-level debugging messages via samsung serial port"
+ depends on PLAT_SAMSUNG
+ help
+ Say Y here if you want the debug print routines to direct
+ their output to the serial port for Samsung platforms. Choose
+ the uart port with the "S3C UART to use for low-level debug"
+ config option.
+
endchoice
config EARLY_PRINTK
@@ -139,7 +148,7 @@ config OC_ETM
kernel code.
config DEBUG_S3C_UART
- depends on PLAT_SAMSUNG
+ depends on DEBUG_SAMSUNG_UART
int "S3C UART to use for low-level debug"
default "0"
help
Thanks,
Thomas.
More information about the linux-arm-kernel
mailing list