From: Mel Gorman <mel@csn.ul.ie>
To: Chris Mason <chris.mason@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jens Axboe <jaxboe@fusionio.com>, linux-mm <linux-mm@kvack.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Shaohua Li <shaohua.li@intel.com>
Subject: Re: hunting an IO hang
Date: Mon, 17 Jan 2011 17:09:07 +0000 [thread overview]
Message-ID: <20110117170907.GC27152@csn.ul.ie> (raw)
In-Reply-To: <1295276272-sup-1788@think>
On Mon, Jan 17, 2011 at 10:02:47AM -0500, Chris Mason wrote:
> Excerpts from Chris Mason's message of 2011-01-17 09:07:40 -0500:
>
> [ various crashes under load with current git ]
>
> >
> > I did have CONFIG_COMPACTION off for my latest reproduce. The last two
> > have been corruption on the page->lru lists, maybe that'll help narrow
> > our bisect pool down.
>
> I've reverted 744ed1442757767ffede5008bb13e0805085902e, and
> d8505dee1a87b8d41b9c4ee1325cd72258226fbc and the run has lasted longer
> than any runs in the past.
>
Confirmed that reverting these patches makes the problem unreproducible
for the many_dd's + fsmark for at least an hour here.
> I'll give this a few hours but they seem the most related to my various
> crashes so far.
>
> -chris
>
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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 policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-01-17 17:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1295225684-sup-7168@think>
[not found] ` <AANLkTikBamG2NG6j-z9fyTx=mk6NXFEE7LpB5z9s6ufr@mail.gmail.com>
[not found] ` <4D339C87.30100@fusionio.com>
[not found] ` <1295228148-sup-7379@think>
[not found] ` <AANLkTimp6ef0W_=ijW=CfH6iC1mQzW3gLr1LZivJ5Bmd@mail.gmail.com>
[not found] ` <AANLkTimr3hN8SDmbwv98hkcVfWoh9tioYg4M+0yanzpb@mail.gmail.com>
[not found] ` <1295229722-sup-6494@think>
2011-01-17 2:30 ` hunting an IO hang Andrew Morton
2011-01-17 2:41 ` Chris Mason
2011-01-17 5:11 ` Andrea Arcangeli
2011-01-17 13:48 ` Minchan Kim
2011-01-17 14:10 ` Chris Mason
2011-01-17 14:26 ` Andrea Arcangeli
2011-01-17 14:47 ` Minchan Kim
2011-01-17 15:09 ` Minchan Kim
2011-01-17 20:39 ` Andrea Arcangeli
2011-01-17 10:27 ` Mel Gorman
2011-01-17 13:21 ` Chris Mason
2011-01-17 13:50 ` Mel Gorman
2011-01-17 14:07 ` Chris Mason
2011-01-17 15:02 ` Chris Mason
2011-01-17 16:32 ` Johannes Weiner
2011-01-17 18:10 ` Mel Gorman
2011-01-17 17:09 ` Mel Gorman [this message]
2011-01-17 17:40 ` Chris Mason
2011-01-17 18:24 ` Linus Torvalds
2011-01-17 21:23 ` Chris Mason
2011-01-17 23:03 ` Mel Gorman
2011-01-18 0:30 ` Shaohua Li
2011-01-17 23:02 ` Linus Torvalds
2011-01-17 23:13 ` Minchan Kim
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=20110117170907.GC27152@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=jaxboe@fusionio.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=shaohua.li@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).