From: Zan Lynx <zlynx@acm.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.22-rc1-mm1 huge pages VM freeze (maybe?)
Date: Tue, 31 Jul 2007 15:44:21 -0600 [thread overview]
Message-ID: <1185918261.6981.13.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]
I was playing with huge pages and libhugetlbfs. Small programs like
"ls" work fine. I tried running Evolution through libhugetlbfs and the
system slowly stops running. One interesting thing is the "ps" command,
it gets stuck like this:
ps D ffff81001e57ed40 0 103558 103483
ffff81001f061dc8 0000000000000096 ffff81003d8586e8 ffff81001cbadc00
0000000000000006 ffffffff80537009 0000000000000030 ffffffff807ff700
ffffffff807ff700 ffffffff807ff700 ffffffff807ff700 ffffffff807ff700
Call Trace:
[<ffffffff80537009>] _spin_unlock+0x29/0x50
[<ffffffff80536425>] __down_read+0x75/0xaf
[<ffffffff80295f49>] access_process_vm+0x49/0x190
[<ffffffff802f3003>] proc_pid_cmdline+0xa3/0x130
[<ffffffff802f4cea>] proc_info_read+0xba/0x100
[<ffffffff802b0085>] vfs_read+0xc5/0x180
[<ffffffff802b0583>] sys_read+0x53/0x90
[<ffffffff8020c1de>] system_call+0x7e/0x83
and nothing will touch it after that.
Here's my kernel command line:
root=/dev/sda2 rootfstype=reiser4 rootflags=no_write_barrier ro
i8042.nomux elevator=cfq resume=/dev/sda3 panic=5 nmi_watchdog=2,panic
debug hugepages=32
Here's the "huge" script I was using to run programs:
#!/bin/sh
export LD_PRELOAD=libhugetlbfs.so
export HUGETLB_MORECORE=yes
export HUGETLB_PATH=/mnt/huge
export HUGETLB_VERBOSE=1
exec "$@"
I don't have any more info than that at the moment but I could reproduce
it with whatever, on request.
--
Zan Lynx <zlynx@acm.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-07-31 21:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 21:44 Zan Lynx [this message]
2007-07-31 22:02 ` 2.6.22-rc1-mm1 huge pages VM freeze (maybe?) Randy Dunlap
2007-07-31 22:01 ` Zan Lynx
2007-08-01 15:47 ` Nish Aravamudan
2007-08-01 15:52 ` Nish Aravamudan
2007-08-02 1:40 ` Zan Lynx
2007-08-03 3:51 ` Nish Aravamudan
2007-08-01 21:41 ` Nish Aravamudan
2007-08-01 15:45 ` Nish Aravamudan
2007-08-01 15:54 ` Randy Dunlap
2007-08-01 15:52 ` Nish Aravamudan
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=1185918261.6981.13.camel@localhost \
--to=zlynx@acm.org \
--cc=linux-kernel@vger.kernel.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