From: Ingo Molnar <mingo@elte.hu>
To: David Miller <davem@davemloft.net>
Cc: greg@kroah.com, jeremy@goop.org, gregkh@suse.de,
linux-kernel@vger.kernel.org, stable@kernel.org,
jkohen@users.sourceforge.net, akpm@linux-foundation.org,
david@unsolicited.net
Subject: Re: [stable] Soft lockups since stable kernel upgrade to 2.6.23.8
Date: Wed, 21 Nov 2007 00:26:33 +0100 [thread overview]
Message-ID: <20071120232633.GA23667@elte.hu> (raw)
In-Reply-To: <20071120.151538.68704351.davem@davemloft.net>
* David Miller <davem@davemloft.net> wrote:
> > so just to reiterate, to make sure we have the same plans: lets
> > leave v2.6.22 and earlier kernels alone - and lets strive for the
> > latest patches and code for v2.6.23 (and v2.6.24, evidently).
>
> I've validated that those patches make 2.6.23 behave on my Niagara
> box.
Great and thanks for testing it! Arjan noticed the shortness of the 1
sec sleep too, my suggestion would be to increase the sleep period to
~50 seconds and the detection threshold to 60 seconds - that should be
large enough - instead of complicating the tick code even more.
Ingo
next prev parent reply other threads:[~2007-11-20 23:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 18:21 Soft lockups since stable kernel upgrade to 2.6.23.8 Javier Kohen
2007-11-17 19:12 ` [stable] " Greg KH
2007-11-17 20:05 ` David
2007-11-17 20:37 ` Greg KH
2007-11-18 0:34 ` Jeremy Fitzhardinge
2007-11-19 23:22 ` Greg KH
2007-11-20 1:40 ` Jeremy Fitzhardinge
2007-11-20 6:05 ` Ingo Molnar
2007-11-20 17:05 ` Greg KH
2007-11-20 20:39 ` Ingo Molnar
2007-11-20 21:03 ` Greg KH
2007-11-20 21:49 ` Ingo Molnar
2007-11-20 22:06 ` Greg KH
2007-11-20 23:15 ` David Miller
2007-11-20 23:26 ` Ingo Molnar [this message]
2007-11-20 23:52 ` Greg KH
2007-11-18 0:55 ` Ingo Molnar
2007-11-20 0:30 ` Chuck Ebbert
2007-11-20 6:08 ` Ingo Molnar
2007-11-20 17:04 ` Greg KH
2007-11-17 19:40 ` David
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=20071120232633.GA23667@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=david@unsolicited.net \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=jeremy@goop.org \
--cc=jkohen@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.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.