All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Linux Kernel <linux-kernel@vger.kernel.org>, tglx@linutronix.de
Cc: Linus Torvalds <torvalds@osdl.org>
Subject: Re: [BUG] 2.6.21: Kernel won't boot with either/both of CONFIG_NO_HZ, CONFIG_HIGH_RES_TIMERS
Date: Mon, 30 Apr 2007 16:37:55 -0400	[thread overview]
Message-ID: <463653A3.5040606@rtr.ca> (raw)
In-Reply-To: <46364F5A.2030208@rtr.ca>

Mark Lord wrote:
> Mark Lord wrote:
>> I have a new notebook (Dell Inspiron 9400) with Core2-Duo T7400 @ 2.1Ghz.
>> When either/both of CONFIG_NO_HZ, CONFIG_HIGH_RES_TIMERS is used,
>> the 2.6.21 kernel hangs on startup just after printing one/both of these:
> ..
> 
> That's a hard hang, by the way.  No magic sysrq key or anything.

I've now built a kernel with the same config, plus all of the kernel debug options,
and this one boots.  I think this means the lockups may be due to a very tight
race condition somewhere, and adding all of the debug goodies was enough
to slow it down and avoid the clash (?)

One thing I notice from the syslog, is that with this kernel
there is only the one "switched to high resolution mode on cpu 0" message,
rather than one per-CPU as on the failed kernel.

Here's the diff for the debug config that works:

--- dot_config.nfg	2007-04-30 16:33:31.000000000 -0400
+++ dot_config.boots	2007-04-30 16:22:48.000000000 -0400
@@ -1,7 +1,7 @@
 #
 # Automatically generated make config: don't edit
 # Linux kernel version: 2.6.21
-# Mon Apr 30 15:42:53 2007
+# Mon Apr 30 16:22:48 2007
 #
 CONFIG_X86_32=y
 CONFIG_GENERIC_TIME=y
@@ -56,7 +56,7 @@
 CONFIG_UID16=y
 CONFIG_SYSCTL_SYSCALL=y
 CONFIG_KALLSYMS=y
-# CONFIG_KALLSYMS_ALL is not set
+CONFIG_KALLSYMS_ALL=y
 # CONFIG_KALLSYMS_EXTRA_PASS is not set
 CONFIG_HOTPLUG=y
 CONFIG_PRINTK=y
@@ -2418,39 +2418,45 @@
 # CONFIG_DEBUG_FS is not set
 # CONFIG_HEADERS_CHECK is not set
 CONFIG_DEBUG_KERNEL=y
-# CONFIG_DEBUG_SHIRQ is not set
+CONFIG_DEBUG_SHIRQ=y
 CONFIG_LOG_BUF_SHIFT=16
-# CONFIG_DETECT_SOFTLOCKUP is not set
+CONFIG_DETECT_SOFTLOCKUP=y
 # CONFIG_SCHEDSTATS is not set
 # CONFIG_TIMER_STATS is not set
-# CONFIG_DEBUG_SLAB is not set
-# CONFIG_DEBUG_PREEMPT is not set
-# CONFIG_DEBUG_RT_MUTEXES is not set
+CONFIG_DEBUG_SLAB=y
+CONFIG_DEBUG_SLAB_LEAK=y
+CONFIG_DEBUG_PREEMPT=y
+CONFIG_DEBUG_RT_MUTEXES=y
+CONFIG_DEBUG_PI_LIST=y
 # CONFIG_RT_MUTEX_TESTER is not set
