From: Nicolas Bareil <nico@chdir.org>
To: Mel Gorman <mel@csn.ul.ie>
Cc: cl@linux.com, akpm@linux-foundation.org,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [BISECTED][REGRESSION] INFO: rcu_sched_state detected stall on CPU
Date: Thu, 06 Jan 2011 13:00:23 +0100 [thread overview]
Message-ID: <87ei8q6y3s.fsf@puppet.chdir.org> (raw)
In-Reply-To: <20110106114533.GH29257@csn.ul.ie> (Mel Gorman's message of "Thu, 6 Jan 2011 11:45:34 +0000")
Mel Gorman <mel@csn.ul.ie> writes:
> There should be a fix for this in Andrew's mm tree. At the moment, I'm
> expecting it to be merged for 2.6.38-rc1 but I'm also expecting it will be
> merged to the stable series as you are not the only person to encounter this
> sort of problem. To be sure, can you confirm if the following patch helps you?
> It's a copy of what is in Andrew's tree. Thanks
Indeed, this commit fixed the issue!
Thanks for your fast reply!
prev parent reply other threads:[~2011-01-06 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 11:38 [BISECTED][REGRESSION] INFO: rcu_sched_state detected stall on CPU Nicolas Bareil
2011-01-06 11:45 ` Mel Gorman
2011-01-06 12:00 ` Nicolas Bareil [this message]
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=87ei8q6y3s.fsf@puppet.chdir.org \
--to=nico@chdir.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--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