From: Andrew Lutomirski <luto@mit.edu>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: minchan.kim@gmail.com, aarcange@redhat.com,
kamezawa.hiroyu@jp.fujitsu.com, fengguang.wu@intel.com,
andi@firstfloor.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mgorman@suse.de,
hannes@cmpxchg.org, riel@redhat.com
Subject: Easy portable testcase! (Re: Kernel falls apart under light memory pressure (i.e. linking vmlinux))
Date: Wed, 25 May 2011 16:17:54 -0400 [thread overview]
Message-ID: <BANLkTinptn4-+u+jgOr2vf2iuiVS3mmYXA@mail.gmail.com> (raw)
On Tue, May 24, 2011 at 8:43 PM, KOSAKI Motohiro
<kosaki.motohiro@jp.fujitsu.com> wrote:
>
> Unfortnately, this log don't tell us why DM don't issue any swap io. ;-)
> I doubt it's DM issue. Can you please try to make swap on out of DM?
>
>
I can do one better: I can tell you how to reproduce the OOM in the
comfort of your own VM without using dm_crypt or a Sandy Bridge
laptop. This is on Fedora 15, but it really ought to work on any
x86_64 distribution that has kvm. You'll probably want at least 6GB
on your host machine because the VM wants 4GB ram.
Here's how:
Step 1: Clone git://gitorious.org/linux-test-utils/reproduce-annoying-mm-bug.git
(You can browse here:)
https://gitorious.org/linux-test-utils/reproduce-annoying-mm-bug
Instructions to reproduce the mm bug:
Step 2: Build Linux v2.6.38.6 with config-2.6.38.6 and the patch
0001-Minchan-patch-for-testing-23-05-2011.patch (both files are in the
git repo)
Step 3: cd back to reproduce-annoying-mm-bug
Step 4: Type this.
$ make
$ qemu-kvm -m 4G -smp 2 -kernel <linux_dir>/arch/x86/boot/bzImage
-initrd initramfs.gz
Step 5: Wait for the VM to boot (it's really fast) and then run ./repro_bug.sh.
Step 6: Wait a bit and watch the fireworks. Note that it can take a
couple minutes to reproduce the bug.
Tested on my Sandy Bridge laptop and on a Xeon W3520.
For whatever reason, on my laptop without the VM I can hit the bug
almost instantaneously. Maybe it's because I'm using dm-crypt on my
laptop.
--Andy
P.S. I think that the mk_trivial_initramfs.sh script is cute, and
maybe I'll try to flesh it out and turn it into a real project some
day.
--
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>
next reply other threads:[~2011-05-25 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 20:17 Andrew Lutomirski [this message]
2011-05-26 8:18 ` Easy portable testcase! (Re: Kernel falls apart under light memory pressure (i.e. linking vmlinux)) KOSAKI Motohiro
2011-05-26 23:58 ` Minchan Kim
2011-05-29 18:28 ` Minchan Kim
2011-05-30 0:28 ` Andrew Lutomirski
2011-06-14 10:10 ` Johannes Weiner
2011-06-14 12:32 ` Andrew Lutomirski
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=BANLkTinptn4-+u+jgOr2vf2iuiVS3mmYXA@mail.gmail.com \
--to=luto@mit.edu \
--cc=aarcange@redhat.com \
--cc=andi@firstfloor.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.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).