Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967208AbWKYVGg (ORCPT ); Sat, 25 Nov 2006 16:06:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S967209AbWKYVGf (ORCPT ); Sat, 25 Nov 2006 16:06:35 -0500 Received: from dvhart.com ([64.146.134.43]:6288 "EHLO dvhart.com") by vger.kernel.org with ESMTP id S967208AbWKYVGf (ORCPT ); Sat, 25 Nov 2006 16:06:35 -0500 Message-ID: <4568AFB1.3050500@mbligh.org> Date: Sat, 25 Nov 2006 13:03:45 -0800 From: "Martin J. Bligh" User-Agent: Thunderbird 1.5.0.7 (X11/20060922) MIME-Version: 1.0 To: Linux Kernel Mailing List Cc: Andy Whitcroft , Andrew Morton Subject: OOM killer firing on 2.6.18 and later during LTP runs Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2551 Lines: 62 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: [] out_of_memory+0x33/0x220 [] __alloc_pages+0x23a/0x2c3 [] __do_page_cache_readahead+0x99/0x212 [] sync_page+0x0/0x45 [] io_schedule+0x28/0x33 [] __wait_on_bit_lock+0x5b/0x66 [] dm_any_congested+0x3b/0x42 [] filemap_nopage+0x14b/0x353 [] __handle_mm_fault+0x387/0x93f [] do_page_fault+0x44b/0x7ba [] autoremove_wake_function+0x0/0x2e oom-killer: gfp_mask=0x280d2, order=0 Call Trace: [] out_of_memory+0x33/0x220 [] __alloc_pages+0x23a/0x2c3 [] __handle_mm_fault+0x1d0/0x93f [] do_page_fault+0x44b/0x7ba [] thread_return+0x0/0xe0 [] 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: [] out_of_memory+0x70/0x262 [] autoremove_wake_function+0x0/0x2e [] __alloc_pages+0x238/0x2c1 [] __do_page_cache_readahead+0xab/0x234 [] sync_page+0x0/0x45 [] io_schedule+0x28/0x33 [] __wait_on_bit_lock+0x5b/0x66 [] dm_any_congested+0x3b/0x42 [] filemap_nopage+0x148/0x34e [] __handle_mm_fault+0x1f8/0x9b0 [] do_page_fault+0x441/0x7b5 [] _spin_unlock_irq+0x9/0xc [] thread_return+0x64/0x100 [] 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/