From: Thomas Gleixner <tglx@linutronix.de>
To: Mark Lord <lkml@rtr.ca>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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: Thu, 03 May 2007 00:41:15 +0200 [thread overview]
Message-ID: <1178145675.2340.28.camel@localhost.localdomain> (raw)
In-Reply-To: <463910BF.9050103@rtr.ca>
On Wed, 2007-05-02 at 18:29 -0400, Mark Lord wrote:
> Oh crap. It's back.
>
> I don't know what's different from before,
> but the system now locks up again exactly the same way,
> even with the lock contention fix applied.
Which is less surprising and confusing than the previous result. It
points to some subtle race condition somewhere, which got affected by
the slightly timing change.
> With or without CONFIG_PROVE_LOCKING=y in the config.
Ok.
> I've gotta get some work done here (this is my primary development machine),
> so it's back to CONFIG_DETECT_SOFTLOCKUP=y for a while.
>
> If anyone has a patch to dump out state/whatever just before that
> last message that preceeds all lockups, then pass it along and
> I'll queue it up for testing as soon as I can.
I try to come up with something, but I'm travelling tomorrow, so it
might be not before end of week.
tglx
next prev parent reply other threads:[~2007-05-02 22: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
2007-05-02 22:29 ` Mark Lord
2007-05-02 22:41 ` Thomas Gleixner [this message]
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=1178145675.2340.28.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