[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1253219756.5213.348.camel@dhcp231-106.rdu.redhat.com>
Date: Thu, 17 Sep 2009 16:35:56 -0400
From: Eric Paris <eparis@...hat.com>
To: David Rientjes <rientjes@...gle.com>
Cc: Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
torvalds@...ux-foundation.org, a.p.zijlstra@...llo.nl
Subject: Re: kernel panic - not syncing: out of memory and no killable
processes
On Thu, 2009-09-17 at 13:29 -0700, David Rientjes wrote:
> 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.
> >
>
> 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.
I'll throw it in.
I did another bisect (mainly because the last one gave a commit that
obviously seemed bogus and Ingo ask me to)
3f2aa307c4d26b4ed6509d0a79e8254c9e07e921 is first bad commit
commit 3f2aa307c4d26b4ed6509d0a79e8254c9e07e921
Author: Ingo Molnar <mingo@...e.hu>
Date: Thu Sep 10 20:34:48 2009 +0200
sched: Disable NEW_FAIR_SLEEPERS for now
I'm about to try a linus latest kernel with just this one patch
reverted.
-Eric
--
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/
Powered by blists - more mailing lists