From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Hugh Dickins <hughd@google.com>
Cc: Pawel Sikora <pluto@agmk.net>,
arekm@pld-linux.org, Anders Ossowicki <aowi@novozymes.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 3.1-rc9: BUG: soft lockup in find_get_pages+0x4e/0x140
Date: Tue, 18 Oct 2011 09:42:00 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1110180806480.7942@p34.internal.lan> (raw)
In-Reply-To: <alpine.LSU.2.00.1110172036300.7358@sister.anvils>
On Mon, 17 Oct 2011, Hugh Dickins wrote:
> On Sat, 15 Oct 2011, Justin Piszcz wrote:
>>
>> With 3.1-rc9 during a filesystem dump, this occurred, I thought a previous
>> patch fixed this but it did not, it occurs MUCH less (first time in a couple
>> of weeks) but the problem still occurs.
>
> Shaohua's nr_skip patch fixed, or at least worked around, the error I
> introduced there in 3.1-rc1. But now you're finding a similar problem
> still in 3.1-rc9: that confirms what you and others already reported,
> that something like it occurs even in 3.0 without my bug.
Thanks,
Patch applied:
# patch -p1 < /tmp/memory_patch.patch
patching file mm/filemap.c
patching file mm/memcontrol.c
Now running 3.1-rc9 + this patch + re-enabled frame pointers.
Justin.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-10-18 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.02.1110152003210.26507@p34.internal.lan>
2011-10-18 4:09 ` Hugh Dickins
2011-10-18 13:42 ` Justin Piszcz [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=alpine.DEB.2.02.1110180806480.7942@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=aowi@novozymes.com \
--cc=arekm@pld-linux.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pluto@agmk.net \
/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