-# CONFIG_DEBUG_SPINLOCK is not set
-# CONFIG_DEBUG_MUTEXES is not set
-# CONFIG_DEBUG_LOCK_ALLOC is not set
-# CONFIG_PROVE_LOCKING is not set
-# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
-# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
-# CONFIG_DEBUG_KOBJECT is not set
-# CONFIG_DEBUG_HIGHMEM is not set
+CONFIG_DEBUG_SPINLOCK=y
+CONFIG_DEBUG_MUTEXES=y
+CONFIG_DEBUG_LOCK_ALLOC=y
+CONFIG_PROVE_LOCKING=y
+CONFIG_LOCKDEP=y
+# CONFIG_DEBUG_LOCKDEP is not set
+CONFIG_TRACE_IRQFLAGS=y
+CONFIG_DEBUG_SPINLOCK_SLEEP=y
+CONFIG_DEBUG_LOCKING_API_SELFTESTS=y
+CONFIG_STACKTRACE=y
+CONFIG_DEBUG_KOBJECT=y
+CONFIG_DEBUG_HIGHMEM=y
 CONFIG_DEBUG_BUGVERBOSE=y
 # CONFIG_DEBUG_INFO is not set
-# CONFIG_DEBUG_VM is not set
-# CONFIG_DEBUG_LIST is not set
-# CONFIG_FRAME_POINTER is not set
+CONFIG_DEBUG_VM=y
+CONFIG_DEBUG_LIST=y
+CONFIG_FRAME_POINTER=y
 CONFIG_FORCED_INLINING=y
 # CONFIG_RCU_TORTURE_TEST is not set
 # CONFIG_FAULT_INJECTION is not set
-# CONFIG_EARLY_PRINTK is not set
-# CONFIG_DEBUG_STACKOVERFLOW is not set
+CONFIG_EARLY_PRINTK=y
+CONFIG_DEBUG_STACKOVERFLOW=y
 # CONFIG_DEBUG_STACK_USAGE is not set
 
 #
 # Page alloc debug is incompatible with Software Suspend on i386
 #
-# CONFIG_DEBUG_RODATA is not set
+CONFIG_DEBUG_RODATA=y
 # CONFIG_4KSTACKS is not set
 CONFIG_X86_FIND_SMP_CONFIG=y
 CONFIG_X86_MPPARSE=y

  reply	other threads:[~2007-04-30 20:38 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 20:17 [BUG] 2.6.21: Kernel won't boot with either/both of CONFIG_NO_HZ, CONFIG_HIGH_RES_TIMERS Mark Lord
2007-04-30 20:19 ` Mark Lord
2007-04-30 20:37   ` Mark Lord [this message]
2007-04-30 23:36     ` Mark Lord
2007-04-30 23:45       ` Thomas Gleixner
2007-04-30 23:46       ` Daniel Walker
2007-05-01  0:02         ` Mark Lord
2007-05-01  0:07           ` Michal Piotrowski
2007-05-01  0:11             ` Mark Lord
2007-05-01  0:13               ` Daniel Walker
2007-05-01  3:33                 ` Mark Lord
2007-05-01  4:32                   ` Daniel Walker
2007-05-01  4:34                   ` Daniel Walker
2007-05-01 13:34           ` Thomas Gleixner
2007-05-01 13:33             ` Mark Lord
2007-05-01 13:34               ` Mark Lord
2007-05-01 13:48                 ` Thomas Gleixner
2007-05-01 14:13                   ` Mark Lord
2007-05-01 14:26                     ` Michal Piotrowski
2007-05-01 14:41                       ` Mark Lord
2007-05-01 15:24                     ` Thomas Gleixner
2007-05-01 16:31                       ` Mark Lord
2007-05-01 16:42                         ` Daniel Walker
2007-05-01 15:57                     ` Thomas Gleixner
2007-05-01 16:52                       ` Mark Lord
2007-05-02  7:47                         ` Thomas Gleixner
2007-05-02  8:05                           ` Andrew Morton
2007-05-02 12:53                             ` Mark Lord
2007-05-02 15:40                             ` Thomas Gleixner
2007-05-02 22:29                               ` Mark Lord
2007-05-02 22:41                                 ` Thomas Gleixner
2007-05-03  2:29                                   ` Mark Lord
2007-05-08 18:46                                     ` Mark Lord

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=463653A3.5040606@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.