From: James Bottomley <James.Bottomley@suse.de>
To: sedat.dilek@gmail.com
Cc: Chris Mason <chris.mason@oracle.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [BUG] fatal hang untarring 90GB file, possibly writeback related.
Date: Mon, 02 May 2011 15:04:55 -0500 [thread overview]
Message-ID: <1304366695.15370.24.camel@mulgrave.site> (raw)
In-Reply-To: <1304100150.2559.28.camel@mulgrave.site>
On Fri, 2011-04-29 at 13:02 -0500, James Bottomley wrote:
> On Fri, 2011-04-29 at 11:31 -0500, James Bottomley wrote:
> > On Fri, 2011-04-29 at 10:37 -0500, James Bottomley wrote:
> > > On Fri, 2011-04-29 at 12:23 +0200, Sedat Dilek wrote:
> > > > But as I see these RCU (CPU) stalls, the patch from [1] might be worth a try.
> > > > First, I have seen negative effects on my UP-system was when playing
> > > > with linux-next [2].
> > > > It was not clear what the origin was and the the side-effects were
> > > > somehow "bizarre".
> > > > The issue could be easily reproduced by tar-ing the kernel build-dir
> > > > to an external USB-hdd.
> > > > The issue kept RCU and TIP folks really busy.
> > > > Before stepping 4 weeks in the dark, give it a try and let me know in
> > > > case of success.
> > >
> > > Well, it's highly unlikely because that's a 2.6.39 artifact and the bug
> > > showed up in 2.6.38 ... I tried it just in case with no effect, so we
> > > know it isn't the cause.
> >
> > Actually, I tell a lie: it does't stop kswapd spinning on PREEMPT, but
> > it does seem to prevent non-PREEMPT from locking up totally (at least it
> > survives three back to back untar runs).
> >
> > It's probable it alters the memory pin conditions that cause the spin,
> > so it's masking the problem rather than fixing it.
>
> Confirmed ... it's just harder to reproduce with the hrtimers init fix.
> The problem definitely still exists (I had to load up the system more
> before doing the tar).
>
> This time I've caught kswapd in mem_cgroup_shrink_node_zone. sysrq-w
> doesn't complete for an unknown reason
As a follow on to this, there's a shrink_zone(0, ...) in the cgroup
path. This causes it to scan all memory exhaustively (generating quite
a lot of work). The comment above it implies it's some type of hack for
cgroup accounting, but reducing it to DEF_PRIORITY makes the hang go
away (verified on both 2.6.39-rc4 and 2.6.38.4). Note that I still get
soft lockups in kswapd0, but they no longer hang the box. I'll prepare
a patch for the next round of debate.
James
--
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-05-02 20:04 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 16:09 [BUG] fatal hang untarring 90GB file, possibly writeback related James Bottomley
2011-04-27 16:33 ` Chris Mason
2011-04-27 16:50 ` James Bottomley
2011-04-27 16:54 ` Chris Mason
2011-04-27 17:21 ` James Bottomley
2011-04-27 17:34 ` Chris Mason
2011-04-27 17:50 ` James Bottomley
2011-04-27 18:25 ` Colin Ian King
2011-04-28 15:57 ` James Bottomley
2011-04-27 20:05 ` James Bottomley
2011-04-28 11:36 ` Colin Ian King
2011-04-28 12:29 ` Chris Mason
2011-04-28 13:42 ` Colin Ian King
2011-04-28 13:45 ` Chris Mason
2011-04-28 14:01 ` Colin Ian King
2011-04-28 14:04 ` Chris Mason
2011-04-28 15:23 ` Colin Ian King
2011-04-28 14:25 ` Jan Kara
2011-04-28 14:33 ` Jan Kara
2011-04-28 14:58 ` Colin Ian King
2011-04-28 22:40 ` Jan Kara
2011-04-28 22:44 ` James Bottomley
2011-05-03 18:55 ` Colin Ian King
2011-04-28 16:11 ` James Bottomley
2011-04-28 14:49 ` James Bottomley
2011-04-28 13:52 ` Jan Kara
2011-04-28 14:07 ` Mel Gorman
2011-04-28 14:25 ` James Bottomley
2011-04-28 15:08 ` Mel Gorman
2011-04-28 16:01 ` James Bottomley
2011-04-28 16:50 ` James Bottomley
2011-04-28 16:56 ` James Bottomley
2011-04-28 17:18 ` Mel Gorman
2011-04-28 18:30 ` James Bottomley
2011-04-28 19:21 ` Mel Gorman
2011-04-28 19:59 ` James Bottomley
2011-04-28 20:27 ` Mel Gorman
2011-04-29 15:02 ` James Bottomley
2011-04-28 21:12 ` James Bottomley
2011-04-28 22:43 ` James Bottomley
2011-05-03 9:13 ` Mel Gorman
2011-05-03 14:13 ` James Bottomley
2011-05-03 14:22 ` James Bottomley
2011-05-06 7:42 ` Mel Gorman
2011-05-06 8:07 ` Mel Gorman
2011-05-09 18:16 ` James Bottomley
2011-05-10 10:21 ` Mel Gorman
2011-05-10 10:33 ` Pekka Enberg
2011-05-10 14:01 ` James Bottomley
2011-05-10 14:35 ` Mel Gorman
2011-05-10 15:29 ` James Bottomley
2011-05-10 15:57 ` James Bottomley
2011-05-10 17:05 ` James Bottomley
2011-05-10 17:17 ` Mel Gorman
2011-05-10 17:29 ` James Bottomley
2011-05-10 21:08 ` Raghavendra D Prabhu
2011-05-11 9:16 ` Mel Gorman
2011-05-06 11:42 ` Mel Gorman
2011-05-06 15:44 ` Mel Gorman
2011-05-06 19:14 ` James Bottomley
2011-05-06 19:37 ` Mel Gorman
2011-05-10 5:37 ` Colin Ian King
2011-05-06 15:58 ` James Bottomley
2011-05-03 9:54 ` Colin Ian King
2011-04-28 17:10 ` Colin Ian King
2011-04-28 0:37 ` Dave Chinner
2011-04-29 10:23 ` Sedat Dilek
2011-04-29 15:37 ` James Bottomley
2011-04-29 16:31 ` James Bottomley
2011-04-29 18:02 ` James Bottomley
2011-05-02 20:04 ` James Bottomley [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=1304366695.15370.24.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=chris.mason@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sedat.dilek@gmail.com \
--cc=tglx@linutronix.de \
/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).