linux-kernel - Re: kernel panic - not syncing: out of memory and no killable processes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.1.00.0909171326340.31112@chino.kir.corp.google.com>
Date:	Thu, 17 Sep 2009 13:29:59 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Eric Paris <eparis@...hat.com>
cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org
Subject: Re: kernel panic - not syncing: out of memory and no killable
 processes

On Thu, 17 Sep 2009, Eric Paris wrote:

> the next-20090916 tree still panic's the same way.  As does Linus'
> latest git tree ab86e5765
> 
> I'll try bisecting between v2.6.31 and master if it would give better
> data than trying to bisect between two -next trees, but I'm sorta stuck
> with a machine that won't boot and doesn't tell me much about why.
> 

It's panicking because the oom killer is getting called during boot and 
there are no user tasks to kill, i.e. there are only kthreads running, 
which it can't kill.  It sounds like something is trying to allocate 
higher order pages that cannot be found on your 512M machine because of 
fragmentation.

Try merging the following patch to get more information such as the 
allocation order and gfp_mask.  It will also show the VM size of all 
kthreads and the state of your system memory to deterine whether there's a 
page allocator issue, lowmem_reserve_ratio is too high, etc.
---
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -540,6 +540,15 @@ retry:
 	/* Found nothing?!?! Either we hang forever, or we panic. */
 	if (!p) {
 		read_unlock(&tasklist_lock);
+		printk(KERN_WARNING "%s invoked oom-killer: "
+			"gfp_mask=0x%x, order=%d, oomkilladj=%d\n",
+			current->comm, gfp_mask, order, current->oomkilladj);
+		task_lock(current);
+		cpuset_print_task_mems_allowed(current);
+		task_unlock(current);
+		dump_stack();
+		show_mem();
+		dump_tasks(NULL);
 		panic("Out of memory and no killable processes...\n");
 	}
 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/