From: Andrew Morton <akpm@osdl.org>
To: Martin Bligh <mbligh@google.com>
Cc: apw@shadowen.org, linux-kernel@vger.kernel.org
Subject: Re: sparsemem panic in 2.6.17-rc5-mm1 and -mm2
Date: Mon, 5 Jun 2006 20:07:27 -0700 [thread overview]
Message-ID: <20060605200727.374cbf05.akpm@osdl.org> (raw)
In-Reply-To: <4484D174.7080902@google.com>
On Mon, 05 Jun 2006 17:51:00 -0700
Martin Bligh <mbligh@google.com> wrote:
> http://test.kernel.org/abat/34264/debug/console.log
>
> Only seems to happen on the sparsemem runs. Possibly a side-effect
> of the page migration stuff, manifesting itself differently?
> Or maybe not?
>
> Out of Memory: Kill process 1 (idle) score 0 and children.
> divide error: 0000 [#1]
> SMP
> last sysfs file:
> CPU: 0
> EIP: 0060:[<c013be6a>] Not tainted VLI
> EFLAGS: 00010246 (2.6.17-rc5-mm2-autokern1 #1)
> EIP is at shrink_active_list+0x5b/0x382
> eax: 00000000 ebx: 00000064 ecx: 00000000 edx: 00000000
> esi: c0474500 edi: c03a8e64 ebp: c03a8dbc esp: c03a8d9c
> ds: 007b es: 007b ss: 0068
> Process idle (pid: 1, threadinfo=c03a8000 task=c0769000)
> Stack: 00000000 00000000 00000020 00000004 c03a8dac c03a8dac c03a8db4
> c03a8db4
> c03a8dbc c03a8dbc c03a8dfc c0137a14 00000000 c0137a37 c03a8df8
> c03a8df4
> c0474000 00000000 00000000 c03a8e64 c0137c5a 00000000 00028028
> 000dc0e0
> Call Trace:
> <c0137a14> get_writeback_state+0x30/0x35 <c0137a37>
> get_dirty_limits+0x1e/0xc4
> <c0137c5a> throttle_vm_writeout+0x18/0x53 <c013c221>
> shrink_zone+0x90/0xc1
> <c013c29f> shrink_zones+0x4d/0x5e <c013c39d> try_to_free_pages+0xed/0x1a8
> <c0136a91> __alloc_pages+0x16e/0x26a <c014e6c9> kmem_getpages+0x5b/0xac
> <c014f42c> cache_grow+0xb5/0x147 <c014f655>
> cache_alloc_refill+0x197/0x1d3
> <c014fad0> kmem_cache_alloc+0x4f/0x5e <c0276dd8> sk_alloc+0x15/0x63
> <c02bb9e0> inet_create+0xfb/0x21a <c027546d> __sock_create+0xc0/0xea
> <c02754b0> sock_create_kern+0xb/0xe <c03c413b> icmp_init+0x3a/0xc3
> <c03c445c> inet_init+0x12b/0x174 <c03aa7f6> do_initcalls+0x53/0xe4
> <c01320d8> register_irq_proc+0x6a/0x90 <c0180000>
> xlate_proc_name+0x87/0x90
> <c0100349> init+0x41/0xdc <c0100308> init+0x0/0xdc
> <c01009d5> kernel_thread_helper+0x5/0xb
> Code: 04 24 00 00 00 00 8d 44 24 10 89 44 24 10 89 44 24 14 83 79 10 00
> 74 38 8b 8a bc 01 00 00 6b 47 04 64 bb 64 00 00 00 31 d2 d3 fb <f7> 35
> 0c 6f 45 c0 ba 02 00 00 00 89 d1 99 f7 f9 01 d8 03 47 18
> EIP: [<c013be6a>] shrink_active_list+0x5b/0x382 SS:ESP 0068:c03a8d9c
rofl. Certainly someone's broken something. I assume the divide-by-zero
is due to total_memory being zero.
We shouldn't be running kswapd_init() as an initcall because sometimes when
things are broken we will run page reclaim during boot.
So I'd assume there's something wrong in the memory setup which is causing
us to enter page reclaim far too early.
Something like this should prevent the immediate oops...
diff -puN mm/vmscan.c~run-kswapd_init-earlier mm/vmscan.c
--- devel/mm/vmscan.c~run-kswapd_init-earlier 2006-06-05 20:02:53.000000000 -0700
+++ devel-akpm/mm/vmscan.c 2006-06-05 20:03:12.000000000 -0700
@@ -1346,7 +1346,7 @@ static int cpu_callback(struct notifier_
}
#endif /* CONFIG_HOTPLUG_CPU */
-static int __init kswapd_init(void)
+int __init kswapd_init(void)
{
pg_data_t *pgdat;
@@ -1365,8 +1365,6 @@ static int __init kswapd_init(void)
return 0;
}
-module_init(kswapd_init)
-
#ifdef CONFIG_NUMA
/*
* Zone reclaim mode
diff -puN include/linux/swap.h~run-kswapd_init-earlier include/linux/swap.h
--- devel/include/linux/swap.h~run-kswapd_init-earlier 2006-06-05 20:02:53.000000000 -0700
+++ devel-akpm/include/linux/swap.h 2006-06-05 20:03:51.000000000 -0700
@@ -176,6 +176,7 @@ extern unsigned long try_to_free_pages(s
extern unsigned long shrink_all_memory(unsigned long nr_pages);
extern int vm_swappiness;
extern int remove_mapping(struct address_space *mapping, struct page *page);
+extern int kswapd_init(void);
/* possible outcome of pageout() */
typedef enum {
diff -puN init/main.c~run-kswapd_init-earlier init/main.c
--- devel/init/main.c~run-kswapd_init-earlier 2006-06-05 20:02:53.000000000 -0700
+++ devel-akpm/init/main.c 2006-06-05 20:04:15.000000000 -0700
@@ -50,6 +50,7 @@
#include <linux/mempolicy.h>
#include <linux/key.h>
#include <linux/root_dev.h>
+#include <linux/swap.h>
#include <asm/io.h>
#include <asm/bugs.h>
@@ -523,6 +524,7 @@ asmlinkage void __init start_kernel(void
kmem_cache_init();
setup_per_cpu_pageset();
numa_policy_init();
+ kswapd_init();
if (late_time_init)
late_time_init();
calibrate_delay();
_
next prev parent reply other threads:[~2006-06-06 3:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 0:51 sparsemem panic in 2.6.17-rc5-mm1 and -mm2 Martin Bligh
2006-06-06 3:07 ` Andrew Morton [this message]
2006-06-06 5:19 ` KAMEZAWA Hiroyuki
2006-06-06 5:36 ` Yasunori Goto
2006-06-06 7:27 ` Andrew Morton
2006-06-07 0:43 ` KAMEZAWA Hiroyuki
2006-06-07 4:58 ` Andrew Morton
2006-06-07 5:36 ` Rusty Russell
2006-06-07 5:50 ` Andrew Morton
2006-06-07 6:49 ` Rusty Russell
2006-06-07 9:26 ` Andy Whitcroft
2006-06-07 16:29 ` Andrew Morton
2006-06-07 16:35 ` Andrew Morton
2006-06-07 17:50 ` Andy Whitcroft
2006-06-15 12:28 ` [PATCH] zone handle unaligned zone boundaries Andy Whitcroft
2006-06-07 17:22 ` sparsemem panic in 2.6.17-rc5-mm1 and -mm2 Andy Whitcroft
2006-06-06 23:42 ` Andrew Morton
2006-06-07 9:16 ` Mel Gorman
2006-06-07 17:38 ` Andy Whitcroft
2006-06-07 17:41 ` Andy Whitcroft
-- strict thread matches above, loose matches on Subject: below --
2006-06-06 3:50 Chuck Ebbert
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=20060605200727.374cbf05.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.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