From: "Martin J. Bligh" <mbligh@mbligh.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Andy Whitcroft <apw@shadowen.org>, Andrew Morton <akpm@osdl.org>
Subject: OOM killer firing on 2.6.18 and later during LTP runs
Date: Sat, 25 Nov 2006 13:03:45 -0800 [thread overview]
Message-ID: <4568AFB1.3050500@mbligh.org> (raw)
On 2.6.18-rc7 and later during LTP:
http://test.kernel.org/abat/48393/debug/console.log
oom-killer: gfp_mask=0x201d2, order=0
Call Trace:
[<ffffffff802638cb>] out_of_memory+0x33/0x220
[<ffffffff80265374>] __alloc_pages+0x23a/0x2c3
[<ffffffff802667d2>] __do_page_cache_readahead+0x99/0x212
[<ffffffff80260799>] sync_page+0x0/0x45
[<ffffffff804b304c>] io_schedule+0x28/0x33
[<ffffffff804b32b8>] __wait_on_bit_lock+0x5b/0x66
[<ffffffff8043d849>] dm_any_congested+0x3b/0x42
[<ffffffff80262e50>] filemap_nopage+0x14b/0x353
[<ffffffff8026cf9a>] __handle_mm_fault+0x387/0x93f
[<ffffffff804b6366>] do_page_fault+0x44b/0x7ba
[<ffffffff80245a4e>] autoremove_wake_function+0x0/0x2e
oom-killer: gfp_mask=0x280d2, order=0
Call Trace:
[<ffffffff802638cb>] out_of_memory+0x33/0x220
[<ffffffff80265374>] __alloc_pages+0x23a/0x2c3
[<ffffffff8026cde3>] __handle_mm_fault+0x1d0/0x93f
[<ffffffff804b6366>] do_page_fault+0x44b/0x7ba
[<ffffffff804b2854>] thread_return+0x0/0xe0
[<ffffffff8020a405>] error_exit+0x0/0x84
--------------------------------------------------
This doesn't seem to happen every run, unfortnately, only
intermittently, and we don't have much data before that, so
hard to tell how long it's been going on.
Still happening on latest kernels.
http://test.kernel.org/abat/62445/debug/console.log
automount invoked oom-killer: gfp_mask=0x201d2, order=0, oomkilladj=0
lamb-payload invoked oom-killer: gfp_mask=0x201d2, order=0, oomkilladj=0
Call Trace:
[<ffffffff80264dca>] out_of_memory+0x70/0x262
[<ffffffff802459f6>] autoremove_wake_function+0x0/0x2e
[<ffffffff802668bf>] __alloc_pages+0x238/0x2c1
[<ffffffff80268070>] __do_page_cache_readahead+0xab/0x234
[<ffffffff8026205c>] sync_page+0x0/0x45
[<ffffffff804bf888>] io_schedule+0x28/0x33
[<ffffffff804bfaeb>] __wait_on_bit_lock+0x5b/0x66
[<ffffffff80446fc9>] dm_any_congested+0x3b/0x42
[<ffffffff80264158>] filemap_nopage+0x148/0x34e
[<ffffffff8026e49a>] __handle_mm_fault+0x1f8/0x9b0
[<ffffffff804c2d0f>] do_page_fault+0x441/0x7b5
[<ffffffff804c0d61>] _spin_unlock_irq+0x9/0xc
[<ffffffff804bf121>] thread_return+0x64/0x100
[<ffffffff804c119d>] error_exit+0x0/0x84
Does at least seem to be the same stack, mostly, and this machine is
using dm it seems, which most of the others aren't
next reply other threads:[~2006-11-25 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-25 21:03 Martin J. Bligh [this message]
2006-11-25 21:28 ` OOM killer firing on 2.6.18 and later during LTP runs Andrew Morton
2006-11-25 21:35 ` Martin J. Bligh
2006-11-25 22:08 ` Andrew Morton
2006-11-26 3:00 ` Dave Jones
2006-11-26 7:11 ` Andrew Morton
2006-11-26 7:25 ` Dave Jones
2006-11-26 7:30 ` Andrew Morton
2006-11-26 11:38 ` Andy Whitcroft
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=4568AFB1.3050500@mbligh.org \
--to=mbligh@mbligh.org \
--cc=akpm@osdl.org \
--cc=apw@shadowen.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