From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Dave Chinner <david@fromorbit.com>,
LKML <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com, minchan.kim@gmail.com
Subject: Re: 2.6.39-rc4+: oom-killer busy killing tasks
Date: Fri, 29 Apr 2011 22:17:01 +0200 [thread overview]
Message-ID: <20110429201701.GA13166@x4.trippels.de> (raw)
In-Reply-To: <alpine.DEB.2.01.1104291250480.18728@trent.utfs.org>
On 2011.04.29 at 12:58 -0700, Christian Kujau wrote:
> On Fri, 29 Apr 2011 at 09:37, Dave Chinner wrote:
> > Did you read the email that pointed to CONFIG_TINY_RCU as the
> > ptotential source of the problem? Can you change to CONFIG_TREE_RCU
> > and see if the problem goes away?
>
> Tried with TREE_RCU, unfortunately the problem persists. However, the OOM
> messages did not make it to the disk this time. Syslog continued to work
> until 11:51 (local time), the slabinfo-8-TREE_RCU.txt file was written to
> until 11:57, the machine was already unusable at that point. At 12:07 I
> took a "screenshot" and then powercycled the machine:
>
> http://nerdbynature.de/bits/2.6.39-rc4/oom/
> (The files marked with -8 are the current ones)
>
> Btw, the xfs filesystem I'm du'ing over is still mounted with "noatime".
>
> Any ideas? Patches to try?
I could be the hrtimer bug again. Would you try to reproduce the issue
with this patch applied?
http://git.us.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=commit;h=ce31332d3c77532d6ea97ddcb475a2b02dd358b4
--
Markus
next prev parent reply other threads:[~2011-04-29 20:17 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 1:57 2.6.39-rc4+: oom-killer busy killing tasks Christian Kujau
2011-04-22 2:58 ` Minchan Kim
2011-04-22 3:03 ` Christian Kujau
2011-04-22 17:41 ` Christian Kujau
2011-04-22 18:46 ` Christian Kujau
2011-04-22 22:47 ` Minchan Kim
2011-04-24 23:46 ` Dave Chinner
2011-04-25 5:51 ` Christian Kujau
2011-04-25 7:19 ` Christian Kujau
2011-04-26 15:14 ` Christian Kujau
2011-04-27 2:26 ` Dave Chinner
2011-04-27 7:46 ` Christian Kujau
2011-04-27 10:28 ` Dave Chinner
2011-04-27 23:16 ` Minchan Kim
2011-04-27 23:56 ` Dave Chinner
2011-04-28 17:30 ` Christian Kujau
2011-04-28 23:37 ` Dave Chinner
2011-04-29 17:32 ` Christian Kujau
2011-04-29 19:58 ` Christian Kujau
2011-04-29 20:17 ` Markus Trippelsdorf [this message]
2011-04-29 20:20 ` Christian Kujau
2011-04-29 20:21 ` Markus Trippelsdorf
2011-04-30 0:17 ` Christian Kujau
2011-05-01 8:01 ` Dave Chinner
2011-05-02 4:59 ` Christian Kujau
2011-05-02 12:19 ` Dave Chinner
2011-05-02 19:59 ` Christian Kujau
2011-05-03 0:51 ` Dave Chinner
2011-05-03 4:04 ` Christian Kujau
2011-05-03 6:36 ` Dave Chinner
2011-05-03 20:53 ` Christian Kujau
2011-05-04 0:46 ` Christian Kujau
2011-05-04 1:51 ` Christian Kujau
2011-05-04 7:36 ` Dave Chinner
2011-05-04 11:12 ` Dave Chinner
2011-05-04 19:10 ` Christian Kujau
2011-05-04 23:15 ` Dave Chinner
2011-05-05 2:07 ` Christian Kujau
2011-05-02 9:26 ` Christian Kujau
2011-05-02 12:38 ` Dave Chinner
2011-04-25 8:02 ` Christian Kujau
2011-04-25 9:50 ` Christian Kujau
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=20110429201701.GA13166@x4.trippels.de \
--to=markus@trippelsdorf.de \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=minchan.kim@gmail.com \
--cc=xfs@oss.sgi.com \
/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).