From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: mel@csn.ul.ie, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, Preeti.Khurana@guavus.com
Subject: Re: rcu_sched_state detected stall on CPU issue
Date: Wed, 16 Mar 2011 19:25:06 -0700 [thread overview]
Message-ID: <20110317022506.GG2304@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110317085938.C938.A69D9226@jp.fujitsu.com>
On Thu, Mar 17, 2011 at 09:18:19AM +0900, KOSAKI Motohiro wrote:
> Hi Paul,
>
> > Hello!
> >
> > It looks like Preeti found a way to loop in kswapd with preemption
> > disabled, please see attached dmesg. This is using 2.6.35-45.fc14.
> >
> > Any thoughts or recent patches that might help?
>
> We fixed a kswapd infinite loop issue when memory is fragmented at 2.6.38.
> Could you please try following commits? (all are mm/vmscan.c change)
>
> commit dc83edd941f412e938841b4989be24aa288a1aa6
> commit 355b09c47a0cbb73b3e65a57c03f157f2e7ddb0b
> commit 4d40502ea580c35414a1466d86f96484910ebaec
> commit 0abdee2bd4118366c62349a304f81537be69af33
> commit 1741c87757448cedd03224f01586504f9256415d
> commit 9950474883e027e6e728cbcff25f7f2bf0c96530
Thank you, Kosaki!
> And, your attached file and your quoted mail don't have /proc/zoneinfo
> information. then I have no way to confirn his environment is heavy
> fragmented or not. If possible, could you please get /proc/zoneinfo
> info?
Preeti, could you please send this info and try out the above patches?
Thanx, Paul
next prev parent reply other threads:[~2011-03-17 2:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110316101820.GA17540@linux.vnet.ibm.com>
2011-03-17 0:18 ` rcu_sched_state detected stall on CPU issue KOSAKI Motohiro
2011-03-17 2:25 ` Paul E. McKenney [this message]
2011-03-17 14:11 ` Preeti Khurana
2011-03-22 4:44 ` Preeti Khurana
2011-03-22 6:32 ` Paul E. McKenney
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=20110317022506.GG2304@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Preeti.Khurana@guavus.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
/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.