From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Lord <lkml@rtr.ca>, Daniel Walker <dwalker@mvista.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [BUG] 2.6.21: Kernel won't boot with either/both of CONFIG_NO_HZ, CONFIG_HIGH_RES_TIMERS
Date: Wed, 02 May 2007 17:40:57 +0200 [thread overview]
Message-ID: <1178120457.25504.17.camel@localhost.localdomain> (raw)
In-Reply-To: <20070502010527.e64dcce9.akpm@linux-foundation.org>
On Wed, 2007-05-02 at 01:05 -0700, Andrew Morton wrote:
> > thanks. Can you apply this patch please:
> > http://lkml.org/lkml/2007/4/13/190
> >
> > It somehow did not make it into 2.6.21.
> >
>
> Alas, poor me. I ain't going to merge a contention-reduction patch when
> we're at -rc6. If a patch fixes a bug, please tell me!
It was not a bug fix at this point, I merily tried to solve the lock
contention problem, which was reported by Steven Rostedt.
The confusing thing on Marks config bisecting was that the softlock
detection fixed his problem. The only difference of the softlock
detection is that it starts the watchdog thread and a one second timer.
I was looking into the code and noticed that this patch did not make it.
Honestly it was a shot into the dark and I'd really like to know why
this makes the problem go away.
Mark, did you ever enable CONFIG_PROVE_LOCKING as a single add on to
your not working config ? If not, can you please try ?
tglx
next prev parent reply other threads:[~2007-05-02 15: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
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 [this message]
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=1178120457.25504.17.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox