From: Michael Guntsche <mike@it-loops.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Page alloc problems with 2.6.32-rc kernels
Date: Tue, 27 Oct 2009 10:50:15 +0100 [thread overview]
Message-ID: <20091027095014.GA22215@gibson.comsick.at> (raw)
Hello list,
I noticed that I get page alloc errors on one of my machines.
It is an old server I use as a fileserver with 512MB RAM. Before
2.6.3[12] I did not see this problem at all.
This only seems to happens when I use mutt on this machine.
I know that it means I am running out of memory here, but I am wondering
why I did not see this before....
mutt: page allocation failure. order:1, mode:0x20
Pid: 21746, comm: mutt Not tainted 2.6.32-rc5 #2
Call Trace:
[<c11981ef>] ? printk+0x18/0x21
[<c1050945>] __alloc_pages_nodemask+0x417/0x4d8
[<c1069edc>] cache_alloc_refill+0x250/0x496
[<c106a1c6>] __kmalloc+0xa4/0xa8
[<c110ddef>] tty_buffer_request_room+0x88/0x11d
[<c110dfb8>] tty_insert_flip_string+0x27/0x93
[<c110e8d9>] pty_write+0x24/0x4a
[<c110a24f>] n_tty_write+0x163/0x3ab
[<c1020960>] ? default_wake_function+0x0/0xd
[<c1107f3c>] tty_write+0x129/0x1c2
[<c110a0ec>] ? n_tty_write+0x0/0x3ab
[<c106cfe0>] vfs_write+0x8e/0x142
[<c1107e13>] ? tty_write+0x0/0x1c2
[<c106d13d>] sys_write+0x3d/0x6b
[<c1002bb5>] syscall_call+0x7/0xb
Mem-Info:
DMA per-cpu:
CPU 0: hi: 0, btch: 1 usd: 0
Normal per-cpu:
CPU 0: hi: 186, btch: 31 usd: 52
active_anon:17616 inactive_anon:20870 isolated_anon:0
active_file:27963 inactive_file:43021 isolated_file:0
unevictable:0 dirty:284 writeback:0 unstable:0 buffer:5599
free:1401 slab_reclaimable:2966 slab_unreclaimable:3731
mapped:4083 shmem:88 pagetables:515 bounce:0
DMA free:2196kB min:84kB low:104kB high:124kB active_anon:1496kB inactive_anon:2340kB active_file:3212kB inactive_file:5884kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15804kB mlocked:0kB dirty:40kB writeback:0kB mapped:648kB shmem:0kB slab_reclaimable:244kB slab_unreclaimable:244kB kernel_stack:176kB pagetables:64kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 491 491
Normal free:3408kB min:2792kB low:3488kB high:4188kB active_anon:68968kB inactive_anon:81140kB active_file:108640kB inactive_file:166200kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:503616kB mlocked:0kB dirty:1096kB writeback:0kB mapped:15684kB shmem:352kB slab_reclaimable:11620kB slab_unreclaimable:14680kB kernel_stack:1688kB pagetables:1996kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0
DMA: 549*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 2196kB
Normal: 754*4kB 35*8kB 7*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3408kB
73515 total pagecache pages
2437 pages in swap cache
Swap cache stats: add 22864, delete 20427, find 290544/291230
Free swap = 456788kB
Total swap = 524280kB
130976 pages RAM
1952 pages reserved
52425 pages shared
86057 pages non-shared
Please put me on CC since I am not subscribed to the list.
Kind regards,
Michael
next reply other threads:[~2009-10-27 9:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 9:50 Michael Guntsche [this message]
2009-10-27 10:38 ` Page alloc problems with 2.6.32-rc kernels Frans Pop
2009-10-27 14:00 ` Michael Guntsche
2009-10-27 14:00 ` Mel Gorman
2009-10-29 8:48 ` Michael Guntsche
2009-10-29 10:05 ` Michael Guntsche
2009-10-29 15:24 ` Michael Guntsche
2009-10-30 19:28 ` Michael Guntsche
2009-10-27 13:01 ` Jiri Kosina
-- strict thread matches above, loose matches on Subject: below --
2009-11-02 12:20 Michael Guntsche
2009-11-04 0:14 ` Frans Pop
2009-11-04 7:17 ` Michael Guntsche
2009-11-04 22:14 ` Frans Pop
2009-11-04 23:07 ` Michael Guntsche
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=20091027095014.GA22215@gibson.comsick.at \
--to=mike@it-loops.com \
--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