Messages in this thread Patch in this message | | | Date | Tue, 16 Aug 2005 18:37:30 +0200 | From | Ingo Molnar <> | Subject | Re: 2.6.13-rc6-rt5 |
| |
* Ingo Molnar <mingo@elte.hu> wrote:
> i removed some debug options from your .config, and that booted. > Here's the diff between the good and bad .config's. Trying to narrow > it down further.
even narrower diff below. My guess would be on CONFIG_DEBUG_STACKOVERFLOW.
Ingo
--- .config.good01 2005-08-16 18:19:05.410509952 +0200 +++ .config.bad00 2005-08-16 18:10:00.242388104 +0200 @@ -1,7 +1,7 @@ # # Automatically generated make config: don't edit # Linux kernel version: 2.6.13-rc6-rt6 -# Tue Aug 16 18:13:48 2005 +# Tue Aug 16 18:05:14 2005 # CONFIG_X86=y CONFIG_MMU=y @@ -156,7 +156,6 @@ # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y CONFIG_HAVE_DEC_LOCK=y -# CONFIG_REGPARM is not set CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set # CONFIG_HZ_250 is not set @@ -1242,21 +1241,25 @@ CONFIG_DEBUG_SLAB=y CONFIG_DEBUG_PREEMPT=y CONFIG_DEBUG_IRQ_FLAGS=y -# CONFIG_WAKEUP_TIMING is not set +CONFIG_WAKEUP_TIMING=y +# CONFIG_WAKEUP_LATENCY_HIST is not set CONFIG_PREEMPT_TRACE=y # CONFIG_CRITICAL_PREEMPT_TIMING is not set # CONFIG_CRITICAL_IRQSOFF_TIMING is not set +CONFIG_LATENCY_TIMING=y +CONFIG_LATENCY_TRACE=y +CONFIG_MCOUNT=y CONFIG_RT_DEADLOCK_DETECT=y # CONFIG_DEBUG_RT_LOCKING_MODE is not set # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y -# CONFIG_DEBUG_INFO is not set +CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_FS is not set -# CONFIG_USE_FRAME_POINTER is not set +CONFIG_FRAME_POINTER=y CONFIG_EARLY_PRINTK=y -# CONFIG_DEBUG_STACKOVERFLOW is not set +CONFIG_DEBUG_STACKOVERFLOW=y # CONFIG_KPROBES is not set -# CONFIG_DEBUG_STACK_USAGE is not set +CONFIG_DEBUG_STACK_USAGE=y # CONFIG_DEBUG_PAGEALLOC is not set # CONFIG_4KSTACKS is not set CONFIG_X86_FIND_SMP_CONFIG=y - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |